Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Entwicklung
    4. Zigbee Adapter mit neuem Converter

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Zigbee Adapter mit neuem Converter

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

      Ich habe gerade so gemacht wie oben beschrien ist und hat sofort funktioniert. Einfach so wie beim updaten, über die Katze im Admin auf Beliebig gehen, url eingeben, fertig.
      Stick rein comPort eingeben, neue Gerät pairen. Pairen war auch in Sekunden fertig.

      Beim url kopieren und eingeben am ende Leerzeichen löschen !

      a200 1 Reply Last reply Reply Quote 0
      • a200
        a200 @dimaiv last edited by

        @dimaiv sagte in Zigbee Adapter mit neuem Converter:

        Beim url kopieren und eingeben am ende Leerzeichen löschen !

        Ich Depp!!!

        1 Reply Last reply Reply Quote 0
        • T
          Tictactoo last edited by

          Ich weiß nicht, ob ich damit hier jetzt an der richtigen Stelle bin, aber besteht vielleicht die Möglichkeit einzubauen in den Adapter, dass man die vorhandenen Geräte nach Hersteller oder Name sortiert?

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Tictactoo last edited by Asgothian

            @Tictactoo sagte in Zigbee Adapter mit neuem Converter:

            Ich weiß nicht, ob ich damit hier jetzt an der richtigen Stelle bin, aber besteht vielleicht die Möglichkeit einzubauen in den Adapter, dass man die vorhandenen Geräte nach Hersteller oder Name sortiert?

            Du bist hier an der falschen Stelle. Nachdem das gesagt hat ein paar Punkte zu der Frage. Ein Umsortieren nach Hersteller

            • setzt voraus das diese Information immer korrekt gefüllt ist - das ist sie nicht.
            • würde zwei Ebenen vor die eigentliche ID des Gerätes setzen (Bsp: zigbee.0.90fd9ffffe6de22b wird zu zigbee.0.Ikea.TRADFRI transformer 10W.90fd9ffffe6de22)
            • würde entweder die Möglichkeit zum Umbenennen der Geräte entfernen oder das Umbenennen der Geräte würde die Adresse im Objektbaum ändern, da der Name teil der Adresse ist.

            Ich denke es gibt noch mehr Gründe die dagegen sprechen - rechne also nicht damit das dieser Wunsch umgesetzt wird.

            T 1 Reply Last reply Reply Quote 0
            • S
              Schrauberheld last edited by Schrauberheld

              Das Problem mit "Currently no devices" hatte ich nach dem Update auch.
              Ohne die Geräteliste zu verändern hab ich die Geräte in den pairing modus versetzt und nach dem neuen pairing war das Problem behoben.

              Nur beim Sonoff Schalter gibts noch Probleme. Aber die hatte ich auch schon vorher. Grade beim Re-Pairing will der Sonoff wohl nicht so.

              Ich hab jetzt den Sonoff aus der Liste entfernt aber besser wirds davon auch nicht.
              @Asgothian + @arteck
              Folgendes habe ich nach dem Löschen im Log beobachtet:

              2019-11-28 19:31:46.417 - debug: zigbee.0 (774) deleteDevice message: {"id":"zigbee.0.00124b001f6695ce"}
              2019-11-28 19:31:46.419 - debug: zigbee.0 (774) deleteDevice sysid: 0x00124b001f6695ce
              2019-11-28 19:31:46.430 - debug: zigbee.0 (774) Remove successful.
              2019-11-28 19:31:46.433 - debug: zigbee.0 (774) Successfully removed from shepherd!
              2019-11-28 19:31:46.896 - debug: zigbee.0 (774) sendTo "deleteDevice" to system.adapter.admin.0 from system.adapter.zigbee.0
              

              Danach den Sonoff zurückgesetzt, pairing will er dann automatisch.
              Aber anscheinend gibt es da keine Kommunikation.
              Statt dessen sehe ich im Log

              2019-11-28 19:32:16.369 - debug: zigbee.0 (774) Successfully pinged 0x00124b001f6695ce undefined
              
              

              Und bei GetMap

              {"parent":"0x00124b0018ed16e2","networkAddress":56014,"ieeeAddr":"0x00124b001f6695ce","lqi":0,"relationship":3,"depth":255},
              

              Kann ich über die Konsole den Traffic im Zigbee Netz sniffen oder sowas?
              Debug ausgabe im Log liefert da leider nichts.

              Edit:
              Hab noch einen weiteren Sonoff Basic ZBR1 mit dem hatte ich vor einigen Tagen auch das Problem dass er sich nicht Koppeln ließ. Der hat nun einige Tage ohne Netzanschluss in seinem Karton verbracht und nun lässt er sich wieder Koppeln.
              Es scheint hier also ein Problem mit dem Zigbee Modul zu geben.
              Ich konnte dem ganzen aber noch ein paar Fehlermeldungen entlocken:

              2019-11-28 20:16:02.586 - debug: zigbee.0 (774) handleDeviceJoined. {"device":{"ID":13,"ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_endpoints":[],"_interviewCompleted":false,"_interviewing":false,"meta":{},"_lastSeen":null}}
              2019-11-28 20:16:02.592 - debug: zigbee.0 (774) handleDeviceInterview. {"status":"started","device":{"ID":13,"ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_endpoints":[],"_interviewCompleted":false,"_interviewing":false,"meta":{},"_lastSeen":1574968562588}}
              2019-11-28 20:16:02.608 - info: zigbee.0 (774) Starting interview of '0x00124b001f6695ce'
              2019-11-28 20:16:02.863 - debug: zigbee.0 (774) handleDeviceAnnounce. {"device":{"ID":13,"ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_endpoints":[],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968562861}}
              2019-11-28 20:16:02.864 - debug: zigbee.0 (774) Device '0x00124b001f6695ce' announced itself
              2019-11-28 20:16:03.541 - debug: zigbee.0 (774) handleMessage. {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563540},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.544 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
              2019-11-28 20:16:03.546 - debug: zigbee.0 (774) Type attributeReport device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563540},"mapped":null,"name":"0x00124b001f6695ce"} incoming event: {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563540},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.559 - debug: zigbee.0 (774) handleMessage. {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563557},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.565 - debug: zigbee.0 (774) handleMessage. {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563564},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.569 - debug: zigbee.0 (774) handleMessage. {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.576 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
              2019-11-28 20:16:03.578 - debug: zigbee.0 (774) Type attributeReport device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"mapped":null,"name":"0x00124b001f6695ce"} incoming event: {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.580 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
              2019-11-28 20:16:03.581 - debug: zigbee.0 (774) Type attributeReport device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"mapped":null,"name":"0x00124b001f6695ce"} incoming event: {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:03.583 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
              2019-11-28 20:16:03.584 - debug: zigbee.0 (774) Type attributeReport device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"mapped":null,"name":"0x00124b001f6695ce"} incoming event: {"type":"attributeReport","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}}},"_binds":[]}],"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968563568},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":47,"groupID":0,"cluster":"genOnOff"}
              2019-11-28 20:16:04.833 - debug: zigbee.0 (774) handleMessage. {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968564830},"endpoint":"[Circular]","data":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:04.835 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'readResponse', cluster 'genBasic', data '{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1}' from endpoint 1 with groupID 0
              2019-11-28 20:16:04.837 - debug: zigbee.0 (774) Type readResponse device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968564830},"mapped":{"zigbeeModel":["BASICZBR3"],"model":"BASICZBR3","vendor":"SONOFF","description":"Zigbee smart switch","supports":"on/off","fromZigbee":[{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["state"]}]},"name":"0x00124b001f6695ce"} incoming event: {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968564830},"endpoint":"[Circular]","data":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:04.864 - debug: zigbee.0 (774) Wrong device 00124b001f6695ce
              2019-11-28 20:16:05.322 - debug: zigbee.0 (774) handleMessage. {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565316},"endpoint":"[Circular]","data":{"zclVersion":1},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:05.325 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'readResponse', cluster 'genBasic', data '{"zclVersion":1}' from endpoint 1 with groupID 0
              2019-11-28 20:16:05.328 - debug: zigbee.0 (774) Type readResponse device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565316},"mapped":{"zigbeeModel":["BASICZBR3"],"model":"BASICZBR3","vendor":"SONOFF","description":"Zigbee smart switch","supports":"on/off","fromZigbee":[{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["state"]}]},"name":"0x00124b001f6695ce"} incoming event: {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565316},"endpoint":"[Circular]","data":{"zclVersion":1},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:05.355 - debug: zigbee.0 (774) Wrong device 00124b001f6695ce
              2019-11-28 20:16:05.449 - debug: zigbee.0 (774) handleMessage. {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1,"hwVersion":1,"dateCode":"20190907-V102"}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_hardwareVersion":1,"_dateCode":"20190907-V102","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565445},"endpoint":"[Circular]","data":{"hwVersion":1,"dateCode":"20190907-V102"},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:05.455 - debug: zigbee.0 (774) Received Zigbee message from '0x00124b001f6695ce', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1,"dateCode":"20190907-V102"}' from endpoint 1 with groupID 0
              2019-11-28 20:16:05.458 - debug: zigbee.0 (774) Type readResponse device {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1,"hwVersion":1,"dateCode":"20190907-V102"}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_hardwareVersion":1,"_dateCode":"20190907-V102","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565445},"mapped":{"zigbeeModel":["BASICZBR3"],"model":"BASICZBR3","vendor":"SONOFF","description":"Zigbee smart switch","supports":"on/off","fromZigbee":[{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["state"]}]},"name":"0x00124b001f6695ce"} incoming event: {"type":"readResponse","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1,"hwVersion":1,"dateCode":"20190907-V102"}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_hardwareVersion":1,"_dateCode":"20190907-V102","_interviewCompleted":false,"_interviewing":true,"meta":{},"_lastSeen":1574968565445},"endpoint":"[Circular]","data":{"hwVersion":1,"dateCode":"20190907-V102"},"linkquality":47,"groupID":0,"cluster":"genBasic"}
              2019-11-28 20:16:05.477 - debug: zigbee.0 (774) handleDeviceInterview. {"status":"successful","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1,"hwVersion":1,"dateCode":"20190907-V102"}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_hardwareVersion":1,"_dateCode":"20190907-V102","_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1574968565445}}
              2019-11-28 20:16:05.479 - info: zigbee.0 (774) Successfully interviewed '0x00124b001f6695ce', device has succesfully been paired
              2019-11-28 20:16:05.481 - info: zigbee.0 (774) Device '0x00124b001f6695ce' is supported, identified as: SONOFF Zigbee smart switch (BASICZBR3)
              2019-11-28 20:16:05.494 - debug: zigbee.0 (774) New device event: {"type":"device","device":{"ID":13,"_type":"Router","ieeeAddr":"0x00124b001f6695ce","_networkAddress":12616,"_manufacturerID":0,"_endpoints":[{"ID":1,"profileID":260,"deviceID":9,"inputClusters":[0,3,4,5,6],"outputClusters":[0],"deviceNetworkAddress":12616,"deviceIeeeAddress":"0x00124b001f6695ce","clusters":{"genOnOff":{"attributes":{"onOff":0}},"genBasic":{"attributes":{"modelId":"BASICZBR3","manufacturerName":"SONOFF","powerSource":1,"zclVersion":1,"hwVersion":1,"dateCode":"20190907-V102"}}},"_binds":[]}],"_manufacturerName":"SONOFF","_powerSource":"Mains (single phase)","_modelID":"BASICZBR3","_zclVersion":1,"_hardwareVersion":1,"_dateCode":"20190907-V102","_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1574968565445},"mapped":{"zigbeeModel":["BASICZBR3"],"model":"BASICZBR3","vendor":"SONOFF","description":"Zigbee smart switch","supports":"on/off","fromZigbee":[{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["state"]}]},"name":"0x00124b001f6695ce"}
              2019-11-28 20:16:05.496 - debug: zigbee.0 (774) new devive 0x00124b001f6695ce 12616 BASICZBR3
              2019-11-28 20:16:05.509 - debug: zigbee.0 (774) Wrong device 00124b001f6695ce
              
              1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active last edited by

                @Asgothian hat die Abschaltung der LED realisiert.. sollte laufen

                Kalle Blomquist 1 Reply Last reply Reply Quote 1
                • ?
                  A Former User last edited by

                  Habe gestern den CC2538 von @dimaiv bekommen.
                  Der erste Test mit einem Aqara Türsensor lief einwandfrei 👍
                  Das Pairing läuft schonmal definitiv schneller. Am Wochenende werden dann die restlichen
                  Sensoren angelernt.

                  1 Reply Last reply Reply Quote 0
                  • MathiasJ
                    MathiasJ @arteck last edited by

                    @arteck
                    Danke, nein, das Forum habe ich nicht gesehen, aber jetzt direkt in meinen Bookmarks aufgenommen.
                    habe mal 2 von den Teilen bestellt.
                    Bin gespannt, wie die Übertragungsrate und der Empfang ist.

                    1 Reply Last reply Reply Quote 0
                    • J
                      Ja.rod last edited by

                      Habe auch den CC2531, läuft nur meine Aqara Sensoren zicken etwas. Ich hatte den Converter schon mal installiert und dann den "Anlernknopf" beim jeweiligen Gerät vermisst (z.B. Osram Steckdose). Ich denke das kommt noch oder ist das überhaupt nicht mehr notwendig? Noch eine Frage eines Laien : Wie kann ich zwischen den Convertern hin und herwechseln, den anderen einfach wieder drüber installieren?

                      Gruß
                      Ja.rod

                      v522533 1 Reply Last reply Reply Quote 0
                      • v522533
                        v522533 @Ja.rod last edited by

                        @Ja-rod

                        der war noch nie notwendig, da immer am coordinator gekoppelt wird.

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          Ja.rod @v522533 last edited by

                          @v522533 Gibt es da nicht ein beschränkte Anzahl an Geräten die am Coordinator angelernt werden können ( 25 Stück, habe ich zumindest beim CC2531 mal gelesen)?

                          v522533 1 Reply Last reply Reply Quote 0
                          • v522533
                            v522533 @Ja.rod last edited by

                            @Ja-rod

                            prinzipiell richtig, aber beim anlernen ganz egal, da es sich um ein mesh netzwerk handelt. darin suchen sich die geräte selbständig einen "partner" ganz egal wo sie angelernt werden.

                            arteck 1 Reply Last reply Reply Quote 0
                            • arteck
                              arteck Developer Most Active @v522533 last edited by arteck

                              @v522533 jetzt fang nicht wieder mit dem Mesh an...

                              und nein die Geräte könne NUR am Stick angelernt werden.. der Knopp der an jedem Router dran war sollte nur dieser als solchen indentifizieren... daraus ist die diskussion und die "guten" Ratschläge entstanden das man es auch an einem Plug oder Lampe oder oder anlernen konnte..was nicht der Fall was.. da sieht man wieder wie viel Usability ausmacht.. ein falsches Icon und bäm.. werden falsch Informationen reininterpretiert

                              v522533 1 Reply Last reply Reply Quote 0
                              • v522533
                                v522533 @arteck last edited by

                                @arteck

                                genau das hab ich ihm doch gesagt, dass immer am coordinator angelernt wird.... verstehe die aufregung nicht

                                1 Reply Last reply Reply Quote 0
                                • Kalle Blomquist
                                  Kalle Blomquist @arteck last edited by

                                  @arteck Ja Super. Funktioniert. Merci👍

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    Moskito last edited by

                                    Dank @dimaiv bin ich jetzt auch auf den CC2538+CC2592 umgestiegen.
                                    Das pairen hat auch schnell und ohne Probleme funktioniert.
                                    Allerdings wirft der Adapter beim durchstarten Fehlermeldungen zu meinen innr SP 120 Steckdosen:

                                    2019-11-29 10:24:37.221  - info: zigbee.0 (16469) Zigbee started
                                    2019-11-29 10:24:47.220  - error: zigbee.0 (16469) Failed to configure 0x00158d000361b933 SP 120, attempt 1 (Error: AREQ - ZDO - bindRsp after 10000ms
                                        at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
                                        at ontimeout (timers.js:436:11)
                                        at tryOnTimeout (timers.js:300:5)
                                        at listOnTimeout (timers.js:263:5)
                                        at Timer.processTimers (timers.js:223:10))
                                    2019-11-29 10:24:47.222  - info: zigbee.0 (16469) Configuring 0x00158d0003565fe6 SP 120
                                    2019-11-29 10:24:57.226  - error: zigbee.0 (16469) Failed to configure 0x00158d0003565fe6 SP 120, attempt 1 (Error: AREQ - ZDO - bindRsp after 10000ms
                                        at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
                                        at ontimeout (timers.js:436:11)
                                        at tryOnTimeout (timers.js:300:5)
                                        at listOnTimeout (timers.js:263:5)
                                        at Timer.processTimers (timers.js:223:10))
                                    2019-11-29 10:24:57.228  - info: zigbee.0 (16469) Configuring 0x00158d0003617967 SP 120
                                    2019-11-29 10:25:07.231  - error: zigbee.0 (16469) Failed to configure 0x00158d0003617967 SP 120, attempt 1 (Error: AREQ - ZDO - bindRsp after 10000ms
                                        at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
                                        at ontimeout (timers.js:436:11)
                                        at tryOnTimeout (timers.js:300:5)
                                        at listOnTimeout (timers.js:263:5)
                                        at Timer.processTimers (timers.js:223:10))
                                    

                                    Funktionieren tut trotzdem alles tadellos bisher...

                                    Achso, eine Sache noch, wenn man das Pairing starten sind die Sekunden doppelt in dem PopUp Fenster zu sehen 😉

                                    1 Reply Last reply Reply Quote 0
                                    • Garfonso
                                      Garfonso Developer @Garfonso last edited by

                                      @arteck
                                      @Asgothian

                                      Ich habe es heute nochmal probiert. Das Ergebnis ist irgendwie dasselbe. Dann hab ich mir mal die db im Texteditor angeguckt (nachdem ich begriffen habe, dass da im Grunde nur Zeilenweise JSON Objekte drinnen stehen). Da hab ich dann relativ schnell entdeckt, dass bei ModelIDs aber auch bei date-irgendwas ein "\u0000" mit drin stand. Das hab ich dann entfernt und seitdem nimmt auch der herdsman die db.
                                      Jetzt geht es auch, schalten scheint schneller. Reichweiten Probleme hab ich leider immer noch an ein paar Ecken (wobei mich immer noch verwirrt, dass die Geräte, die beim direkt ansprechen problematisch sind mit Gruppen sehr zuverlässig schalten).

                                      Was mich etwas wundert ist, dass ich im debug log diese Ausgabe bekomme:

                                      2019-11-29 10:38:28.041  - debug: zigbee.0 (524) Zigbee network parameters: {"panID":7102,"extendedPanID":"0xdddddddddddddddd","channel":11}2019-11-29 10:38:28.041  - debug: zigbee.0 (524) Zigbee network parameters: {"panID":7102,"extendedPanID":"0xdddddddddddddddd","channel":11}
                                      

                                      Dabei steht in der Config von der Instanz eine andere extendedPanID. Hab ich damals bei dem breaking update was falsch gemacht? Oder wird die noch irgendwo anders gespeichert? (in der db jedenfalls nicht). Welche ist denn nun die richtige? 😉

                                      1 Reply Last reply Reply Quote 0
                                      • simatec
                                        simatec Developer Most Active last edited by

                                        Die aktuelle Versionsnummer verusacht Probleme.
                                        Ist mir gerade beim Update von Admin aufgefallen.

                                        2019-11-29 15:48:03.063  - error: admin.0 (2591) uncaught exception: Invalid Version: 1.0.0a
                                        2019-11-29 15:48:03.064  - error: admin.0 (2591) TypeError: Invalid Version: 1.0.0a
                                        

                                        oder das "a" geht es 😉

                                        Asgothian 2 Replies Last reply Reply Quote 0
                                        • Asgothian
                                          Asgothian Developer @simatec last edited by

                                          @simatec
                                          Welche Version des Admin hast du ? ich hab mit der die gestern als neuste angeboten wurde keine Probleme gehabt (3.7.1 glaub ich)

                                          A.

                                          simatec 1 Reply Last reply Reply Quote 0
                                          • T
                                            tazdevil20 last edited by tazdevil20

                                            @simatec
                                            hatte gestern das gleiche Problem. Bin nur noch nicht dazu gekommen das ganze zu posten.

                                            Hier meine Logs:

                                            2019-11-28 21:38:01.022  - info: host.iobroker instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                                            2019-11-28 21:38:01.023  - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled
                                            2019-11-28 21:38:31.040  - info: host.iobroker instance system.adapter.admin.0 started with pid 25016
                                            2019-11-28 21:38:34.721  - info: admin.0 (25016) starting. Version 3.7.2 in /opt/iobroker/node_modules/iobroker.admin, node: v10.17.0
                                            2019-11-28 21:38:34.852  - info: admin.0 (25016) requesting all states
                                            2019-11-28 21:38:34.854  - info: admin.0 (25016) requesting all objects
                                            2019-11-28 21:38:37.142  - info: admin.0 (25016) received all objects
                                            2019-11-28 21:38:37.336  - info: admin.0 (25016) http server listening on port 8081
                                            2019-11-28 21:38:37.337  - info: admin.0 (25016) Use link "http://localhost:8081" to configure.
                                            2019-11-28 21:38:37.736  - error: admin.0 (25016) uncaught exception: Invalid Version: 1.0.0a
                                            2019-11-28 21:38:37.738  - error: admin.0 (25016) TypeError: Invalid Version: 1.0.0a
                                                at new SemVer (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:332:11)
                                                at compare (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:647:10)
                                                at Function.gt (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:683:10)
                                                at upToDate (/opt/iobroker/node_modules/iobroker.admin/main.js:223:16)
                                                at adapter.getState (/opt/iobroker/node_modules/iobroker.admin/main.js:267:22)
                                                at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
                                                at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                                                at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                                                at process._tickCallback (internal/process/next_tick.js:68:7)
                                            2019-11-28 21:38:37.742  - info: admin.0 (25016) terminating http server on port 8081
                                            2019-11-28 21:38:37.753  - info: admin.0 (25016) terminating
                                            2019-11-28 21:38:37.755  - info: admin.0 (25016) Terminated (NO_ERROR): Without reason
                                            2019-11-28 21:38:38.329  - error: host.iobroker Caught by controller[0]: TypeError: Invalid Version: 1.0.0a
                                            2019-11-28 21:38:38.331  - error: host.iobroker Caught by controller[0]:     at new SemVer (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:332:11)
                                            2019-11-28 21:38:38.332  - error: host.iobroker Caught by controller[0]:     at compare (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:647:10)
                                            2019-11-28 21:38:38.333  - error: host.iobroker Caught by controller[0]:     at Function.gt (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:683:10)
                                            2019-11-28 21:38:38.333  - error: host.iobroker Caught by controller[0]:     at upToDate (/opt/iobroker/node_modules/iobroker.admin/main.js:223:16)
                                            2019-11-28 21:38:38.334  - error: host.iobroker Caught by controller[0]:     at adapter.getState (/opt/iobroker/node_modules/iobroker.admin/main.js:267:22)
                                            2019-11-28 21:38:38.334  - error: host.iobroker Caught by controller[0]:     at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
                                            2019-11-28 21:38:38.335  - error: host.iobroker Caught by controller[0]:     at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                                            2019-11-28 21:38:38.335  - error: host.iobroker Caught by controller[0]:     at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                                            2019-11-28 21:38:38.336  - error: host.iobroker Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:68:7)
                                            2019-11-28 21:38:38.336  - info: host.iobroker instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                                            2019-11-28 21:38:38.337  - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled
                                            2019-11-28 21:38:50.225  - info: history.0 (20770) disabled logging of zigbee.0.00158d00032142d5.temperature
                                            2019-11-28 21:38:51.414  - info: history.0 (20770) disabled logging of zigbee.0.00158d00034d1ca8.temperature
                                            2019-11-28 21:38:51.819  - info: host.iobroker object deleted system.adapter.zigbee.0
                                            2019-11-28 21:39:00.026  - info: javascript.0 (20240) script.js.Sonstiges.MinMax_Temperatur: Garten Temperatur Max: 13.22  Garten Temperatur Min: 8.34
                                            2019-11-28 21:39:08.363  - info: host.iobroker instance system.adapter.admin.0 started with pid 25648
                                            2019-11-28 21:39:13.183  - info: admin.0 (25648) starting. Version 3.7.2 in /opt/iobroker/node_modules/iobroker.admin, node: v10.17.0
                                            2019-11-28 21:39:13.281  - info: admin.0 (25648) requesting all states
                                            2019-11-28 21:39:13.283  - info: admin.0 (25648) requesting all objects
                                            2019-11-28 21:39:16.064  - info: admin.0 (25648) received all objects
                                            2019-11-28 21:39:16.318  - info: admin.0 (25648) http server listening on port 8081
                                            2019-11-28 21:39:16.320  - info: admin.0 (25648) Use link "http://localhost:8081" to configure.
                                            2019-11-28 21:39:16.760  - error: admin.0 (25648) uncaught exception: Invalid Version: 1.0.0a
                                            2019-11-28 21:39:16.761  - error: admin.0 (25648) TypeError: Invalid Version: 1.0.0a
                                                at new SemVer (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:332:11)
                                                at compare (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:647:10)
                                                at Function.gt (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:683:10)
                                                at upToDate (/opt/iobroker/node_modules/iobroker.admin/main.js:223:16)
                                                at adapter.getState (/opt/iobroker/node_modules/iobroker.admin/main.js:267:22)
                                                at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
                                                at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                                                at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                                                at process._tickCallback (internal/process/next_tick.js:68:7)
                                            2019-11-28 21:39:16.765  - info: admin.0 (25648) terminating http server on port 8081
                                            2019-11-28 21:39:16.776  - info: admin.0 (25648) terminating
                                            2019-11-28 21:39:16.779  - info: admin.0 (25648) Terminated (NO_ERROR): Without reason
                                            2019-11-28 21:39:17.873  - error: host.iobroker Caught by controller[0]: TypeError: Invalid Version: 1.0.0a
                                            2019-11-28 21:39:17.875  - error: host.iobroker Caught by controller[0]:     at new SemVer (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:332:11)
                                            2019-11-28 21:39:17.875  - error: host.iobroker Caught by controller[0]:     at compare (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:647:10)
                                            2019-11-28 21:39:17.876  - error: host.iobroker Caught by controller[0]:     at Function.gt (/opt/iobroker/node_modules/iobroker.admin/node_modules/semver/semver.js:683:10)
                                            2019-11-28 21:39:17.876  - error: host.iobroker Caught by controller[0]:     at upToDate (/opt/iobroker/node_modules/iobroker.admin/main.js:223:16)
                                            2019-11-28 21:39:17.877  - error: host.iobroker Caught by controller[0]:     at adapter.getState (/opt/iobroker/node_modules/iobroker.admin/main.js:267:22)
                                            2019-11-28 21:39:17.885  - error: host.iobroker Caught by controller[0]:     at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
                                            2019-11-28 21:39:17.886  - error: host.iobroker Caught by controller[0]:     at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                                            2019-11-28 21:39:17.887  - error: host.iobroker Caught by controller[0]:     at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                                            2019-11-28 21:39:17.887  - error: host.iobroker Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:68:7)
                                            2019-11-28 21:39:17.887  - info: host.iobroker instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
                                            2019-11-28 21:39:17.888  - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled
                                            2019-11-28 21:39:47.920  - info: host.iobroker instance system.adapter.admin.0 started with pid 26406
                                            2019-11-28 21:39:51.861  - info: admin.0 (26406) starting. Version 3.7.2 in /opt/iobroker/node_modules/iobroker.admin, node: v10.17.0
                                            2019-11-28 21:39:51.937  - info: admin.0 (26406) requesting all states
                                            2019-11-28 21:39:51.939  - info: admin.0 (26406) requesting all objects
                                            2019-11-28 21:39:54.478  - info: admin.0 (26406) received all objects
                                            2019-11-28 21:39:54.772  - info: admin.0 (26406) http server listening on port 8081
                                            2019-11-28 21:39:54.774  - info: admin.0 (26406) Use link "http://localhost:8081" to configure.
                                            2019-11-28 21:40:00.015  - info: javascript.0 (20240) script.js.Sonstiges.MinMax_Temperatur: Garten Temperatur Max: 13.22  Garten Temperatur Min: 8.34
                                            2019-11-28 21:40:00.029  - info: host.iobroker instance system.adapter.dwd.0 started with pid 26714
                                            2019-11-28 21:40:03.951  - info: dwd.0 (26714) starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v10.17.0
                                            2019-11-28 21:40:05.918  - info: dwd.0 (26714) Terminated (NO_ERROR): Without reason
                                            2019-11-28 21:40:06.439  - info: host.iobroker instance system.adapter.dwd.0 terminated with code 0 (NO_ERROR)
                                            

                                            Nach dem ich den zigbee 1.0.0a Adapter deinstalliert habe ist der Admin auch wieder gestartet. Danach habe ich den Adapter wieder installiert. Ein normales iobroker restart hat dann einwandfrei funktioniert. Jedoch durfte ich alle Geräte neu pairen.

                                            Ist die Admin 3.7.2.

                                            Ich glaube der Adapter sollte idealer Weise einen anderen Namen haben und nicht gleich heißen wie ein anderer (auch wenn dieser eine Weiterentwicklung ist - jedoch andere URL, ...).

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.0k
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            herdsman shpeherd zigbee adapter
                                            58
                                            498
                                            87407
                                            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