Z-Stack_3.x.0 coordinator 20230507 feedback

[Koenkk]

Please provide your feedback to the Z-Stack_3.x.0 coordinator 20230507 firmware here.

I hope this solves the NWK_TABLE_FULL many people were experiencing.

Changelog

20230507

• Enable child aging to fix issues like #13478 (but not for older Xiaomi devices as they do not implement child aging correctly which gets them kicked out of the network)
• Increase message timeout from 7 to 8 seconds to increase message delivery success rate for devices using a 7.5 seconds poll interval (#13478)
• Improve performance with larger network
  • Optimize table sizes
  • Increase stack_size from 1024 to 8192
• Add firmware for CC1352P7
• SimpleLink SDK 7.10.00.98

Download

• ~20230401~
• ~20230410~
• 20230507

[popy2k14]

@Koenkk Also installed 20230507 and network (~160 devices) came backup and is reponsive as hell :-) Will keep an eye on it the next days and come back here if there are troubles.

One strange thing (which i dont know if this is from the new firmware) is that a device showed up with id 0x0000000000000000.

Any ideas from where this is comming?

PS.: did'nt remove/add any device nor opened i the network for paring.

thx

[alexruffell]

@popy2k14 I had something similar happen where the device had 0x0000 network address like the coordinator and an IEEE address of 0xfffffffffffffff. I am not sure, but it seems like after deleting it some of the zigbee errors quieted down. Mine appeared while I was trying to add a device (way slower than usual and required multiple attempts)

[popy2k14]

Ok, thx. So i will delete it and see how it goes.

Thx

[popy2k14]

@Koenkk the 0x000... id is back.

I "force" removed it 2 days ago. Can i use the block option without any negative side effects? I assume that the id 0x000... will never be used from any device, right?

[Koenkk]

@popy2k14 can you provide the herdsman debug logging of when this device is added?

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

[popy2k14]

@Koenkk ok, i have enabled the herdsman log and forced removed the device, without blocking. Hope it happens soon, then i will grab the log.

[Venom84]

@Koenkk Also installed 20230507 and network (~160 devices) came backup and is reponsive as hell :-) Will keep an eye on it the next days and come back here if there are troubles.

One strange thing (which i dont know if this is from the new firmware) is that a device showed up with id 0x0000000000000000.

Any ideas from where this is comming?

PS.: did'nt remove/add any device nor opened i the network for paring.

thx

@Koenkk I have the same thing happening on my network. Its been happening for a while now since sometime in 2022 but each time i delete it, it just comes back again. I have been ignoring it but if you would like herdsman logs please let me know and ill get some to you.

[popy2k14]

@Venom84 thx a lot for the info. So it seem's not related to this issue. If it comes back and i could grab a log i will open an new issue.

[cloudbr34k84]

I just had a huge issue where my adapter just crashed. Out of the blue. Was fine one min then I got to turn off lights and I see more than half my devices are all offline. @popy2k14 you have 160 devices! do you have a large or small house. I have a large house and I'm struggling here hey. i have 130 devices mainly Routers as well. Im keen to here how you are going and what you have done.

[okastl]

TI Flash Programmer log (I've renamed hex file, as all my archival hex files are in the same folder)

I recommend using cc2538-bsl.py to flash. It works.

[okastl]

Using 20230507 with two setups. No problems so far.

Setup 1: Total 127 By device type Router: 94 End devices: 33

Setup 2: Total 51 By device type End devices: 29 Router: 22

I'll observe, if the known problem of devices vanishing from the NVM after restoring network backup is still present.

[cloudbr34k84]

Using 20230507 with two setups. No problems so far.

Setup 1: Total 127 By device type Router: 94 End devices: 33

Setup 2: Total 51 By device type End devices: 29 Router: 22

I'll observe, if the known problem of devices vanishing from the NVM after restoring network backup is still present.

So no problems ever? My system crashed for no reason whats so ever, for the past 2 hours I have been trying to get the Adapter to connect. I decided to update the firmware. I since stopped using my Sonoff P Coordinator and use Zigstar Lan Adapter. was going great until 2 hours go. I have updated the firmware and still not getting anywhere ahh lol

[okastl]

So no problems ever?

Not with 20230507 (which this thread is about). Using it for about 5 days with Sonoff P stick and quite recent z2m dev.

[Venom84]

@Venom84 thx a lot for the info. So it seem's not related to this issue. If it comes back and i could grab a log i will open an new issue.

No problem at all @popy2k14 if you do open a new issue for this please could you tag me in it as I'd like to follow and provide logs if needed.

[popy2k14]

@Venom84 i hope i will remember on our conversation, but i will try my best :-)

