My Zigbee setup is just too flaky!
I’m running Z2M with a ZZH Stick (latest firmware). All the usual suspects accounted for: USB extension cable. Wi-Fi Channels separated. System downed and forced to rebuild etc. etc. But I still get multiple drop off’s or non-responses all the time.
I ve got 80 devices on the mesh, some battery some mains and my LQI’s seem pretty decent.
I notice the Z2M Logs are almost exclusively full of the following errors (from a variety of devices)… 0xc7: NWK_TABLE_FULL
No network route' (205)
No converter available for 'state' (21)
Although I think this last one is caused by the 3 IKEA Tradri Repeaters and may be fairly meaningless.
I can see what you mean about the known issues now I have trawled GitHub. Ive also posted into Koenkk’s Z2M page to see if anyone has an fix for it now (assuming 0507 is now 6 months old I’m hoping so !).
In the meantime I will downgrade to 1226.
Thanks again.
There are test builds in the threads. I think the latest I saw was 20231127 or thereabouts.
If you’re game, it may help the cause to test the new builds. I hate to admit I’m not doing so myself. I’m happily stable and not going to rock the boat. If my test nets act up I will test with those.
Do you happen to know where 20231127 might be held ? - Ive scoured everywhere I can think of but am only encountering posts that are months out of date. Ive posted into the GitHub discussion but no replies in 5 days.
My network is now worse than ever. About 30% of my devices are off-line and even a re-pair only sorts them for a few hours.
Fantastic - thank you so much !
This afternoon I’ve installed 20231112 and re-paired a bunch of devices. Fingers Crossed ! It’s back up now and error log is looking much better. Like 98% better !
I’m going to give it a while to settle and see how it goes.
I have also provided feedback into the GitHub discussion.
Thank you for this! I was setting up a new SLZB-06 PoE Zigbee dongle running the 20230507 firmware, and kept hitting the NWK_TABLE_FULL error. After downgrading to 20221226 via the dongle’s web UI, I’m not seeing those errors any more.