NEWS
ZigBee neue Version 1.8.x
-
-
@arteck
die Tuya? Einfach neu Pairen oder entfernen und dann neu Pairen? -
@arteck
hab sie ohne zu löschen neu verbunden. Allerdings kam am Standort immer nur2023-07-11 10:02:49.606 - warn: zigbee.0 (6116) Device '0xa4c138dc44bd0f4a' announced itself
und die Steckdose ging danach sofort aus dem Pairing-Mode.
Ich musste sie nahe dem Controller einstecken (Bad ging so, da nahe am Raspi), damit auch das Interview startete:
2023-07-11 10:22:51.082 - info: zigbee.0 (6116) Starting interview of '0xa4c138dc44bd0f4a' 2023-07-11 10:22:51.094 - warn: zigbee.0 (6116) Device '0xa4c138dc44bd0f4a' announced itself 2023-07-11 10:22:51.480 - info: zigbee.0 (6116) Successfully interviewed '0xa4c138dc44bd0f4a', device has successfully been paired 2023-07-11 10:22:51.480 - info: zigbee.0 (6116) Device '0xa4c138dc44bd0f4a' is supported, identified as: TuYa Smart plug (with power monitoring) (TS011F_plug_1) 2023-07-11 10:22:51.482 - info: zigbee.0 (6116) Configuring 0xa4c138dc44bd0f4a TS011F 2023-07-11 10:22:52.397 - info: zigbee.0 (6116) DeviceConfigure successful 0xa4c138dc44bd0f4a TS011F
Publish Meldungen sind noch da, schalten geht jetzt - Sentry wieder rein?
-
-
@arteck Wie es aussieht klappt es mit der 1.8.15. Timestamp ok, Werte werde ich die nächsten Tage mal im Auge behalten.
Danke für den Fix
Reiner
-
ich habe hier einen Tuya ZY-M100-S und versucht diesen einzubinden (Zigbee Adapter Version 1.8.18, Admin 6.6.1, js-Controller 4.0.24), auf zigbee2mqtt.io ist der Sensor gelistet.
Leider wird bei mir ein TS0601 erkannt
Mit folgender Meldung im log (schaut unauffällig aus):
2023-07-20 18:18:00.856 - info: zigbee.0 (784) Starting interview of '0xa4c138611008805f' 2023-07-20 18:18:01.022 - info: zigbee.0 (784) Successfully interviewed '0xa4c138611008805f', device has successfully been paired 2023-07-20 18:18:38.900 - info: zigbee.0 (784) Starting interview of '0xa4c138611008805f'
Unter den Objekten schaut´s so aus:
und der Inhalt von
msg_from_zigbee
beinhaltet:{ "type": "commandDataReport", "data": { "seq": 46080, "dpValues": [ { "dp": 9, "datatype": 2, "data": { "type": "Buffer", "data": [ 0, 0, 0, 129 ] } } ] }, "linkquality": 97, "groupID": 0, "cluster": "manuSpecificTuya", "meta": { "zclTransactionSequenceNumber": 246, "manufacturerCode": null, "frameControl": { "frameType": 1, "manufacturerSpecific": false, "direction": 1, "disableDefaultResponse": false, "reservedBits": 0 } }, "endpoint_id": 1 }
Siehst du eine Möglichkeit den Sensor zu integrieren, da ich mich nicht im Stande sehe dies zu tun?
Falls du noch mehr Info´s brauchst, gib Bescheid.Vielen Dank für deine Rückmeldung!
-
-
Guten Morgen @arteck
hier zu finden: https://www.zigbee2mqtt.io/devices/ZY-M100-S.html
-
@latzi dann wirds ne neue charge geben deiner _tze204_qasjif9e ist noch nicht inder config drin
zuerst adapter von GIT installieren ..dann die Zeile tauschen (position ca. 4180)
fingerprint: tuya.fingerprint('TS0601', ['_TZE204_sxm7l9xa']),
nach
fingerprint: tuya.fingerprint('TS0601', ['_TZE204_sxm7l9xa', '_TZE204_qasjif9e']),
in der
/opt/iobroker/node_modules/zigbee-herdsman-converters/devices/tuya.js
dann adapter neu starten.. evtl. musst du deu pairen
-
@arteck
sehr cool, Dankeschön - ein Schritt weiter.In den Objekten tauchen jetzt deutlich mehr Datenpunkte auf, es werden aber nur
illuminance
,link_quality
undmsg_from_zigbee
aktualisiert, der Rest bleibtnull
.Hast du dazu auch noch eine Idee?
Vielen, herzlichen Dank für deine grenzgeniale Arbeit hier!
-
@latzi die null werte kannst du beschreiben.. womit kein plan
-
@arteck sagte in ZigBee neue Version 1.8.x:
Hi, fleissiger lieber Developer
hast du dir mal das Issue Occupancy timeout angeschaut ? -
@ilovegym issue gesehen.. ja nachgestellt nein
machmal bitte
https://github.com/ioBroker/ioBroker.zigbee/wiki/debug-messages-with-zigbee.0.info.debugmessages
und ändere den Wert.. poste mal was unter ELEVATED steht und die msg_from_zigbee .. vielleicht seh ich da schon was
-
@arteck
ich habe das gleiche Problem. Ich habe den ieee Wert eingetragen und den Wert zigbee.0.00158d00075d69e8.occupancy_timeout auf 120 geändert. Im log steht dann:zigbee.0 2023-07-21 11:43:21.121 warn ELEVATED Change state 'occupancy_timeout' at device 0x00158d00075d69e8 type 'RTCGQ11LM'
Dann eine Bewegung ausgelöst. zigbee.0.00158d00075d69e8.no_motion stellt sich auf 0, ist ja richtig. Nach 120 sec. springt der Wert auf 120 sec und zählt dann von dort aus weiter!
Im Log gibt es keinen weiteren Eintrag.Ich hoffe, ich konnte helfen
Bester Grüße
-
@schmuh nochmal... die daten passen nicht
sdu stellst den auf 120 aber im datenpunkt 100 ..ja was den jetzt ??
-
@arteck
das war ein Screenshot von einem anderen Versuch -
@schmuh ok dann verstehe ich das PROBLEM nicht..sry..
-
ok, gemacht: (da ist noch n Fehler von ner Missglueckten Anmeldung eines Tradfri drin, kannste ignorieren..)
2023-07-21 12:31:58.821 - info: zigbee.0 (444344) Starting Zigbee npm ... 2023-07-21 12:31:58.940 - info: zigbee.0 (444344) Installed Version: iobroker.zigbee@1.8.18 2023-07-21 12:31:58.763 - info: zigbee.0 (444344) starting. Version 1.8.18 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.16.1, js-controller: 5.0.8 2023-07-21 12:31:58.820 - info: zigbee.0 (444344) delete old Backup files. keep only last 10 2023-07-21 12:31:58.821 - info: zigbee.0 (444344) Starting Zigbee npm ... 2023-07-21 12:31:58.940 - info: zigbee.0 (444344) Installed Version: iobroker.zigbee@1.8.18 2023-07-21 12:32:00.412 - info: zigbee.0 (444344) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2023-07-21 12:32:00.419 - info: zigbee.0 (444344) Unable to disable LED, unsupported function. 2023-07-21 12:32:00.427 - info: zigbee.0 (444344) --> transmitPower : high 2023-07-21 12:32:00.528 - info: zigbee.0 (444344) Currently 227 devices are joined: . . . 2023-07-21 12:32:00.951 - info: zigbee.0 (444344) Zigbee started 2023-07-21 12:32:01.100 - warn: zigbee.0 (444344) download icon Tradfri-1 for undefined Device not available. Check your devices. 2023-07-21 12:32:01.235 - info: zigbee.0 (444344) debug devices set to ["00158d0002278b91"] 2023-07-21 12:32:01.579 - error: zigbee.0 (444344) Device 0xf4b3b1fffe9e1f4d "undefined" not described in statesMapping. 2023-07-21 12:32:01.908 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"available":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Available' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":10}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '10' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:32:00.412 - info: zigbee.0 (444344) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2023-07-21 12:32:00.419 - info: zigbee.0 (444344) Unable to disable LED, unsupported function. 2023-07-21 12:32:00.427 - info: zigbee.0 (444344) --> transmitPower : high 2023-07-21 12:32:00.528 - info: zigbee.0 (444344) Currently 227 devices are joined: . . . . . 2023-07-21 12:32:00.951 - info: zigbee.0 (444344) Zigbee started 2023-07-21 12:32:01.100 - warn: zigbee.0 (444344) download icon Tradfri-1 for undefined Device not available. Check your devices. 2023-07-21 12:32:01.235 - info: zigbee.0 (444344) debug devices set to ["00158d0002278b91"] 2023-07-21 12:32:01.579 - error: zigbee.0 (444344) Device 0xf4b3b1fffe9e1f4d "undefined" not described in statesMapping. 2023-07-21 12:32:01.908 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"available":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Available' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":10}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:01.909 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '10' from device 00158d0002278b91 for 'Link quality' . 2023-07-21 12:32:26.026 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":69}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:26.026 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '69' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:32:26.026 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":69}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:26.026 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '69' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:32:26.027 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:33:56.028 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:33:56.029 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:33:56.029 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:33:56.028 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:33:56.029 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:33:56.029 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:34:13.450 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":109}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:34:13.450 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '109' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:34:13.451 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:34:13.451 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:34:13.451 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:35:43.451 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:35:43.452 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:35:43.452 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:35:43.451 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:35:43.452 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:35:43.452 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion' . . . 2023-07-21 12:36:20.089 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":91}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:36:20.089 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '91' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:36:20.090 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:36:20.090 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:36:20.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:36:20.089 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"linkquality":91}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:36:20.089 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated '91' from device 00158d0002278b91 for 'Link quality' 2023-07-21 12:36:20.090 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":true}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:36:20.090 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:36:20.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'true' from device 00158d0002278b91 for 'Time from last motion' . . . 2023-07-21 12:37:50.090 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:37:50.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:37:50.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion' 2023-07-21 12:37:50.090 - warn: zigbee.0 (444344) ELEVATED publishToState: message received '{"occupancy":false}' from device 00158d0002278b91 type 'RTCGQ01LM' 2023-07-21 12:37:50.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Occupancy' 2023-07-21 12:37:50.091 - warn: zigbee.0 (444344) ELEVATED publishToState: value generated 'false' from device 00158d0002278b91 for 'Time from last motion'
-
@arteck sagte in ZigBee neue Version 1.8.x:
die null werte kannst du beschreiben.. womit kein plan
okay, hab ich gemacht (in der Beschreibung stehen Richtwerte), jedoch werden die Werte
,available
presence
undtarget_distance
nicht aktualisiert - und somit auch keine Bewegung erkannt, hier die Objekte:
Woran kann das liegen?
Edit: Nach Neustart wurde
available
aktualisiert -
@latzi sagte in ZigBee neue Version 1.8.x:
@arteck sagte in ZigBee neue Version 1.8.x:
die null werte kannst du beschreiben.. womit kein plan
okay, hab ich gemacht (in der Beschreibung stehen Richtwerte), jedoch werden die Werte
available
,presence
undtarget_distance
nicht aktualisiert - und somit auch keine Bewegung erkannt, hier die Objekte:
Woran kann das liegen?
Moin,
dass Dein Device gerade nicht
available
ist, ist Dir schon klar?VG
Bernd