I’ve been hunting down the fix to this problem for weeks, and finally figured out what’s going on, and wanted to share in case others have the same issue.
I have a number of Aeotec switches in my setup, and they’re fantastic. Small, decent price, easy to install, hidden in the box so I don’t have to change all of my decor, etc. And, until I started messing with my configuration.yaml file, worked perfectly fine. When I turned my switch off, the HASS front end reflected the change, everything was great.
But then, in the midst of a HASS upgrade and me playing with the configuration.yaml file, the updates stopped happening. When I physically changed the switch state, it didn’t update the system. If I rebooted HASS, it reflected, but that’s not ideal, obviously. The weird thing is that my GE outlets, also zwave, didn’t have the problem. They functioned just fine, leading me to believe it wasn’t my z-stick, it had to be something with the switches themselves.
Either me adding a soft reset automation to my configuration (which I read somewhere is a no-no for some z-wave devices) or a HASS upgrade messed up the notification configuration in the switches. After a long, arduous search for how to fix it (including removing and re-pairing the switches) I found out that there is a config setting in the switch itself for Notification Status, and it can be set to None, Hail, or Basic. (For searchability of this post, I also looked into the command_class_hail setting, but that wasn’t it) I installed ozwcp (see here for installation instructions: Tutorial: compiling open-zwave-control-panel), changed the Notification Status to Basic for all my Aeotec switches, and voilà! problem solved.
Hopefully this helps anyone else searching for how to fix this issue - maybe even myself the next time I break everything, hah