@cloudbr34k84 I'll used cc2538-bsl.py to update directly on my superviced HASS.OS. Not at home atm, but from my mind: Stop Z2M, wget new file, unzip new file, run the script (i can post my CLI if you need it), start Z2M.

Yes it's stable since i installed it (~3 days) and also snappy. After update i had one dropped ikea fyrtur blind, but the are crap and this happens after some weeks. But all other devices are working as they should.

[cloudbr34k84]

Hey @Koenkk Need some help. I have updated to your firmware after issues where all my devices were going offline. I am having trouble getting the adapter to stay connected, and when it does all the devices slowly come online, then I think the adapter just stops. ALl the suggestions don't seem to work. the only option it start again and re add 130 devices

2023-05-15T21:46:33.879Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed 2023-05-15T21:46:39.880Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":42723,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":187,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,94,11,2,0]}} 2023-05-15T21:46:39.880Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,227,166,1,1,0,239,187,0,30,5,24,94,11,2,0,111] 2023-05-15T21:46:39.881Z zigbee-herdsman:controller:endpoint Read 0xa4c1385627cb8095/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:warn 16-05-2023 07:46:39: Failed to ping 'Front Balcony Wall Light Left' (attempt 1/1, Read 0xa4c1385627cb8095/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)) Zigbee2MQTT:debug 16-05-2023 07:46:42: Active device 'Front Balcony Wall Light Left' was last seen '685.14' minutes ago. 2023-05-15T21:46:44.888Z zigbee-herdsman:controller:endpoint Read 0xa4c13872560a92d8/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2023-05-15T21:46:44.888Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c13872560a92d8:33554/1 (0,0,13) 2023-05-15T21:46:45.882Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":50388,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":188,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,234,11,2,0]}} 2023-05-15T21:46:45.883Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,212,196,1,1,0,239,188,0,30,5,24,234,11,2,0,137] 2023-05-15T21:46:45.883Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c1380fdda423fd/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:46:45.883Z zigbee-herdsman:controller:device:error Default response to 0xa4c1380fdda423fd failed 2023-05-15T21:46:51.885Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":41446,"destendpoint":1,"srcendpoint":1,"clusterid":768,"transid":189,"options":0,"radius":30,"len":7,"data":{"type":"Buffer","data":[1,214,10,114,1,0,0]}} 2023-05-15T21:46:51.886Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,17,36,1,230,161,1,1,0,3,189,0,30,7,1,214,10,114,1,0,0,122] 2023-05-15T21:46:51.886Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c1386b082c6ab4:50388/1 (0,0,11) 2023-05-15T21:46:51.887Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c1386b082c6ab4/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:46:51.887Z zigbee-herdsman:controller:device:error Default response to 0xa4c1386b082c6ab4 failed 2023-05-15T21:46:57.891Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":22972,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":190,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,182,11,2,0]}} 2023-05-15T21:46:57.892Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,188,89,1,1,0,239,190,0,30,5,24,182,11,2,0,34] 2023-05-15T21:46:57.892Z zigbee-herdsman:controller:endpoint Command 0x00158d0006b39f15/1 lightingColorCtrl.moveToColorTemp({"colortemp":370,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:error 16-05-2023 07:46:57: Publish 'set' 'color_temp' to 'Front Patio Downlight Right' failed: 'Error: Command 0x00158d0006b39f15/1 lightingColorCtrl.moveToColorTemp({"colortemp":370,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)' Zigbee2MQTT:debug 16-05-2023 07:46:57: Error: Command 0x00158d0006b39f15/1 lightingColorCtrl.moveToColorTemp({"colortemp":370,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) 2023-05-15T21:47:02.533Z zigbee-herdsman:controller:endpoint Read 0xa4c138cd7ccb25b4/1 genLevelCtrl(["currentLevel"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2023-05-15T21:47:02.533Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138cd7ccb25b4:25615/1 (0,0,11) 2023-05-15T21:47:03.893Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":10764,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":191,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,112,11,2,0]}} 2023-05-15T21:47:03.894Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,12,42,1,1,0,239,191,0,30,5,24,112,11,2,0,38] 2023-05-15T21:47:03.894Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138821dc3a3ed/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:03.894Z zigbee-herdsman:controller:device:error Default response to 0xa4c138821dc3a3ed failed 2023-05-15T21:47:09.894Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":192,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,154,11,2,0]}} 2023-05-15T21:47:09.895Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,192,0,30,5,24,154,11,2,0,12] 2023-05-15T21:47:09.895Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138cbe77d1397/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:09.895Z zigbee-herdsman:controller:device:error Default response to 0xa4c138cbe77d1397 failed 2023-05-15T21:47:15.896Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":33554,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":193,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,221,0,0,0]}} 2023-05-15T21:47:15.896Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,18,131,1,1,0,0,193,0,30,5,16,221,0,0,0,172] 2023-05-15T21:47:15.897Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138da52889bec:64099/1 (0,0,8) 2023-05-15T21:47:15.897Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:15.898Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed 2023-05-15T21:47:21.898Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":50388,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":194,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,236,11,2,0]}} 2023-05-15T21:47:21.898Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,212,196,1,1,0,239,194,0,30,5,24,236,11,2,0,241] 2023-05-15T21:47:21.899Z zigbee-herdsman:controller:endpoint Read 0xa4c13872560a92d8/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:warn 16-05-2023 07:47:21: Failed to ping 'Front Balcony Wall Light Right' (attempt 1/1, Read 0xa4c13872560a92d8/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)) Zigbee2MQTT:debug 16-05-2023 07:47:24: Active device 'Front Balcony Wall Light Right' was last seen '679.95' minutes ago. 2023-05-15T21:47:26.904Z zigbee-herdsman:controller:endpoint Read 0xa4c138261e50941a/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2023-05-15T21:47:26.905Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138261e50941a:21957/1 (0,0,8) 2023-05-15T21:47:27.900Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":25615,"destendpoint":1,"srcendpoint":1,"clusterid":8,"transid":195,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,222,0,0,0]}} 2023-05-15T21:47:27.900Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,15,100,1,1,8,0,195,0,30,5,16,222,0,0,0,95] 2023-05-15T21:47:27.900Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c1386b082c6ab4/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:27.901Z zigbee-herdsman:controller:device:error Default response to 0xa4c1386b082c6ab4 failed 2023-05-15T21:47:33.902Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":196,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,155,11,2,0]}} 2023-05-15T21:47:33.902Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,196,0,30,5,24,155,11,2,0,9] 2023-05-15T21:47:33.903Z zigbee-herdsman:controller:endpoint Read 0xa4c138cd7ccb25b4/1 genLevelCtrl(["currentLevel"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:error 16-05-2023 07:47:33: Failed to read state of 'Front Patio Pendant Bulb 4' after reconnect (Read 0xa4c138cd7ccb25b4/1 genLevelCtrl(["currentLevel"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)) 2023-05-15T21:47:39.904Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":21957,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":197,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,223,0,0,0]}} 2023-05-15T21:47:39.905Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,197,85,1,1,0,0,197,0,30,5,16,223,0,0,0,171] 2023-05-15T21:47:39.905Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138da52889bec:64099/1 (0,0,5) 2023-05-15T21:47:39.906Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:39.906Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed 2023-05-15T21:47:45.912Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":198,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,156,11,2,0]}} 2023-05-15T21:47:45.912Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,198,0,30,5,24,156,11,2,0,12] 2023-05-15T21:47:45.913Z zigbee-herdsman:controller:endpoint Read 0xa4c138261e50941a/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:warn 16-05-2023 07:47:45: Failed to ping 'Front Balcony Downlight' (attempt 1/1, Read 0xa4c138261e50941a/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)) Zigbee2MQTT:debug 16-05-2023 07:47:48: Active device 'Front Balcony Downlight' was last seen '686.32' minutes ago. 2023-05-15T21:47:50.918Z zigbee-herdsman:controller:endpoint Read 0x680ae2fffe7d3a32/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2023-05-15T21:47:50.918Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0x680ae2fffe7d3a32:23170/1 (0,0,5) 2023-05-15T21:47:51.914Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":23170,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":199,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[16,224,0,0,0]}} 2023-05-15T21:47:51.915Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,130,90,1,1,0,0,199,0,30,5,16,224,0,0,0,222] 2023-05-15T21:47:51.915Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138da52889bec:64099/1 (0,0,4) 2023-05-15T21:47:51.916Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:47:51.916Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed Zigbee2MQTT:debug 16-05-2023 07:47:52: Saving state to file /config/zigbee2mqtt/state.json 2023-05-15T21:47:57.915Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":200,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,157,11,2,0]}} 2023-05-15T21:47:57.916Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,200,0,30,5,24,157,11,2,0,3] 2023-05-15T21:47:57.916Z zigbee-herdsman:controller:endpoint Read 0x680ae2fffe7d3a32/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) Zigbee2MQTT:warn 16-05-2023 07:47:57: Failed to ping 'Hamptons Lane EM Plug' (attempt 1/1, Read 0x680ae2fffe7d3a32/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms)) Zigbee2MQTT:debug 16-05-2023 07:48:00: Active device 'Hamptons Lane EM Plug' was last seen '541.08' minutes ago. 2023-05-15T21:48:03.916Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138da52889bec:64099/1 (0,0,2) 2023-05-15T21:48:03.917Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":201,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,158,11,2,0]}} 2023-05-15T21:48:03.917Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,201,0,30,5,24,158,11,2,0,1] 2023-05-15T21:48:03.917Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:48:03.917Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed Zigbee2MQTT:debug 16-05-2023 07:48:05: Received MQTT message on 'zigbee2mqtt/bridge/request/permit_join' with data '{"device":null,"time":254,"transaction":"emjqe-1","value":true}' Zigbee2MQTT:info 16-05-2023 07:48:05: Zigbee: allowing new devices to join. 2023-05-15T21:48:09.918Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":254,"tcsignificance":0} 2023-05-15T21:48:09.918Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,5,37,54,15,252,255,254,0,228] 2023-05-15T21:48:09.918Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0xa4c138da52889bec:64099/1 (0,0,2) 2023-05-15T21:48:09.919Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:48:09.919Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed 2023-05-15T21:48:15.921Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":64099,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":202,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,159,11,2,0]}} 2023-05-15T21:48:15.921Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,15,36,1,99,250,1,1,0,239,202,0,30,5,24,159,11,2,0,3] Zigbee2MQTT:error 16-05-2023 07:48:15: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'SRSP - ZDO - mgmtPermitJoinReq after 6000ms' Zigbee2MQTT:debug 16-05-2023 07:48:15: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) Zigbee2MQTT:info 16-05-2023 07:48:15: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"SRSP - ZDO - mgmtPermitJoinReq after 6000ms","status":"error","transaction":"emjqe-1"}' 2023-05-15T21:48:21.925Z zigbee-herdsman:controller:endpoint DefaultResponse 0xa4c138da52889bec/1 61184(2, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms) 2023-05-15T21:48:21.925Z zigbee-herdsman:controller:device:error Default response to 0xa4c138da52889bec failed

