The defaults are listed here Default Config - Home Assistant
Perfect!
Many thanks for all your time and help!
I have loads of issues with my Skyconnect and Z2M after the arrival of 1.38.0 and the change from ezsp to ember.
1.38.0 is unusable for me (can’t toggle lights from HA, and lights becomes unresponsive), so I am staying on 1.37.1, but ember is still not playing nice.
I am happy it’s high summer in Denmark and the sun sets at 23 PM, so we are not using lights at the moment. Hopefully stability will happen soon. Otherwise I will migrate back to ZHA, that is finally starting to get those extra features I was missing before, like automatic OTA update and support for the devices I use.
But I still like to keep my lights separate from HA, so I hope for resolution.
1 Like
No but if you visit Z2M’s github, you can see many people have issues with 1.38.0, also when they are on other firmwares. And although unrelated, ember adding fuel to the fire is just to underline that Z2M is in a quite unstable spot at the moment.
Here is an example of a coordinator on the zstack firmware:
After updating from zigbee2mqtt docker version 1.37.1 to 1.38.0 FUT035Z+ are not controlable anymore via Home Assistant · Issue #23109 · Koenkk/zigbee2mqtt (github.com)
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.
- Does your SMLight zigbee coordinator have any upper limit on how many devices it can connect to…?
- What is the zigbee channel you are using?
- What is/are the wifi channel(s) you are using?
- What is/are the wifi channel(s) your neighbors are using?
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.
1 Like
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:
