@JBR Could you post a screenshot of your automation?
Try removing âturn onâ from the routine. Depending on which model this is and how you have the default dimmer level set (if thatâs even one of the options in settings), it might be interpreted by the device as âturn on and set dimmer to 100%â. Meanwhile, the âDimmer: 50%â is all you need since the device interprets that command as also instructing it to turn on. How you have it set now, Iâd guess the dimmer is actually trying to go to 100% after that turn on command, but only making it up to a little above 50% before the 50% command comes in.
1 Like
That works! It solves for the âset then dimâ action that I was experiencing. The downside is when you donât set âturn onâ in the routine, you no longer have the âturn off afterâ setting available. The workaround is to create an additional routine that will turn off the lights if the sensors do not sense motion after five minutes. Thanks for help!
1 Like
philh30,
Thought I would check and see how the testing is going. Also - how does a new driver get pushed to âmy systemâ or is it the whole smartthing system?
Thanks!
New version dated 2022-10-02T20:15:36.272663991 will be pushed out to hubs within the next 12 hours. Or, if you have the CLI, you can grab the new version immediately with smartthings edge:drivers:install. I think this catches up on all of the recent requests, so let me know if I missed something.
This version changes the way that on/off and dim commands are sent to the device, since the default handlers were overriding the dimming speed settings. With these changes, z-wave commands should respect the z-wave dimming speed (step size and timing) configured in settings. @David_Donnelly
I think with this change, the âTurn Onâ command will no longer set dimmers to 100%, though that behavior may differ depending on model. @JBR
Parameters 16 (switch mode) and 20 (minimum dim) have been added to the middle generation of dimmers. @DavinD @evanhunter
Added. I couldnât find much information about this fingerprint, so let me know if the options in the settings menu donât seem right. @Npackard @jds13
Added. I couldnât find details on this one either, but based on the 3132 model ID, I donât think itâs one of the latest models, and is part of the slightly older generation. If youâre able to get triple-tap button events to show up, then let me know because that means I guessed wrong. @bpc135798642
@csstup Added LED indicator settings to plug-ins and added your fingerprints.
3 Likes
Replaced the groovy driver with yours which installed easily and works. I have dozens of these switches in vacation rentals and have the constant problem that people dim them all the way. Just turning them off confuses them. With your driver I can speed up dimming enough that it is less confusinfg, but my hope was to have them turn off immediately and still brighten and dim normally. What I find is the âall on/offâ timing is not triggered by the paddle switch, and speeding up dimming enough to make turn off instant basically disables use as a dimmer at all from the paddle switch. Correct? Iâm guessing that since you delved into these there are not config params to allow what i would like to happen.
You should ignore the âAll On/Offâ settings. They refer to a specific âAll Onâ command that z-wave controllers can send out to toggle all the lights in the network at once. ST doesnât use it, but itâs possible to have a secondary controller on a network that uses it. The Manual and Z-wave dimming settings will be the ones that youâll see an impact from.
Iâm not sure how to pull off what youâre looking for. One option you could try is that the update I just pushed out adds minimum dim level to the settings menu. Itâll only work if the firmware on the dimmer is new enough (5.26+) to support it. You may be able to set that to a level thatâs high enough so that the renters can never dim the light so much that the bulbs go completely dark. All of the dimmers I have installed now are from the newer generation which have different configuration options, so I donât know for sure how that particular setting will work.
Thanks for the driver, the info, and the suggestions. Will the update roll out on your channel invite/install page or is there another process to get it? I just installed today and donât have a minimum dim setting. If features are tied to fingerprints, the switch I just tried it on is older. I have new ones at another place.
I can get things workable after a fashion now. Wish I had known more about zwave before i bought GE dimmers.
Driver updates will automatically push out to your hub within 12 hours, sometimes much faster. Iâve enabled that setting on the generation of dimmers that could possibly have a high enough firmware version. If yours show a Button capability on the device detail screen and have settings for Association Groups 2 and 3 at the bottom of the settings menu, then theyâre new enough that you should see that new setting option pop up. However, whether it will work will still depend on the actual firmware version on your devices.
Awesome news, Iâll give in a try once the driver updates on my end. Thank you!
Regarding 0063/6363/3130 - it works fine. There is no LED indicator but presumably the parameter will be ignored. I donât use the device with Association groups but this may help other users.
I have two GE dimmers. 0063-4944-3339 (âge-dimmer-sceneâ) was perfect with your previous release(s). 0063-4944-3038 (âge-dimmer-assocâ) now works great! Thanks! Minimum Dim Threshold is perfect (and is necessary with my LED bulbs), and Z-Wave ramping now works as I hoped.
Thank you very very much for these updates! They are very much appreciated.
Thanks! 0063/6363/3130 is working. As far as settings, this plug doesnât have an LED, so the LED indicator setting isnât needed, but not a show stopper. Also, I just noticed I have 2 Jasco ZW3102
Energy Monitoring Lamp Modules (0063/4450/3031) that are finding edge drivers. Theyâre currently using the Z-Wave Metering Dimmer DTH. Any plans to support these? Thanks again.
Thanks @philh30, very much appreciated ! Everything is working using your Edge driver, including the Triple TapâŚ! The SmartThings app shows triggers up to 6 presses, toggles up or down. What additional info do you need to know about the switch?
I guessed wrong! That means it has the wrong options in the settings menu (some, like the LED, will still work though). Up to 6x presses is surprising - I havenât seen any go past 3x. Do you have the model number?
Thanks so much. Working good.
Philh30,
Wanted to let you know that all the features I asked for are present and working !! THANK YOU!
But (there is always a âbutâ), I am trying to nail down a strange behavior. That behavior is: at times, I will walk into my office, during the day, the motion detector will detect motion, but the light will not come on.
So, I turn on the light at the switch manually or via the SmartThing app. When I leave the room and after the no-motion preset time, the light goes off. When I then come back into the room, the motion detector sees motion, and the light turns on. (so on initial motion - no reaction?)
Now, this morning when I came into the office for the first time, the motion/light interaction worked and the light came on.
I will continue to monitor but thought you should know - in incase you see this behavior from others. Or if you have a solution.
And yes, this could be caused by a host of other sources: internet, home wifi, SmartThings, motion sensor, etc.
1 Like
Do you have the light detection turned on perhaps? That always drives me batty when I forget to turn it off and motion lights donât turn onâŚ
nathancu,
I am not sure what you mean by âlight detectionâ.
The motion sensor does work by itself, I see that in the SmartThings App. But sometimes the light does not come on when motion is sensed. And it seems to be somehow connected to if the light was previously turned on at the switch or via the SmartThings app.
But then again, like this morning when I walked into the room for the first time, the light came on immeditely.
But even that âseemsâ to be inconsistent. At the moment I think I am experiencing a random event(s) - maybe.
Sorry - *Looks at thread title again - thought this was the thread for the 24xxx/26xxx motion switch/dimmers - they coincidentally have a setting at Param 14 where an onboard light sensor can keep the onboard motion sensor from turning on the light. If this IS one of those - turn that offâŚ