David

> > > From a different bug, but EN-US translation: >  Then I would assume that the text in french is "Au prochain lancement". But unfortunately I don't really...

> > > > We are not able to trigger the scene twice without having to wait for a fix delay; > > Why? This is more theoretical than a...

> > Ok thanks for the clarification @dr1rrb :) I will implement this, just one question, with scene you mean the `central_scene`? Are your scene sensor actually looking like this:...

Hey @robertsLando , I finally took time to validate that. So for the discovery I used ```json { "type": "trigger", "object_id": "scene_down", "discovery_payload": { "automation_type": "trigger", "type": "button_double_press", "subtype": "turn_off",...

BTW I just realized that if for the `subtype` we could just use `button_`, there is no easy conversion between central_scene items in the OZW device config and the `type`...

@robertsLando I would love to, but I already have a lot of pending projects (the life story of all of us ;)). So it probably won't be before the end...

This should have been fixed now, could you please validate if the issue is still present @sakshi173 ?

This would also help to: - Ensure that a newly implemented feature is not accessible only through internal APIs - Detect behavior changes on WinUI.

This is a regression introduced by https://github.com/unoplatform/uno/pull/15946. Reverting here https://github.com/unoplatform/uno/pull/16253

@jeromelaban