Dimmer Is Not Turning On without Specific On Command: Platform Change? (1 Feb 2023)

I initially had this issue when adding a new virtual dimmer: [ST Edge] vEdge Creator: a virtual device generator for end users - #1280 by NickA

But now it is preventing a routine from turning on a physical dimmer unless you add “Turn ON” and dim level, this was not the previous behaviour, as all my routines for dimmers only use a dimming level, until now. At this point it is only one of 27 that I have had to change, it is a GE Zigbee and I have others of the same model, it is using @philh30 GE Zigbee Switch driver.
Has anyone else had this occur with their dimmer routine?
Do we need to change all of our dimmer automations?


It is slowly progressing through the house 3 more have stopped working so I am going to have to bite the bullet and change all of my dimming routines

Tagging @johnconstantelo just because he has a lot of Zigbee devices and might have observed something.


1 Like

Yes, and only with my switches. My bulbs don’t behave this way, and neither do my other dimmable non-switch devices, like the LED rings in my Halo smoke detectors. All Zigbee btw.

What I’m seeing is if the dim level is already 100% and you set the level to anything less than that, nothing happens; BUT, if the level is anything other than 100 and you set it to 100 the light will come on. You don’t need a routine to see that happen, just do it through the app on the dimmer. You will also notice the slider “jump” back to the original setting before going to what you selected. In other words, if my dim level was 100% and I selected 50% by moving the slider, it jumped back to 100% and then jumped to 50% but it never turns on the light. If you reverse that process and select 100%, the same “jumping” happens, but this time the light will turn on.

FYI @nayelyz, this is something new that I’ve not seen before.

1 Like

I just wanted to vaguely say that the handling of dimmers does seem to have exercised the minds of the engineering staff over the last few months as seen in various pull requests. Whether those creating drivers are singing from the same hymn sheet as those developing the apps isn’t always clear, and I don’t think the community really know what the hymn sheet says.


I suppose this is as good a place as any to mention that many community members would like the option to change the dim level without actually turning the device on.

This is commonly used when you want the device to be ready for the next time someone manually presses the switch, but you don’t actually want the light on yet. Or you want it to be ready for the next time a motion sensor triggers it.

For example, there might be a use case that from 7 AM in the morning until 11 at night, the light comes on at 100% when the switch is pressed. But from 11 PM until 6:59 AM you want the light to come on at 60%.

So you have a routine that changes the dim level every night at 11 PM. But that doesn’t mean you want the light to come on then. You just want it to be ready to come on if needed, but not at full brightness during that time period.

This does mean that you are separating the “on” setting, and the “level” setting, but that’s what the third-party standards do for Z wave and Zigbee.

I have seen on some other Z wave platforms a convention that setting to 100% means “set and turn on” while setting to 99% down to 1% just changes the level and requires a separate on command to turn the light on. (Setting to 0% also turns the light off.)

I suppose it’s possible that if they’ve hired some engineers who had previously worked on one of those other platforms, they might have brought that convention with them. :thinking:

By the way, you see the same conventions in some dumb dimmer switches. The ones with a rotary dial. For some of these, turning the dial changes the setting, but doesn’t turn the light on or off – – you have to press the button in the middle to do that. For others, any change on the dial, turns the light on to that setting. And there are even a few, particularly the ones designed for “mid century modern” homes from the 1960s, where turning the dial does not normally turn the light on until you press the button, but if you turn it all the way as far as it will go, the light does come on to maximum brightness.

So there are different ways to handle this, but I agree, it would be nice if the explanation to the end-user was clearer. And for an automated system, I do think it makes sense to provide the option to only set the level. From a UI standpoint maybe this should be a checkbox for “turn on” with a default of checked. That way doing the minimum work in setting up a routine would cause the light to come on at that level, but you could uncheck the box if you only wanted to change the level in order to make the light ready for the next time it came on. A “baby sleeping” option. :baby:t4:



What do you have Default Dim Level set to on the misbehaving dimmers? I remember running into this issue a while back and I think the problem (or maybe the solution?) was setting Default Dim Level to either 0 or 100.

1 Like

3%, 10%, 60% on one
25% on two others.
I have never used 0%, only off, also I only have one dimmer that uses 100% and that is in the garage.

I have a gut feeling this is somehow tied to Smart Lighting as if I remember correctly in the old version you had to turn it on and then dim it, but I stopped using Smart Lighting to go on to the edge beta. I don’t use the new edge version as I never liked that it was so visibly disconnected from routines and devices.
Guessing someone updated it to match the new smart lighting?