I had already set the log level of Zigbee2mqtt set to log_level: debug. The problem is, at the time when the stick loses its communication, there is no entry at the output of the log. Almost nothing. If i then stop the Zigbee2mqtt Docker I end up with a error like “couldn´t stop zigbb2mqtt”. This happens when the blue LED of the CC2652RB-Stick turns of and i stop the docker. see below the log:
[08:44:59] root@openhab:/opt/z2m_docker# ./normal_start.sh
Using '/app/data' as data directory
> zigbee2mqtt@1.14.2 start /app
> node index.js
zigbee2mqtt:info 2020-08-13 08:45:04: Logging to console and directory: '/app/data/log/2020-08-13.08-45-04' filename: log.txt
zigbee2mqtt:debug 2020-08-13 08:45:04: Removing old log directory '/app/data/log/2020-08-12.20-50-41'
zigbee2mqtt:debug 2020-08-13 08:45:05: Can't load state from file /app/data/state.json (doesn't exist)
zigbee2mqtt:info 2020-08-13 08:45:05: Starting zigbee2mqtt version 1.14.2 (commit #faaf3e4)
zigbee2mqtt:info 2020-08-13 08:45:05: Starting zigbee-herdsman...
zigbee2mqtt:debug 2020-08-13 08:45:05: Using zigbee-herdsman with settings: '{"network":{"panID":6757,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/app/data/database.db","databaseBackupPath":"/app/data/database.db.backup","backupPath":"/app/data/coordinator_backup.json","serialPort":{"path":"/dev/ttyUSB-CC2652RB"},"adapter":{"concurrent":null}}'
zigbee2mqtt:info 2020-08-13 08:45:16: zigbee-herdsman started
zigbee2mqtt:info 2020-08-13 08:45:16: Coordinator firmware version: '{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}'
zigbee2mqtt:debug 2020-08-13 08:45:16: Zigbee network parameters: {"panID":6757,"extendedPanID":"0xdddddddddddddddd","channel":11}
zigbee2mqtt:info 2020-08-13 08:45:16: Currently 0 devices are joined:
zigbee2mqtt:warn 2020-08-13 08:45:16: `permit_join` set to `true` in configuration.yaml.
zigbee2mqtt:warn 2020-08-13 08:45:16: Allowing new devices to join.
zigbee2mqtt:warn 2020-08-13 08:45:16: Set `permit_join` to `false` once you joined all devices.
zigbee2mqtt:info 2020-08-13 08:45:16: Zigbee: allowing new devices to join.
zigbee2mqtt:info 2020-08-13 08:45:16: Connecting to MQTT server at mqtt://192.168.1.35:1883
zigbee2mqtt:info 2020-08-13 08:45:16: Connected to MQTT server
zigbee2mqtt:info 2020-08-13 08:45:16: MQTT publish: topic 'zigbee2mqtt_test/bridge/state', payload 'online'
zigbee2mqtt:info 2020-08-13 08:45:16: MQTT publish: topic 'zigbee2mqtt_test/bridge/config', payload '{"version":"1.14.2","commit":"faaf3e4","coordinator":{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}},"log_level":"debug","permit_join":true}'
^Czigbee2mqtt:debug 2020-08-13 08:45:47: Saving state to file /app/data/state.json
zigbee2mqtt:info 2020-08-13 08:45:47: MQTT publish: topic 'zigbee2mqtt_test/bridge/state', payload 'offline'
zigbee2mqtt:info 2020-08-13 08:45:47: Disconnecting from MQTT server
zigbee2mqtt:error 2020-08-13 08:45:53: Failed to stop zigbee
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.14.2 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.14.2 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-08-13T06_45_53_294Z-debug.log
[08:45:53] root@openhab:/opt/z2m_docker#
The Blue LED turns off (stick gets reset) at about 08:45:20 - 08:45:25. The Last Log-entry before this happens is:
MQTT publish: topic 'zigbee2mqtt_test/bridge/config', payload '{"version":"1.14.2","commit":"faaf3e4","coordinator":{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}},"log_level":"debug","permit_join":true}'
when the problem comes up, no additional logging is seen. When the blue LED was off, i stoppt the docker-container (at 08:45:47) and got an error (see above).
The behaviour of the Stick, if i stop the Container just before the blue LED turns of is seen in the log below:
> zigbee2mqtt@1.14.2 start /app
> node index.js
zigbee2mqtt:info 2020-08-13 08:56:12: Logging to console and directory: '/app/data/log/2020-08-13.08-56-12' filename: log.txt
zigbee2mqtt:debug 2020-08-13 08:56:12: Removing old log directory '/app/data/log/2020-08-12.21-05-26'
zigbee2mqtt:debug 2020-08-13 08:56:13: Loaded state from file /app/data/state.json
zigbee2mqtt:info 2020-08-13 08:56:13: Starting zigbee2mqtt version 1.14.2 (commit #faaf3e4)
zigbee2mqtt:info 2020-08-13 08:56:13: Starting zigbee-herdsman...
zigbee2mqtt:debug 2020-08-13 08:56:13: Using zigbee-herdsman with settings: '{"network":{"panID":6757,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/app/data/database.db","databaseBackupPath":"/app/data/database.db.backup","backupPath":"/app/data/coordinator_backup.json","serialPort":{"path":"/dev/ttyUSB-CC2652RB"},"adapter":{"concurrent":null}}'
zigbee2mqtt:info 2020-08-13 08:56:23: zigbee-herdsman started
zigbee2mqtt:info 2020-08-13 08:56:23: Coordinator firmware version: '{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}'
zigbee2mqtt:debug 2020-08-13 08:56:23: Zigbee network parameters: {"panID":6757,"extendedPanID":"0xdddddddddddddddd","channel":11}
zigbee2mqtt:info 2020-08-13 08:56:23: Currently 0 devices are joined:
zigbee2mqtt:warn 2020-08-13 08:56:23: `permit_join` set to `true` in configuration.yaml.
zigbee2mqtt:warn 2020-08-13 08:56:23: Allowing new devices to join.
zigbee2mqtt:warn 2020-08-13 08:56:23: Set `permit_join` to `false` once you joined all devices.
zigbee2mqtt:info 2020-08-13 08:56:23: Zigbee: allowing new devices to join.
zigbee2mqtt:info 2020-08-13 08:56:23: Connecting to MQTT server at mqtt://192.168.1.35:1883
zigbee2mqtt:info 2020-08-13 08:56:23: Connected to MQTT server
zigbee2mqtt:info 2020-08-13 08:56:23: MQTT publish: topic 'zigbee2mqtt_test/bridge/state', payload 'online'
zigbee2mqtt:info 2020-08-13 08:56:23: MQTT publish: topic 'zigbee2mqtt_test/bridge/config', payload '{"version":"1.14.2","commit":"faaf3e4","coordinator":{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}},"log_level":"debug","permit_join":true}'
^Czigbee2mqtt:debug 2020-08-13 08:56:26: Saving state to file /app/data/state.json
zigbee2mqtt:info 2020-08-13 08:56:26: MQTT publish: topic 'zigbee2mqtt_test/bridge/state', payload 'offline'
zigbee2mqtt:info 2020-08-13 08:56:26: Disconnecting from MQTT server
zigbee2mqtt:info 2020-08-13 08:56:26: zigbee-herdsman stopped
[08:56:27] root@openhab:/opt/z2m_docker#
There is no error to be seen, as the stick doesn´t gets a reset.
Here is my “configuration.yaml” for the z2m in docker (CC2652RB):
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt_test
server: 'mqtt://192.168.1.35:1883'
user: openhabian
password: '**********'
serial:
port: /dev/ttyUSB-CC2652RB
advanced:
network_key:
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
- *
pan_id: 6757
log_level: debug
And for comparison from bare-metal z2m (CC2531):
homeassistant: false
permit_join: false
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://192.168.1.35:1883'
user: openhabian
password: '************'
include_device_information: false
serial:
port: /dev/ttyACM-CC2531
disable_led: true
devices: devices.yaml
advanced:
channel: 25
network_key: [*, *, *, *, *, *, *, *, *, *, *, *, *, *, *, *]
pan_id: 0x1a66
#availability_timeout: 60
#availability_whitelist: ['LA_WZ_r','LA_WZ_l']
and hope to find that here.
