I know this is not a support forum but maybe someone can point to a post or web page or something to start looking into a problem i have. I’ve searched but could not find anything for this problem.
I’ve been using Home assistant for years now. 6 months ago or so I decided to buy Home Asisstant green box cause I thought it might be better to just have a reliable hardware and stop fussing with apps on my nas and what not. And its easier to explain to my wife that if that box is off or doing something wierd possibly every automation is dead and switch to old school dials and stuff.
The main use or the most critical is heating. I have boiler control, temp sensors everywhere and eTRVs. All local zigby network. I have a usb stick zigby adapter on the box and the network extends the house with several plugged in zigby devices for range.
Things stop working, actions on eTRVS and boiler switches dont occur, and slowly the system grinds to a halt or almost. Some errors pop up in the log. If i restart the Green Box everything works perfectly, but slwoly it degrades.
I would want to troubleshoot this somehow without stopping the system altogether. But I’m a bit at a loss on how to do this. Any log that i should turn on? any info somewhere to guide me into trouble shooting this kind of behaviours would be appreciated.
Thanks!
I can provide logs, hardware specs, versions etc if anyone is interested buy i thougth nobody would spned the time into this.
Well as it runs smoothly after a restart, then you should “collect” a log after restart, say 1st hours or 6 … go through it, save it somewhere.
Then when it feels like it starts to slow down, repeat above.
If you haven’t read your log-files, or collected any relevant info, any answers here will only be based upon wild guessing
So monitor your log-file after restart, and later, look for " Errors / Time-outs " etc, most likely in red colors. #Settings/System/Logs
And then “Fill in the blanks” here,
as you mention above. Everything, also like which Zigbee integration etc.
2025-12-12 10:52:48.812 ERROR (MainThread) [homeassistant.components.automation.heating_main] Heating Main: Error executing script. Error for call_service at pos 2: Failed to send request: device did not respond
But that is not very helpfull the call_service is the call for that particular “device” to do something, like set a thermostat to a given temperature.
There are no other logs (in the HA web UI) about this.
And i guess it makes sense the device did not respond to that command. But it seems to be server related cause a restart makes it go away (although this might not be entirely true).
Im gonna see if i can enable more logs about it and gather info. Strangely i don’t remember any of this happening when using my home made NAS as a HA server.
I cant Commend upon your discrepancies in hardware and different HAOS installations, but i actually also just bought a HA-Green (a month ago), but it’s to early for me to make any opinions, beside it definitely consume less power(which was the main purpose, as it will have an isolated environment/Purpose), and in the end i will never end up with identical solutions, on this and my current Installation.
Other seems to have similar issues with ZHA, but first of all good “best practice” of Zigbee network, in a “modern” home, with various electronic Devices/Equipment is essentiall, below is a link from a community member whom dida good work in covering most issues there is to think about.
Feel Free to update this post if/when you more logs/info to add, like how many device Zigbees/repeater, but also location of the usb-dongle, compared to your Router/TV /NAS and HA-Server etc, also how large your WIFI-Network is, and Which Channel you Zigbees communicate on
Ok, so I read that post and tried to apply some of the things. Most I had already covered before, like moving away the zigbee antenna from EM noise, extending zigbee range with plugged in routers etc etc.
The one thing I had neglected to do (facepalm moment) is keep up to date with the firmware updates of the USB zigbee dongle. I remember updating as soon as i got it, and maybe one more time. But there was another update (or several i don’t know)
After the update, 36ish hours so far, no more issues. So I’m gonna pin this to the dongle firmware for now.
No more failed calls to the TRVs, pretty stable for now. Lets hope that was it.
There was a complete shutdown and startup of the Green hardware in the middle, but I don’t think it mattered, but still remains to be seen. Will post if the problems come back.
I wonder if there is a need for the zigbee integration to go hunt for firwmare updates if possible and alert for them.
I always try to read(if possible) what new updates are for,before updating(but always good to check if one have the latest, most i.e integrations in here provide such info, … Some hardware vendors NOoo …
Xros our fingers that you’ll have luck here
Not that i know if that is the cause, but it’s basically an error-message in “clear-text” , read and research
And how does your ZHA-Map looks like ?, are your “zigbee routers” Bulps, which you turn on and of frequently ?.
Not very informative !.., on which channels are your WIFI And your Zigbee running, you did read they use same frequency 2.4gHz, same as alot other things as you should be aware of now.
Googled that error for you. Weirdly, the results all point to an error which happens if you have Multiprotocol firmware on your coordinator. Technical Documentation
Which firmware did you flash on your zigbee usb dongle? If it said something like MultiPan firmware, that’s your issue. MultiPan is not supported by HA precisely because of instability & crashing issues like this. Sonoff have decided to ignore that and are still offering it as an option in their web flasher
Make sure your dongle is flashed with zigbee coordinator firmware only (first option)
It didn’t occur to me that OP would even think of flashing his Dongle’s firmware , as he for some reason posted a “extensive” Dongle info upon my request for relevant info of his system
However after your research i check this “hardware spec” above, atleast it seems like
cp210x is a windows driver(if im not wrong) , im not sure what i’m following here anymore and why
Im unsure how to understand what firmware im putting in, last update i just used the automatic tool from sonoff web. Will see if i can extract some info from there.
Ok, then you’re definitely on zigbee coordinator firmware.
The only remaining logical explanation is that you have a spammy zigbee device on your network?
Did you recently add any new devices (especially Tuya ones)?
It might be good to list the model numbers of all your devices here, in case something jumps out immediately for anyone reading this.
Other than that, maybe enable ZHA debug logging so you’ll have a better understanding of what’s going on in your network.
All zigby is sonoff, and a switch that i just dont’t remember. Im gonna turn on debug when the problem starts.
For the moment i added a saving state and restart automation to restart HA every day. That will probably walkaround the issue for now. I will update this thread when i have more info.
…
, as he for some reason posted a “extensive” Dongle info upon my request for relevant info of his system
, im not sure what i’m following here anymore and why
