WTH State of scene?

[petro]

@123

Scenes set an entity’s state, they don’t monitor an entity’s state. So if various entity states happen to match a defined scene, the scene is not automagically turned on.

Yes, this is what I was getting at with my comments. Basically, scenes don’t have on/off states.

@code-in-progress

Not that I know of. They only have 3 attributes that I know of: entity_id (list of entities in the scene), id , and friendly_name .

All entities have a last_updated and last_changed. I don’t use scenes so I cant say if either of those are changed when the scene is executed. I would assume last_changed never changes if the state is always ‘scening’. Last updated may change when you activate it. Someone with scenes should toss this into the template editor and see what happens:

{{ states.scene.xxxx.last_updated }}

@sophof

Afaik it should be possible to create a scene sensor based on the entities in the scene. It seems to me for instance that it is possible to recreate such a sensor in appdaemon by simply subscribing to all state changes with the right condition and then checking if all states are ‘in place’, or am I missing something?

Yes it should be possible, I was trying to make it known about the complications behind doing this. I’m not against something like this, but we’d need to have requirements before implementing it.