Some days ago (I can’t say exactly) my Z-Wave setup started lagging badly after having been totally fine for months. It can take 20 seconds before a light is turned on in a room by the motion sensor, and everything else seems lagging too. Am I the only one seing this, or does anybody else have the same problem? Nothing has changed in the system. From the Z-Wave JS UI log it seems like anything that happens there is instant, so it must be something between Home Assistant and (running on a virtual machine on my server) and Z-Wave JS UI (running on a separate Pi). Any suggestions would be appreciated!
Weird, it seems to have been a Fibaro motion sensor that was dead, but there was nothing in the Z-Wave JS UI log that showed it was trying to reach it. I replace the battery now (which had gone directly from 30 % to 0) and everything seems responsive now. I’ll take up the thread again if I’m wrong.
You can look at the controllers stats for dropped tx/rx and if excessive check stats device by device for cause.
Zwave issues are generally
- controller power
- Controller connection
- device poor connection(shows in stats)
Thanks for answering, it seems like not is all well after all. Annoying as heck. This is the statistics since 04 last night, so around eight hours (I have a “self heal” crontab reboot of the Pi at 04). Does this sound bad enough that it can be the problem? I’m running a Home Seer G8, just like in my house.
The 58 devices on the network are within ten meters from the controller, and the mesh seems to be OK too. The red one is a battery powered smoke detector:
No. I don’t believe so. When it is primary cause dropped is in hundreds or thousands. You won’t need to ask.
What is battery level on battery devices? I change batteries at 40%. I find below that they can cause issues.
I don’t think you should do this.
Devices will fix routes on their own. If you daily/weekly rebuild their route you will end up in situations where network never stabilizes. One day all is good the next it’s bad. If an individual device has a problem then you rebuild route for that device. Doing this for the entire network is like throwing the chessboard up in air and trying to put pieces back in middle of game. You may get some pieces right but not guaranteed. Best to always do one by one as needed to avoid problem. Personally I have never needed to do this over 10yrs with my current network and all is rock solid.
Doing this may also create a lot of network traffic but I’m not sure about this. Again, more bad than good in my experience.
Thanks for the input, I turned off the reboot now. It’s a prehistoric thing from when Home Assistant was quite unstable, 7-10 years ago.
I found a dimmer that wasn’t working correctly, I will replace that tomorrow and see if that helps.
The dimmer must have been it. It’s been two days now (one day was without power because of the storm Dave), and no delays since I replaced that. THanks for the help, I have disabled the “self heal” reboot at 04. The dropping has dropped too, especially of messages, that’s totally gone with twice as many messages as my previuos screenshot, where there were 12 TX and 3 RX dropped. And the RX total commands dropped is one third in twice as many messages:
