My Ge switches gave issues with physical in ST but something changed along the way and they started working with maybe a second delay on reporting (sometimes there was that delay sometimes not) so I hope this can be resolved
I just paired a GE Z-Wave paddle dimmer (12724) to Hubitat; also discovered as device. Not only are physical events not logged, no on/off action from the UI is logged either and no current state is displayed by the Hubitat UI (even when ‘Generic Z-Wave Dimmer’ is chosen for driver). Is this what everyone else is seeing with this device? Just wondering if it is worthwhile trying to redo the pairing process or just wait until this device is properly supported.
FWIW, when this device is operated from the SmartThings app, the event log shows:
2018-02-23 2:16:25.042 PM EST
moments ago DEVICE switch on Bedroom Lights switch is on true
2018-02-23 2:16:20.606 PM EST
moments ago COMMAND on on command was sent to Bedroom Lights true
The log shows about 5 sec. elapse from the app issued command to ST logging the new state of the device. That’s about what I see when looking for changes in the app to be reflected by my physical press of the switch.
Digital events are logged for me when I turn it on/off via web browser. If my hub is close then physical on events are logged. Sounds like you may have another issue happening if your digital events are missing.
Ah… things changed when I rebooted the Hubitat. i noticed that the UI wasn’t updating the current state for my other devices. Now it does show on/off under current states for the GE Z-Wave switch and digital events are logged.
If you find events not showing up, try opening a console (f12) and see if the browser is blocking a connection or throwing errors. This could be helpful to support.
I’m seeing one of my GE Z-wave switches not registering or logging On/Off events that physically happen. I can control the switch in the devices page for the device. The page/log will update the switches status to reflect the physical changes immediately if I press the Refresh button on the devices page for the device…
For example, I am glueing 2 switches together with Rule Machine. If switch 1 turns on, turn switch 2 on. If switch 1 turns off, turn switch 2 off and vice versa. They are not consistently doing this with physical switch changes and when they don’t, a device change is not logged or reflected in the devices page. If I go to Devices, select the device and then press refresh it wakes up, updates the devices status to the correct status (on/off) and runs the rule it missed making the other switch match the on/off status.
I have many of these setups as well affected by this issue. I have slowed down my migration from ST because of this.
Are these the older model GE Z-Wave? The first version didn’t have the ability to report instant change events due to patents and not licensing it. Manually refreshing the device will report back current state.
What others have done is excessively poll these devices for status. This isn’t ideal but we are exploring options to get status updates faster. Obviously we can get it on refresh, but repeatedly sending refresh isn’t ideal either.
Patrick please see my post above of additional troubleshooting. The older GE devices do report status if the hub is close. These were the Iris labeled GE switches in clamshell packaging.
What I find strange is my older batch of GE Z-Wave Switches (ones with larger LED) report physical status events immediately. My newer ones (ones with tiny LED) seem to be the ones not reporting physical events consistently. NONE of mine are Z-Wave Plus.
That looks suspiciously like a line voltage switch installed in a low voltage data-ring. There is a full junction box behind it, right? Not just electrical wires spliced in open wood? O_o
Ok good. As a commercial electrician, I’ve seen enough to know not to trust anyone to know what they’re doing. 
Thanks, yeah. Its odd, but it appears that lack of repeaters or potentially older repeaters might be blocking something as well.
The more info we can gather the more we will be able to sort out and find the cause.
Building solid mesh networks are tricky and sometimes difficult. I have plug in outlets all over my house to strengthen my mesh and its still not perfect.
We will get to the bottom of it, just takes time and more data. Everyone’s mesh and device mix is different combined with environmental differences, there isn’t a perfect model.
And the just add more repeaters doesn’t mean things will always get better.
Just out of curiosity, do you see any difference in reporting after a z-wave repair and about 20 minutes?
I’d like to just mention that both of the GE/Jasco switches that I mentioned are within 10 ft of the Hubitat and I ran ZWave repair after adding them.
So, quick question is the issue you are experiencing a display quirk aka the actual event is in the device event log but the device view doesn’t update properly?
Nope. It’s not in the event log. It doesn’t trigger the Rule Machine rule. Not until I hit refresh or programatically change the state in the devices page.
OK. So that means 1 of 2 things either the device didn’t send the status or we didn’t get it.
When you click refresh, we are sending out a command to the device and then we are getting the response.
Does moving the hub closer change anything?
How many other zwave hubs do you have running?
What I am trying to avoid is messing up my mesh for ST during this transition. I will move a few more switches and test a few scenarios this weekend and share results.
If you have any other ideas of things you want me to try, please let me know. I want to make this successful. But given other people that have migrated more devices are experiencing similar results I fear there is something else causing this or a backup plan is needed. I have mostly focused on one section of my house at this point as a test plus a few switches that turn on based on time of day.
@ogiewon curios to know how much of your HA remains on ST and how solid your Hubitat mesh is compared to what it was on ST.
