Error NWK_TABLE_FULL is mentioned in Z2M FAQ and root cause as well as suggested actionable solutions to that is to avoid and reduce EMI/RMI/RMF interference or at the very least try change WiFi channel or Zigbee channel so that they do not overlapp. (It can also help to add more Zigbee Router devices even if not the root cause). Follow these tips:
Zigbee2MQTT documentation also has some of the similar best practice tips but it is not as detailed:
Not getting the NWrk errors anymore.
The 3rd rebuild of the Home Assistant zigbee2MQTT network was using a Poe Ethernet SMLight coordinator sited at the Center of the house away from any signal noise. (To avoid the usb/proximity to computer issues)
Rolled out 50+ router devices in a concentric circle way from SMLight.
Did not add any hue bulbs ( as they were diagnosed as the issue in build 2) but did add 8 ikea zigbee relays as it was reported in build 1 they are the root of all good zigbee2MQTT networks.
Then added in the 40 odd end point devices.
It was rock solid for a month.
Then at the end of last week, when the node Red 14 update was made available it collapsed into a heap (Node Red not related to zigbee2MQTT issues).
What wasnât offline was not responding.
I moved about 20 critical devices off onto an Aqara hub so could keep key door/window/ blind controllers/and leak sensors working.
By this time Home Assistant was unstable too so advised to simplify Home Assistant by removing integrations.
Home Assistant is now stable but nothing works, zigbee is largely non functional and with all the integrations disabled Home Assistant is largely idle.
I have run up a Home Assistant green with a skeletal system of zigbee2MQTT and Mqtt.
Just received a second SMLight. Will shut down the old SMLight.
Will migrate all the routers across to the new SMLight then all the Aqara hub devices, then the remainder of the old end point devices.
I had setup the old smlight on a channel that was clear of zigbee and Wi-Fi, Iâll recheck that before bringing the new one up.
Iâll wipe the old Home Assistant and start again with only officially supported add ons and use the Homey and Hubitats to reach other integrations to avoid overloading Home Assistant again.
Then use a central Mqtt and Node Red combo to manage it all.
Good point!
Is it possible to install today 1.37 of zigbee2MQTT on a current Home Assistant or will need to build in docker externally?
Not sure really, as I donât use a supervised install.
You can install an older version from a backup.
You should listen to Hedda. He knows this stuff.
When you do this, I would recommend you go slow. Test what you have for a couple of weeks, if possible, making sure it is stable, and then moving onto the next few to migrate.
And, yes, listen to Hedda.
Did you succeed with the downgrade?
Thank for this very helpful indeed.
I had implemented 95% of your recommendations.
Using an SMLight Poe Ethernet CC2652P coordinator, to enable me to pretty locate the coordinator in the best location for house keeping it away from usb, computers, electronic devices, power cables etc etc.
Zigbee network of 70+ router devices and 50 end points was totally solid for about a month.
It was built on the SMLight, with the 70 router devices (8 of which were ikea relays) paired in situ in a 3d spiral out from the coordinator. Covering all 12 rooms.
Then paired the 50 end point devices, door, window, leak, blind controllers, again in situ.
Not had any problems with Aqara devices, they pair quickly and easily but ensure I always perform a reset before pairing. I have found the Tuya battery devices need a new battery when they start playing up because the battery values reported are not reliable. BTW the new ikea battery zigbee devices are now designed to use the ikea rechargeable batteries.
The coordinator is on channel 11 (hue hubs on 15 & 20).
This was my third rebuild of zigbee2MQTT since Christmas. It was absolutely solid for a whole month. The only issue was zigbee2MQTT UI would override any device setting changes, checking the retain box would be unchecked immediately 1 second later, same for QOS etc.
Then the end of last week, Home Assistant started taking 20 seconds to respond clicks or sometime not at all, the UI was not completely updating the screen. It consistent across iOS app, web interface, on safari, chrome on multiple computers and devices. Node Red was crashing constantly, never seen it do that in nearly three years of usage.
I moved off key devices, mainly Aqara blind controllers and leak sensors, onto an Aqara hub.
On the advice of the Home Assistant forum disabled every integration I can, and now with~80 zigbee devices, 20 of which are offline, another 20 unresponsive, the Home Assistant is largely ineffective.
Fortunately the two hue hubs are working fine and remain solid so most lighting is working, leaving only two rooms kitchen and a bathroom under Home Assistant control that arenât working.
All other automation is down.
What I donât understand is how the hue hub sat behind a 65â on the wall controls the 50 odd zigbee lights without issue and the zigbee2MQTT coordinator is so sensitive.
The only logical conclusion is that hue builds all its own devices to a standard, and zigbee2MQTT is attempting to bring a broad house of devices under one control.
No, I havenât worked out how to do that yet.
I am focused on removing variables that could cause zigbee2MQTT to fail by installing on Home Assistant green with a completely default install with no integrations to see if a solid zigbee2MQTT with ~100 devices is possible in this house.
As it looks like I canât install zigbee2MQTT 1.37.5 on the Home Assistant green Iâll have to run up a docker for it, so it probably will make more sense to run an MQTT broker and Node Red up there too.
That will help keep the loading down on Home Assistant green.
But then if integrations cause Home Assistant to become unstable, and I canât run a stable version of zigbee2MQTT on it, what is the Home Assistant green doing?
A conundrumâŚ
The core reason for moving node Red, Mqtt and z2m into Home Assistant was to ease the maintenance of NR, MQTT and zigbee2MQTT.
So if I guess I need to make a decision, zigbee2MQTT 1.38 and Home Assistant or zigbee2MQTT 1.37.5 and no Home Assistant.
You havenât talked about your wifi channels.
Kinda covered most of your questions in the thread except.
Wi-Fi signals from neighboursâŚâŚ good point. We are deluged on all quarters buy neighbour wifis.
The construction of these dorma bungalows is such that Wi-Fi is a common issue, that I resolved with three UniFi APs for the 6 downstairs rooms and one for the 6 upstairs rooms.
The two hue hubs on 15 and 20, are rock solid, not had any issues since Build 2, when it became apparent that zigbee2MQTT could handle the number of devices needed.
So hue has been solids since Feb when I built it.
Home Assistant zigbee2MQTT on channel 11.
I had setup UniFi to place the 2.4Ghz channels away from Home Assistant, I have not changed that and the Home Assistant zigbee2MQTT was solid absolutely solid for a whole month.
Because of the construction design of the house a single neighbour changing Wi-Fi would have such a catastrophic failure not just in zigbee2MQTT but also node Red and Home Assistant itself.
Thanks for your input it helps a lot to rule things out.
And I guess you there are reasons you donât want to use ZHA, even though that would simplify things further if thatâs your aim?
I am choosing to keep things separate, so if HA restarts or whatever, then Z2M is not impacted. But I definitely see the appeal of the other direction.
After 30 years of do this, home automation, from X.10 through to now.
I am leaning more and more to a range of autonomous hubs, Tado, Hue, Eufy, etc etc and have them do the basics and they do well, these operate as the autonomous nervous system, run most things without any interaction.
Then put a âbrainâ over it all, probably Node Red.
Integrate what I can into NR the. Use the broad collection of hubs, homey Hubitat, Home Assistant etc and have them handle edge integrations, Shelly, Govee, etc etc as long as it all feeds into Mqtt or a direct into NR (using MQTT makes it easier to migrate automations)
If I am doing home automation rebuild 4 in 6 months time to put it all in place.
Sorry just remembered I did not reply
House Wi-Fi and zigbee settings
Zigbee
Hue 1 25
Hue 2 20
zigbee2MQTT 11
Wi-Fi 2.4gHz
6 upstairs & 11 downstairs
The Hue systems are doing fine and they are competing with the Wi-Fi
Which 2.4GHz Wi-Fi Channels and channel width do you use on your three UniFi WiFi Access Points?
Note to not set WiFi channel to âAutoâ on any WiFi Access Point radio. Instead specific set hard Wi-Fi channels on each WiFi access point that do not overlap with the Zigbee channel used.
Also wondering how close those three UniFi WiFi Access Points are to your Zigbee devices? Especially how close they are to the Zigbee Coordinator and Zigbee Router devices) as WiFi APs are relativly high power so can drown out and jam Zigbee signals just by being too close even if not they are not on the exact same frequency range.
Regardless, probably a good idea to try different Zigbee channel AND different Wi-Fi channels as well.
Example; if use Zigbee channel 11 then should not at all be using WiFi channels 1, 2, 3, 4, or 5. See:
[quote=âHedda, post:55, topic:742417â]
Which 2.4GHz Wi-Fi Channels and channel width do you use on your three UniFi WiFi Access Points?
The three APs and UDR are on channels 6 and 11 with a 20 width
Note to not set WiFi channel to âAutoâ on any WiFi Access Point radio. Instead specific set hard Wi-Fi channels on each WiFi access point that do not overlap with the Zigbee channel used.
Channels not set to auto and are fixed
Also wondering how close those three UniFi WiFi Access Points are to your Zigbee devices? Especially how close they are to the Zigbee Coordinator and Zigbee Router devices) as WiFi APs are relativly high power so can drown out and jam Zigbee signals just by being too close even if not they are not on the exact same frequency range.
The SMLight is ~10 feet and a wall to the ap in the ceiling of the landing and ~12 ft and a floor to the one in the ceiling of the kitchen.
Regardless, probably a good idea to try different Zigbee channel AND different Wi-Fi channels as well.
The hue hubs are on 20 and 25 and the SMLight is on 11, with the 2.4gHz operating in the higher bands. It worked solidly for a month right out to the bottom of the garden and the door sensors on the gates.
Example; if use Zigbee channel 11 then should not at all be using WiFi channels 1, 2, 3, 4, or 5. See:
Yup I thought I had that covered.
[/quote
Even if I get basic zigbee working again I still have to get zigbee2MQTT fixed as well, from build 3( when I powered everything off, removed batteries, reset every device to factory, wiped and uninstalled Mqtt and zigbee2MQTT from Home Assistant then powered off, the added everything back, 50+ routers in a 3d concentric circle away from SMLight including 8 ikea relays, then the end devices.
Everything was solid no drop offs at all for a month, zigbee2MQTT would not allow any device settings to be set using the UI, clicking on retain was disabled within a second of selecting it.
So it looks like I am at the very least destined to repeat it all again, but check that zigbee2MQTT is allowing device config.
]
By the way, have you asked for assistance in Zigbee2MQTTâs own community or support channels? As I do not believe this is the correct nor best place to continue if the root cause of your problems might lie in the Zigbee2MQTT application and not your generic Zigbee network mesh:
#zigbee2mqtt, #release-branch , #development-branch , #installation-hassio , #installation-docker, #zigbee-shepherd , #documentation , #hardware)That is, please note and be aware that this âZigbeeâ section in the Home Assistant forum was only ever intended to cover Home Assistantâs own native ZHA integration as well as Zigbee devices that can be used with it, (in fact it was originally named âZHAâ and then renamed to âZigbeeâ to indicate it is also about Zigbee devices too), but it has never been meant for support issues with every other third-party gateway/bridge/hub that can support Zigbee devices and present them to Home Assistant using other protocols.
IMHO this is becoming a problem when everyone expected to get support here if they have problems that are not really with Home Assistant but instead problems with the configuration or inter-workings of Zigbee2MQTT, deCONZ, Philips Hue Bridge, IKEA Tradfri Gateway, Samsung SmartThings, etc. as help with those type of problems should really be gotten via their own support channels and communities as they have nothing directly to do with Home Assistant, or as last resort you could post to the section about third party integrations â Third party integrations - Home Assistant Community
Same problem here, Three day ago Zigbee2MQTT stop and work randomly in loop.
Try HA Reboot - poweroff - reboot addon - reboot Zigbee2MQTT in his interface, nothing
Hi have HA on rpi 3b+ and conbee II, updated to the latest firmware
Home Assistant
Iâm trying to restore from a full backup that I had made and downloaded in mid-June. I update you
p.s sorry for my bad english
Valid point.
I do need to engage in the zigbee2MQTT community to figure out why it is overriding device settings.
But that was overshadowed by Home Assistant stalling, node Red crashing and zigbee2MQTT experiencing a cascade failure.
Rightly or wrongly the commonality here was Home Assistant.
Home Assistant seemed a logical path of pursuit.
By disabling 95% of add ons and integrations returned Home Assistant to stability.
zigbee2MQTT appears to have returned to normality too, re pairing lost and unresponsive devices leaves me only with two dead devices that I will re pair again.
Given zigbee2MQTT was stable, all the environmental elements favourable before, during and after the week long outage, it appears the cause of both the Node Red and zigbee2MQTT issues were down to the Home Assistant âwobblyâ, possibly through a misbehaving integration.
I have restored several integrations as they are pivotal to the home automations, but will run up a Homey and a Hubitat with the intention of integrate through them into Mqtt, then if they have a problem it wonât bring down the core zigbee2MQTT and node Red.
But it is now clear that your problem has nothing to do with Zigbee in Home Assistant. Again, âZigbee2MQTT instabilityâ is not the same as a âZigbee problem with or in Home Assistentâ, at best it third-party integration issue, which still means that discussion does not belong this this forum about âZigbeeâ in Home Assistent.