Zigbee-Adapter 1.0.2 Danalock

Matdos

Coole Sache danke dir schon mal 👍👍👍

smarthomegirl

Hallo,
@Asgothian bist du denn schon weiter voran gekommen?

Mein hier beschriebenes Problem besteht nach wie vor. Jedes Mal wenn der ioBroker neugestartet werden muss (wegen Stromausfall, Gewitter, etc.) kommt keine Statusrückmeldung mehr. Ich muss dann wieder das Danalock neu anlernen. Das ist echt nervig.

Gibt es denn keine Möglichkeit dieses Problem zu beheben?

patrick039212

Leider das selbe Problem, zusätzlich kann ich das Danalock in der Instanz nicht löschen...
Gestern hat noch alles funktioniert, was ich nur gesehen habe wenn ich auf das blaue ! klicke steht

configured:false

Adapter gelöscht neu installiert sehe keinen Status mehr und kann das schloss weder schließen noch öffnen ....

@Asgothian wird es ein update geben ?

ed:

Wenn ich es neuverbinden möchte

Error: Failed to do action 0x000b57fffe59e779 V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
    at Object.delayAction [as action] (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69)). undefined

smarthomegirl

Hallo @Asgothian,

leider habe ich IMMERNOCH dieses Problem. Neuerdings sendet das Danalock aus dem Nix keine Statusrückmeldung mehr, ohne dass ich ein Update o. ä. gemacht habe. Dann muss ich das Schloss wieder neu anlernen. Das ist echt blöd. :disappointed_relieved: :disappointed:

@Asgothian wird es denn bald ein Update geben?

Liebe und kühle Grüße.

smarteule

Geht mir auch so. Verzweifle bald.

Gr

patrick039212

gibt es schon eine Lösung ? habe den neuen Adapter installiert 1.2, leider kann ich den stat garnicht mehr ändern und der Status wird nicht korrekt angezeigt...

3573) system.adapter.admin.0: logging true
falsezigbee.0	2020-09-22 19:03:43.477	debug	(3573) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":52903,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
falsezigbee.0	2020-09-22 19:03:43.474	debug	(3573) convert state, unlock, {}
falsezigbee.0	2020-09-22 19:03:43.472	debug	(3573) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":52903,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
falsezigbee.0	2020-09-22 19:03:43.464	debug	(3573) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
falsezigbee.0	2020-09-22 19:03:43.461	debug	(3573) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
falsezigbee.0	2020-09-22 19:03:43.454	debug	(3573) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"unlock","ack":false,"ts":1600794223445,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1600794214614}
falsezigbee.0	2020-09-22 19:03:36.225	debug	(3573) system.adapter.admin.0: logging false
falsezigbee.0	2020-09-22 19:03:34.648	debug	(3573) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":52903,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
falsezigbee.0	2020-09-22 19:03:34.645	debug	(3573) convert state, unlock, {}
falsezigbee.0	2020-09-22 19:03:34.643	debug	(3573) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":52903,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
falsezigbee.0	2020-09-22 19:03:34.637	debug	(3573) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
falsezigbee.0	2020-09-22 19:03:34.633	debug	(3573) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
falsezigbee.0	2020-09-22 19:03:34.625	debug	(3573) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"unlock","ack":false,"ts":1600794214614,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1600794214614}
falsezigbee.0

Asgothian

@patrick039212
@smarthomegirl
@smarteule

I have to admit that i had fallen into more than a bit of a hole and have not done zip on stuff over the summer. But i have gone back to look at it again. I still think that the lock is not configured correctly / not reconfigured correctly when the adapter is restarted.

I will push an update with a bit of test code soon - although this will most likely be an update to the zigbee-shepherd-converters, rather than the zigbee adapter.

A.
p.s. Ich bitte den englischen Text zu entschuldigen - irgendwie ist meine Sprachdatei durcheinander geraten ;)

Asgothian

@patrick039212
Ich brauche noch mal ein paar Details. Kannst Du bitte den folgenden Test machen ?

Danalock aus dem Adapter entfernen (unpair)
Danalock neu pairen

Wenn ich das richtig erinnere sollte das Schloss jetzt sauber funktionieren und auch den Status melden.

Jetzt kommt das entscheidende:

