If the use case is there they make sense. I have 5 total in my house. Many more Inovelli dimmers/switchs. Because not every application fits. The other place I have the switch version of the Jasco is the switch on the stairs down to the basement. Because this guy is so fast by the time you turn the corner it's on. However that guy stays in Occupancy mode ALL the time. Then I have a Zooz and an Enerwave in the laundry room keeping the lights on as long as someone is down there. The Zooz also serves to track humidity down there.
My masterbath is similar to yours. The Jasco can't see the whole thing, it's just by the door. So this gets the lights on quick. Then an Aeon 6 in the ceiling seeing the toilet and shower area (shower is pretty open so this works) and humidity for controlling the fan.
Me too.. I specifically decided to let the occupant decide if a fan "event" occurred and turn ON the fan (switch, in my case.) However, OFF is left to Hubitat: 4 mins after motion stops, the fan will go off.
Since the motion dimmer (and switch) don't support double tap in hardware, you likely won't find it in many Hubitat drivers (user or other).
You have options, though.
There is a ST driver for it that supports triple tap in software (has to be triple tap, because when in occupancy mode the motion sensor counts as the first "ON" event). You could port that to Hubitat.
You could ask a developer to add it to the driver (make a new user driver that supports it). May/may not have success there.
I am seeing Null Pointer errors on this driver and can't seem to figure out why. I know you haven't touched these in awhile and maybe this doesn't affect any functionality but hitting the refresh button doesn't seem to do anything and I suspect this is the reason. any suggestions?
I have confirmed that refresh is not happening at all, not automatically, nor when I hit refresh. If I hit each setting button on the device screen individually the state refreshes. But otherwise not.
Sorry, have been busy with work and kids lately. I did nothing with the buttons when I ported it. Something must have changed on the HE side that is no longer compatible with the methods the driver uses. I'll try to take a peek at it.
I second @aaron. You guys with the development skills I no longer have make these products what they are. I really would appreciate getting Michael Struck's full functionality working. I am in the process of porting over my SmartThings and in a couple of rooms I made use of buttons, Association groups, and the functions setMotionSenseOff() as well as Med, Low, High. Also Used setTimeout(), Occupancy and Vacancy. Most important is button press.
Thanks for this driver. Exactly what I needed. Integrated driver does not expose the important features of this switch, which is setting things such as occupancy mode for zero lag pir to switch lights instantly. Thank you for your work.