Sometimes my wife will dim the light down to say 20%. Then later one of us will turn the light off.
I cannot get the Motion Lighting rule to turn the light on to level 100. Please see my rule below and let me know what I might be doing wrong. What ends up happening is the rule will turn on the light, at the last level it was previously on at.
Try it from the dimmer's device page, and see what happens there.
Thanks for the suggestion. I tried the following: I toggled off āuse last level for onā and set the āon levelā to 100. Still, seems to use the last level that was on.
After saving these changes:
I dimmed the light to 10%, then turned them off. I then asked Alexa to turn on the light, but the light turned on to 10% instead of all the way up to 100%.
What kind of device is this? CasƩta or RA2?
Caseta
You likely set the upper and/or lower dimmer trims... See here to adjust
Thanks but I donāt think this is related. I can get to 100% brightness when I physically press the dimmer or when I ask Alexa to turn on the light at 100%.
@bravenel thanks for taking a moment out of your busy day (weekend I should add) to post/help. Is there any chance you might have any other suggestions?
What happens when you control the device from its device page? Can you (a) set the level to 100? (b) turn it on/off after that?
We need to isolate where the problem is, so we start with the device page.
@bravenel yes, I can set level and also turn on/off from the device page. However, note that Iāve toggled off āUse last level for on?ā Yet it still powers on to the last level it was on.
Iāve even set the āon levelā to 100 but the last level on is always used.
You are misunderstanding me it seems. Forget about the toggle for Use Last Level on, and the On Level setting. When you do Set Level 100 what happens with the light?
It turns on to 100
OK, and now do On and Off work as expected?
Yes.
The Motion Lighting instance you showed above uses Set Level to turn on the lights. So if that isn't working, the next step would be to turn on logging for that app, and show what happens when it tries to turn on the lights.
Not that I have much to add here, but just to throw out a quick thought . . .
I noticed:
Are you trying to use both a "Dim" and a "Switch" setting to turn on the lights? Try only the Dim.
I'm thinking if you are using both, you may have set up a race condition where the Dim tries to set to 100%, but before it completes and updates the "level" property in Hubitat, the Switch to "on" reads the now-outdated Hubitat level property of 10% and then retries turning on the light, again via setLevel, but this time, using 10% from the level property and effectively negating the prior attempt to turn on to 100%. Basically, you may be getting "Set to 100%, Set to 10%" in immediate succession, so you never notice the 100% attempt.
Just grasping - maybe it helps. Good luck.
Yeah, sometimes people don't understand that setLevel turns on a light, and that it doesn't need a separate on command.
Yep - an easy mistake to make. I recall that, in some of the Hubitat apps (I forget which apps -- maybe the "Groups and Scenes" app), if a device is a dimmer, and has both a level as well as a switch setting, it only appears in the "select dimmers" device selection section rather than in both the "select dimmers" and "select switches" so that you don't get this confusion. Those seemingly minor refinements are a nice touch to help avoid errors.
Based on your advice I removed the āturn on switchā command and just left dimmer level command on. Your flowers sir: 
@bravenel When I use Alexa to turn on the light, it continues to use the last level setting, even though I have disabled that option on the device page and the On Level is at 100.
Attaching the log.
Alexa was able to turn on the light, but the level used was 41 instead of 100.
Download the Hubitat app
