Looks like it major issue for me as well.
From 70+ devices I migrated so far is about half of them
Jasco Zigbee Dimmers
- endpointId: 01
- application: 12
- model: 45857
- manufacturer: Jasco Products
Example: This will not run
Looks like it major issue for me as well.
From 70+ devices I migrated so far is about half of them
Jasco Zigbee Dimmers
Example: This will not run
Thanks for posting further details! @bravenel and @chuck.schwer contacted me yesterday via PM so Hubitat engineering is definitely aware and investigating a solution.
Is there anything one can do if every switch action is shown as ādigitalā, no matter whether I do it physically or remotely?
Is this a device limitation or could it possibly be fixed via device driver? Any way I can get my hands on the generic Z-wave switch device driver code so I can mess around with it?
Just reporting that I see the issue as well.
I can turn on/off GE Z-Wave Switches and Dimmers within hubitat, but no log appears whatsoever. In addition, Physical presses do not show up in the log and consequently cannot trigger rules.
FWIW my Zigbee Generic dimmer reports logs just fine.
Which driver did you use for this device?
We have a generic zigbee switch driver, but not a dimmer driver.
Can you try the generic zigbee switch driver and see if it reports physical? If it does I should be able to create a dimmer driver for these...
There is a zigbee dimmer driver but it looks suspect...
I'm using
ZigBee Dimmer System
I changed it to
Generic Zigbee Switch System
still no joy.
Based on this
It will probably take some extra effort to solve it.
I have a ge zigbee dimmer headed my way to tune a driver for it, we already support the ge zigbee switch which reports correctly.
It should be noted that ge has both zigbee and zwave devices. The older non reporting zwave devices require polling to retreive their status, due to ge not wanting to pay the licensing to Lutron, we are reviewing options to resolve this.
I have been PMāing with @bravenel and @chuck.schwer regarding this issue so I thought I would summarize additional testing that I did this morning for others to be aware of and maybe validate.
Its worth noting my house is two story and U shaped and my network closet is at the bottom of the U under the stairs on the first level. This is where my Hubitat hub, ST hub, and wireless router are located. All Hubitat devices are on the first level only as I havenāt migrated anything upstairs yet due to the physical event problem.
Bruce suggested turning off the ST hub to see if it may be causing interference so last night I shut down the SmartThings hub before I went to bed, left Hubitat in the same place and ran a zwave repair.
This morning nothing was different than before so the ST hub isnāt causing interference.
To summarize something is definitely up with distance from hub and physical event reporting. I have GE switches of different generations that all can report physical events if close to the hub: old Iris clamshell packaging, green boxed v1/2, and zwave plus fan controllers.
Donāt know whether it helps but every time I have attempted to add the GE Z-Wave summer it detects only as device and I have to go into settings to change it to generic Z-Wave dimmer.
Hopefully this can be fixed though; older model GE devices could be a hardware limitation of GE switch and not Hubitat. Still waiting on a response from Hubitat on my findings.
Yes I reported this to support and the finger print has been added but will be fixed in a future release.
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.