Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All routers stop working intermittently. #22

Open
ikey-ru opened this issue May 11, 2022 · 3 comments
Open

All routers stop working intermittently. #22

ikey-ru opened this issue May 11, 2022 · 3 comments

Comments

@ikey-ru
Copy link

ikey-ru commented May 11, 2022

The problem has happened several times already. All routers stop transmitting a signal. Only those devices that directly reach the stick work. Only turning off helps - turning on the power of the stick and clearing the memory.
Снимок экрана 2022-05-11 в 03 09 45

The second picture with the checkbox enabled NoneOffTheAbove
1
During normal operation, the map looks completely different.

@hacker-cb
Copy link
Contributor

Sometimes map in z2m is broken, but all works fine.
Actually, map is not very stable and not informative.

@ikey-ru
Copy link
Author

ikey-ru commented May 11, 2022

In my case, more than half of the devices break down, as they worked through routers.

debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:12:36: Publish 'set' 'state' to '0x00124b0005abf840' failed: 'Error: Command 0x00124b0005abf840/1 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
мая 11 23:13:17 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:17: Publish 'set' 'state' to '0x00124b002252afdd' failed: 'Error: Command 0x00124b002252afdd/7 genOnOff.on({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Failed to read state of '0x00124b0017fd335d' after reconnect (Read 0x00124b0017fd335d/1 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":25453,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":125,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,19,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)')))
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Publish 'set' 'state' to '0x00124b002252b2f2' failed: 'Error: Command 0x00124b002252b2f2/6 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33273,"destendpoint":6,"srcendpoint":1,"clusterid":6,"transid":146,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,21,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Failed to read state of '0x00124b002252b2f2' after reconnect (Read 0x00124b002252b2f2/1 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":33273,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":160,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,22,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)')))
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Failed to read state of '0x842e14fffe3a525a' after reconnect (Read 0x842e14fffe3a525a/1 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":61906,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":172,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,23,0,0,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)')))
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Publish 'set' 'state' to '0x00124b00209e9a03' failed: 'Error: Command 0x00124b00209e9a03/2 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":44735,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":177,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,24,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
мая 11 23:13:49 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:13:49: Publish 'set' 'state' to '0x00124b00209e9a03' failed: 'Error: Command 0x00124b00209e9a03/2 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> AF - dataRequest - {"dstaddr":44735,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":178,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,25,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))'
мая 11 23:14:08 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:14:08: Failed to read state of '0x00124b00184bd9c1' after reconnect (Read 0x00124b00184bd9c1/1 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUP_CLUSTER_COMMAND'))
мая 11 23:14:08 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:14:08: Failed to read state of '0x00124b002263be9b' after reconnect (Read 0x00124b002263be9b/1 genOnOff(["onOff"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUP_CLUSTER_COMMAND'))
мая 11 23:23:21 debian npm[66415]: Zigbee2MQTT:error 2022-05-11 23:23:21: Publish 'set' 'state' to '0x00124b00209e9a03' failed: 'Error: Command 0x00124b00209e9a03/1 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SREQ '--> ZDO - extRouteDisc - {"dstAddr":44735,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))'

@ikey-ru
Copy link
Author

ikey-ru commented May 11, 2022

After power off/on stick all ok:
Снимок экрана 2022-05-11 в 23 22 11

zStack30x v.20211222
It's happening for the fourth time in a year. I replaced the entire module CC2538, installed the latest firmware, but after 2 months the situation repeated itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants