Quantcast
Channel: Configuration - Home Assistant Community
Viewing all articles
Browse latest Browse all 95541

New Scenes Editor

$
0
0

@reclusivemonkey wrote:

I read about the new changes to scenes in 102. Most of my scenes pointed to scripts, with just the odd one or two entities in there, so no problem I’ll just add everything to scripts and trigger the scripts from the scene. I thought this was my best option as I use both Alexa and Siri in conjunction with HA and I wasn’t sure they would both ‘support scripts’, but they have always handled scenes fine.

However, my scenes no longer seem to trigger my scripts. Here is an example of a scene;

---
- name: bedtime
  entities:
    script.bedtime:
      state: on

Pretty simple. Yet it does not turn on the scene in HA, and thus neither from Alexa or Siri. I get no errors in my log. Nor does it register in the logbook as being turned on. When I turn the script on using services, it works fine.

Well ok I thought, if my ‘scenes’ are just going to point at a script I may as well use the new scenes editor (I prefer yaml in most areas) so I set this up, and added the scene.bedtime entity. Except adding the scene seems to be in the ‘off’ state. I can also see this is the case in the scenes.yaml file.

Now I think I can fix this by just completely abandoning scenes and working with scripts. I am guessing they will work with Alexa and Siri (once I remove all the old scenes of course as there will be naming conflicts). My post here is not so much asking for help, but wondering if I have completely got the wrong end of the stick with the new scenes or is there something amiss here? If 102 was the first version of HA I had installed, I would be completely scratching my head here. Has anyone else had this kind of experience?

Posts: 3

Participants: 2

Read full topic


Viewing all articles
Browse latest Browse all 95541

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>