Please help, when I save any scene it turns off every light

[hyperfive (dan)]

Hello,

For some reason every time I edit a scene and press save, it turns off every single light in the house.

The scene I am editing only has 3 lights in it.

Thanks for your help!

Dan

[Mats789]

Seems strange. Could you share your scene perhaps? Look in the logs what triggered this.

[123 (Taras)]

@hyperfive

every time I edit a scene and press save

When you do that, it not only reloads all scenes, it also immediately activates all of them. It’s a known, and undesirable, behavior and mentioned in the following WTH:

WTH is there no way to create or edit scenes without realtime state changes?

It isn’t at all intuitive that editing a scene will immediately apply it. This is often incredibly inconvenient, and sometimes potentially dangerous. I might want to edit a scene involving a door lock, or a valve or switch that controls an important appliance, or any number of things where actually applying it would be undesirable. It seems like the default should be to be able to edit and make changes without those being applied in real life, with a “Preview Scene” option to use if desired.

[hyperfive (dan)]

Thanks everyone for the help, I figured this out and feel silly why this was happening.

I looked at the logbook and quickly figured out what the issue was.

I have a scene (goodnight) that when activated triggers an automation to run (more goodnight features). When digging in, I incorrectly configured the goodnight automation to be triggered upon a state change of the scene, which was working. But it also gets triggered when the scene becomes unavailable, which happens to all scenes right after you make a change to any scene.

So I had to change the automation to be triggered by the call_service event.

 event_type: 'call_service'
    event_data:
      domain: scene
      service: turn_on
      service_data:
        entity_id: 'scene.my_scene'

Hopefully this helps someone in the future

Thanks again for the help.

[123 (Taras)]

@hyperfive

gets triggered when the scene becomes unavailable

You can use a State Trigger’s to, from, not_to, and not_from options to fine-tune which state-changes to accept/ignore.