[popy2k14]

@cloudbr34k84 is it possible you have wifi incompatibility issues? On which channel you are running your ZigBee network? 25 is the recommended one. When you change your channel it could be you have to re-pair some devices.

Other reason for crashes maybe also hardware related: power supply, too long or bad USB extension cable, or as it was in my case ARM platform with kernel USB bug. Since I switched to an Intel x64 platform, all is running stable.

Hope this helps.

[cloudbr34k84]

@cloudbr34k84 is it possible you have wifi incompatibility issues? On which channel you are running your ZigBee network? 25 is the recommended one. When you change your channel it could be you have to re-pair some devices.

Other reason for crashes maybe also hardware related: power supply, too long or bad USB extension cable, or as it was in my case ARM platform with kernel USB bug. Since I switched to an Intel x64 platform, all is running stable.

Hope this helps.

I'm running HAOS in intel with zigstar Lan adapter so does not require USB cabe on channel 26.

It just seems my adapter whether it was so off, would just crash

Anyway im rebuilding again tonight after family goes to sleep

[BartRuSec]

@slugzero, with regards to https://github.com/Koenkk/Z-Stack-firmware/issues/439#issuecomment-1532736240, almost week ago I have upgraded FW to version 20230507 and z2m to 1.30.4-dev commit: dddd2bc. Since then no issues with my TS0044 device so far.

