My Aeotec Illimino Switch was working just fine a few hours ago. Then I tried to add a rule for double taps, and found that it would not report double taps. After messing around trying to understand that, now it won't report state at all. I've tried the built in driver and universal z-wave driver. I've repaired my z-wave network. I've excluded; factory reset; and re-included the switch. Still nothing.
I've had this happen to a Leviton switch too. What causes this and how do you fix it?
I'd love to post the logs, but nothing shows up in them. It simply doesn't react to the state change.
What hub model are you running? Anything in Logs, particularly with debug logging enabled, for anything from this device? (Probably not if you don't ultimately see events, but worth looking...)
With the newer hub models, shutting down the hub, pulling power for about 30 seconds, then reapplying power -- to both fully restart the hub and the Z-Wave radio, unlike a normal reboot or shutdown -- might be a good first step, though that's more likely to be a problem with your entire network and not a single device.
Troubleshooting steps here, including ones related to "ghost" devices, would also make a good starting point:
Unfortunately, the logs are completely empty. I've checked debug, info, all of it, and nothing there at all.
The extra hard reboot is an idea I haven't tried. I'll try that later.
Is it possble for the lifeline association group to get messed up? It would, I think, cause a problem like this. I dont know an easy way to check that.
It might not be related, but I have had variations on this problem before. As I said, I had a Leviton switch that did exactly this. I also have a custom app for Rhasspy voice assistant that occasionally just stops responding to MQTT messages. A reboot of the HE C7 usually fixes it, but it does seem similar in that the driver just stops working right.
I've seen some devices lose this if you update the firmware but I don't know of it randomly happening. A configure() command with the built-in Illumino drivers looks like it sets this again, however, so if that isn't something you had tried, you could (though it's also run on inclusion, which I see you've already tried re-doing).
You can try clearing out the device by changing to the "Device" driver, and using the command buttons initialize and then clear the states. Then put the correct driver back and press initialize.
So...on a last ditch effort, I reinstalled the switch device firmware. As far as I can tell, it is the exact same firmware that was already on it. That seems to have fixed all the problems. It is now registering all the events, taps, double taps, etc.
I really don't know what happened, but that seemed to have fixed it.
