The last few days I’ve had some issues with HASS and my Z-wave network at home. It all began after reading in the manual for my Nodon Soft Remote that it could be used for direct association with other units to control them directly, without going through the controller. I never got the association to work but since my experiments, HASS no longer updates the GUI with the current status of my Z-wave switches. My automations still work and from time to time I can also control the lights from the GUI by clicking the appropriate command, although it’s very slow to respond, 10-20 sec if ever. The GUI won’t update in either case. When using the switch.turn_on or switch.turn_off services in the Services tab, the action is immediate but the GUI doesn’t update.
I’ve tried healing my Z-wave network, restarting HASS, rebooting my system and restoring the zwcfg-file from backups created well before this experiment but it makes no difference. I’m running v0.67.1 in a virtual Ubuntu 16.04 machine (no venv, no Docker).
TL;DR My HASS GUI is not updating the status of my Z-wave switches. Automations and services still works.
Does anyone have any ideas on why this happened and how I can get around it to get a working GUI again?
It’s possible that you’ve removed the association between the device and the controller. I’d check that. The associations are held in the devices, which would explain why rebuilding your config didn’t help.
Yes, I would have thought so too if I couldn’t control my switches at all, my automations still work and if I’m using the services tab the switches respond immeadiately (but the GUI doesn’t update). My next step will probably be to remove the remote and the switches from my network and re-add them in a different order. I’ve got a spare switch in my drawer that has never been connected to my network, I’ll add that one first and see if things come back online.
Although I don’t have very many units, I’m not very keen on the idea of having to rebuild my entire network but I guess that’s what I’ll have to do if I can’t think of another way to solve this.
That’s really weird - that it’s working through the services tab, but not the GUI, makes it sound like your install is somehow broken. I’d back up your configuration, do a fresh install, and restore your old config.
Oh, I’m assuming that you’re not using any other Python based programs in that VM? If you are, that could be the source of your problems - with conflicting library version requirements.
Time to fire up that RPi again I guess! I had some trouble upgrading Python earlier this spring, but once I got it going everything seemed to be running just fine, it wasn’t until I started messing with direct associations that the GUI went bananas.
Actually, I have been considering moving HASS and other home server applications to Docker, this might just be the nudge I need to get going…