[popy2k14]

@cloudbr34k84 is it possible you have wifi incompatibility issues? On which channel you are running your ZigBee network? 25 is the recommended one. When you change your channel it could be you have to re-pair some devices. Other reason for crashes maybe also hardware related: power supply, too long or bad USB extension cable, or as it was in my case ARM platform with kernel USB bug. Since I switched to an Intel x64 platform, all is running stable. Hope this helps.

I'm running HAOS in intel with zigstar Lan adapter so does not require USB cabe on channel 26.

It just seems my adapter whether it was so off, would just crash

Anyway im rebuilding again tonight after family goes to sleep

Keep us updated.

[Koenkk]

@cloudbr34k84 I believe in your case the TuYa devices on your network are too spammy and make the coordinator crash. Since you have two coordinator, I suggest have 2 networks with each 80 devices on it.

[cloudbr34k84]

@cloudbr34k84 I believe in your case the TuYa devices on your network are too spammy and make the coordinator crash. Since you have two coordinator, I suggest have 2 networks with each 80 devices on it.

Based in that, then I get rid of my 6 in1 sensors. They are constantly updating 6 sensors every second and I have those in each room. Thank you for the suggestion.

[popy2k14]

@Koenkk do you have a list of spammy devices/manufacturer? This would be nice (maybe also in the Wiki) so you're support maybe gets lower 😬

