I still have a few of the old GE ZWave Plus toggle dimmers around (14295), which I like for 3 ways since the companion switch has the identical look and feel to the dimmer (using Zooz makes me have a on/off conventional switch as the companion). At some point in the past year, they have all stopped reporting status to Hubitat, or Hubitat has stopped recognizing their status updates. Reincluding them has no impact. I am using Jason's "GE Zwave Plus Dimmer" driver. I have just switched my C-8 to Zwave-JS, and the Zwave log shows the following when turning the switch on:
I have seen posts here saying Zwave JS breaks older GE Dimmers. Since I have a few, I have been holding off on going to JS. I also have some Fibaro devices, which apparently also don't play nice with JS.
I have not heard if that has been resolved, but there are the lots of JS updates in the latest platform release.
If they still don't work on the current platform, from what I have read, you can just revert back to Zip and get everything working again, and then replace those devices to move to JS in the future.
I'm just staying with Zip for now, I have no specific need for JS.
Ah, that's interesting. As far as troubleshooting goes, it may be more difficult to figure out since you made a change that potentially causes an additional issue with those devices.
I'm one platform down from current, and my older GE dimmers have been working fine. You can try air-gapping them buy pulling out the slider for a few seconds and see if they reconnect. I would also pull up the Zwave logs in settings and see if anything happens when you send commands from the switch. Maybe they are just dead?
Last resort I would factory reset them and try re-pairing them to the hub. You can try swapping in a virtual device, then delete the driver and and exclude, then re-pair and swap it back with the virtual device placeholder, to keep your device ID the same for apps. Personally, I've always had issues with swapping, so I would just remove it, re-add it, and then edit apps that were using the dimmer to use the new driver instance, if it works after that.
Just to be clear, this issue is not limited to one switch, it is all of this switches of this type in my setup (4). At some point, they all just stopped transmitting status, although they still accept Z-wave commands which makes no sense at all.
As a solution, I ordered 2 of the new Enbrighten ZWN3018 800LR toggle dimmers, which still work with the old companion switches (Enbrighten Z-Wave Long Range Dimmer Switch, 800 Series, Toggle | Line/Load Swapping, Direct 3-Way (No Add-On Needed), White or Light Almond, Hub Required, Works with Alexa & Google Home - Amazon.com). They are smaller than the older switches, don't have heatsink fins, and the toggle portion lights up when the switch is off, in one of 8 colors. The only problem is that they removed the ability to set the ramp rate for on and off, which is a big step backwards. All the ZWave Parameters dealing with ramp rates for on/off and local/remote have been removed. The only way to set these dimmers to "Instant on/off" is to set them to Switch Mode, which removes dimming functionality entirely.
Not really anything I can look at here.. The device stopped reporting before the migration, so it's not a ZWave-JS issue..
There is nothing in the logs so it appears that it just isn't reporting..
The only thing I could think of is possibly an association issue, which doesn't really make sense as it just stopped one day and this problem should have been from the beginning..
But you could switch to the "Generic Z-Wave DT Multilevel Switch" driver and hit configure.. If it's an association issue, it will start reporting after..
After scratching my head about this for a while, and adding/excluding/testing several of this model of switch in a test rig, I finally came back to the old IT support question "Did you try turning it off and back on?". My hub is on a UPS, and while it has been rebooted several times for updates, I recalled that the Z-Wave radio does not reset unless power is removed entirely. Once I did that, I found that newly included switches reported their status once again, but those included long ago did not. Excluding those switches and including them again restored their reporting capabilty as well. Mystery solved!
