SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.

Schmetterfliege

Kurzes Update:

Nachdem @Asgothian sich die pull requests vom herdsman angeschaut hat, sollte eigentlich seit gestern Abend dieses Device supportet sein.

Was ich gemacht habe: per "Katze" -> "von Github" -> Zigbee ausgewählt und installiert.
Das hat meinen Zigbee Adapter auch geupdated, zumindest wurden einzelne Pakete geupdated.
Anschließend habe ich die beiden "falschen" Plugs gelöscht (force) und einen State cleanup gemacht.
Dann den Adapter neu gestartet und versucht die Plugs nochmal zu pairen.
Leider mit dem selben Ergebnis.

Zigbee zu deinstallieren und "von scratch" neu zu installieren habe ich jetzt noch nicht versucht, da ich nicht weiß ob das notwendig ist (würde gerne die 33 Devices die funktionieren nicht alle nochmal anlernen müssen^^).

Für weiteren Input bin ich offen!

Schmetterfliege

Update2:
In den herdsman-converters unter tuya.js finde ich aber auch den Converter für genau mein Device (würde ich zumindest anhand der Vendor ID behaupten?)

Schmetterfliege

Hab mal noch ein bisschen tiefer gebuddelt...

Unter "/opt/iobroker/node_modules/zigbee-herdsman-converters/devices" gibt es die tuya.js.
Dort fehlt bei mir der entsprechende Fingerprint:

 fingerprint: [
            {modelID: 'TS011F', manufacturerName: '_TZ3000_5f43h46b'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_cphmq0q7'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_dpo1ysak'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_ew3ldmgx'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_jvzvulen'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_mraovvmm'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_nfnmi125'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_ps3dmato'},
            {modelID: 'TS011F', manufacturerName: '_TZ3000_w0qqde0g'},
        ],

Bei mir fehlt der entsprechende Eintrag: {modelID: 'TS011F', manufacturerName: '_TZ3000_u5u4cakc'}

Bedeutet für mich dass ich nicht die aktuellste Version dieser Datei habe.
Abgesehen davon ist der Converter aber exakt gleich, also müsste es theoretisch doch erstmal reichen da den Fingerprint hinzuzufügen.
Frage 1: kann ich das ohne Risiko? Die Datei ist schreibgeschützt, aber mit sudo könnte ich reinschreiben.

Frage 2: im Netz habe ich gelesen dass die neueste FW dieser Plugs sie zu reinen Polling Devices macht.
Auch im Commit auf Github, in dem der Fingerprint hinzugefügt wurde, steht der Kommentar dass diese Version polling benötigt. Also gehe ich mal stark davon aus dass meine Plugs mit genau dieser FW ausgeliefert wurden und deshalb auch diesen Fingerprint haben.
Mir ist klar, was Polling generell ist. Aber nur zur Sicherheit für mich:
Bedeutet dass, dass die Plugs mir keine Werte liefern, außer ich polle die immer und immer wieder aktiv?
Bei 10 Stück dürfte das doch ziemlich uncool für meinen Pi sein, oder?

Schmetterfliege

@alexzi habe glaube ich die Lösung, siehe meinen Kommentar direkt darüber.
Frage 1 habe ich mir selbst beantwortet:

Bleibt Frage 2... wie polle ich das nun?^^

EDIT: Schalten funktioniert. Nur Werte werden tatsächlich nicht geliefert.

Asgothian

@schmetterfliege sagte in SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.:

EDIT: Schalten funktioniert. Nur Werte werden tatsächlich nicht geliefert.

Im Objektbaum den State zigbee.0.info.debugmessages finden
84ba20fffe77b200 eintragen.
Adapter nicht neu starten
den State zigbee.0.84ba20fffe77b200.device_query finden und mit "true" oder über den ggf. dargestellten Button triggern.
90 Sekunden warten
im Log nach Meldungen mit dem Schlu2sselwort "ELEVATED" schauen ob da Meldungen kommen die Load power, Load voltage oder andere fehlende Informationen beinhalten.

A.

alexzi

@schmetterfliege
danke schon mal soweit. Was genau hast du jetzt gemacht? den Fingerprint in der tuya.js ergänzt?

Schmetterfliege

@asgothian

Vielen Dank, werde das in Kürze mal machen! :)

@alexzi ich werde dir in Kürze eine etwas detailliertere "Anleitung" basteln. Aber im Prinzip habe ich nur im Converter (in
tuya.js) den Fingerprint hinzugefügt, ja :)

Schmetterfliege

Also,

die Debug Messages habe ich ausgeben lassen, die fehlenden Werte finde ich da allerdings nicht.

2021-12-17 12:21:05.335 - warn: zigbee.0 (23201) ELEVATED: User stateChange zigbee.0.84ba20fffe77b200.device_query {"val":true,"ack":false,"ts":1639740065331,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1639690785654}
2021-12-17 12:21:05.342 - warn: zigbee.0 (23201) ELEVATED Change state 'device_query' at device 0x84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.439 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"linkquality":199}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.440 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '199' from device 84ba20fffe77b200 for 'Link quality'
2021-12-17 12:21:05.440 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":199,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":222,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.440 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":199,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":222,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b200 for 'Message from Zigbee'
2021-12-17 12:21:05.442 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.442 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b200 for 'On/off state of the switch'
2021-12-17 12:21:05.524 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"linkquality":207}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.525 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '207' from device 84ba20fffe77b200 for 'Link quality'
2021-12-17 12:21:05.525 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":207,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":223,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.525 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":207,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":223,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b200 for 'Message from Zigbee'
2021-12-17 12:21:05.527 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.527 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b200 for 'On/off state of the switch'
2021-12-17 12:21:05.609 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"linkquality":199}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.609 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '199' from device 84ba20fffe77b200 for 'Link quality'
2021-12-17 12:21:05.610 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":199,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":224,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.610 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":199,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":224,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b200 for 'Message from Zigbee'
2021-12-17 12:21:05.612 - warn: zigbee.0 (23201) ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b200 type 'TS011F_plug_1'
2021-12-17 12:21:05.613 - warn: zigbee.0 (23201) ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b200 for 'On/off state of the switch'

@Asgothian
Im Herdsman-converters Github sind einige Issues diesbezüglich offen, und da hat jemand einen Converter gebastelt der die Devices dann auch alle 60 sec pollt.
Ich verlinke das mal hier: LINK
Ich habe mir das mal angeschaut, und zumindest alle libraries existieren auf meinem Pi.
Mal unabhängig von den Versionen - kann ich einfach aus meiner Tuya.js den Fingerprint wieder löschen, und stattdessen dieses File auch im selben Ordner ablegen - und er würde dann beim pairen das Gerät finden und alle 60 Sekunden pollen?
Oder kann ich ggfs in Tuya.js einfach einen neuen Converter machen und das von dem User copy-pasten?

