For the past three days my Zwave stops working when I wake up. It works again after shutting down HA and restarting. Something happens during the night…
Unfortunately I am not an expert enough in understanding where to look in the HA log and identifying what causes the problem.
Can anyone help me ?
What hardware are you using?
Other than zwave all else works?
HAOS correct? No VM or docker?
Zwavejs or zwavejsui?
Next time it happens you should llook to see if Zwavejs / zwavejsui has stopped.
Look at HA logs
HA >> settings >> system >> logs to see if there is related info
Look at zwavejs / zwavejsui logs to see if related info. I forget where logs are for HAOS addon.
And does it go down at any particular time?
- Yellow Box
- Everything else works
- Installation methodHome Assistant OS
- Core2025.12.4
- Supervisor2025.12.3
- Operating System16.3
- Frontend20251203.3
- I believe that I have Zwave JS UI but on the sidebar it shows Zwave JS
- I will try to look at the log next time it happens.
It works fine when I go to sleep at around 11 pm and it is down at around 7 am
If you also have the ZWave JS Addon installed, remove it. There can only be Zwave JS add-on OR Zwave JS UI add-on running on a mesh.
When I asked for what time, you had already said overnight…
There is a Home Assistant event that happens in the 4am hour and I was wondering if this is related to that. You should be able to look at logs to see when this is crash is happening.
Does this imply that I have both ? How do I remove ZWave JS without damaging my mesh network ?
The screen shot is from ZWave JS .
Check if you have backup services configured that disable the z-wave add on during backup. Most services have settings to stop specific addons. This one should not be one of them. Also check the settings for the add on itself (auto start, watchdog, …)
2 Likes
Not exacttly certain where that is from, but if you have both add-ons installed
(look here in the add-ons list), 
(Click the 3-dots menu top right then system info)
and you want to run ZwaveJS-UI, uninstall the ZwaveJS one and restart.
Always have a fresh backup that you can get to whenever doing any kind of install or removal of components.
I went into the list of Addons and the ZWave JS is not installed, so that is not the issue.
Exactly what happens at 4 am ?
The “stop addons” has not an active check mark, so that does not seem the issue.
Also, I am not aware of having made any recent changes to either the backup settings or to Zwave itself. I replaced a Zwave device three days ago but I do not see how that would cause the issue.
1 Like
Another possible cause might be the power source. During backup the storage requires more power and for a longer time on end, which would explain why it happens at night. Maybe the time when devices go unavailable is a hint to check the time and if that corresponds to specific events.
Do you have an automation that runs at that time?
I have 343 Automations, so it is likely that one Automation or another will run during the night.
I definitely will look at the log if it happens again tomorrow and will report back here.
I was thinking along the lines of automations that do heavy stuff like restart HA, or things running at specific times. The automations that run all the time would cause trouble at any time of the day, not night. There will be considerably less automations active while you sleep I imagine. The log ook might tell you what was going on at the time entities went unavailable.
I will check tomorrow. I am not aware of “heavy” stuff happening at any time, though I’d love to know how to create an automation that restarts HA at a defined time.
Run through this list
For example, I don’t see an extender cable on your list of stuff.
Consider a powered usb hub. I use an inexpensive Belkin. This will provide stable power to the stick,
Thanks. It did not happen this morning and I guess that this is because I power cycled my Yellow Box yesterday. We will see over the next few days.
I am not sure that I need an extender cable with the 64 Zwave devices that I have, but I will keep it in mind. Thanks again.
USB3 port chips are known to make interference with radio sticks, so an USB extension cable is often used to get it a bit away from those chips.
The Raspberry Pis and the Home Assistant Versions of them are all known to have extremeoy limited power designs, so powering USB sticks can often bring the power draw over de har they are designed to handle.
A common solution is to use a powered USB hub, so the radio sticks do not have to draw power from the Raspberry Pi/Home Assistant server.
A drop in power that only shortly go under the required limit of power supplied can cause unpredictable situations.
Often the server do not crash completely, but some hardware components might get in a state that cause them to get stuck and become unresponsive.
This info is very interesting.