What happened?
I decided to switch to ember driver on my SLZB-06M. I flashed firmware via OTA (20240510 ). Unfortunately Zigbee2MQTT fails to start... I have checked different baud rates but without success. With ezsp driver works, but with errors.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
port: tcp://10.10.10.245:6638
baudrate: 115200
adapter: ember
rtscts: false
Zigbee2MQTT version
1.38.0-1
Adapter firmware version
7.4.1.0 build 0
Adapter
ember
Setup
Add-on on Home Assistant OS on RPI4
Debug log
[10:09:27] INFO: Preparing to start...
[10:09:28] INFO: Socat not enabled
[10:09:30] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received frame with CRC error
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-06-21 10:09:36] error: zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2024-06-21 10:09:38] warning: zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e]
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Received unexpected reset from NCP, with reason=RESET_SOFTWARE.
[2024-06-21 10:09:38] error: zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Error while parsing received frame, status=HOST_FATAL_ERROR.
[2024-06-21 10:09:38] error: zh:ember: !!! NCP FATAL ERROR reason=HOST_FATAL_ERROR. ATTEMPTING RESET... !!!
[2024-06-21 10:14:37] error: z2m:mqtt: Not connected to MQTT server!
[2024-06-21 10:14:37] error: z2m:mqtt: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
[10:14:38] INFO: Preparing to start...
[10:14:39] INFO: Socat not enabled
[10:14:41] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:14:47] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see #21462
[2024-06-21 10:14:47] error: zh:ezsp:uart: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
[2024-06-21 10:14:47] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
at Frame.checkCRC (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
at SerialDriver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
at Parser.emit (node:events:517:28)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)
at Socket.emit (node:events:517:28)'
What happened?
I decided to switch to ember driver on my SLZB-06M. I flashed firmware via OTA (20240510 ). Unfortunately Zigbee2MQTT fails to start... I have checked different baud rates but without success. With ezsp driver works, but with errors.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
port: tcp://10.10.10.245:6638
baudrate: 115200
adapter: ember
rtscts: false
Zigbee2MQTT version
1.38.0-1
Adapter firmware version
7.4.1.0 build 0
Adapter
ember
Setup
Add-on on Home Assistant OS on RPI4
Debug log
[10:09:27] INFO: Preparing to start...
[10:09:28] INFO: Socat not enabled
[10:09:30] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received frame with CRC error
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-06-21 10:09:36] error: zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2024-06-21 10:09:38] warning: zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e]
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Received unexpected reset from NCP, with reason=RESET_SOFTWARE.
[2024-06-21 10:09:38] error: zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Error while parsing received frame, status=HOST_FATAL_ERROR.
[2024-06-21 10:09:38] error: zh:ember: !!! NCP FATAL ERROR reason=HOST_FATAL_ERROR. ATTEMPTING RESET... !!!
[2024-06-21 10:14:37] error: z2m:mqtt: Not connected to MQTT server!
[2024-06-21 10:14:37] error: z2m:mqtt: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
[10:14:38] INFO: Preparing to start...
[10:14:39] INFO: Socat not enabled
[10:14:41] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:14:47] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see #21462
[2024-06-21 10:14:47] error: zh:ezsp:uart: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
[2024-06-21 10:14:47] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
at Frame.checkCRC (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
at SerialDriver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
at Parser.emit (node:events:517:28)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)
at Socket.emit (node:events:517:28)'