[cloudbr34k84]

@Koenkk do you have a list of spammy devices/manufacturer? This would be nice (maybe also in the Wiki) so you're support maybe gets lower 😬

In Australia limited to zigbee devices light switches especially price. I think the 6 in 1 air quality sensor are definitely contributing. They should be banned lol

[sjorge]

My personal list of devices i avoid:- tuya (does not support reporting configuration -> at mercy of device for spammyness level, uses custom tuya dp over zigbee not pure ZCL spec)- xiaomi (mostly the older stuff, does not support reporting configuration, no child aging)- gledopto light, older stuff is horrible, newer stuff seems better but i have not tried any of itI’m extremely picky though 😅Honorabel mentions:- legrand (firmware is not the best, very unfriendly when reaching out to them)- wiser (same, as legrand, only ever dealt with their TRV though)(Amazing brands: Ubisys ans Develco, their support are super helpful, they provide testing fw if you report bugs! Mostly follow ZCL well)Note, this is all personal experience, i got a whole drawer full of ‘test’ devices 😅~ sjorgeOn 16 May 2023, at 22:48, Brad @.***> wrote:

@Koenkk do you have a list of spammy devices/manufacturer? This would be nice (maybe also in the Wiki) so you're support maybe gets lower 😬

In Australia limited to zigbee devices light switches especially price. I think the 6 in 1 air quality sensor are definitely contributing. They should be banned lol

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[cloudbr34k84]

Also I could not reduce reporting. I'm not the only one who has trouble with reporting in tuya devices.

[cloudbr34k84]

@cloudbr34k84 I believe in your case the TuYa devices on your network are too spammy and make the coordinator crash. Since you have two coordinator, I suggest have 2 networks with each 80 devices on it.

I can add these via tuya integration as I have a tuya zigbee hub. Would having that network connected with devices cause issues with my Z2M zigbee network??

[rolf-tx]

@Koenkk 20230507 - running some for 10 days on HA using ZHA on Sonoff 3.0 Plus Two devices became unavailable, both of them twice at different times. 1) eWelink SWITCH-ZR03-1 2) Kwikset SMARTCODE_DEADBOLT_10T_W3

Power cycle ZR03 brought it back Restarting HA core brought Kwikset back

[casakampa]

Have been running the new beta firmware 20230507 for a few days, coming from the beta firmware 20221102 (which ran stable on a Electrolama ZZH! for months), and everything works smooth.

[cloudbr34k84]

AN update. Still have 1 or 2 devices drop off the network, Link Quality is not good even right next to the adapter—nothing over 150. I have 1 downlight I can't get to connect to the mesh network.

error 2023-05-18 20:37:28: Publish 'set' 'state' to 'Kitchen Strip Light' failed: 'Error: Command 0xcc86ecfffea0b99d/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 (Timeout - 11978 - 1 - 69 - 6 - 11 after 10000ms)

error 2023-05-18 20:34:01: Failed to configure 'Powder Room Light Switches', attempt 1 (Error: Read 0xa4c1389a34414fb0/1 genBasic(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 838 - 1 - 20 - 0 - 1 after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7))

[popy2k14]

@Venom84 @Koenkk it happened again. Device 0x000... popped up. I have got an herdsman log, see here: https://github.com/Koenkk/zigbee2mqtt/issues/17720

[popy2k14]

PS.: Other than that the firmware runs way better than before. Slowdowns are much more less frequent.

