Probably important to note that this same device shows 94% (even though it’s off) even when I go into my device list and select it from there and not just the dashboard card itself. The device in question is an older GE ZW3005 dimming switch and my setup is HAOS via VM on Synology and a TubesZB PoE Z-Wave Controller + Z-Wave JS UI.
I’ve got a switch or two that are creating current state issues with my dashboard cards. I’m using Mushroom light template cards and I can pretty consistently count on seeing my “basement” light icon orange whenever I open up my HA app on my mobile device or view the dashboard from a PC browser. The light isn’t actually on but the card thinks that it is and even shows a percentage (94% as I type this) but the light itself is actually off. If I tap the card (set to toggle) as to turn it off it will then report the proper state as off even though nothing was actually changed.
I’m newer to HA so I’m not sure the info to provide to help trouble shoot this but I was hoping that it’s maybe something common that I did wrong whenever creating this dashboard that was an easy fix or some sort of known bug w/o delving too deeply into the code side of things. There also is nothing listed in the “logbook” events window of the device. Typically I see state changes/reports and things like that for my other devices.
There’s a solid change I move this switch to another location soon and replace it with a new 800LR on/off switch but I wanted to see if I could track this down before adding any other variables to the equation.
Since HA tells you that the state is on even when the lights are off, this is probably not a dashboard issue. You’re probably looking at poor network connectivity (whatever network the light uses, whether it’s Zigbee, WiFi, etc.) or a light with faulty hardware/firmware.
Yeah, I started out thinking it was a Dashboard issue specifically as I’ve been recently building out a new mobile dashboard w/mushroom cards and that’s where I first saw it. As I was typing this up though I did some more digging and it’s even showing as being “on” from the Z-Wave integration when viewed from a browser as well.
The switch in question is an ancient one and has been on the radar for being replaced anyway. It’s a dimmer switch and the location it’s in would really be better suited for an on/off switch with a higher wattage rating. Zooz finally has some heavy duty on/off light switches so I’ve got a couple of locations with a few LED lights that I want to deploy them in due to in-rush of the LEDs.
I was going to move it to a less mission critical location that also happens to be half the distance to the Z-Wave controller. I’m not sure it’s a comms issue. This switch is the from the very first generation of Z-Wave switches to hit the consumer market a couple of decades ago so it’s likely just a bit wonky (technical term) due to practically being a prototype.
I’m currently working out some other kinks in my HA system but I’ve got about a dozen new 800LR Z-Wave devices in a box next to me as I type this waiting to go into service. A couple of my older switches are going to be replaced with this update including this one. I may or may not factory reset the switch in question, exclude it and try it in another location just to see if it displays the same wonkiness.