Yeah, you can do that for basic on/off under the device. However, I have SL routines that change the behavior of motion switches during certain hours. I use it to vary the intensity of the light based on motion vs the switch being activated. That can only be done via a routine. I suppose I can write two routines for two different time intervals but that’s a regression from what SL offers.
1 Like
+1 on exposing dim level if you have time, it would be greatly appreciated
1 Like
I will be pushing out a driver update this Saturday (Feb 12, 2022) that will require a hub reboot.
This update will add the dimmer’s default level as a custom capability so that it shows on the detail view and can be used in automations.
Adding custom capabilities to drivers is currently a bit messy - when your hub receives this update the driver will hang, and hub control (app control, routines, scenes, events, smartapps) of your motion switches/dimmers will become nonfunctional. Physical control (including motion activation of the light) will still work. I anticipate that you’ll be impacted by this even if you only have motion switches, and no dimmers.
A hub reboot will be required after your hub receives the update to restart the driver and resume hub control. The easiest way to reboot your hub (and the only way to reboot your hub remotely) is, ironically, through the Groovy IDE’s My Hubs tab.
The update has been pushed out. The version of the driver will show as 2022-02-12 when the update is applied to your hub, which should happen sometime in the next 24 hours.
If you have the CLI installed and would like to force the update immediately, you can use the smartthings edge:drivers:install command.
1 Like
I didn’t get the driver update… even after pulling with the CLI. Still on 02-03T19.
1 Like
Odd. I’ll try packaging the update again when I get home in a few hours.
1 Like
Packaged again. Version should now be 2022-02-15T if you want to try pushing it through the CLI.
Very strange… I pushed through CLI again… tried rebooted hub after an hour of not getting it…still on 2022-02-03T19… Other drivers (for other device types) have recent updates.
Check if your device is on the more generic GE Z-Wave Switch/Dimmer/Fan/Outlet - that driver supports the motion switches/dimmers (and was last updated 2022-02-03T19) but doesn’t have the custom capabilities to control the configuration parameters. If it is, then use the driver change tool in the app to swap your device to this driver, which is the GE Z-Wave Motion Switch/Dimmer driver.
I have the 0215 driver update for the motion switch/dimmer and rebooted the hub, but i don’t see the brightness level anywhere for control on the device settings or the automation settings. Im wondering if im missing something?
I removed it from the settings menu so as not to conflict with the detail view. It should show up on the Dimmer as the last item on the detail view and also here in routines:
Any luck? If it shows on detail view as a crossed out cloud, swipe down on the screen to trigger a refresh and it should poll the device for the current setting.
Try swapping to my generic GE Z-Wave Switch/Dimmer/Fan/Outlet driver and then back?
no change 
Which model/fingerprint is it? Is it otherwise showing as a dimmer, with current dim % as the second capability on the detail view?
I have the ZW3008 jasco switch which I understand to be the equivalent of 26933. I dont see the dimmer capability though.
It sounds like it’s being mapped to the switch profile, which doesn’t have either of the dimmer capabilities on it. Your device does act like a dimmer though - if you hold the physical buttons up/down it increases/decreases the dimming level?
Do you have the CLI installed? If so, could you run smartthings devices, find your device in the list, and then run smartthings devices <device id> -y? I don’t recall what the field is labeled, but you should see your device’s fingerprint somewhere in the list in the form of 0063-0000-0000.
Should be:
deviceManufacturerCode: 0063-494D-3034
1 Like
it works, sorry about that, thanks for the help!
1 Like
No harm done, but the following lines are repeated in capabilitydefs.lua:
capabilitydefs.TimeoutDuration = {}
capabilitydefs.TimeoutDuration.name = “platinummassive43262.jascoTimeoutDuration”
capabilitydefs.TimeoutDuration.capability = capabilities[capabilitydefs.TimeoutDuration.name]
I just happened to be looking at how you handled the custom capabilities.
1 Like