Danalock V3 issues after update to 1.8.0

[004helix]

I suspended update my installation from 1.6.0 to 1.7.1 due to bug https://github.com/Koenkk/zigbee2mqtt/issues/2339

However, I updated to 1.8.0 2 days ago. My Danalock worked fine for a day, but suddenly stopped to report it's status. There was some restarts of zigbee2mqtt container yesterday. Coordinator was unavaibale for hour or so during these restarts. Now I see in logs that zigbee2mqtt didn't configure Danalock on start.

First start after update from 1.6.0 to 1.8.0:

> zigbee2mqtt@1.8.0 start /app
> node index.js

zigbee2mqtt:info  2019-12-15 21:34:13: Logging to console and directory: '/app/data/log/2019-12-15.21-34-13'
zigbee2mqtt:info  2019-12-15 21:34:13: Starting zigbee2mqtt version 1.8.0 (commit #da4d26a)
zigbee2mqtt:info  2019-12-15 21:34:13: Starting zigbee-herdsman...
zigbee2mqtt:info  2019-12-15 21:34:15: zigbee-herdsman started
zigbee2mqtt:info  2019-12-15 21:34:15: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190425}}'
zigbee2mqtt:info  2019-12-15 21:34:15: Currently 3 devices are joined:
zigbee2mqtt:info  2019-12-15 21:34:15: door_lock (...): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
zigbee2mqtt:info  2019-12-15 21:34:15: door_contact (...): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee2mqtt:info  2019-12-15 21:34:15: kitchen_water_leak (...): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
zigbee2mqtt:info  2019-12-15 21:34:15: Zigbee: disabling joining new devices.
zigbee2mqtt:info  2019-12-15 21:34:15: Connecting to MQTT server at mqtt://mosquitto
zigbee2mqtt:info  2019-12-15 21:34:15: Configuring 'door_lock'
zigbee2mqtt:info  2019-12-15 21:34:15: Connected to MQTT server
zigbee2mqtt:info  2019-12-15 21:34:15: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info  2019-12-15 21:34:15: MQTT publish: topic 'zigbee2mqtt/door_lock', payload '{"state":"LOCK","linkquality":73,"battery":100,"battery_low":false,"user":65535,"source":1}'
zigbee2mqtt:info  2019-12-15 21:34:15: MQTT publish: topic 'zigbee2mqtt/door_contact', payload '{"contact":true,"linkquality":102,"battery":100,"voltage":3335}'
zigbee2mqtt:info  2019-12-15 21:34:15: MQTT publish: topic 'zigbee2mqtt/kitchen_water_leak', payload '{"battery":100,"voltage":3035,"linkquality":10,"water_leak":false}'
zigbee2mqtt:info  2019-12-15 21:34:15: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.8.0","commit":"da4d26a","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190425}},"log_level":"info","permit_join":false}'
zigbee2mqtt:info  2019-12-15 21:34:21: Succesfully configured 'door_lock'

After restart:

Using '/app/data' as data directory

> zigbee2mqtt@1.8.0 start /app
> node index.js

zigbee2mqtt:info  2019-12-17 20:51:11: Logging to console and directory: '/app/data/log/2019-12-17.20-51-10'
zigbee2mqtt:info  2019-12-17 20:51:11: Starting zigbee2mqtt version 1.8.0 (commit #da4d26a)
zigbee2mqtt:info  2019-12-17 20:51:11: Starting zigbee-herdsman...
zigbee2mqtt:info  2019-12-17 20:51:12: zigbee-herdsman started
zigbee2mqtt:info  2019-12-17 20:51:12: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190425}}'
zigbee2mqtt:info  2019-12-17 20:51:12: Currently 3 devices are joined:
zigbee2mqtt:info  2019-12-17 20:51:12: door_lock (...): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
zigbee2mqtt:info  2019-12-17 20:51:12: door_contact (...): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee2mqtt:info  2019-12-17 20:51:12: kitchen_water_leak (...): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
zigbee2mqtt:info  2019-12-17 20:51:12: Zigbee: disabling joining new devices.
zigbee2mqtt:info  2019-12-17 20:51:12: Connecting to MQTT server at mqtt://mosquitto
zigbee2mqtt:info  2019-12-17 20:51:12: Connected to MQTT server
zigbee2mqtt:info  2019-12-17 20:51:12: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info  2019-12-17 20:51:12: MQTT publish: topic 'zigbee2mqtt/door_lock', payload '{"state":"LOCK","linkquality":94,"battery":100,"battery_low":false,"user":65535,"source":1}'
zigbee2mqtt:info  2019-12-17 20:51:12: MQTT publish: topic 'zigbee2mqtt/door_contact', payload '{"contact":true,"linkquality":107,"battery":100,"voltage":3325}'
zigbee2mqtt:info  2019-12-17 20:51:12: MQTT publish: topic 'zigbee2mqtt/kitchen_water_leak', payload '{"battery":100,"voltage":3035,"linkquality":0,"water_leak":false}'
zigbee2mqtt:info  2019-12-17 20:51:12: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.8.0","commit":"da4d26a","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190425}},"log_level":"info","permit_join":false}'

I stopped container, restored database.db from 1.6.0 backup and started again. Danalock started to report it's status again. I think it's a bad idea to restore database every start

Is there any option to force to configure devices every start?

[Koenkk]

Does it work again when forcing a configure? https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.