[cloudbr34k84]

@cloudbr34k84 is it possible you have wifi incompatibility issues? On which channel you are running your ZigBee network? 25 is the recommended one. When you change your channel it could be you have to re-pair some devices. Other reason for crashes maybe also hardware related: power supply, too long or bad USB extension cable, or as it was in my case ARM platform with kernel USB bug. Since I switched to an Intel x64 platform, all is running stable. Hope this helps.

I'm running HAOS in intel with zigstar Lan adapter so does not require USB cabe on channel 26. It just seems my adapter whether it was so off, would just crash Anyway im rebuilding again tonight after family goes to sleep

Keep us updated.

Hey so what is your link quality like? Also where is your HA machine and coordinator. Mine is positioned second level roughly in the middle of the house (upstairs lounge), but this lounge has Xbox, tv, and a mesh router close by. See image. The reason is I have another switch board that connects Xbox, tv, mesh HA and my Z2M adapter directly to Lan. Any thought suggestions. I'm wondering if I should get some more of these PoE z2M adapters and flash them as routers and position then around the house. Would they act as better routers?

[juppyjupp]

Hi Brad, did i see it right, the USB stick directly plugged into the NUC is your Zigbee coordinator? Then start with a simple change. Use an USB extention cable (50cm will be enough) to connect your USB stick to your NUC and place the Stick away from the NUC and other electrical devices. Each electrical device is generating "electrical noise" which influence the link quality. I had a good expierience decouple my SONOFF USB coordinater from my PI with a 50cm USB extension.

[lux73]

or Read the FAQ! - the Extension and more - is mentioned there Improve network range and stability!

so many Problems in Forums would disappear if People would read sometimes ^^

[cloudbr34k84]

Hi Brad, did i see it right, the USB stick directly plugged into the NUC is your Zigbee coordinator? Then start with a simple change. Use an USB extention cable (50cm will be enough) to connect your USB stick to your NUC and place the Stick away from the NUC and other electrical devices. Each electrical device is generating "electrical noise" which influence the link quality. I had a good experience decouple my SONOFF USB coordinator from my PI with a 50cm USB extension.

Nah thats my Bluetooth dongle. Im using a PoE zigsta adapter its the white box on the right side of the picture on the carpet. I Yerah ok so maybe thats the issue with thr TV, xbox, and a mesh AP close by. I need to find another place for this PoE adapter.

[cloudbr34k84]

or Read the FAQ! - the Extension and more - is mentioned there Improve network range and stability!

so many Problems in Forums would disappear if People would read sometimes ^^

Done all of that mate, On channel 26 Using PoE zigbee adapter I been using Zigbee for a few years, but the number of devices has grown and with a bigger house (480sq over 2 levels) comes more issues in trying to create a mesh system. My issue was i had tuya devices that were very chatty (not in the FAQ or help guide) so i removed those and its more stable in that regards. Just have some random drops off in areas they shouldnt.

[lux73]

this was more a General Hint - not personally to you :-)

[lux73]

btw Zigbee Chan 26 is not optimal - some Devices could not connect on this Channel

i would recommend maximum Chan 25, not higher

[popy2k14]

yes, use channel 25. It's the prefered one regarding device & wifi compatibility.

[zen2]

Also I could not reduce reporting. I'm not the only one who has trouble with reporting in tuya devices.

I control reporting of electrical measurement plugs here:

Min/max rep interval: seconds between reports Min rep change: minimum delta values for reporting

[sjorge]

Not sure if related to this latest firmware but OTA update seem to be very very slow... resulting in the device giving up. (I only tried philips as those are the one ones with pending updates for me)

[epower53]

Not sure if related to this latest firmware but OTA update seem to be very very slow... resulting in the device giving up. (I only tried philips as those are the one ones with pending updates for me)

I've noticed the same, but it's not so slow that the updates fail. Using 20221226 my individual OTA times were in the 25-40 minute range. Now they're in the 80-100 minute range. Is there an internal throttle setting to keep OTA traffic from causing network congestion? If so, perhaps this could be exposed to the z2m frontend to allow people to set it based on personal preference.

[sjorge]

This one has been going for about 8 hours now, hasn't failed yet 🤞

[cloudbr34k84]

btw Zigbee Chan 26 is not optimal - some Devices could not connect on this Channel

i would recommend maximum Chan 25, not higher

Yeah ok, will change channel and repair. 👌👌