@alexzi
Zunächst solltest du prüfen, ob dein converter genau so aussieht wie er sollte.
Dazu auf dem Pi (oder was du benutzt) unter /opt/iobroker/node_modules/zigbee-herdsman-converters/devices zb. mit "nano" die Datei Tuya.js öffnen. Dort dann nach "BW-SHP15" suchen, um zu dem entsprechenden Converter zu kommen.
Oben sind die Fingerprints, darunter dann was der Converter macht. Der relevante Teil in der Tuya.js sieht dann so aus:

{
       fingerprint: [
           {modelID: 'TS011F', manufacturerName: '_TZ3000_5f43h46b'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_cphmq0q7'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_dpo1ysak'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_ew3ldmgx'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_jvzvulen'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_mraovvmm'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_nfnmi125'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_ps3dmato'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_w0qqde0g'},
           {modelID: 'TS011F', manufacturerName: '_TZ3000_u5u4cakc'},

       ],
       model: 'TS011F_plug_1',
       description: 'Smart plug (with power monitoring)',
       vendor: 'TuYa',
       whiteLabel: [{vendor: 'LELLKI', model: 'TS011F_plug'}, {vendor: 'NEO', model: 'NAS-WR01B'},
           {vendor: 'BlitzWolf', model: 'BW-SHP15'}],
       fromZigbee: [fz.on_off, fz.electrical_measurement, fz.metering, fz.ignore_basic_report, fz.tuya_switch_power_outage_memory],
       toZigbee: [tz.on_off, tz.tuya_switch_power_outage_memory],
       configure: async (device, coordinatorEndpoint, logger) => {
           const endpoint = device.getEndpoint(1);
           await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff', 'haElectricalMeasurement', 'seMetering']);
           await reporting.rmsVoltage(endpoint, {change: 5});
           await reporting.rmsCurrent(endpoint, {change: 50});
           await reporting.activePower(endpoint, {change: 10});
           await reporting.currentSummDelivered(endpoint);
           endpoint.saveClusterAttributeKeyValue('haElectricalMeasurement', {acCurrentDivisor: 1000, acCurrentMultiplier: 1});
           endpoint.saveClusterAttributeKeyValue('seMetering', {divisor: 100, multiplier: 1});
           device.save();
       },
       exposes: [e.switch(), e.power(), e.current(), e.voltage().withAccess(ea.STATE),
           e.energy(), exposes.enum('power_outage_memory', ea.STATE_SET, ['on', 'off', 'restore'])
               .withDescription('Recover state after power outage')],
   },

Bei mir ist der Fingerprint mit

{modelID: 'TS011F', manufacturerName: '_TZ3000_u5u4cakc'},

bereits nachgetragen, bei dir wird er fehlen. Sollte alles unter dem Fingerprint genau so aussehen wie in meinem Auszug, kannst du einfach den Fingerprint hinzufügen und solltest dann in der Lage sein den Plug erfolgreich zu pairen. Eben aktuell noch mit der Einschränkung, dass:

keine Werte zurückgeliefert werden (Voltage, Power, etc.)
schalten am Plug selbst wird nicht im IoBroker reflektiert.
d.h.: wenn du den Knopf am Plug drückst, bekommt das der IoBroker nicht mit. Umgekehrt klappt es aber, also über IoBroker schalten funktioniert tadellos.

Schmetterfliege

Fun fact:
Vor ~ 22 Stunden gabs einen Commit im Herdsman-converters (Tuya.js) der den Fingerprint zum plug_3 hinzufügt (der Converter hat polling schon mit drin).
Da hab ich spaßeshalber mal den Fingerprint bei mir ebenfalls hinzugefügt und den Plug neu konfiguriert.

EDIT: ich hatte nur den Fingerprint hinzugefügt, nicht aber den Converter gecheckt. Da sind inzwischen auch einige Zeilen anders, die ich jetzt ebenfalls übernommen, und dann das ganze nochmal getestet habe.
Als TS011F_plug_3 funktioniert es jetzt insoweit, dass mein Zigbee Adapter nicht mehr crasht und ich die Dose weiterhin korrekt schalten kann. Nur das polling scheint nix zu tun - jedenfalls bekomme ich keine Werte.
Allerdings weiß ich natürlich nicht, ob das Polling so im Zigbee Adapter überhaupt unterstützt wird!
Falls die Werte jetzt gepollt werden, kommen sie jedenfalls nicht im Zigbee Adapter an.

Also noch ist alles eher suboptimal^^

arteck

das ding sollte gehen hab gerde zur sicherheit nochmal den Converter hochgezogen auf GIT also alle mal JETZT installieren.

onb die Probleme mit der Frimware des sticks zusammenhängen falls dieser nicht erkannt wurde.. dazu kann ich nix sagen .. hab die Dose nicht hier.

arteck

@schmetterfliege sagte in SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.:

Allerdings weiß ich natürlich nicht, ob das Polling so im Zigbee Adapter überhaupt unterstützt wird!

wenn du daten haben willst musst du diese selbst abholen. per blockly oder script..

den device_query button triggern

Schmetterfliege

Spoiler: der letzte Edit ganz unten ist der relevanteste.

@arteck
Vielen Dank für deine Rückmeldung und deine Mühe!
Ich habe über GIT geupdatet (Adapter -> Expertenmodus -> Katze -> von Git -> Zigbee Adapter ausgewählt).
Dann das Device gelöscht (erst Objektbaum, dann im Zigbee Adapter) und neu angelernt.
Er wurde auch als plug_3 erkannt und hinzugefügt, allerdings kann ich ihn nicht steuern.

Also im Adapter on/off triggern hat keine Auswirkung. Ebenso nicht wenn ich im Objektbaum den Wert auf true/false setze.
Da sieht er übrigens so aus:

Also es wird quasi gar nichts erkannt.

