Outsidewall
commented
6 months ago Hello, Have you tried updating the dongle's firmware to 7.4.2, I had many errors with 7.4.1 the uplift fixed them.
Closed fred-gb closed 6 months ago
Outsidewall
commented
6 months ago Hello, Have you tried updating the dongle's firmware to 7.4.2, I had many errors with 7.4.1 the uplift fixed them.
fred-gb
commented
6 months ago π
With latest-devsame errors
error 2024-04-26 17:59:27Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":251} messageTag=255]
warning 2024-04-26 17:59:29Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".and docker logs
[2024-04-26 19:00:07] debug: zh:ember:ezsp: ezspIncomingNetworkStatusHandler(): callback called with: [errorCode=ROUTE_ERROR_ADDRESS_CONFLICT], [target=0]
[2024-04-26 19:00:07] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=0] Added to rxQueue
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=1]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: <=== [FRAME: ID=196:"INCOMING_NETWORK_STATUS_HANDLER" Seq=51 Len=8]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: ezspIncomingNetworkStatusHandler(): callback called with: [errorCode=ROUTE_ERROR_ADDRESS_CONFLICT], [target=0]
[2024-04-26 19:00:07] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=1] Added to rxQueue
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=2]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: <=== [FRAME: ID=196:"INCOMING_NETWORK_STATUS_HANDLER" Seq=51 Len=8]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: ezspIncomingNetworkStatusHandler(): callback called with: [errorCode=ROUTE_ERROR_ADDRESS_CONFLICT], [target=0]
[2024-04-26 19:00:07] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=2] Added to rxQueue
[2024-04-26 19:00:07] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=3]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: <=== [FRAME: ID=196:"INCOMING_NETWORK_STATUS_HANDLER" Seq=51 Len=8]
[2024-04-26 19:00:07] debug: zh:ember:ezsp: ezspIncomingNetworkStatusHandler(): callback called with: [errorCode=ROUTE_ERROR_ADDRESS_CONFLICT], [target=0]
[2024-04-26 19:00:07] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
[2024-04-26 19:00:10] debug: z2m: Saving state to file /app/data/state.json
[2024-04-26 19:00:12] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-04-26 19:00:12] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-04-26 19:00:12] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=3] Added to rxQueue
[2024-04-26 19:00:12] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=4]
[2024-04-26 19:00:12] debug: zh:ember:ezsp: <=== [FRAME: ID=69:"INCOMING_MESSAGE_HANDLER" Seq=51 Len=40]
[2024-04-26 19:00:12] debug: zh:ember:ezsp: ezspIncomingMessageHandler(): callback called with: [type=UNICAST], [apsFrame={"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":256,"groupId":0,"sequence":222}], [lastHopLqi=76], [lastHopRssi=175], [sender=4754], [bindingIndex=255], [addressIndex=255], [messageContents=081b0a01002045e2ff201fe4ff2000]
[2024-04-26 19:00:12] debug: zh:controller: Data is from unknown device with address '4754', skipping...
[2024-04-26 19:00:18] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-04-26 19:00:18] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-04-26 19:00:18] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=4] Added to rxQueue
[2024-04-26 19:00:18] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=5]
[2024-04-26 19:00:18] debug: zh:ember:ezsp: <=== [FRAME: ID=69:"INCOMING_MESSAGE_HANDLER" Seq=51 Len=39]
[2024-04-26 19:00:18] debug: zh:ember:ezsp: ezspIncomingMessageHandler(): callback called with: [type=UNICAST], [apsFrame={"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":256,"groupId":0,"sequence":197}], [lastHopLqi=52], [lastHopRssi=169], [sender=22388], [bindingIndex=255], [addressIndex=255], [messageContents=08120a010020c0e2ff2036e4ff2000]
[2024-04-26 19:00:18] debug: zh:controller: Data is from unknown device with address '22388', skipping...π
fred-gb
commented
6 months ago I tried today on my "production" site to switch with dongle with 7.4.2 firmware and the latest-dev docker images.
And I have lot of errors, I can't use devices on battery.
When I try to open network to new device:
error 2024-04-27 09:02:42[ZDO] Failed permit joining request with status=NETWORK_BUSY.
error 2024-04-27 09:02:42~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY.And conflict errors.
I have 55 devices on my network.
Unusable... π
Outsidewall
commented
6 months ago @fred-gb You might have some sort of network storm going on, I wonder if removing the devices from power/unpluging them, restart the docker container, and carefully put them back one at a time, maybe one of them is causing the issue.
Nerivec
commented
6 months ago Since address 0 is the reserved address for the coordinator (adapter), seems something is very wrong/strange. Having two of these would definitely create all sorts of issues.
Can you check Z2M frontend and give me the list of addresses you see in "IEEE Address" column (both)? Also try getting some debug level logs from a cold start of Z2M (set to debug level before you start/restart) and running for about 15minutes after that. If you are using latest release (1.37), logs are all in one place, you just need to set the level to debug.
fred-gb
commented
6 months ago Thanks @Nerivec
I restart one dev plateform.
This is a docker-compose:
version: '3.8'
services:
zigbee2mqtt:
container_name: zigbee2mqtt
image: koenkk/zigbee2mqtt:1.37.0
# image: koenkk/zigbee2mqtt:latest-dev
restart: unless-stopped
volumes:
- ./z2m:/app/data
- /run/udev:/run/udev:ro
ports:
# Frontend port
- 8080:8080
environment:
- TZ=Europe/Paris
devices:
# Make sure this matched your adapter location
- /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240219194401-if00:/dev/ttyACM0
mosquitto:
image: eclipse-mosquitto
hostname: mosquitto
container_name: mosquitto
restart: unless-stopped
ports:
- "1883:1883"
- "9001:9001"
volumes:
- ./mosquitto:/etc/mosquitto
- ./mosquitto/mosquitto.conf:/mosquitto/config/mosquitto.confZ2M configuration:
homeassistant: false
availability: true
advanced:
log_level: debug
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
permit_join: false
frontend:
port: 8080
host: 0.0.0.0
auth_token: zigbee2mqtt
url: http://192.168.10.116:8080
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.10.116
user: admin
password: admin
serial:
port: /dev/ttyACM0
adapter: ember
device_options:
legacy: false
devices:
'0xa49e69fffe051947':
friendly_name: '0xa49e69fffe051947'My Z2M frontend:
So. With all this new dev install I try to pair a new module: TO-Q-SY2-163JZT
Pairing works, but after, commands do not work.
This logs after somes minutes:
info 2024-05-02 16:12:08Zigbee: disabling joining new devices.
info 2024-05-02 16:12:08[STACK STATUS] Network closed.
error 2024-05-02 16:12:09Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":79} messageTag=5]
error 2024-05-02 16:12:09Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":78} messageTag=255]
info 2024-05-02 16:12:12Zigbee: allowing new devices to join.
info 2024-05-02 16:12:12[STACK STATUS] Network opened.
error 2024-05-02 16:12:13Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":80} messageTag=255]
error 2024-05-02 16:12:13Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":81} messageTag=6]
info 2024-05-02 16:12:48Interview for '0xa49e69fffe051947' started
info 2024-05-02 16:12:48Device '0xa49e69fffe051947' joined
info 2024-05-02 16:12:48Starting interview of '0xa49e69fffe051947'
warning 2024-05-02 16:13:15[ZDO] Node descriptor for "19448" reports device is only compliant to revision "22" of the ZigBee specification (current revision: 23).
warning 2024-05-02 16:13:16Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
info 2024-05-02 16:13:17Succesfully interviewed '0xa49e69fffe051947'
info 2024-05-02 16:13:17Successfully interviewed '0xa49e69fffe051947', device has successfully been paired
info 2024-05-02 16:13:17Device '0xa49e69fffe051947' is supported, identified as: TONGOU Smart circuit breaker (TO-Q-SY2-163JZT)
info 2024-05-02 16:13:17Configuring '0xa49e69fffe051947'
warning 2024-05-02 16:13:17Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 16:13:22Failed to configure '0xa49e69fffe051947', attempt 1 (Error: Bind 0xa49e69fffe051947/1 msTemperatureMeasurement from '0xe8e07efffeefa989/1' failed (Delivery failed for {"profileId":0,"clusterId":33,"sourceEndpoint":0,"destinationEndpoint":0,"options":4416,"groupId":0,"sequence":111}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
info 2024-05-02 16:13:25Configuring '0xa49e69fffe051947'
error 2024-05-02 16:13:29Failed to configure '0xa49e69fffe051947', attempt 2 (Error: ZCL command 0xa49e69fffe051947/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":115}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
info 2024-05-02 16:13:35Configuring '0xa49e69fffe051947'
error 2024-05-02 16:13:40Failed to configure '0xa49e69fffe051947', attempt 3 (Error: ZCL command 0xa49e69fffe051947/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":119}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
error 2024-05-02 16:14:04Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":124})'
error 2024-05-02 16:14:09Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":125})'
error 2024-05-02 16:15:33Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":128} messageTag=17]
error 2024-05-02 16:15:33Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":129} messageTag=33]
info 2024-05-02 16:16:26[STACK STATUS] Network closed.
error 2024-05-02 16:16:27Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":130} messageTag=34]
error 2024-05-02 16:16:27Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":131} messageTag=18]
error 2024-05-02 16:35:01Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":151})'
error 2024-05-02 16:35:07Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":152})'
error 2024-05-02 16:41:02Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":159})'
error 2024-05-02 16:41:11Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":160})'
error 2024-05-02 16:42:02Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":170})'
error 2024-05-02 16:42:07Publish 'set' 'state' to '0xa49e69fffe051947' failed: 'Error: ZCL command 0xa49e69fffe051947/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":171})'
info 2024-05-02 16:42:29Configuring '0xa49e69fffe051947'
error 2024-05-02 16:42:34Failed to configure '0xa49e69fffe051947', attempt 4 (Error: ZCL command 0xa49e69fffe051947/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":176}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))The reconfiguration button does not work.
I try to apparing another device, a PIR313-E.
I'm unable to add to network. Interview failed. And make a loop:
info 2024-05-02 17:17:02Interview for '0x3c6a2cfffed22b98' started
info 2024-05-02 17:17:02Starting interview of '0x3c6a2cfffed22b98'
info 2024-05-02 17:17:18Removing device '0x3c6a2cfffed22b98' (block: false, force: true)
info 2024-05-02 17:17:18Successfully removed device '0x3c6a2cfffed22b98' (block: false, force: true)
info 2024-05-02 17:17:27Interview for '0x3c6a2cfffed22b98' started
info 2024-05-02 17:17:27Device '0x3c6a2cfffed22b98' joined
info 2024-05-02 17:17:27Starting interview of '0x3c6a2cfffed22b98'
info 2024-05-02 17:17:27Zigbee: allowing new devices to join.
error 2024-05-02 17:17:32Interview failed for '0x3c6a2cfffed22b98 with error 'Error: Interview failed because can not get active endpoints ('0x3c6a2cfffed22b98')'
error 2024-05-02 17:17:32Failed to interview '0x3c6a2cfffed22b98', device has not successfully been paired
info 2024-05-02 17:17:39Interview for '0x3c6a2cfffed22b98' started
info 2024-05-02 17:17:39Starting interview of '0x3c6a2cfffed22b98'
info 2024-05-02 17:17:47[STACK STATUS] Network opened.
error 2024-05-02 17:17:48Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":88} messageTag=30]
warning 2024-05-02 17:17:53Device '0x3c6a2cfffed22b98' left the network
error 2024-05-02 17:18:18Interview failed for '0x3c6a2cfffed22b98 with error 'Error: DatabaseEntry with ID '3' does not exist'
error 2024-05-02 17:18:18Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":91} messageTag=37]
error 2024-05-02 17:18:33Interview failed for '0x3c6a2cfffed22b98 with error 'Error: DatabaseEntry with ID '3' does not exist'
info 2024-05-02 17:19:35Interview for '0x3c6a2cfffed22b98' started
info 2024-05-02 17:19:35Device '0x3c6a2cfffed22b98' joined
info 2024-05-02 17:19:35Starting interview of '0x3c6a2cfffed22b98'
error 2024-05-02 17:20:05Interview failed for '0x3c6a2cfffed22b98 with error 'Error: Interview failed because can not get active endpoints ('0x3c6a2cfffed22b98')'
error 2024-05-02 17:20:05Failed to interview '0x3c6a2cfffed22b98', device has not successfully been pairedCHANGE! While I write this post, I success pair the two devices, with this logs:
error 2024-05-02 17:25:21Interview failed for '0xa49e69fffe051947 with error 'Error: Delivery failed for {"profileId":0,"clusterId":4,"sourceEndpoint":0,"destinationEndpoint":0,"options":4160,"groupId":0,"sequence":162}'
error 2024-05-02 17:25:21Failed to interview '0xa49e69fffe051947', device has not successfully been paired
info 2024-05-02 17:25:26Interview for '0xa49e69fffe051947' started
info 2024-05-02 17:25:26Starting interview of '0xa49e69fffe051947'
error 2024-05-02 17:25:42Interview failed for '0xa49e69fffe051947 with error 'Error: Interview failed because can not get active endpoints ('0xa49e69fffe051947')'
error 2024-05-02 17:25:42Failed to interview '0xa49e69fffe051947', device has not successfully been paired
info 2024-05-02 17:25:47Succesfully interviewed '0x3c6a2cfffed22b98'
info 2024-05-02 17:25:47Successfully interviewed '0x3c6a2cfffed22b98', device has successfully been paired
info 2024-05-02 17:25:47Device '0x3c6a2cfffed22b98' is supported, identified as: OWON Motion sensor (PIR313-E)
info 2024-05-02 17:25:47Configuring '0x3c6a2cfffed22b98'
warning 2024-05-02 17:25:47Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
info 2024-05-02 17:25:50Successfully configured '0x3c6a2cfffed22b98'
info 2024-05-02 17:26:19Configuring '0xa49e69fffe051947'
error 2024-05-02 17:26:24Failed to configure '0xa49e69fffe051947', attempt 5 (Error: ZCL command 0xa49e69fffe051947/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":192}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
info 2024-05-02 17:27:12Configuring '0xa49e69fffe051947'
error 2024-05-02 17:27:16Failed to configure '0xa49e69fffe051947', attempt 6 (Error: ZCL command 0xa49e69fffe051947/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Delivery failed for {"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4160,"groupId":0,"sequence":193}) at EmberOneWaitress.deliveryFailedFor (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:96:31) at EmberAdapter.onMessageSentDeliveryFailed (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:558:30) at Ezsp.emit (node:events:517:28) at Ezsp.ezspMessageSentHandler (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:3957:18) at Ezsp.callbackDispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:794:18) at Ezsp.tick (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:448:22) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
warning 2024-05-02 17:27:27Device '0xa49e69fffe051947' left the network
error 2024-05-02 17:27:31~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY.
error 2024-05-02 17:27:33Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":254} messageTag=255]
error 2024-05-02 17:27:34Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":199} messageTag=91]
error 2024-05-02 17:27:38Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":205} messageTag=255]
info 2024-05-02 17:28:02Interview for '0xa49e69fffe051947' started
info 2024-05-02 17:28:02Device '0xa49e69fffe051947' joined
info 2024-05-02 17:28:02Starting interview of '0xa49e69fffe051947'
warning 2024-05-02 17:28:17Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
info 2024-05-02 17:28:19Succesfully interviewed '0xa49e69fffe051947'
info 2024-05-02 17:28:19Successfully interviewed '0xa49e69fffe051947', device has successfully been paired
info 2024-05-02 17:28:19Device '0xa49e69fffe051947' is supported, identified as: TONGOU Smart circuit breaker (TO-Q-SY2-163JZT)
warning 2024-05-02 17:28:19Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 17:28:25~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY.
info 2024-05-02 17:28:32[STACK STATUS] Network closed.
error 2024-05-02 17:28:33Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":41440,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"options":256,"groupId":0,"sequence":234} messageTag=117]
error 2024-05-02 17:28:33Delivery of BROADCAST failed for "65532" [apsFrame={"profileId":0,"clusterId":54,"sourceEndpoint":0,"destinationEndpoint":0,"options":256,"groupId":0,"sequence":236} messageTag=58]And come back from hell, the loop in error!
warning 2024-05-02 17:33:49Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 17:33:56Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":38} messageTag=255]
error 2024-05-02 17:33:56Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":48} messageTag=255]
warning 2024-05-02 17:34:03Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
warning 2024-05-02 17:34:17Received network/route error ROUTE_ERROR_MANY_TO_ONE_ROUTE_FAILURE for "12040".
warning 2024-05-02 17:34:17Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 17:35:31Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":219} messageTag=255]
error 2024-05-02 17:35:31Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":221} messageTag=255]
error 2024-05-02 17:35:31Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":217} messageTag=255]
warning 2024-05-02 17:35:48Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 17:35:56Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":253} messageTag=255]
error 2024-05-02 17:36:01Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":3} messageTag=255]
error 2024-05-02 17:36:06Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":129} messageTag=255]
error 2024-05-02 17:36:06Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":7} messageTag=255]
error 2024-05-02 17:36:11Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":93} messageTag=255]
error 2024-05-02 17:36:16Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":21} messageTag=255]
warning 2024-05-02 17:36:18Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
error 2024-05-02 17:36:21Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":182} messageTag=255]
error 2024-05-02 17:36:21Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":97} messageTag=255]
error 2024-05-02 17:36:46Delivery of BROADCAST failed for "65533" [apsFrame={"profileId":0,"clusterId":0,"sourceEndpoint":0,"destinationEndpoint":0,"options":1024,"groupId":0,"sequence":142} messageTag=255]
warning 2024-05-02 17:36:48Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".Thanks if you can help me!
Nerivec
commented
6 months ago This is likely all linked to the 0 conflict. You will have to figure out which device is causing this strange behavior. I'm guessing the rest of your troubles will disappear after that.
I see you mentioned a "backup" adapter. If you have two adapters with the exact same network configuration, running at the same time, around the same location, that will definitely create issues. Unplug one when you run the other. Similarly, if you have two adapters made to run on the same network configuration, but they have different IEEE address, that can create issues if you swap back and forth.
If the above doesn't fix it, can you post the log file it created when you ran that last test?
Last resort, like @Outsidewall said, you may have to remove all devices and add them back one by one, until you find the culprit. I see you have a lixee device, try that one first; the zlinky_tic has caused plenty of troubles in the past.
Did you use the firmware from darkxst? If not, try that one ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl I have yet to have time to test 7.4.2, though the changelog from silabs seems minimal. Still, you could try 7.4.1 instead if nothing else seems to work.
lettore
commented
6 months ago I have the same problem with EMBER driver, I thought something happened to my board while switching to 7.4.2 firmware but returning back to EZSP adapter mode in 1.37.0 version fixed all errors.
I got the same Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0". error and plus a [ZDO clusterId=32799 sender=37662] Support not implemented upstream.
In the meanwhile IKEA remote stopped working, but from the dashboard I was able to turn on or off devices.
I also had some CRC errors at the start of the container, something I never seen before.
LDprg
commented
6 months ago Having same issue with the ember driver. I am using 7.4.2 firmware on and dongle-e. But only with Smoke detectors from Develco.
error: z2m: Failed to interview '0x0015bc003101c7e8', device has not successfully been paired
error: zh:controller: Interview failed for '0x0015bc003101c7e8 with error 'Error: Interview failed because can not get active endpoints ('0x0015bc003101c7e8')'
phenix1990
commented
6 months ago Same here. I have a docker installation on a Pi5 with Sonof zigbee dongle-e.
I moved all files and devices from my previous pi4 and other zigbee stick to the new setup. Z2m is on version 1.37.0 Sonof firmware was first 7.4.1, same issues on 7.4.2 Moved same time from ezsp to ember
short time after booting i get 5 times per second:
warning zh:ember:ezsp: Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".
After a hour or two the network is dead with error
error: zh:ember:uart:ash: Received ERROR from NCP, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT. error: zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR error: zh:ember:ezsp: [SEND COMMAND] Cannot send second one before processing response from first one.
Then i have to restart the container two make it work for another period.
Nerivec
commented
6 months ago @LDprg That's likely a battery-powered device that needs to wake up before it can configure properly. Try pushing a button on it before doing the configure. (You may need to push the button at 2-3 seconds intervals until it's done to keep it awake.)
Can someone with the Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0". issue provide a full debug-level log from z2m start to after that error starts occurring?
PS: Also, anyone not using a firmware from darkxst, please switch to it (Sonoff Dongle E 7.4.1). There has been issues with some others. https://github.com/Koenkk/zigbee2mqtt/discussions/21462#discussioncomment-8536401
phenix1990
commented
6 months ago So i went back to ember driver with firmware 7.4.1 and debug level.
I dont know why but z2m crashed also with ezsp this evening with 7.4.2.
@Nerivec here are the loggings from container restart. Sorry for the long list, can I make this code fence scrollable in vertical?
lettore
commented
6 months ago @LDprg That's likely a battery-powered device that needs to wake up before it can configure properly. Try pushing a button on it before doing the configure. (You may need to push the button at 2-3 seconds intervals until it's done to keep it awake.)
Can someone with the
Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0".issue provide a fulldebug-level log from z2m start to after that error starts occurring?PS: Also, anyone not using a firmware from darkxst, please switch to it (Sonoff Dongle E 7.4.1). There has been issues with some others. #21462 (reply in thread)
Mine is not battery powered and without any changes works fine with EZSP, just when turning to EMBER driver after initialization it reports Received network/route error ROUTE_ERROR_ADDRESS_CONFLICT for "0". more time per second, it doesn't receive remote commands , and the same as @phenix1990 after some minutes it hangs up as the board is not responding anymore. In fact to have it working again I have to remove it from USB port and replug. The only problem I have with 1.37.0 with EZSP and Sonoff Dongle E 7.4.2 is that when I start pairing it throws another error, ERROR : Received undefined command from '0'. This don't affect anything, pairing works as expected. I think ember driver is not mature enough for production.
Nerivec
commented
6 months ago @phenix1990 You should be able to upload the file directly next time with Attach files π
Can you please check with ezsp, if you see the same messages in the logs? In ember this is a warning, but in ezsp, it is a debug so you would not see it unless you are looking for it in the logs directly (you will need log level set to debug of course).
Look for lines that say
handleNetworkStatus: nwk="0", errorCode="13"which is the equivalent of the ones you are receiving with ember.
phenix1990
commented
6 months ago @Nerivec yep, found this error with ezsp
handleNetworkStatus: nwk=0, errorCode=13so its not related to ember? I also updated z2m from 1.32.2 to 1.37 due to some interesting changes. As mentioned other change was switching from Slaesh's CC2652RB stick to sonof dongle-e. And pi4 to pi5.
A lot of changes but i was optimistic. Now its dark and i cant control some lights from time to time. Good my wife already sleeping today :innocent:
Nerivec
commented
6 months ago When you switched from zstack to ezsp/ember, you re-paired everything, correct? Just making sure that by some weird coincidence you didn't manage to start ezsp/ember with a zstack-based network... π
You may have to re-pair devices one by one, until you start seeing the error again (make sure to run the network with zero devices for a few minutes first, just in case the error appears right away for some reason...). You don't have many, so it should be pretty quick. Easiest way to get a "clean slate" (remove all devices and ensure the creation of a new network), is to use GENERATE for network settings (also pick a good channel while you're at it, see docs)
Basically something like this:
advanced:
channel: 20
network_key: GENERATE
pan_id: GENERATE
ext_pan_id: GENERATEInfact i didnt re-paired all devices because it seem to work for some people without.
For most of my devices re-pairing is no problem, just 3 hard wired ones will be a bit painfull to process. But then i have a task for the rest of the weekend. Thanks for the help so far!
Update: just 3 devices later i have repeating the same error.
[2024-05-04 23:17:38] debug: z2m: MQTT publish: topic 'zigbee2mqtt/AirQualityTester', payload '{"co2":381,"device":{"applicationVersion":70,"dateCode":"","friendlyName":"AirQualityTester","hardwareVersion":1,"ieeeAddr":"0xa4c13874fb41ee57","manufacturerID":4417,"manufacturerName":"_TZE200_dwcarsat","model":"TS0601_smart_air_house_keeper","networkAddress":18694,"powerSource":"Mains (single phase)","stackVersion":0,"type":"Router","zclVersion":3},"formaldehyd":7,"humidity":57.5,"last_seen":"2024-05-04T23:17:23+02:00","linkquality":144,"pm25":3,"temperature":20.1,"voc":34}'
[2024-05-04 23:17:38] debug: z2m: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/rename', payload '{"data":{"from":"0xa4c13874fb41ee57","homeassistant_rename":false,"to":"AirQualityTester"},"status":"ok","transaction":"6sr6u-3"}'
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4 frmNum=1] Added to rxQueue
...
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=DATA]
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=4]
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: <--- [FRAME type=ERROR]
[2024-05-04 23:17:38] error: zh:ember:uart:ash: Received ERROR from NCP, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-05-04 23:17:38] error: zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: Error while parsing received frame in NOT_CONNECTED state (flags=0), status=ASH_NCP_FATAL_ERROR.
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=6]
[2024-05-04 23:17:38] debug: zh:ember:ezsp: <=== [FRAME: ID=69:"INCOMING_MESSAGE_HANDLER" Seq=115 Len=38]
[2024-05-04 23:17:38] debug: zh:ember:ezsp: ezspIncomingMessageHandler(): callback called with: [type=UNICAST], [apsFrame={"profileId":260,"clusterId":61184,"sourceEndpoint":1,"destinationEndpoint":1,"options":256,"groupId":0,"sequence":97}], [lastHopLqi=144], [lastHopRssi=192], [sender=18694], [bindingIndex=255], [addressIndex=255], [messageContents=099a02000012020004000000cb]
[2024-05-04 23:17:38] debug: zh:controller: Received payload: clusterID=61184, address=18694, groupID=0, endpoint=1, destinationEndpoint=1, wasBroadcast=false, linkQuality=144, frame={"header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"manufacturerCode":null,"transactionSequenceNumber":154,"commandIdentifier":2},"payload":{"seq":0,"dpValues":[{"dp":18,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,203]}}]},"command":{"ID":2,"parameters":[{"name":"seq","type":33},{"name":"dpValues","type":1011}],"name":"dataReport"}}
[2024-05-04 23:17:38] debug: zh:controller:endpoint: ZCL command 0xa4c13874fb41ee57/1 manuSpecificTuya.defaultRsp({"cmdId":2,"statusCode":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":154,"writeUndiv":false})
[2024-05-04 23:17:38] debug: zh:ember:queue: Status queue=0 priorityQueue=0.
[2024-05-04 23:17:38] debug: z2m: Received Zigbee message from 'AirQualityTester', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,203],"type":"Buffer"},"datatype":2,"dp":18}],"seq":0}' from endpoint 1 with groupID 0
[2024-05-04 23:17:38] debug: z2m: MQTT publish: topic 'zigbee2mqtt/AirQualityTester', payload '{"co2":381,"device":{"applicationVersion":70,"dateCode":"","friendlyName":"AirQualityTester","hardwareVersion":1,"ieeeAddr":"0xa4c13874fb41ee57","manufacturerID":4417,"manufacturerName":"_TZE200_dwcarsat","model":"TS0601_smart_air_house_keeper","networkAddress":18694,"powerSource":"Mains (single phase)","stackVersion":0,"type":"Router","zclVersion":3},"formaldehyd":7,"humidity":57.5,"last_seen":"2024-05-04T23:17:38+02:00","linkquality":144,"pm25":3,"temperature":20.3,"voc":34}'
[2024-05-04 23:17:38] debug: zh:ember: ~~~> [ZCL to=18694 apsFrame={"profileId":260,"clusterId":61184,"sourceEndpoint":1,"destinationEndpoint":1,"options":4352,"groupId":0,"sequence":0} header={"frameControl":{"reservedBits":0,"frameType":0,"direction":0,"disableDefaultResponse":true,"manufacturerSpecific":false},"manufacturerCode":null,"transactionSequenceNumber":154,"commandIdentifier":11}]
[2024-05-04 23:17:38] debug: zh:ember:ezsp: [SEND COMMAND] NOT CONNECTED
[2024-05-04 23:17:38] debug: zh:ember:queue: Dispatching deferred: Network not ready
[2024-05-04 23:17:38] debug: zh:ember:queue: Dispatching stopped; queue=1 priorityQueue=0
[2024-05-04 23:17:38] debug: zh:ember:uart:ash: Error while parsing received frame in NOT_CONNECTED state (flags=0), status=ASH_NCP_FATAL_ERROR.
[2024-05-04 23:17:40] debug: zh:ember:queue: Dispatching started.
[2024-05-04 23:17:40] debug: zh:ember: ~~~> [ZCL to=18694 apsFrame={"profileId":260,"clusterId":61184,"sourceEndpoint":1,"destinationEndpoint":1,"options":4352,"groupId":0,"sequence":0} header={"frameControl":{"reservedBits":0,"frameType":0,"direction":0,"disableDefaultResponse":true,"manufacturerSpecific":false},"manufacturerCode":null,"transactionSequenceNumber":154,"commandIdentifier":11}]
[2024-05-04 23:17:40] error: zh:ember:ezsp: [SEND COMMAND] Cannot send second one before processing response from first one.
[2024-05-04 23:17:40] debug: zh:controller:endpoint: ZCL command 0xa4c13874fb41ee57/1 manuSpecificTuya.defaultRsp({"cmdId":2,"statusCode":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":154,"writeUndiv":false}) failed (ERROR_INVALID_CALL)
[2024-05-04 23:17:40] error: zh:controller:device: Default response to 0xa4c13874fb41ee57 failedA bit later i wasnt able to activate join of new devices and got this error every time I try:
[2024-05-04 23:27:32] error: zh:controller:device: Default response to 0xa4c13874fb41ee57 failed
[2024-05-04 23:28:51] debug: z2m: Received MQTT message on 'zigbee2mqtt/bridge/request/permit_join' with data '{"device":null,"time":254,"transaction":"6sr6u-5","value":true}'
[2024-05-04 23:28:51] info: z2m: Zigbee: allowing new devices to join.
[2024-05-04 23:28:51] debug: zh:ember:queue: Status queue=0 priorityQueue=0.
[2024-05-04 23:28:51] error: zh:ember:ezsp: [SEND COMMAND] Cannot send second one before processing response from first one.
[2024-05-04 23:28:51] error: z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'ERROR_INVALID_CALL'
[2024-05-04 23:28:51] debug: z2m: Error: ERROR_INVALID_CALL
at Ezsp.startCommand (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:462:19)
at Ezsp.ezspImportTransientKey (/app/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:5922:14)
at preJoining (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:3004:55)
at Object.func (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:3071:49)
at EmberRequestQueue.dispatch (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/requestQueue.ts:117:58)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
[2024-05-04 23:28:51] debug: z2m: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"ERROR_INVALID_CALL","status":"error","transaction":"6sr6u-5"}'
[2024-05-04 23:31:59] debug: z2m: Saving state to file /app/data/state.json
[2024-05-04 23:32:24] debug: z2m: Received MQTT message on 'zigbee2mqtt/bridge/request/permit_join' with data '{"device":null,"time":254,"transaction":"6sr6u-6","value":true}'
[2024-05-04 23:32:24] info: z2m: Zigbee: allowing new devices to join.
[2024-05-04 23:32:24] debug: zh:ember:queue: Status queue=0 priorityQueue=0.
[2024-05-04 23:32:24] error: zh:ember:ezsp: [SEND COMMAND] Cannot send second one before processing response from first one.
[2024-05-04 23:32:24] error: z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'ERROR_INVALID_CALL'
...(repeats for every click)I added the complete log of the beginning of reconnection after generating new keys and IDs. The issue started from first device, before no errors except
zh:ember:uart:ash: Received frame with CRC error
The first device is a Phillips Hue motion sensor. startOfReconnection.log
fred-gb
commented
6 months ago Bonjour, ππ»
After somes days. It's a very good surprise for me.
First step: upgrade to zigbee2mqtt, firmware 7.4.2, drivers EZSP
First good surprise, my Button PTM216 finally works!
I read in the last few days, that switching to ember drivers will cause re-inclusion of modules. So this morning I'm getting ready to do this.
https://github.com/Koenkk/zigbee2mqtt/assets/17061623/126a71f6-6c6e-4a9b-bb85-5328a240fef3
π
I switched to EMBER drivers in debug mode and... ALL WORKS FINE WITHOUT NEED REINCLUDED ANY DEVICE! π₯³
Very nice surprise to start this day!
Now I'm waiting for next z2m release after https://github.com/Koenkk/zigbee-herdsman/pull/1052
I let open this issue for @phenix1990 .
Nerivec
commented
6 months ago @phenix1990 I included a few fixes for the next release (hotfix coming out soon). Let me know how it goes after that.
phenix1990
commented
6 months ago @phenix1990 I included a few fixes for the next release (hotfix coming out soon). Let me know how it goes after that.
I already updated z2m but with older adapter version and ezsp driver. Tomorrow evening I hopefully will have time to test with ember and 7.4.1 Firmware.
Update: Gone back to ember and firmware 7.4.1 and no errors so far the first 2 hours. I will check if it stays like that for a whole day but so far so good π
Nerivec
commented
6 months ago Closing this to avoid mixing issues any further. @phenix1990 If you encounter any trouble, please open a new issue.
zerpex
commented
5 months ago Hi there,
Same issue with SonOff Dongle E 7.4.2 firmware even with z2m 1.38.0-dev. Only way to recover : switch back to ezsp.
LDprg
commented
5 months ago Hi there,
Same issue with SonOff Dongle E 7.4.2 firmware even with z2m 1.38.0-dev. Only way to recover : switch back to ezsp.
Try 7.4.3 firmware downloaded from https://github.com/darkxst/silabs-firmware-builder/blob/4.4.3/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl
@zerpex You also may need to change network ids and reconnect all devices. Because you won't be able to change the driver when other devices keep the network up with the same id. So you either completely power off all router devices or reconnect them into a new network. Config for devices is saved network independent in the config file.
See your logs for errors, they mostly tell you the problem.
zerpex
commented
5 months ago Hi @LDprg . I just updated to 7.4.3. This is better (Z2M is usable) and seems to work. Anyway, I still have the ROUTE_ERROR_ADDRESS_CONFLICT for "0".
How can I change this network ID ? Had a look around, be I was unable to find where...
phenix1990
commented
5 months ago Hi @LDprg . I just updated to 7.4.3. This is better (Z2M is usable) and seems to work. Anyway, I still have the ROUTE_ERROR_ADDRESS_CONFLICT for "0".
How can I change this network ID ? Had a look around, be I was unable to find where...
its written some posts above. Just enter the keyword Generate in your z2m config and repair your devices. also was necessary for me.
advanced:
channel: 20
network_key: GENERATE
pan_id: GENERATE
ext_pan_id: GENERATE@zerpex You will need to set following flags in the config to GENERATE. Z2M will automatically fill them with new values
advanced:
channel: 20
pan_id: GENERATE
ext_pan_id: GENERATE
network_key: GENERATEYou might also want to delete the mqtt cache since it might cause weird malformed data in mqtt. This shouldn't affect zigbee2mqtt directly.
zerpex
commented
5 months ago Thanks a lot. I confiirm that with firmware 7.4.3 and these parameters, everything works with ember !
What happened?
I get lots of error logs lines=
And many devices are unusable. Pass to timeout state and back.
These modules, no communication anymore. https://www.zigbee2mqtt.io/devices/PIR313-E.html
Network is slow, lot of timeouts.
And when I get back to driver
eszpand my second backup Sonoff ZBDongle-E (under 7.3 firmware), my zigbee network is working normally again.I know in life we as to do somes choices, but between switches PTM216 and multisensor PIR313-E, it's difficult to decide!
What did you expect to happen?
For operating PTM216 switches, I follow this tutorial: https://github.com/Koenkk/zigbee2mqtt/discussions/21462
How to reproduce it (minimal and precise)
emberZigbee2MQTT version
1.36.1
Adapter firmware version
7.4.1 [GA]
Adapter
Sonoff ZBDongle-E
Setup
LXC container Ubuntu, Nomad as orchestrator, Z2M Docker version
Debug log
When I try to wakeup device on battery:
When I activate "Permit join"