Adapter auf Debug stellen
Adapter neu starten. Ich erwarte Zeilen wie diese:

DeviceConfigure 0x90fd9ffffe6de22b TRADFRI transformer 10W not needed

für das Danalock. Wenn diese Zeilen kommen, und das Schloss in der Folge nicht reagiert habe kann ich kurzfristig eine Adapterversion zur Verfügung stellen die eine chance hat das Problem zu beseitigen.

A.

patrick039212

@Asgothian

leider kann ich das Schloss nicht entfernen ... es lässt sich einfach nicht löschen ...

Failed to remove TypeError: Cannot read property 'stack' of undefined at ZigbeeController.remove (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:358:65)

Asgothian

@patrick039212
Auch mit "force" für lost devices nicht ?

patrick039212

@Asgothian
nein es wird immer als Aktiv angezeigt... ohne force kommt diese Meldung

Failed to remove TypeError: Cannot read property 'stack' of undefined at ZigbeeController.remove (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:358:65)

Asgothian

@patrick039212
können wir uns per TS/Discord und Anydesk zusammen hängen, dann kann ich das Schloss 'raus patchen'

patrick039212

@Asgothian

LOG inkl. versuch über iobroker zusperren

zigbee.0	2020-09-22 23:34:29.375	debug	(5369) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '255.353' seconds ago.
zigbee.0	2020-09-22 23:34:16.935	debug	(5369) system.adapter.admin.0: logging true
zigbee.0	2020-09-22 23:34:09.348	debug	(5369) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":58277,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-22 23:34:09.346	debug	(5369) convert state, unlock, {}
zigbee.0	2020-09-22 23:34:09.345	debug	(5369) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
zigbee.0	2020-09-22 23:34:09.339	debug	(5369) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
zigbee.0	2020-09-22 23:34:09.336	debug	(5369) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
zigbee.0	2020-09-22 23:34:09.331	debug	(5369) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"unlock","ack":false,"ts":1600810449323,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1600810449323}
zigbee.0	2020-09-22 23:33:57.847	debug	(5369) system.adapter.admin.0: logging false
zigbee.0	2020-09-22 23:32:29.285	error	at runMicrotasks (<anonymous>)
zigbee.0	2020-09-22 23:32:29.285	error	at /opt/iobroker/node_modules/iobroker.zigbee/main.js:369:48
zigbee.0	2020-09-22 23:32:29.285	error	at Object.convertSet (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman-converters/converters/toZigbee.js:1459:26)
zigbee.0	2020-09-22 23:32:29.285	error	at Endpoint.command (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:360:16)
zigbee.0	2020-09-22 23:32:29.285	error	at __awaiter (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:23:12)
zigbee.0	2020-09-22 23:32:29.285	error	at new Promise (<anonymous>)
zigbee.0	2020-09-22 23:32:29.285	error	at /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:27:71
zigbee.0	2020-09-22 23:32:29.285	error	at Generator.next (<anonymous>)
zigbee.0	2020-09-22 23:32:29.285	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:362:37)
zigbee.0	2020-09-22 23:32:29.285	error	at Object.getCommand (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/zcl/utils.js:107:19)
zigbee.0	2020-09-22 23:32:29.285	error	(5369) Error on send command to 0x000b57fffe59e779. Error: Error: Cluster 'closuresDoorLock' has no command 'lockedDoor'
zigbee.0	2020-09-22 23:32:29.266	debug	(5369) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":58277,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-22 23:32:29.265	debug	(5369) convert state, locked, {}
zigbee.0	2020-09-22 23:32:29.261	debug	(5369) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
zigbee.0	2020-09-22 23:32:29.253	debug	(5369) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
zigbee.0	2020-09-22 23:32:29.249	debug	(5369) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
zigbee.0	2020-09-22 23:32:29.227	debug	(5369) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"locked","ack":false,"ts":1600810349220,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1600799408406}
zigbee.0	2020-09-22 23:30:14.097	debug	(5369) Publish {"state":"LOCK","lock_state":"locked"}
zigbee.0	2020-09-22 23:30:14.063	debug	(5369) Type attributeReport device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profile
zigbee.0	2020-09-22 23:30:14.054	debug	(5369) Received Zigbee message from '0x000b57fffe59e779', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID null
zigbee.0	2020-09-22 23:30:14.032	debug	(5369) handleMessage. {"type":"attributeReport","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":
zigbee.0	2020-09-22 23:30:08.301	debug	(5369) Publish {"state":"LOCK","lock_state":"locked"}
zigbee.0	2020-09-22 23:30:07.983	debug	(5369) Type attributeReport device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profile
zigbee.0	2020-09-22 23:30:07.979	debug	(5369) Received Zigbee message from '0x000b57fffe59e779', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID null
zigbee.0	2020-09-22 23:30:07.938	debug	(5369) handleMessage. {"type":"attributeReport","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":58277,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":
zigbee.0	2020-09-22 23:29:29.375	debug	(5369) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '3555.098' seconds ago.
zigbee.0	2020-09-22 23:24:29.375	debug	(5369) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '3255.098' seconds ago.

Asgothian

@patrick039212 sagte in Zigbee-Adapter 1.0.2 Danalock:

Installier mal bitte den Adapter von meinem GitHub. Ich hab da nen Hack eingebaut das das Schloss bei jedem Start zwangsweise ein Configure durchläuft. (https://github.com/asgothian/ioBroker.zigbee)

Vielleicht sind die Fehler dann weg.

Ansonsten scheint das Problem mit dem nicht löschen können vom experimentellen Support für den Conbee zu stammen. Die Meldungen die du hattest kommen tief aus dem Zigbee-Herdsman. Wenn ich das mit nem conbee 1 nachstellen kann kann ich mal schauen was da im Argen ist.

A.

patrick039212

@Asgothian said in Zigbee-Adapter 1.0.2 Danalock:

https://github.com/asgothian/ioBroker.zigbee

Danke werde ich sofort testen,
heute habe ich leider wieder die verbindung verloren, habe nun meinen PI in der nähe vom Schloss angeschlossen, nachdem ich in der Danalock APP das pairing gestartet habe konnte ich ohne probleme das Schloss im Adapter löschen.

Ed:

Leider ändert sich bei mir der Status nicht mehr von locked / unlocked... öffnen schließen ist über den Adapter möglich

Adapter start

zigbee.0	2020-09-25 13:01:54.397	debug	(2647) Publish available for 0x00158d00042e3307 = true
zigbee.0	2020-09-25 13:01:54.385	debug	(2647) Publish available for 0x00158d000358efeb = true
zigbee.0	2020-09-25 13:01:54.355	debug	(2647) Publish available for 0x000b57fffe59e779 = true
zigbee.0	2020-09-25 13:01:53.405	info	(2647) Zigbee started
zigbee.0	2020-09-25 13:01:53.400	info	(2647) 0x00158d00042e3307 (addr 10193): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee.0	2020-09-25 13:01:53.396	debug	(2647) New device event: {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],
zigbee.0	2020-09-25 13:01:53.392	info	(2647) 0x00158d000358efeb (addr 9532): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee.0	2020-09-25 13:01:53.386	debug	(2647) New device event: {"type":"device","device":{"ID":3,"_type":"EndDevice","_ieeeAddr":"0x00158d000358efeb","_networkAddress":9532,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"
zigbee.0	2020-09-25 13:01:53.374	info	(2647) 0x000b57fffe59e779 (addr 23663): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
zigbee.0	2020-09-25 13:01:53.360	debug	(2647) New device event: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":23663,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"de
zigbee.0	2020-09-25 13:01:53.352	debug	(2647) DeviceConfigure 0x00158d00042e3307 lumi.sensor_magnet not needed
zigbee.0	2020-09-25 13:01:53.350	debug	(2647) DeviceConfigure 0x00158d000358efeb lumi.sensor_magnet not needed
zigbee.0	2020-09-25 13:01:53.348	debug	(2647) DeviceConfigure 0x000b57fffe59e779 V3-BTZB not needed
zigbee.0	2020-09-25 13:01:53.345	debug	(2647) Publish available for 0x00158d00042e3307 = true
zigbee.0	2020-09-25 13:01:53.343	debug	(2647) Publish available for 0x00158d000358efeb = true
zigbee.0	2020-09-25 13:01:53.336	debug	(2647) Publish available for 0x000b57fffe59e779 = true
zigbee.0	2020-09-25 13:01:53.333	info	(2647) Currently 3 devices are joined:
zigbee.0	2020-09-25 13:01:53.316	info	(2647) Unable to set transmit power, unsupported function.
zigbee.0	2020-09-25 13:01:53.307	info	(2647) --> transmitPower : normal
zigbee.0	2020-09-25 13:01:53.305	info	(2647) Unable to disable LED, unsupported function.
zigbee.0	2020-09-25 13:01:53.301	debug	(2647) Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":11}
zigbee.0	2020-09-25 13:01:53.117	info	(2647) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":88,"maintrel":0,"revision":"0x26580700"}}
zigbee.0	2020-09-25 13:01:53.062	debug	(2647) zigbee-herdsman started
zigbee.0	2020-09-25 13:01:52.435	debug	(2647) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2020_09_25-13_01_51.tar.gz success
zigbee.0	2020-09-25 13:01:51.910	debug	(2647) Starting zigbee-herdsman...
zigbee.0	2020-09-25 13:01:51.905	info	(2647) Starting Zigbee...
zigbee.0	2020-09-25 13:01:51.747	debug	(2647) Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databas
zigbee.0	2020-09-25 13:01:51.740	error	(2647) Serial port not selected! Go to settings page.
zigbee.0	2020-09-25 13:01:51.653	info	(2647) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6

öffnen / schließen über iobroker

zigbee.0	2020-09-25 13:11:14.755	debug	(2647) system.adapter.admin.0: logging true
zigbee.0	2020-09-25 13:11:05.310	debug	(2647) convert result {"readAfterWriteTime":200}
zigbee.0	2020-09-25 13:11:03.680	debug	(2647) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":23663,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-25 13:11:03.678	debug	(2647) convert state, lock, {}
zigbee.0	2020-09-25 13:11:03.676	debug	(2647) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":23663,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
zigbee.0	2020-09-25 13:11:03.674	debug	(2647) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
zigbee.0	2020-09-25 13:11:03.671	debug	(2647) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
zigbee.0	2020-09-25 13:11:03.645	debug	(2647) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"lock","ack":false,"ts":1601032263636,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1601032263636}
zigbee.0	2020-09-25 13:10:52.276	debug	(2647) convert result {"readAfterWriteTime":200}
zigbee.0	2020-09-25 13:10:52.035	debug	(2647) system.adapter.admin.0: logging false
zigbee.0	2020-09-25 13:10:48.088	debug	(2647) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":23663,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-25 13:10:48.085	debug	(2647) convert state, unlock, {}
zigbee.0	2020-09-25 13:10:48.084	debug	(2647) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":23663,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
zigbee.0	2020-09-25 13:10:48.079	debug	(2647) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
zigbee.0	2020-09-25 13:10:48.076	debug	(2647) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'

Wenn ich das Schloss mit der Hand öffne / schließe bleibt der LOG komplett leer ...

Löschen war jetzt kein Problem mehr - nach update
Nach neu pairing zeigt er mir wieder den Status an ...

Asgothian

@patrick039212 das sieht so aus als ob mein Hack nicht wirkt. Da muss ich noch mal schauen.

Kannst du noch einmal von github (github.com/asgothian/ioBroker.zigbee) installieren, den Adapter mit debug an neu starten und dann ein log Posten ?

Ggf. Geht es mit dem Statusupdate jetzt.

A.

patrick039212

@Asgothian
Hallo,

sry das ich erst jetzt mich Rückmelde, ich habe bis jetzt leider noch nicht die Zeit gefunden den Adapter nochmals Upzudaten, eines kann ich bis jetzt aber sagen, auch ohne das neue Update von dir (dein letzter Post) hatte ich bis heute keine weiteren Probleme mehr.
Sobald das Schloss geöffnet bzw. geschlossen wird bekomme ich über Telegramm eine Rückmeldung, somit müsste der Status theoretisch im Iobroker geändert werden, aber ich sehe mir das am Abend nochmals alles und gebe dann Bescheid.

Danke jedenfalls für deine Hilfe :)

Asgothian

@patrick039212
Hallo Patrick,

bleibt das auch so wenn du den Zigbee Adapter neu startest ? Wenn nein, dann müsstest Du bitte noch den Test machen.

A.

patrick039212

@Asgothian
werde ich heute Abend nochmal alles testen, bin leider noch in der Firma... Gebe dir aber jedenfalls Bescheid :)

patrick039212

@Asgothian

Funktioniert trotz neustart alles :)

zigbee.0	2020-09-30 14:23:39.521	debug	(1205) system.adapter.admin.0: logging true
zigbee.0	2020-09-30 14:23:37.063	debug	(1205) Publish {"state":"LOCK","lock_state":"locked"}
zigbee.0	2020-09-30 14:23:37.051	debug	(1205) Type attributeReport device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profile
zigbee.0	2020-09-30 14:23:37.047	debug	(1205) Received Zigbee message from '0x000b57fffe59e779', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID null
zigbee.0	2020-09-30 14:23:37.036	debug	(1205) handleMessage. {"type":"attributeReport","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":
zigbee.0	2020-09-30 14:23:36.543	debug	(1205) Publish {"action":"lock","action_user":65535,"action_source":1,"action_source_name":"rf"}
zigbee.0	2020-09-30 14:23:36.534	debug	(1205) Type commandOperationEventNotification device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints"
zigbee.0	2020-09-30 14:23:36.529	debug	(1205) Received Zigbee message from '0x000b57fffe59e779', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":1,"userid":65535,"pin":0,"zigbe
zigbee.0	2020-09-30 14:23:36.516	debug	(1205) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"
zigbee.0	2020-09-30 14:23:33.993	debug	(1205) convert result {"readAfterWriteTime":200}
zigbee.0	2020-09-30 14:23:29.951	debug	(1205) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":22061,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-30 14:23:29.948	debug	(1205) convert state, lock, {}
zigbee.0	2020-09-30 14:23:29.946	debug	(1205) entity: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":1
zigbee.0	2020-09-30 14:23:29.942	debug	(1205) State changes. dev: 0x000b57fffe59e779 model: V3-BTZB states: [{"stateDesc":{"id":"lockState","prop":"state","name":"Lock state","role":"state","write":true,"read":true,"type":"string"},"value
zigbee.0	2020-09-30 14:23:29.939	debug	(1205) Change state 'lockState' at device 0x000b57fffe59e779 type 'V3-BTZB'
zigbee.0	2020-09-30 14:23:29.929	debug	(1205) User stateChange zigbee.0.000b57fffe59e779.lockState {"val":"lock","ack":false,"ts":1601468609921,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1601468609921}
zigbee.0	2020-09-30 14:23:26.003	debug	(1205) Publish {"state":"UNLOCK","lock_state":"unlocked"}
zigbee.0	2020-09-30 14:23:25.994	debug	(1205) Type attributeReport device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profile
zigbee.0	2020-09-30 14:23:25.990	debug	(1205) Received Zigbee message from '0x000b57fffe59e779', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":2}' from endpoint 1 with groupID null
zigbee.0	2020-09-30 14:23:25.981	debug	(1205) handleMessage. {"type":"attributeReport","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":
zigbee.0	2020-09-30 14:23:25.573	debug	(1205) Publish {"action":"unlock","action_user":65535,"action_source":1,"action_source_name":"rf"}
zigbee.0	2020-09-30 14:23:25.528	debug	(1205) Type commandOperationEventNotification device {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints"
zigbee.0	2020-09-30 14:23:25.520	debug	(1205) Received Zigbee message from '0x000b57fffe59e779', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":2,"userid":65535,"pin":0,"zigbe
zigbee.0	2020-09-30 14:23:25.503	debug	(1205) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"
zigbee.0	2020-09-30 14:23:23.020	debug	(1205) convert result {"readAfterWriteTime":200}
zigbee.0	2020-09-30 14:23:18.021	debug	(1205) target: {"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":22061,"deviceIeeeAddress":"0x000b57fffe59e779","cluster
zigbee.0	2020-09-30 14:23:18.018	debug	(1205) convert state, unlock, {}

Community Forum

NEWS

Zigbee-Adapter 1.0.2 Danalock

Support us

392

32.4k

81.5k

1.3m