Frage aller Fragen: Wenn ich den Adapter so wie oben beschrieben installiere (was ja dann "nur" ein Update ist), sollte ich davon ausgehen dass meine Files dann alle exakt so sind wie in der aktuellsten Github Version? Oder wären Änderungen die ich vorher manuell gemacht hab (zb Fingerprint hinzufügen) immer noch vorhanden? Falls ja, könnte das ja mein Problem sein :(

Edit: theoretisch updatet das ja "nur" den Zigbee Adapter, und nicht das was ich von herdsman-converter habe.
Oder updatet das dann auch alles was ich unter zigbee-herdsman-converter habe?

96 -rw-r--r--+ 1 iobroker iobroker 95465 Oct 26  1985 tuya.js

Zumindest diesem ls Eintrag nach wurde die Datei das letzte mal am 26. Oktober modifiziert, oder?
Ich selbst habe die Datei doch heute Mittag schon mal modifiziert, hätte das nicht dieses Datum auf den 18. Dezember setzen müssen?

Edit2:

"_from": "zigbee-herdsman-converters@14.0.347",
  "_id": "zigbee-herdsman-converters@14.0.347",

Laut package.json im herdsman-converter Folder hat es zumindest die gleiche Version wie im Zigbee Adapter aufgeführt.
= Alle Dateien dürften dann auch exakt so sein wie in der aktuellen Adapter Version erwartet und meine Änderungen von heute Mittag dürften weg sein?

Edit3:
Ich hab mal einen zweiten Plug hinzugefügt. Den kann ich auch wieder schalten.
Wenn ich allerdings versuche den ersten zu schalten, crasht der Zigbee Adapter instant.
Ich hab mal das Debugging für den zweiten Plug (der den Adapter nicht abschießt) eingeschaltet und Device-Query getriggert, das hier ist der Output:


zigbee.0
2021-12-18 00:43:08.480	warn	ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b835 for 'On/off state of the switch'

zigbee.0
2021-12-18 00:43:08.479	warn	ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.478	warn	ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":15,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b835 for 'Message from Zigbee'

zigbee.0
2021-12-18 00:43:08.477	warn	ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":15,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.477	warn	ELEVATED publishToState: value generated '127' from device 84ba20fffe77b835 for 'Link quality'

zigbee.0
2021-12-18 00:43:08.476	warn	ELEVATED publishToState: message received '{"linkquality":127}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.403	warn	ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b835 for 'On/off state of the switch'

zigbee.0
2021-12-18 00:43:08.403	warn	ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.398	warn	ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":14,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b835 for 'Message from Zigbee'

zigbee.0
2021-12-18 00:43:08.398	warn	ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":14,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.397	warn	ELEVATED publishToState: value generated '127' from device 84ba20fffe77b835 for 'Link quality'

zigbee.0
2021-12-18 00:43:08.396	warn	ELEVATED publishToState: message received '{"linkquality":127}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.317	warn	ELEVATED publishToState: value generated 'true' from device 84ba20fffe77b835 for 'On/off state of the switch'

zigbee.0
2021-12-18 00:43:08.316	warn	ELEVATED publishToState: message received '{"state":"ON"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.312	warn	ELEVATED publishToState: value generated '"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":13,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 84ba20fffe77b835 for 'Message from Zigbee'

zigbee.0
2021-12-18 00:43:08.311	warn	ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"readResponse\",\"data\":{\"onOff\":1},\"linkquality\":127,\"groupID\":null,\"cluster\":\"genOnOff\",\"meta\":{\"zclTransactionSequenceNumber\":13,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":0,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":true,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.311	warn	ELEVATED publishToState: value generated '127' from device 84ba20fffe77b835 for 'Link quality'

zigbee.0
2021-12-18 00:43:08.310	warn	ELEVATED publishToState: message received '{"linkquality":127}' from device 84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.209	warn	ELEVATED Change state 'device_query' at device 0x84ba20fffe77b835 type 'TS011F_plug_3'

zigbee.0
2021-12-18 00:43:08.198	warn	ELEVATED: User stateChange zigbee.0.84ba20fffe77b835.device_query {"val":true,"ack":false,"ts":1639784588192,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1639784565583}

EditDrölfzig:
Hab den ersten Plug, der den Adapter crasht wenn ich ihn schalten will, nochmal gelöscht während er am Strom hängt und dann neu hinzugefügt. Auch den kann ich jetzt wieder über den Adapter schalten und es crasht (zumindest jetzt gerade) nicht mehr den Adapter.
Aber auch bei dem keine Werte wenn ich Device-Query trigger und in der Debug Ausgabe sehe ich auch keinerlei Eintrag zu Watt, Voltage etc. Nur Link Quality und State.
ABER: (EditUnendlich) wenn ich den Plug an seinem Knöpfchen ein/ausschalte und dann Device_Query trigger, dann wird der State tatsächlich im Adapter geupdated. Polling funktioniert also schonmal, aber eben nur für den State, nicht für die anderen Values.

alexzi

@Schmetterfliege
erst mal Danke für die vielen Test und Info. Bin trotzdem zu blöd die tuya.js zu aktualisieren, zumindest nicht über die Katze oder sonst wie. Manuell möchte ich eigentlich nicht drin rumfrickeln. Kannst du mir evtl. kurz schreiben wie ich die neue Datei bzw. Dateien bekomme? Merci

Schmetterfliege

@alexzi

Ich habe tatsächlich einfach nur über die Katze den Zigbee Adapter ausgewählt und dann von Github geupdated.
Alle manuellen Änderungen die ich gemacht habe waren weg, und die verschiedenen Versionen von dependencies waren auch so wie im Repository angegeben. Das Update hat also auch auf jeden Fall geklappt.

An welcher Stelle hängt es denn bei dir?
Hast du über die Katze geupdated und die Devices werden immer noch nicht erkannt?
Falls dem so ist, schaue doch mal in die tuya.js und Kopiere die beiden entsprechenden converter raus (plug_1 und plug_3), damit ich das mal vergleichen kann mit dem was ich habe.

Übrigens: Ich stehe in Kontakt mit Tuya und kenne nun zumindest den Grund wieso das Polling nicht geht etc.
Mal schauen ob die ihre Änderungen wieder rückgängig machen - ansonsten gehen die Plugs sofort zurück nach China...

Schmetterfliege

@arteck

Das Problem konnte nun weitestgehend gelöst werden, siehe:
https://github.com/Koenkk/zigbee2mqtt/issues/9057

Wäre es möglich diese Änderungen im Zigbee Adapter zu übernehmen?

LPTR

@schmetterfliege
Ich habe die SHP-15 seit gestern und sie laufen tadellos.
Adaperversion 1.6.11

arteck

@schmetterfliege probier mal jetzt

Schmetterfliege

@arteck
hammergeil! Vielen Dank für das sehr zügige Update!
Funktioniert genau wie erwartet :)

Schmetterfliege

