Agreed, I went with the older chipset for stability. Ordered the new ones for testing. I may have missed what version is in use here.
Currently 5gb RAM using 40% of it.
27gb high performance ssd disk space using 43% of it
Allocated 4 high performance M1 processors
If it a resource problem then not sure how anyone runs it on a Rasberry Pi 
Nope your good, just have seen folks run out of memory have Z2M issues. Just removing one issue at a time. I have had great results with SMLights
1 Like
Do you have a hypervisor or something?
I have worked my way through two different sonoff coordinators, both recommended by Home Assistant. Each time performing a full rebuild.
A month ago moved to smlight all to get zigbee2MQTT stable.
It was rock solid until 4 days ago when the node Red update 14 came out, not saying related but gives a timeline.
Since then zigbee2MQTT has collapsed, node Red started crashing, so had nothing to lose by moving to NR 14. It made no difference.
I’ll start from scratch again on the green, a known stable platform, I’ll seriously reduce expectations and demands on NR and see if I can get Home Assistant to run Mqtt zigbee2MQTT and maybe an external node Red, in case it all implodes again.
Thanks for all your help.
I am running it on the VMware for Apple silicon.
If you think nr14 may be to blame, have you tried removing that to see if z2m stabilises?
1 Like
That is what my gut was thinking too. My node red experience is limited though.
Mine also.
zigbee2MQTT became unstable before NR 14 was installed.
When NR 14 crashes and goes offline zigbee2MQTT is still unstable with many devices falling offline with a lot more unresponsive for 24 hours.
Its ok time to rebuild again
Ok building a new Home Assistant instance on a Home Assistant Green.
I have run it up for the first time and it has found a bunch of stuff locally.
To keep this as standard as possible so as not to interfere with zigbee2MQTT operations which devices should I allow Home Assistant to automatically connect to?
Nanoleaf?
Appletv?
Hue?
Logitech Harmony?
Plex?
Shelly devices?
Tado?
Sonos?
Any I should avoid because they may interfere with zigbee2MQTT.
My purpose here is to see if a stable zigbee can be built and maintained in Home Assistant and want to avoid any of the mistakes I made the last three times I built zigbee networks with Home Assistant.
So I may have answered my own questions ensure nothing connects to Home Assistant apart from zigbee2MQTT?
None will, but if course hue is ZigBee, so it may interfere if they use the same channel.
Incorporating hue in HA won’t create interference, but the fact that you have hue may create interference.
I have played safe, ignored all the notifications about local devices and deleted everything not directly Home Assistant.
It had added radio? Shopping list? Sun? Weather? And it auto added the Sonos, deleted them all to reach the vanilla just Home Assistant to ensure the success of a reliable zigbee2MQTT.
Yeh, I had the hue bulbs and Motion sensors in Home Assistant, but had to remove them and put them on hue hubs to restore basic lighting functionality.
With hue Hubs it causes problems for Home Assistant.
Without hue hubs I can’t have reliable lighting.
And people start getting annoyed when stairs lighting is intermittent
The hue hubs are in 20 and 15, Home Assistant 11.
Which ran for a month solidly until last weekend.
All zigbee devices came under Home Assistant zigbee2MQTT for builds 1 and 2.
But as build 2 became unreliable I was advised to move hue bulbs off Home Assistant zigbee2MQTT as it was known to cause unreliability and I was assured that by separating the channels Hue and Home Assistant zigbee2MQTT could happily coexist.
The other advise was that having 90 hue bulbs and 100 other zigbee devices on Home Assistant zigbee2MQTT was too much.
Build 3 was wiping Home Assistant Mqtt, zigbee2MQTT and node Red completely.
Switch from the second sonoff usb zigbee coordinator, 1st one was in build one, to the smlight Poe Ethernet coordinator. And that worked perfectly for a whole month,the best since Christmas!! Until end of last week.
So build 4 is underway, this time on Home Assistant hardware, using the smlight Poe ethernet coordinator totally vanilla.
I run up node Red outside of Home Assistant to ensure no external corruption.
And only install Home Assistant approved add one, mosquito Mqtt broker and zigbee2MQTT.
Or do you believe I should install these outside of Home Assistant ?
I am leaning towards having Home Assistant manage Mqtt and zigbee2MQTT.
To keep it clean I’ll do all automation in node Red.
And I will not install any helpers, blueprints, HACS integrations and no other Add ons.
That way we can test the your unlucky or operator issue by ruling out the operator issue by only using Home Assistant hardware, and core add ons.
Then if the fundamental zigbee issues re-arise then we have conclusive evidence of luck or more specifically unlucky!
It will take a while to get this back up again, but while most of the house automations are in taters, at least most of the lighting is stable
It looks like the Sun integration is integral to home assistant - I keep removing to to keep this Home Assistant Green as default as possible and Home Assistant keep reinstalling Sun on its own.
Home Assistant has auto installed
Home assistant core
home assistant host
Home Assistant operating system
Home Assistant supervisor
and I installed Mosquito broker and zigbee2MQTT from Add Ons.
Is there anything here I need to delete to ensure a default Home Assistant install with just zigbee2MQTT running zigbee devices?
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)