Table of Content
Nothing terrible just wanted to make sure that I was understanding the right way. Input - If an intent matches, it can trigger a transition to another scene. This stage adds a slot prompt for a single, unfilled and required slot. If you don't define any slots in the scene, this stage does nothing. After condition evaluation, if the scene doesn't define a transition, it continues to slot filling.
I believe the exact same thing is happening to the scene and script entities. Except in our case, scenes do not have a standard view in the Google Home app so we’re unable to move them into a room from inside the app. Here I can see the scenes in Google Home that I added through Home Assistant. For example, “unlock” isn’t an available starter, but you can set “lock” as an action.
Sample EXECUTE commands
If the doorbell rings in the evening, turn on the porch lights and set the light brightness to 75%. Set your smart lights' brightness and color when the TV turns on. All home members can check when a household Routine starts. A household Routine where Google Home turns on your connected porch light and sets the thermostat to 75°F everyday at sunset.
This method allows you to execute any number of actions when the scene is enabled, even those that aren’t currently natively available via Google Home (HVAC, audio control, etc…). But, if you need to change any setting (brightness level, color, etc.), you need to go back into the code and change the rule. If you think this could be a hassle over the long run, go on to method 3. Google Home supports the concept activating scenes to simplify common room configurations. This trait allows users to group devices under the same service and update them simultaneously. It’s very similar to the routines control inside Google Home, but instead, the scene handling is done by the respective linked service.
Ways to start a Routine
Prompts - Assistant delivers the prompt queue to the user and clears the queue. The prompt queue is the merged collection of prompts that were aggregated since the last time this stage cleared the queue. Dialog separation - In combination with intents, scenes let you group dialogs into logical chunks, giving you easy ways to build user request and Action response pairs. I haven’t been able to figure out how to assign a scene to a rooms inside the Google Home app.
For no match and no input events, the scene, by default, transitions to the End conversation scene after three occurrences. Transition - When a scene meets criteria that you define, such as matching an intent or completing slot filling, you can transition to another scene to carry out even more logic. Alternatively, you can transition to the End conversation system scene, which ends the conversation with the user.
Device STATES
The device supports the ActivateScene command with the deactivate parameter to true. Action.devices.traits.Scene - This trait is used to implement virtual devices together with the SCENE device type. I ended up creating virtual switches that I control from Google Home, as the scenes did not appear at all. To add items to the scene, or add new scenes, follow the commented steps in the code above. In this post , I will show you 3 ways to set up scenes in openHAB and connect them with Google Home/Assistant for voice control. It would be great if Google added a UI to manage scenes, or increased their visibility in the Google Home app.
Sign up to receive personalized promotional communications aboutSignify related brandson their products, services, events and promotions.Learn more. True to cancel a scene if it is reversible, false to activate a scene. Devices with this trait may report the following attributes as part of the SYNC operation. To learn more about handling SYNC intents, see Intent fulfillment. Probably the Google Home Routine is a hood choice, but you might see the same issue as I listed before.
action.devices.commands.ActivateScene
For multiple secondary devices - just repeat the last 'Set' line as necessary for all devices in a scene. Just remember you cannot set KPL buttons that way - you need to create a scene with only that button in it. Also - there is no point setting a KPL button to the state - it's only either on or off... I don’t think Insteon scenes support the ‘direct dim’ command like dimmer lights do. 9) When a “Device” has been added successfully it will appear in the “Spoken device list”.
In fact I’m not even sure where GH is supposed to display the smartthings scenes, it seems that it changed over time. The latest info i found was to create a routine and add an “adjust action” scene, however in there I also cant see anyof my ST scenes. What I have found is that scenes do not show up for other google home accounts unless the SmartThings scene is assigned to a room. This worked for me in the past but now it seems that the Google Home app crashes when I try to add an ST scene to a room. I have since created virtual switches and created automations to run a scene when the switch is turned on. Then you just add it to a Google Home routine to hide the ugly command (“Turn On Good Night Scene Switch”).
It’s very easy to set up, you just need to tag the switch with a Lighting tag and connect Google Home to your myopenhab cloud and it’s much quicker than ifttt. Main post updated (added Method 3.5) - with the generic rule implementation you suggested, @rlkoshak . It works well, I just made a few minor changes (kept “Scene_” in front of all the items, for easier persistence definition (all “Scene_” items can be persisted by one statement). The LightingScenes group is not required, but you can add the whole group to your main sitemap, for example, and make all scenes available from that screen.
I haven’t had issues with this, but if I find the time, I’ll probably put all my scene storage items in a single group, and persist that group between restarts. Ah but routines are just one of the methods I listed above- you don’t need them! The only reliable place I could find scenes are when I am editing a routine… under home controls… under the scene adjustment option. Or if I know the “✨magic phrase✨”, I can say something like “Hey Google, activate the monthly driveway lights”. So a piece of advice - make your ISY scenes into Google Switches, or if they are simple, make them Google Lights. Once I reset my mental model and changed my scenes to switches VIOLA!
No comments:
Post a Comment