@arteck
kurzer Nachtrag:
Das Update hat funktioniert, die Plugs funktionieren auch wie erwartet, allerdings wird mein Log nun mit Warnings vollgespammt wenn ich Geräte steuere.
Ich hänge mal das Log von beginn der Installation bis jetzt an.
Ich habe in der Küche 2 Tradfri Remote Controls. Die funktionieren auch noch problemlos, hauen aber nun warnings ins Log wenn ich die benutze.

2022-01-08 22:41:47.409 - info: zigbee.0 (10089) starting. Version 1.6.11 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.0, js-controller: 3.3.21
2022-01-08 22:41:47.563 - info: zigbee.0 (10089) Starting Zigbee npm ...
2022-01-08 22:41:47.565 - warn: zigbee.0 (10089) 4 extensions initialized
2022-01-08 22:41:47.566 - warn: zigbee.0 (10089) extension DeviceAvailability
2022-01-08 22:41:47.567 - warn: zigbee.0 (10089) extension DeviceConfigure
2022-01-08 22:41:47.568 - warn: zigbee.0 (10089) extension DeviceEvent
2022-01-08 22:41:47.569 - warn: zigbee.0 (10089) extension DelayedAction
2022-01-08 22:41:48.203 - info: zigbee.0 (10089) Installed Version: ioBroker/ioBroker.zigbee
2022-01-08 22:41:48.241 - info: zigbee.0 (10089) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":88,"maintrel":0,"revision":"0x26580700"}}
2022-01-08 22:41:48.265 - info: zigbee.0 (10089) Unable to disable LED, unsupported function.
2022-01-08 22:41:48.282 - info: zigbee.0 (10089) --> transmitPower : normal
2022-01-08 22:41:48.493 - info: zigbee.0 (10089) Unable to set transmit power, unsupported function.
2022-01-08 22:41:48.500 - info: zigbee.0 (10089) Currently 45 devices are joined:
2022-01-08 22:41:48.691 - info: zigbee.0 (10089) Configuring 0x84ba20fffe77b835 TS011F
2022-01-08 22:41:48.695 - info: zigbee.0 (10089) 0x00158d000410e87b (addr 32835): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.715 - info: zigbee.0 (10089) 0x00158d000411103a (addr 26950): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.717 - info: zigbee.0 (10089) 0x00158d000410e8ca (addr 1223): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.719 - info: zigbee.0 (10089) 0x00158d000309a45a (addr 35075): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.721 - info: zigbee.0 (10089) 0x00158d0005221c38 (addr 31581): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.723 - info: zigbee.0 (10089) 0x00158d0005221fbe (addr 11411): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.725 - info: zigbee.0 (10089) 0x00158d0005221c37 (addr 57703): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.727 - info: zigbee.0 (10089) 0x00158d00052debfb (addr 30191): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.729 - info: zigbee.0 (10089) 0x00158d00051dfd12 (addr 48749): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
2022-01-08 22:41:48.731 - info: zigbee.0 (10089) 0x00158d00051e1633 (addr 39535): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
2022-01-08 22:41:48.734 - info: zigbee.0 (10089) 0x00158d000283e67b (addr 50956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.737 - info: zigbee.0 (10089) 0x00158d000283e64e (addr 18527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.739 - info: zigbee.0 (10089) 0x00158d000163f2bc (addr 63165): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.741 - info: zigbee.0 (10089) 0x00158d00041d8697 (addr 26015): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.743 - info: zigbee.0 (10089) 0x00158d000412fc1e (addr 39417): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.745 - info: zigbee.0 (10089) 0x00158d000282eec7 (addr 19057): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.747 - info: zigbee.0 (10089) 0x00158d0003f0f373 (addr 46914): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:41:48.749 - info: zigbee.0 (10089) 0x00158d0005cf8b49 (addr 43071): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:41:48.751 - info: zigbee.0 (10089) 0x00178801089def32 (addr 26711): 929002240401 - Philips Hue smart plug - EU (Router)
2022-01-08 22:41:48.753 - info: zigbee.0 (10089) 0x00178801089de95e (addr 39138): 929002240401 - Philips Hue smart plug - EU (Router)
2022-01-08 22:41:48.755 - info: zigbee.0 (10089) 0x00158d00076565a1 (addr 35956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.757 - info: zigbee.0 (10089) 0x00158d000774f35a (addr 23883): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.758 - info: zigbee.0 (10089) 0x00158d0001e4e9e3 (addr 29911): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.765 - info: zigbee.0 (10089) 0x00158d00019f3736 (addr 26600): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:41:48.769 - info: zigbee.0 (10089) 0x00158d000774f34a (addr 13527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.773 - info: zigbee.0 (10089) 0x00158d00077dce53 (addr 62480): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.775 - info: zigbee.0 (10089) 0x00158d00075f6607 (addr 3323): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.777 - info: zigbee.0 (10089) 0x00158d000774f31c (addr 31399): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.779 - info: zigbee.0 (10089) 0x00158d00077dce21 (addr 56764): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.781 - info: zigbee.0 (10089) 0x00158d000774f2c9 (addr 16865): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.786 - info: zigbee.0 (10089) 0x00158d000774f2cb (addr 13799): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.787 - info: zigbee.0 (10089) 0x00158d00073c0c65 (addr 815): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:41:48.789 - info: zigbee.0 (10089) 0x00158d00044eefbe (addr 41589): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:41:48.791 - info: zigbee.0 (10089) 0x84fd27fffe245425 (addr 308): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:41:48.795 - info: zigbee.0 (10089) 0x00158d0005cf4ea4 (addr 42668): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:41:48.800 - info: zigbee.0 (10089) 0x804b50fffef8cf51 (addr 60471): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:41:48.805 - info: zigbee.0 (10089) 0x84ba20fffe77b835 (addr 487): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:41:48.810 - info: zigbee.0 (10089) 0x84ba20fffe77b200 (addr 29486): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:41:48.812 - info: zigbee.0 (10089) 0x84fd27fffe1f8f5d (addr 43353): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:41:48.813 - info: zigbee.0 (10089) 0x84fd27fffe1f8f8c (addr 8187): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:41:48.815 - info: zigbee.0 (10089) 0xb4e3f9fffeaae8c8 (addr 59871): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
2022-01-08 22:41:48.817 - info: zigbee.0 (10089) 0x842e14fffe89313a (addr 26171): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
2022-01-08 22:41:48.819 - info: zigbee.0 (10089) 0x842e14fffe285173 (addr 60803): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
2022-01-08 22:41:48.820 - info: zigbee.0 (10089) 0x804b50fffe606093 (addr 21921): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
2022-01-08 22:41:48.822 - info: zigbee.0 (10089) 0x540f57fffe8971d1 (addr 40423): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:41:48.824 - warn: zigbee.0 (10089) config :{"port":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2253809-if00","panID":"6754","extPanID":"DDDDDDDDDDDDDDDD","channel":"11","disableLed":false,"precfgkey":"abcdef01234567899876543210fedcba","countDown":"60","adapterType":"deconz","debugHerdsman":false,"transmitPower":null,"extPanIdFix":true,"disablePing":false,"external":"","startWithInconsistent":false}
2022-01-08 22:41:48.824 - info: zigbee.0 (10089) Zigbee started
2022-01-08 22:41:48.953 - info: zigbee.0 (10089) debug devices set to []
2022-01-08 22:41:48.956 - warn: zigbee.0 (10089) State "zigbee.0.info.undefinedDevices" has no existing object, this might lead to an error in future versions
2022-01-08 22:41:49.708 - info: zigbee.0 (10089) Configuring 0x84ba20fffe77b200 TS011F
2022-01-08 22:41:50.058 - info: zigbee.0 (10089) DeviceConfigure successful 0x84ba20fffe77b200 TS011F
2022-01-08 22:41:50.089 - info: zigbee.0 (10089) Configuring 0xb4e3f9fffeaae8c8 TRADFRI Driver 30W
2022-01-08 22:41:50.095 - info: zigbee.0 (10089) DeviceConfigure successful 0xb4e3f9fffeaae8c8 TRADFRI Driver 30W
2022-01-08 22:41:50.278 - info: zigbee.0 (10089) Configuring 0x804b50fffe606093 TRADFRI Driver 30W
2022-01-08 22:41:50.283 - info: zigbee.0 (10089) DeviceConfigure successful 0x804b50fffe606093 TRADFRI Driver 30W
2022-01-08 22:41:50.458 - info: zigbee.0 (10089) Configuring 0x540f57fffe8971d1 TS011F
2022-01-08 22:41:50.581 - info: zigbee.0 (10089) DeviceConfigure successful 0x540f57fffe8971d1 TS011F
2022-01-08 22:41:52.542 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true)
2022-01-08 22:41:54.334 - info: zigbee.0 (10089) Got terminate signal TERMINATE_YOURSELF
2022-01-08 22:41:54.335 - info: zigbee.0 (10089) cleaned everything up...
2022-01-08 22:41:54.501 - info: zigbee.0 (10089) Zigbee: disabling joining new devices.
2022-01-08 22:41:54.661 - info: zigbee.0 (10089) terminating
2022-01-08 22:41:54.663 - info: zigbee.0 (10089) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-01-08 22:41:55.496 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal
2022-01-08 22:41:55.530 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.531 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.532 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.533 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.533 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.534 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.535 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.536 - warn: zigbee.0 (10089) redis mget 0 11, err: DB closed
2022-01-08 22:41:55.536 - warn: zigbee.0 (10089) redis mget 0 8, err: DB closed
2022-01-08 22:41:55.537 - warn: zigbee.0 (10089) redis mget 0 11, err: DB closed
2022-01-08 22:41:55.537 - warn: zigbee.0 (10089) redis mget 0 8, err: DB closed
2022-01-08 22:41:55.538 - warn: zigbee.0 (10089) redis mget 0 11, err: DB closed
2022-01-08 22:41:55.538 - warn: zigbee.0 (10089) redis mget 0 11, err: DB closed
2022-01-08 22:41:55.538 - warn: zigbee.0 (10089) redis mget 0 8, err: DB closed
2022-01-08 22:41:55.538 - warn: zigbee.0 (10089) redis mget 0 8, err: DB closed
2022-01-08 22:41:55.539 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.539 - warn: zigbee.0 (10089) redis mget 0 14, err: DB closed
2022-01-08 22:41:55.539 - warn: zigbee.0 (10089) redis mget 0 14, err: DB closed
2022-01-08 22:41:55.539 - warn: zigbee.0 (10089) redis mget 0 9, err: DB closed
2022-01-08 22:41:55.540 - warn: zigbee.0 (10089) redis mget 0 11, err: DB closed
2022-01-08 22:41:55.836 - info: zigbee.0 (10089) terminating with timeout
2022-01-08 22:41:56.148 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.148 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.149 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.150 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.150 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.151 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.151 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.152 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.152 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.153 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.153 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.154 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.154 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.155 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.155 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.162 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.165 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.168 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.171 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.174 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.177 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.181 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.184 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.186 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.189 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.530 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 killing pid 10089
2022-01-08 22:41:56.664 - warn: zigbee.0 (10089) Cannot get view: Connection is closed.
2022-01-08 22:41:56.665 - warn: zigbee.0 (10089) Cannot get view: Connection is closed.
2022-01-08 22:41:56.665 - warn: zigbee.0 (10089) Cannot get view: Connection is closed.
2022-01-08 22:41:56.665 - warn: zigbee.0 (10089) Cannot get view: Connection is closed.
2022-01-08 22:41:56.666 - warn: zigbee.0 (10089) Cannot get view: Connection is closed.
2022-01-08 22:41:56.716 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00052debfb.link_quality: Connection is closed.
2022-01-08 22:41:56.717 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.717 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00051dfd12.available: Connection is closed.
2022-01-08 22:41:56.717 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.718 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00051dfd12.link_quality: Connection is closed.
2022-01-08 22:41:56.718 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.718 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00051e1633.available: Connection is closed.
2022-01-08 22:41:56.719 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.719 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00051e1633.link_quality: Connection is closed.
2022-01-08 22:41:56.720 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.720 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000283e67b.available: Connection is closed.
2022-01-08 22:41:56.720 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.721 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000283e67b.link_quality: Connection is closed.
2022-01-08 22:41:56.721 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.721 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000283e64e.available: Connection is closed.
2022-01-08 22:41:56.722 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.722 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000283e64e.link_quality: Connection is closed.
2022-01-08 22:41:56.723 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.723 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000163f2bc.available: Connection is closed.
2022-01-08 22:41:56.723 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.724 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000163f2bc.link_quality: Connection is closed.
2022-01-08 22:41:56.724 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.724 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00041d8697.available: Connection is closed.
2022-01-08 22:41:56.725 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.725 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00041d8697.link_quality: Connection is closed.
2022-01-08 22:41:56.726 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.726 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000412fc1e.available: Connection is closed.
2022-01-08 22:41:56.726 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.727 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000412fc1e.link_quality: Connection is closed.
2022-01-08 22:41:56.727 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.728 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000282eec7.available: Connection is closed.
2022-01-08 22:41:56.728 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.728 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000282eec7.link_quality: Connection is closed.
2022-01-08 22:41:56.729 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.729 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0003f0f373.available: Connection is closed.
2022-01-08 22:41:56.729 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.730 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0003f0f373.link_quality: Connection is closed.
2022-01-08 22:41:56.730 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.730 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf8b49.available: Connection is closed.
2022-01-08 22:41:56.731 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.732 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf8b49.link_quality: Connection is closed.
2022-01-08 22:41:56.732 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.732 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00178801089def32.available: Connection is closed.
2022-01-08 22:41:56.733 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.733 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00178801089def32.link_quality: Connection is closed.
2022-01-08 22:41:56.733 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.734 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00178801089de95e.available: Connection is closed.
2022-01-08 22:41:56.734 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.735 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00178801089de95e.link_quality: Connection is closed.
2022-01-08 22:41:56.735 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.735 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00076565a1.available: Connection is closed.
2022-01-08 22:41:56.736 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.736 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00076565a1.link_quality: Connection is closed.
2022-01-08 22:41:56.736 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.737 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f35a.available: Connection is closed.
2022-01-08 22:41:56.737 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.737 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f35a.link_quality: Connection is closed.
2022-01-08 22:41:56.738 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.738 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0001e4e9e3.available: Connection is closed.
2022-01-08 22:41:56.739 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.739 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0001e4e9e3.link_quality: Connection is closed.
2022-01-08 22:41:56.739 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.740 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00019f3736.available: Connection is closed.
2022-01-08 22:41:56.740 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.740 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00019f3736.link_quality: Connection is closed.
2022-01-08 22:41:56.741 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.741 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f34a.available: Connection is closed.
2022-01-08 22:41:56.742 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.742 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f34a.link_quality: Connection is closed.
2022-01-08 22:41:56.743 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.743 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00077dce53.available: Connection is closed.
2022-01-08 22:41:56.743 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.744 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00077dce53.link_quality: Connection is closed.
2022-01-08 22:41:56.744 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.744 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00075f6607.available: Connection is closed.
2022-01-08 22:41:56.745 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.745 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00075f6607.link_quality: Connection is closed.
2022-01-08 22:41:56.746 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.746 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f31c.available: Connection is closed.
2022-01-08 22:41:56.746 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.747 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f31c.link_quality: Connection is closed.
2022-01-08 22:41:56.747 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.747 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00077dce21.available: Connection is closed.
2022-01-08 22:41:56.748 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.748 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00077dce21.link_quality: Connection is closed.
2022-01-08 22:41:56.748 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.749 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f2c9.available: Connection is closed.
2022-01-08 22:41:56.749 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.750 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f2c9.link_quality: Connection is closed.
2022-01-08 22:41:56.750 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.750 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f2cb.available: Connection is closed.
2022-01-08 22:41:56.751 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.751 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d000774f2cb.link_quality: Connection is closed.
2022-01-08 22:41:56.751 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.752 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00073c0c65.available: Connection is closed.
2022-01-08 22:41:56.752 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.752 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00073c0c65.link_quality: Connection is closed.
2022-01-08 22:41:56.753 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.753 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00044eefbe.available: Connection is closed.
2022-01-08 22:41:56.754 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.754 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d00044eefbe.link_quality: Connection is closed.
2022-01-08 22:41:56.754 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.755 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe245425.available: Connection is closed.
2022-01-08 22:41:56.755 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.755 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe245425.link_quality: Connection is closed.
2022-01-08 22:41:56.756 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.756 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf4ea4.available: Connection is closed.
2022-01-08 22:41:56.756 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.757 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf4ea4.link_quality: Connection is closed.
2022-01-08 22:41:56.757 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.758 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.804b50fffef8cf51.available: Connection is closed.
2022-01-08 22:41:56.758 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.758 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.804b50fffef8cf51.link_quality: Connection is closed.
2022-01-08 22:41:56.759 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.759 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84ba20fffe77b835.available: Connection is closed.
2022-01-08 22:41:56.759 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.760 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84ba20fffe77b835.link_quality: Connection is closed.
2022-01-08 22:41:56.760 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.760 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84ba20fffe77b200.available: Connection is closed.
2022-01-08 22:41:56.761 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.761 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84ba20fffe77b200.link_quality: Connection is closed.
2022-01-08 22:41:56.761 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.762 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe1f8f5d.available: Connection is closed.
2022-01-08 22:41:56.762 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.762 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe1f8f5d.link_quality: Connection is closed.
2022-01-08 22:41:56.763 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.763 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe1f8f8c.available: Connection is closed.
2022-01-08 22:41:56.763 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.764 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.84fd27fffe1f8f8c.link_quality: Connection is closed.
2022-01-08 22:41:56.764 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.765 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.b4e3f9fffeaae8c8.available: Connection is closed.
2022-01-08 22:41:56.765 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.765 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.b4e3f9fffeaae8c8.link_quality: Connection is closed.
2022-01-08 22:41:56.766 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.766 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.842e14fffe89313a.available: Connection is closed.
2022-01-08 22:41:56.767 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.767 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.842e14fffe89313a.link_quality: Connection is closed.
2022-01-08 22:41:56.767 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.768 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.842e14fffe285173.available: Connection is closed.
2022-01-08 22:41:56.768 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.768 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.842e14fffe285173.link_quality: Connection is closed.
2022-01-08 22:41:56.769 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.769 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.804b50fffe606093.available: Connection is closed.
2022-01-08 22:41:56.769 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.770 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.804b50fffe606093.link_quality: Connection is closed.
2022-01-08 22:41:56.770 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.770 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.540f57fffe8971d1.available: Connection is closed.
2022-01-08 22:41:56.771 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.771 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.540f57fffe8971d1.link_quality: Connection is closed.
2022-01-08 22:41:56.772 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.772 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf4ea4.occupancy: Connection is closed.
2022-01-08 22:41:56.772 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:56.776 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.778 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.785 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.787 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.790 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.804 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.806 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.809 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.812 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.814 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.817 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.819 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.822 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.825 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.827 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.830 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.833 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.835 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.838 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.841 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.843 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.846 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.848 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.851 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.853 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.856 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.858 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.861 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.863 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.866 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.869 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.871 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.875 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.878 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
at runMicrotasks ()
at runNextTicks (internal/process/task_queues.js:62:5)
at processImmediate (internal/timers.js:434:9)
2022-01-08 22:41:56.880 - error: zigbee.0 (10089) getDevices error: TypeError: Cannot read property 'resolveEntity' of undefined
at /opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:257:64
2022-01-08 22:41:56.884 - warn: zigbee.0 (10089) Could not perform strict object check of state zigbee.0.00158d0005cf4ea4.no_motion: Connection is closed.
2022-01-08 22:41:56.885 - warn: zigbee.0 (10089) get state error: Connection is closed.
2022-01-08 22:41:57.196 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-01-08 22:41:58.539 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 10117
2022-01-08 22:42:02.938 - info: zigbee.0 (10117) starting. Version 1.6.11 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.20.0, js-controller: 3.3.21
2022-01-08 22:42:03.050 - info: zigbee.0 (10117) Starting Zigbee npm ...
2022-01-08 22:42:03.051 - warn: zigbee.0 (10117) 4 extensions initialized
2022-01-08 22:42:03.052 - warn: zigbee.0 (10117) extension DeviceAvailability
2022-01-08 22:42:03.053 - warn: zigbee.0 (10117) extension DeviceConfigure
2022-01-08 22:42:03.053 - warn: zigbee.0 (10117) extension DeviceEvent
2022-01-08 22:42:03.053 - warn: zigbee.0 (10117) extension DelayedAction
2022-01-08 22:42:03.560 - info: zigbee.0 (10117) Installed Version: ioBroker/ioBroker.zigbee
2022-01-08 22:42:03.589 - info: zigbee.0 (10117) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":88,"maintrel":0,"revision":"0x26580700"}}
2022-01-08 22:42:03.610 - info: zigbee.0 (10117) Unable to disable LED, unsupported function.
2022-01-08 22:42:03.621 - info: zigbee.0 (10117) --> transmitPower : normal
2022-01-08 22:42:03.791 - info: zigbee.0 (10117) Unable to set transmit power, unsupported function.
2022-01-08 22:42:03.799 - info: zigbee.0 (10117) Currently 45 devices are joined:
2022-01-08 22:42:03.954 - info: zigbee.0 (10117) Configuring 0x84ba20fffe77b835 TS011F
2022-01-08 22:42:03.958 - info: zigbee.0 (10117) 0x00158d000410e87b (addr 32835): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.972 - info: zigbee.0 (10117) 0x00158d000411103a (addr 26950): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.974 - info: zigbee.0 (10117) 0x00158d000410e8ca (addr 1223): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.976 - info: zigbee.0 (10117) 0x00158d000309a45a (addr 35075): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.977 - info: zigbee.0 (10117) 0x00158d0005221c38 (addr 31581): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:03.978 - info: zigbee.0 (10117) 0x00158d0005221fbe (addr 11411): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:03.980 - info: zigbee.0 (10117) 0x00158d0005221c37 (addr 57703): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:03.981 - info: zigbee.0 (10117) 0x00158d00052debfb (addr 30191): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:03.983 - info: zigbee.0 (10117) 0x00158d00051dfd12 (addr 48749): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
2022-01-08 22:42:03.984 - info: zigbee.0 (10117) 0x00158d00051e1633 (addr 39535): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
2022-01-08 22:42:03.986 - info: zigbee.0 (10117) 0x00158d000283e67b (addr 50956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.989 - info: zigbee.0 (10117) 0x00158d000283e64e (addr 18527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.991 - info: zigbee.0 (10117) 0x00158d000163f2bc (addr 63165): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.992 - info: zigbee.0 (10117) 0x00158d00041d8697 (addr 26015): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.994 - info: zigbee.0 (10117) 0x00158d000412fc1e (addr 39417): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.995 - info: zigbee.0 (10117) 0x00158d000282eec7 (addr 19057): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:03.996 - info: zigbee.0 (10117) 0x00158d0003f0f373 (addr 46914): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:42:03.998 - info: zigbee.0 (10117) 0x00158d0005cf8b49 (addr 43071): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:42:03.999 - info: zigbee.0 (10117) 0x00178801089def32 (addr 26711): 929002240401 - Philips Hue smart plug - EU (Router)
2022-01-08 22:42:04.001 - info: zigbee.0 (10117) 0x00178801089de95e (addr 39138): 929002240401 - Philips Hue smart plug - EU (Router)
2022-01-08 22:42:04.002 - info: zigbee.0 (10117) 0x00158d00076565a1 (addr 35956): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.003 - info: zigbee.0 (10117) 0x00158d000774f35a (addr 23883): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.005 - info: zigbee.0 (10117) 0x00158d0001e4e9e3 (addr 29911): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:04.006 - info: zigbee.0 (10117) 0x00158d00019f3736 (addr 26600): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2022-01-08 22:42:04.007 - info: zigbee.0 (10117) 0x00158d000774f34a (addr 13527): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.009 - info: zigbee.0 (10117) 0x00158d00077dce53 (addr 62480): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.010 - info: zigbee.0 (10117) 0x00158d00075f6607 (addr 3323): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.011 - info: zigbee.0 (10117) 0x00158d000774f31c (addr 31399): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.013 - info: zigbee.0 (10117) 0x00158d00077dce21 (addr 56764): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.014 - info: zigbee.0 (10117) 0x00158d000774f2c9 (addr 16865): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.017 - info: zigbee.0 (10117) 0x00158d000774f2cb (addr 13799): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.019 - info: zigbee.0 (10117) 0x00158d00073c0c65 (addr 815): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2022-01-08 22:42:04.020 - info: zigbee.0 (10117) 0x00158d00044eefbe (addr 41589): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:42:04.022 - info: zigbee.0 (10117) 0x84fd27fffe245425 (addr 308): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:42:04.023 - info: zigbee.0 (10117) 0x00158d0005cf4ea4 (addr 42668): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2022-01-08 22:42:04.025 - info: zigbee.0 (10117) 0x804b50fffef8cf51 (addr 60471): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:42:04.027 - info: zigbee.0 (10117) 0x84ba20fffe77b835 (addr 487): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:42:04.029 - info: zigbee.0 (10117) 0x84ba20fffe77b200 (addr 29486): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:42:04.030 - info: zigbee.0 (10117) 0x84fd27fffe1f8f5d (addr 43353): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:42:04.032 - info: zigbee.0 (10117) 0x84fd27fffe1f8f8c (addr 8187): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2022-01-08 22:42:04.033 - info: zigbee.0 (10117) 0xb4e3f9fffeaae8c8 (addr 59871): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
2022-01-08 22:42:04.034 - info: zigbee.0 (10117) 0x842e14fffe89313a (addr 26171): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
2022-01-08 22:42:04.035 - info: zigbee.0 (10117) 0x842e14fffe285173 (addr 60803): E2001/E2002 - IKEA STYRBAR remote control N2 (EndDevice)
2022-01-08 22:42:04.037 - info: zigbee.0 (10117) 0x804b50fffe606093 (addr 21921): ICPSHC24-30EU-IL-1 - IKEA TRADFRI driver for wireless control (30 watt) (Router)
2022-01-08 22:42:04.038 - info: zigbee.0 (10117) 0x540f57fffe8971d1 (addr 40423): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
2022-01-08 22:42:04.039 - warn: zigbee.0 (10117) config :{"port":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2253809-if00","panID":"6754","extPanID":"DDDDDDDDDDDDDDDD","channel":"11","disableLed":false,"precfgkey":"abcdef01234567899876543210fedcba","countDown":"60","adapterType":"deconz","debugHerdsman":false,"transmitPower":null,"extPanIdFix":true,"disablePing":false,"external":"","startWithInconsistent":false}
2022-01-08 22:42:04.040 - info: zigbee.0 (10117) Zigbee started
2022-01-08 22:42:04.147 - info: zigbee.0 (10117) debug devices set to []
2022-01-08 22:43:03.996 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x84ba20fffe77b835 TS011F, attempt 1 (Error: Read 0x84ba20fffe77b835/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)
at DeconzAdapter.sendZclFrameToEndpoint (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:641:23))
2022-01-08 22:43:03.998 - info: zigbee.0 (10117) Configuring 0x84fd27fffe1f8f5d TRADFRI on/off switch
2022-01-08 22:43:36.915 - info: zigbee.0 (10117) Zigbee: allowing new devices to join.
2022-01-08 22:43:48.292 - info: zigbee.0 (10117) Starting interview of '0x84ba20fffe80c9ba'
2022-01-08 22:43:49.801 - info: zigbee.0 (10117) Successfully interviewed '0x84ba20fffe80c9ba', device has succesfully been paired
2022-01-08 22:43:49.801 - info: zigbee.0 (10117) Device '0x84ba20fffe80c9ba' is supported, identified as: TuYa Smart plug (with power monitoring by polling) (TS011F_plug_3)
2022-01-08 22:43:49.804 - info: zigbee.0 (10117) Configuring 0x84ba20fffe80c9ba TS011F
2022-01-08 22:43:49.929 - info: zigbee.0 (10117) DeviceConfigure successful 0x84ba20fffe80c9ba TS011F
2022-01-08 22:44:01.437 - warn: zigbee.0 (10117) SetState_typed called without type
2022-01-08 22:44:04.362 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x84fd27fffe1f8f5d TRADFRI on/off switch, attempt 1 (Error: Bind 0x84fd27fffe1f8f5d/1 genOnOff from '901' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
2022-01-08 22:44:04.363 - info: zigbee.0 (10117) Configuring 0x84fd27fffe1f8f8c TRADFRI on/off switch
2022-01-08 22:44:05.587 - warn: zigbee.0 (10117) DeviceAvailability:Failed to ping 0x84ba20fffe77b835 TS011F
2022-01-08 22:44:38.635 - info: zigbee.0 (10117) Zigbee: stop joining
2022-01-08 22:45:04.401 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x84fd27fffe1f8f8c TRADFRI on/off switch, attempt 1 (Error: Bind 0x84fd27fffe1f8f8c/1 genOnOff from '901' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
2022-01-08 22:45:04.402 - info: zigbee.0 (10117) Configuring 0x842e14fffe89313a Remote Control N2
2022-01-08 22:46:04.613 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x842e14fffe89313a Remote Control N2, attempt 1 (Error: Bind 0x842e14fffe89313a/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
2022-01-08 22:46:04.614 - info: zigbee.0 (10117) Configuring 0x842e14fffe285173 Remote Control N2
2022-01-08 22:46:07.876 - warn: zigbee.0 (10117) SetState_typed called without type
2022-01-08 22:47:05.557 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 1 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
2022-01-08 22:47:44.618 - warn: zigbee.0 (10117) SetState_typed called without type
2022-01-08 22:48:45.631 - error: zigbee.0 (10117) Send command to 0x84ba20fffe80c9ba failed with no error code (no response received)
2022-01-08 22:49:03.882 - warn: zigbee.0 (10117) SetState_typed called without type
2022-01-08 22:52:37.065 - info: zigbee.0 (10117) Configuring 0x842e14fffe285173 Remote Control N2
2022-01-08 22:53:37.661 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 2 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19))
2022-01-08 22:58:31.232 - info: hue-extended.0 (23663) Attempt 1x - Successfully set Bad Kevin.
2022-01-08 23:02:10.523 - info: zigbee.0 (10117) Configuring 0x842e14fffe285173 Remote Control N2
2022-01-08 23:02:18.456 - info: zigbee.0 (10117) Configuring 0x842e14fffe89313a Remote Control N2
2022-01-08 23:02:21.525 - info: zigbee.0 (10117) DeviceConfigure successful 0x842e14fffe89313a Remote Control N2
2022-01-08 23:03:10.742 - warn: zigbee.0 (10117) DeviceConfigure:DeviceConfigure failed 0x842e14fffe285173 Remote Control N2, attempt 3 (Error: Bind 0x842e14fffe285173/1 genPowerCfg from '0x00212effff065d89/1' failed (waiting for response TIMEOUT)
at DeconzAdapter.bind (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:753:19)
at runNextTicks (internal/process/task_queues.js:62:5)
at processTimers (internal/timers.js:494:9))

Und:
Wenn ich über den Zigbee Adapter den Power Plug ein/ausschalte, steht folgendes im log:

zigbee.0 2022-01-08 23:07:14.263	warn	SetState_typed called without type

Ich beobachte das ganze mal und berichte wieder :)

Note: ich hab über Github geupdated, dann Zigbee selbst nochmal neu gestartet (über iobroker), und dann einen neuen Plug hinzugefügt. Wieso nun so viele andere Geräte ebenfalls konfiguriert werden - obwohl sie es schon sind - weiß ich nicht.

Asgothian

@schmetterfliege sagte in SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.:

Und:
Wenn ich über den Zigbee Adapter den Power Plug ein/ausschalte, steht folgendes im log:

was bedeutet "über den Zigbee Adapter" ausschalten ?

A.

Community Forum

NEWS

SHP-15+Zigbee Adp.: "TS011F" not described in statesMapping.

Support us

748

32.5k

81.8k

1.3m