Prevent transitioning?

[fbloemhof]

In some situations, by example my toilet, I am seeing some unwanted behavior. The last time the lights were on it was mid day so they were on full brightness and high kelvin. When they again get triggered later on in the evening, the light initially turns on at this state and then transitions to the state as AL wants it.

Is there a way to prevent this?

I am using Zigbee2MQTT if this matters.

[basnijholt]

Do you have separate_turn_on_commands enabled? If so, this is the expected behaviour.

[fbloemhof]

Nope, that is disabled. I can repro it with the default config. 27 jan 2024 21:40:45 Bas Nijholt ***@***.***>:

…

Do you have *separate_turn_on_commands* enabled? If so, this is the expected behaviour. — Reply to this email directly, view it on GitHub[#912 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACCZAO62XIIYKGGOVXMQDUDYQVQ4NAVCNFSM6AAAAABCNSUGCSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DENRXGQYTI]. You are receiving this because you authored the thread. [Tracking afbeelding][https://github.com/notifications/beacon/ACCZAO2OZBFYUPJQ5SRIXP3YQVQ4NA5CNFSM6AAAAABCNSUGCSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAPYTJM.gif]

[basnijholt]

Then perhaps your light doesn't allow to turn on with arbitrary settings. You can try this out by turning it off and then calling light.turn_on with different settings than what it had before it turned off.

[fbloemhof]

Hm indeed, same behavior. Then it perhaps is an Z2M issue. 27 jan 2024 22:31:04 Bas Nijholt ***@***.***>:

…

Then perhaps your light doesn't allow to turn on with arbitrary settings. You can try this out by turning it off and then calling *light.turn_on* with different settings than what it had before it turned off. — Reply to this email directly, view it on GitHub[#912 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACCZAO4XS3WZZQ23KSEEIV3YQVWZLAVCNFSM6AAAAABCNSUGCSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DENRXGY2TS]. You are receiving this because you authored the thread. [Tracking afbeelding][https://github.com/notifications/beacon/ACCZAOZE2CJGEWISOACE7RDYQVWZLA5CNFSM6AAAAABCNSUGCSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAPYTYW.gif]

[fbloemhof]

When I bypass the Z2M group the behavior differs. It still seems a little off but it is better then using the Z2M group. Will do some more testing later. 27 jan 2024 22:38:26 Freek ***@***.***>:

…

Hm indeed, same behavior. Then it perhaps is an Z2M issue. 27 jan 2024 22:31:04 Bas Nijholt ***@***.***>: > > Then perhaps your light doesn't allow to turn on with arbitrary settings. You can try this out by turning it off and then calling *light.turn_on* with different settings than what it had before it turned off. > > — > Reply to this email directly, view it on GitHub[#912 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACCZAO4XS3WZZQ23KSEEIV3YQVWZLAVCNFSM6AAAAABCNSUGCSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DENRXGY2TS]. > You are receiving this because you authored the thread. > [Tracking afbeelding][https://github.com/notifications/beacon/ACCZAOZE2CJGEWISOACE7RDYQVWZLA5CNFSM6AAAAABCNSUGCSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAPYTYW.gif] >

[fbloemhof]

With an HA light group the behavior is the same. Only when I call a single light it seems ok (but I still can see some transitioning).

[fbloemhof]

Okay considdering my test results in Koenkk/zigbee2mqtt#21081, it seems a Zigbee thing.

Is it possible to work this around in AL by intercepting the light.turn_off and setting some values somewhere in the middle? From bright to lower bright is more annoying than in reverse.