I recently upgraded from 2.1.5.124 to 2.1.7.118. I have all GE/Jasco Z-Wave switches, dimmers, fan controls. Many of these devices, at random, appear to be failing to recognize Off events. I have many dashboards around my home. At random times, when we turn Off the devices (either physically, digitally from a dashboard, or via Alexa integration with Hubitat), the dashboard buttons still show them as On.
I am also seeing behaviors where during the turn off process for dimmers, I will see the dimmer level representation on the dashboard buttons, change to a lower level as they turn off. I know these dimmers have fade-to-off features, so wondering if something is happening there.
As a side note, these problems were not happening under 2.1.5.124. That was pretty rock solid. Only started after upgrade. I only upgraded because I figured 2.1.6 should be pretty solid by now, but during the upgrade realized it was grabbing 2.1.7. I have also previously analyzed my Z-Wave network with Z-Wave Toolbox, and it was all responding 100%.
Any thoughts to help the situation? Maybe I need to rollback to 2.1.5? I have a backup right before that upgrade.
Using OOTB drivers for all but 3. Those 3 switches/dimmers that are using a custom driver, is for double-tap functionality. I have not seen an issue with them.
What also just caught my attention is that the change log for 2.1.7.118 shows changes to the GE Zigbee dimmers for related functionality. I also now see 2.1.7.121 is available. Hmm.
EDIT: Nope... I remoted into my hub to try it, and I can't reproduce the issue... Using the "Generic Z-Wave Smart Dimmer" driver, I get no errors and the status updates every time. So it wasn't what I was thinking I guess.
I am running 2.1.7.121, but I don't think that will make any obvious difference.
I seen the same but I believe it's more a dashboard refresh issue, not sure, most of my switches use the generic smart driver, 2 of them use your driver and other 2 use the zooz scene driver.
There is a bug in 2.1.7 (that was just identified a few minutes ago) that could cause state changes to not update in a specific, low frequency situation. It mainly would be seen if you are using zwave device associations.
But as troy is on 2.1.6, that would not apply to his situation.
I have these issues with my GE Fan and Dimmer switches starting with the update last week. My rules will fire to turn on my fans in the bathroom but don't trigger off anymore; same as dimmer switches.
GE Fan Switch using built-in GR Fan Driver
GE Dimmer (14294) using Jason driver
For this, I assume you are using the "GE Z-Wave Plus Dimmer", and are on the current version? I ask because versions <2.1.0 definitely have on/off reporting issues on some firmware revs. If using a different driver, let me know.
If you turn on debug logging, do you see any errors?
I don't know of any changes in 2.1.7 that should have broken this driver. I don't have a lot to go off of, because my 14294 are working fine on 2.1.7.121...
I just tested every feature on it as a double check. Maybe there is something else entirely going on?
It was stated above that I am on 2.1.6. That is not correct. My problems started with 2.1.7.118, and continued with 2.1.7.121.
I rolled back to 2.1.5.124, found my backup from right before the upgrade to 2.1.7.118, then recreated all my changes since then (was only 3 days ago).
All my GE Smart Fan switches (using Built-in Driver) don't trigger rules for the OFF events starting with 217 updates.
I would rather not rolling back to 216 but what choices do I have? Is this support can help or it is a GE driver thing? I can turn off these devices in the Device page; no with rules.
Sorry for the troubles. Are there any errors in your live logs when a rule is running? For more details about troubleshooting, please check out this document:
