Yes, to a degree. There are two activation methods to deal with - local and zwave.
You can handle the zwave level easily using the apps such as motion lighting or rule machine.
Local on the other hand is more difficult to manage and has three possible options:
- Use rule machine to adjust the level when turned on based on desired criteria such as mode. The light would come on at the previous level first, and then be dimmed accordingly. Nothing like 100% brightness at 2am when trying to use the restroom
- Use rule machine to adjust the level based on mode, instead of waiting for it to be turned on. This would set the dimmer to the desired level for when it’s next turned on. However, this will cause the light to be turned on. You can immediately turn it off, but this could cause confusion as lights would be randomly turning on/off.
- You can change the default level local preference on the dimmer. The switch will always default to this level when being turned on with the switch. It would avoid both of the problems above, but still isn’t the cleanest solution. You still lack the ability to change the default level based on the mode.
The ideal solution at least in my mind would be to expose the default level local preference as a custom command. A great example of this would be @BertABCD1234’s custom driver here: Hubitat notification LED The default and notification led values are exposed with his driver.
I’d be happy to help test the functionality if he was willing to code it, which is beyond my ability.