[FlyingDomotic]

I upgraded slaesh CC2652RB from 20230410 to 20230507 this evening (Z2M 1.30.4 commit: b2dd21e1, with 117 devices, including 11 routers).

Since, every set failed with 'Error: Command 0x000d6ffffe659a61/3 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: 'MAC channel access failure' (225))

Reverting to 20230410 fixed the issue.

Note I'm using non default channel 15.

[deviantintegral]

I've just had my adapter completely crash out. It's no longer responding, even after restarting the server and using https://github.com/mvp/uhubctl to reset power to the adapter. I likely need to pull it from the port to fix it, which I can't do right now. Here's the logs from before it crashed. I will re-enable debug logging when I do, but I'll say that this took several days or even a week before it happened.

May 20 20:08:35 zigbee2mqtt npm[9396]: Zigbee2MQTT:info  2023-05-20 20:08:35: MQTT publish: topic 'zigbee2mqtt/Pedestal 4/availability', payload 'offline'
May 20 20:08:38 zigbee2mqtt npm[9396]: Zigbee2MQTT:error 2023-05-20 20:08:38: Publish 'set' 'color_temp' to 'Main Floor Hallway' failed: 'Error: Command 1 lightingColorCtrl.moveToColorTemp({"colortemp":373,"transtime":450}) failed (SRSP - AF - dataRequest
Ext after 6000ms)'
May 20 20:08:55 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:08:55: Failed to ping 'Desk 1' (attempt 1/1, Read 0xb0ce1814030112c2/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"
disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:09:20 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:09:20: Failed to ping 'Door 2' (attempt 1/1, Read 0xb0ce1814030151bf/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"
disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:09:52 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:09:52: Failed to ping 'Josephine’s Side Table' (attempt 1/1, Read 0xa4c138e8c3e759b7/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disable
Recovery":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:10:03 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:10:03: Failed to ping 'Emily’s Side Table' (attempt 1/1, Read 0xa4c138d11f67cdfd/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableReco
very":true,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:10:27 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:10:27: Failed to ping 'Desk 2' (attempt 1/1, Read 0xb0ce18140301d37f/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"
disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:12:05 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:12:05: Failed to ping 'Desk 1' (attempt 1/1, Read 0xb0ce1814030112c2/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":true,"
disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:12:22 zigbee2mqtt npm[9396]: Zigbee2MQTT:warn  2023-05-20 20:12:22: Failed to ping 'Pedestal 1' (attempt 1/2, Read 0xb0ce18140301289c/1 genBasic(["zclVersion"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":tr
ue,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (SRSP - AF - dataRequest after 6000ms))
May 20 20:12:31 zigbee2mqtt npm[9396]: Error: SRSP - SYS - version after 6000ms
May 20 20:12:31 zigbee2mqtt npm[9396]:     at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
May 20 20:12:31 zigbee2mqtt npm[9396]:     at listOnTimeout (node:internal/timers:559:17)
May 20 20:12:31 zigbee2mqtt npm[9396]:     at processTimers (node:internal/timers:502:7)
May 20 20:12:31 zigbee2mqtt systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
May 20 20:12:31 zigbee2mqtt systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
May 20 20:12:31 zigbee2mqtt systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 1.
May 20 20:12:31 zigbee2mqtt systemd[1]: Stopped zigbee2mqtt.

Bus 001 Device 015: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

If anyone has any other tricks for remotely resetting a zzh! I'd be glad to hear them!

[lvanjaarsveld]

20230507 feels more responsive.

I do have way more unavailable for all sensors. Just witnessed one and looks like the addon is restarting. Logging mentions a ton of timeouts before.

[cloudbr34k84]

An update. Moved my coordinator away from as much interference as possible. Changed to channel 25. Repaird all 125 devices. I have light that im trying to link but just can't get it to stay paired. Definitely more responsive since I removed the chatty tuya devices. Fingers crossed. I might add some more of the ham geek adapters and flash them with router firmware to see if that helps with coverage.

[qba667]

@Koenkk Great work, just switched to your implementation for the CC1352P7 using BeagleBoard BeaglePlay. Before I was using older self complied version. So far all good - but this is experimental network.

In free time I will try to address dual stack implementation to utilize Sub 1GHz features of the chip. The idea is to have Zigbee and proprietary 868 MHz protocol stack running on same radio chip using DMM approach from TI.