Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. solved: fritzdect adapter error

    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

    solved: fritzdect adapter error

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      ts020339 last edited by ts020339

      Hallo Zusammen,

      ich habe das folgende Problem mit dem fritzdect Adapter (installiert v2.2.3), ich erhalte beim Auslesen keine Daten und es werden keine Objekte angelegt:

      fritzdect.0
      	2022-03-30 20:18:17.531	error	no response part in returned message
      fritzdect.0
      	2022-03-30 20:18:17.531	error	fritzbox returned this {}
      fritzdect.0
      	2022-03-30 20:18:17.530	error	errorHandlerTypeError: Converting circular structure to JSON --> starting at object with constructor 'Socket' | property 'parser' -> object with constructor 'HTTPParser' --- property 'socket' closes the circle
      fritzdect.0
      	2022-03-30 20:18:17.520	info	checking user permissions
      fritzdect.0
      	2022-03-30 20:18:17.223	info	fritzdect uses USER: ioBroker
      fritzdect.0
      	2022-03-30 20:18:17.204	info	fritzdect entered ready
      fritzdect.0
      	2022-03-30 20:18:17.179	info	starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v14.19.1, js-controller: 4.0.21
      

      ABER:
      wenn ich in den Einstellungen mir die Debug Outputs anschauen, habe ich dort alle notwendigen Daten und diese sind auch korrekt. Z.B. Debug Output "Meine Geräte":

      [{"identifier":"11960 0255392","id":"16","functionbitmask":"320","fwversion":"03.54","manufacturer":"AVM","productname":"Comet DECT","present":"1","txbusy":"0","name":"Heizung Dachgeschoss Nebenraum","battery":"100","batterylow":"0","temperature":{"celsius":"190","offset":"0"},"hkr":{"tist":"38","tsoll":"28","absenk":"28","komfort":"28","lock":"0","devicelock":"0","errorcode":"0","windowopenactiv":"0","windowopenactiveendtime":"0","boostactive":"0","boostactiveendtime":"0","batterylow":"0","battery":"100","nextchange":{"endperiod":"1648706400","tchange":"28"},"summeractive":"0","holidayactive":"0"}},{"identifier":"11960 0137176","id":"17","functionbitmask":"320","fwversion":"03.54","manufacturer":"AVM","productname":"Comet DECT","present":"1","txbusy":"0","name":"Heizung Dachgeschoss Hauptraum","battery":"100","batterylow":"0","temperature":{"celsius":"185","offset":"0"},"hkr":{"tist":"37","tsoll":"28","absenk":"28","komfort":"28","lock":"0","devicelock":"0","errorcode":"0","windowopenactiv":"0","windowopenactiveendtime":"0","boostactive":"0","boostactiveendtime":"0","batterylow":"0","battery":"100","nextchange":{"endperiod":"1648706400","tchange":"28"},"summeractive":"0","holidayactive":"0"}},{"identifier":"11960 0128936","id":"18","functionbitmask":"320","fwversion":"03.54","manufacturer":"AVM","productname":"Comet DECT","present":"1","txbusy":"0","name":"Heizung Bad Handtuchhalter","battery":"100","batterylow":"0","temperature":{"celsius":"210","offset":"0"},"hkr":{"tist":"42","tsoll":"32","absenk":"32","komfort":"44","lock":"0","devicelock":"0","errorcode":"0","windowopenactiv":"0","windowopenactiveendtime":"0","boostactive":"0","boostactiveendtime":"0","batterylow":"0","battery":"100","nextchange":{"endperiod":"1648702800","tchange":"44"},"summeractive":"0","holidayactive":"0"}}]
      

      Auch die anderne Debug-Outputs ("meine Gruppen", "meine Templates") liefern die korrekten Daten.
      Das heißt für mich doch, dass der Adapter die Daten korrekt auslesen kann? Nur warum sagt er dann im "normalen" Log, dass das erhaltene Objekt leer ist?

      Kann mir hier jemand weiterhelfen?

      Danke schonmal!

      Tim

      Systemdata xx
      Hardwaresystem: Docker Container auf QNAP NAS-HS-453DX
      Arbeitsspeicher: 8GB
      Festplattenart: SSD
      Betriebssystem: buanet docker Container
      Node-Version: 10.x.x
      Nodejs-Version: v14.19.1
      NPM-Version: 6.14.16
      1 Reply Last reply Reply Quote 0
      • B
        boonekampxxl last edited by

        hallo,

        ich habe den selben fehler.
        wie hast du das gelöst?

        T 1 Reply Last reply Reply Quote 1
        • T
          ts020339 @boonekampxxl last edited by

          @boonekampxxl Tut mir leid, war lange nicht im Forum eingelogged. Für den Fall, dass es Dich noch interessiert: VErsion 2.2.6 aus github hat die meisten Probleme gelöst.
          GRüße

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

          Support us

          ioBroker
          Community Adapters
          Donate

          754
          Online

          31.8k
          Users

          80.0k
          Topics

          1.3m
          Posts

          fritzdect
          2
          3
          238
          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