Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Fritzdect: did not get session ID

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Fritzdect: did not get session ID

    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jan1 @günni1955 last edited by

      @günni1955
      Der Adapter läuft ohne Probleme und Objekte werden erstellt. Das ganze sogar auf der 7590 mit Beta FW 7.24

      1 Reply Last reply Reply Quote 0
      • J
        Jan1 last edited by

        So, jetzt muss ich mich selber berichtigen. Seit dem Update auf die 7.24 der7090 kommt irgendwann das Problem, dass sich der Adapter zwar verbindet, aber die Geräte nicht mehr steuern kann und iese Fehlermeldungen erzeugt:

        fritzdect.0	2020-11-15 08:11:11.399	error	(754) no response part in returned message
        fritzdect.0	2020-11-15 08:11:11.399	error	(754) fritzbox returned this {}
        fritzdect.0	2020-11-15 08:11:10.718	error	(754) no response part in returned message
        
        fritzdect.0	2020-11-15 08:19:16.614	info	(1658334) setting up Switch/DECT2xx object Kamera
        fritzdect.0	2020-11-15 08:19:16.606	info	(1658334) setting up Thermostat/DECT3xx object Heizung Bad
        fritzdect.0	2020-11-15 08:19:16.580	info	(1658334) setting up Thermostat/DECT3xx object Heizung Wohnzimmer
        fritzdect.0	2020-11-15 08:19:16.579	info	(1658334) create Devices 3
        fritzdect.0	2020-11-15 08:19:16.351	info	(1658334) Talking to FritzBox with firmware: 07.24-83272 BETA
        fritzdect.0	2020-11-15 08:19:09.749	info	(1658334) entered ready
        fritzdect.0	2020-11-15 08:19:09.722	info	(1658334) starting. Version 0.3.2 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v14.15.0, js-controller: 3.1.6
        
        fritzdect.0	2020-11-15 08:30:00.028	info	(1668526) Comet ID: 109710188104 identified for command (mode) : 0
        fritzdect.0	2020-11-15 08:30:00.024	info	(1668526) Comet ID: 092950223000 identified for command (mode) : 0
        fritzdect.0	2020-11-15 08:30:00.019	info	(1668526) Comet ID: 109710188104 identified for command (targettemp) : 21.5
        fritzdect.0	2020-11-15 08:30:00.015	info	(1668526) Comet ID: 092950223000 identified for command (targettemp) : 21
        fritzdect.0	2020-11-15 08:28:09.907	error	(1668526) no response part in returned message
        fritzdect.0	2020-11-15 08:28:09.906	error	(1668526) fritzbox returned this {}
        fritzdect.0	2020-11-15 08:28:09.502	error	(1668526) no response part in returned message
        fritzdect.0	2020-11-15 08:28:09.501	error	(1668526) fritzbox returned this {}
        fritzdect.0	2020-11-15 08:28:08.532	info	(1668526) setting up Switch/DECT2xx object Kamera
        fritzdect.0	2020-11-15 08:28:08.527	info	(1668526) setting up Thermostat/DECT3xx object Heizung Bad
        fritzdect.0	2020-11-15 08:28:08.516	info	(1668526) setting up Thermostat/DECT3xx object Heizung Wohnzimmer
        fritzdect.0	2020-11-15 08:28:08.515	info	(1668526) create Devices 3
        fritzdect.0	2020-11-15 08:28:08.115	error	(1668526) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=blo
        fritzdect.0	2020-11-15 08:28:08.114	error	(1668526) statuscode not in errorhandler
        fritzdect.0	2020-11-15 08:28:08.114	error	(1668526) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block",
        fritzdect.0	2020-11-15 08:28:07.543	error	(1668526) Did not get session id- invalid username or password?
        fritzdect.0	2020-11-15 08:28:07.542	error	(1668526) fritzbox returned this "0000000000000000"
        fritzdect.0	2020-11-15 08:28:05.357	info	(1668526) entered ready
        fritzdect.0	2020-11-15 08:28:05.328	info	(1668526) starting. Version 0.3.2 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v14.15.0, js-controller: 3.1.6
        host.Beelink	2020-11-15 08:28:03.605	info	instance system.adapter.fritzdect.0 started with pid 1668526
        host.Beelink	2020-11-15 08:27:33.567	info	Restart adapter system.adapter.fritzdect.0 because enabled
        host.Beelink	2020-11-15 08:27:33.563	info	instance system.adapter.fritzdect.0 terminated with code 0 (NO_ERROR)
        fritzdect.0	2020-11-15 08:27:33.035	info	(1658334) Terminated (NO_ERROR): Without reason
        fritzdect.0	2020-11-15 08:27:33.034	info	(1658334) terminating
        fritzdect.0	2020-11-15 08:27:33.033	error	at processTicksAndRejections (internal/process/task_queues.js:93:5)
        fritzdect.0	2020-11-15 08:27:33.033	error	at runMicrotasks (<anonymous>)
        fritzdect.0	2020-11-15 08:27:33.033	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
        fritzdect.0	2020-11-15 08:27:33.033	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
        fritzdect.0	2020-11-15 08:27:33.033	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:608:33
        fritzdect.0	2020-11-15 08:27:33.033	error	at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:137:47
        fritzdect.0	2020-11-15 08:27:33.033	error	(1658334) TypeError: Cannot read property 'val' of null
        fritzdect.0	2020-11-15 08:27:33.032	error	(1658334) uncaught exception: Cannot read property 'val' of null
        fritzdect.0	2020-11-15 08:27:33.030	info	(1658334) cleaned everything up...
        fritzdect.0	2020-11-15 08:27:33.029	error	at processTicksAndRejections (internal/process/task_queues.js:93:5)
        fritzdect.0	2020-11-15 08:27:33.029	error	at runMicrotasks (<anonymous>)
        fritzdect.0	2020-11-15 08:27:33.029	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
        fritzdect.0	2020-11-15 08:27:33.029	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
        fritzdect.0	2020-11-15 08:27:33.029	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:608:33
        fritzdect.0	2020-11-15 08:27:33.029	error	at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:137:47
        fritzdect.0	2020-11-15 08:27:33.029	error	(1658334) TypeError: Cannot read property 'val' of null
        fritzdect.0	2020-11-15 08:27:33.027	error	(1658334) uncaught exception: Cannot read property 'val' of null
        fritzdect.0	2020-11-15 08:27:33.024	info	(1658334) Comet ID: 109710188104 identified for command (mode) : 0
        fritzdect.0	2020-11-15 08:27:33.022	info	(1658334) Comet ID: 092950223000 identified for command (mode) : 0
        

        Das hatte ich vor ein paar Tagen wie man am Datum sieht und da hatte ich den Adapter noch mal neu installiert. Der lief ein Tag ohne Probleme und heute wieder das selbe Problem.

        ? 1 Reply Last reply Reply Quote 0
        • ?
          A Former User @Jan1 last edited by

          @Jan1 Hi,
          update mal auf die neuste Github Version, da ist viel geändert worden.. 1.0.1 läuft besser.

          J 1 Reply Last reply Reply Quote 0
          • J
            Jan1 @Guest last edited by

            @ilovegym
            Wollte jetzt mal die Fritz wieder auf 7.21 zurücksetzten 🙂
            OK dann teste ich mal die Git Version.

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @Jan1 last edited by

              @Jan1 ja, wenn das Zurücksetzen einfach so geht, ist ja gut.. bei meiner Testbox gings ohne Probleme, weil ich von der "Wetteranzeige" und sonstigen neuen Funktionen ehrlich gesagt nicht viel halte, und die 7.21 einwandfrei läuft..
              Auf der produktiven Fritzbox kann ich nicht zurück, ohne Werksreset, das mach ich dann mal am Wochenende, ist nicht viel einzustellen, aber ne Stunde off..
              Meine Fritzbox macht ausser Wlan, Dect, Telefonie nicht viel, DHCP, DNS sind woanders.
              Wenn die Thermostate nicht wären, wär se auch schon lange durch was anderes ersetzt worden..

              J 2 Replies Last reply Reply Quote 0
              • J
                Jan1 @Guest last edited by

                @ilovegym
                Die Fritz hat sich jetzt erstmal geweigert, somit hab ich die Git Adapter Version drauf. Es dauert immer so ein bis zwei Tage, bis das Problem überhaupt auftaucht. Ich beobachte nun mal ein paar Tage das Logfile, wenn die Git Version ohne Fehler läuft, bleibt die Fritz auf der Beta, wenn nicht werde ich wohl auch mal am WE das Ding zurück setzten müssen.

                1 Reply Last reply Reply Quote 0
                • G
                  günni1955 @günni1955 last edited by

                  @günni1955
                  Bei mir hat sich die Lage entspannt. Die aktuelle FW Vers. 7.21 ist nicht die Ursache, dass sich der Adapter nicht
                  connected sondern der Fehler zwischen beiden Ohren..😨
                  Es lag an der Anmeldung im Heimnetz. Die war in der FB falsch eingetragen.

                  Kaum macht man es richtig...

                  Gruß GH

                  1 Reply Last reply Reply Quote 0
                  • J
                    Jan1 @Guest last edited by

                    @ilovegym
                    So, heute wieder Fehler im Log, allerdings macht die Fritz und die angeschlossenen Geräte was sie sollen. Könntest Du mir bitte das Log erklären, was da schief läuft und was ich eventuell ändern könnte?

                    fritzdect.0	2020-11-18 07:19:21.041	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:19:21.041	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:19:21.040	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:19:20.954	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:19:20.954	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:19:20.953	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:17:21.372	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:17:21.372	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:17:21.371	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:17:21.149	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:17:21.149	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:17:21.148	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:15:21.298	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:15:21.297	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:15:21.296	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:15:21.185	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:15:21.185	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:15:21.184	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:13:21.224	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:13:21.224	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:13:21.223	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:13:21.102	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:13:21.102	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:13:21.101	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block","x
                    fritzdect.0	2020-11-18 07:11:21.326	error	(15199) error calling the fritzbox {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=block
                    fritzdect.0	2020-11-18 07:11:21.325	error	(15199) statuscode not in errorhandler
                    fritzdect.0	2020-11-18 07:11:21.324	error	(15199) fritzbox returned this {"error":null,"response":{"statusCode":303,"body":"","headers":{"connection":"close","location":"/","x-frame-options":"SAMEORIGIN","x-xss-protection":"1; mode=
                    
                    ? 1 Reply Last reply Reply Quote 0
                    • ?
                      A Former User @Jan1 last edited by

                      @Jan1 wegen dem Fehler hab ich schon ein Issue auf Github aufgemacht, da kommt ein Fehlercode, den der Adapter nicht abfängt, und deshalb diese Warnung.
                      Funktionieren tut aber alles, soweit ich das sehe. Sieht halt im Log nicht so nett aus..

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        Jan1 @Guest last edited by

                        @ilovegym
                        Alles klar und Danke für die Hilfe.
                        Ja es funktioniert alles, nur das Log wird irgendwann komplett damit zugemüllt. Wenn ich den Adapter neu starte, hören die Fehlermeldungen auch auf, obwohl die Scripte im Hintergrund noch genau das selbe über den Adapter steuern wie vorher.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Support us

                        ioBroker
                        Community Adapters
                        Donate
                        FAQ Cloud / IOT
                        HowTo: Node.js-Update
                        HowTo: Backup/Restore
                        Downloads
                        BLOG

                        741
                        Online

                        31.9k
                        Users

                        80.1k
                        Topics

                        1.3m
                        Posts

                        solved
                        5
                        15
                        1576
                        Loading More Posts
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes
                        Reply
                        • Reply as topic
                        Log in to reply
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                        The ioBroker Community 2014-2023
                        logo