topic Re: Is there a way for nested conditions? in Home Automation

Is there a way for nested conditions?

zludany — Sat, 24 Feb 2024 17:53:16 GMT

Why is the automation script below having an error thrown: redundant struct

metadata:

name: fitness custom

description: Scripted automation

automations:

starters:

- type: assistant.event.OkGoogle

eventData: query

is: "training time"

- type: device.state.TemperatureControl

state: temperatureAmbient

lessThan: 18C

device: Thermal sensor Wellness - Wellness room

actions:

- type: device.command.ActivateScene # Activate or deactivate a scene.

activate: true

devices: Wintertime Wellness ON

starters:

- type: assistant.event.OkGoogle

eventData: query

is: "training time"

- type: device.state.TemperatureControl

state: temperatureAmbient

greaterThan: 22C

device: Thermal sensor Wellness - Wellness room

actions:

- type: device.command.ActivateScene # Activate or deactivate a scene.

activate: true

devices: Summertime Wellness ON

Re: Is there a way for nested conditions?

salbando — Sun, 25 Feb 2024 22:35:27 GMT

In order to have more than one starter you need a hyphen in front of each occurrence of the word "starter" with the appropriate indenting.

Re: Is there a way for nested conditions?

zludany — Mon, 26 Feb 2024 07:16:02 GMT

Ok, where to put the hyphen??

I haven't seen hyphens in front of starters neither in code examples, nor by the pilot.

Re: Is there a way for nested conditions?

salbando — Mon, 26 Feb 2024 14:54:37 GMT

Here is an example:

metadata: name: Dog or cat notification description: Testing out the dog and cat sensing automations: - starters: type: device.event.AnimalCatDetection device: Front Yard camera - Front Yard actions: type: home.command.Notification title: Cat body: I tawt I taw a puddy tat members: - John G - # - Krista G - # - starters: type: device.event.AnimalDogDetection device: Front Yard camera - Front Yard actions: type: home.command.Notification title: Dog body: Oh, dog! members: - John G - # - Krista G - #

I should also remind you that in your example in the first starter block if either is true then that action will be performed. In other words, if you say "training time" OR the temperature is less than 18C then you action will be performed. It doesn't seem to me that this is your intent.

Re: Is there a way for nested conditions?

zludany — Mon, 26 Feb 2024 16:44:45 GMT

I can't see the much needed hyphens in your code by the multiple starters.

My identation was also seemed correct.

The error message was about repeating columns error in struct.

Where can i make the logical and formula definition?

Re: Is there a way for nested conditions?

salbando — Mon, 26 Feb 2024 17:13:56 GMT

The hyphen is how YAML stores multiple values for each key. If your familiar with programming it is how YAML stores array values. Without it, the script will see it as redundant or repeated values for the same single variable.

Re: Is there a way for nested conditions?

zludany — Mon, 26 Feb 2024 22:14:46 GMT

Ok, thanks, but how to put AND clause between the starters?

Re: Is there a way for nested conditions?

salbando — Mon, 26 Feb 2024 23:42:09 GMT

In general, all starters are always "or", but they are also a type of conditional because they are basically saying, "If starter, then 'the rest of the script tries to execute'." An "if" inside of another "if" is logically equivalent to an "and". Therefore, by making your ambient temperature a conditional, you will effectively achieve an "and". So your script would look something like this:

metadata: name: fitness custom description: Scripted automation automations: - starters: type: assistant.event.OkGoogle eventData: query is: training time condition: type: device.state.TemperatureControl state: temperatureAmbient lessThan: 18C device: Thermal sensor Wellness - Wellness room actions: type: device.command.ActivateScene # Activate or deactivate a scene. activate: true devices: Wintertime Wellness ON - starters: type: assistant.event.OkGoogle eventData: query is: training time condition: type: device.state.TemperatureControl state: temperatureAmbient greaterThan: 22C device: Thermal sensor Wellness - Wellness room actions: type: device.command.ActivateScene # Activate or deactivate a scene. activate: true devices: Summertime Wellness ON

You will notice that the hyphen that you had on "type" isn't necessary (it doesn't hurt either) because there is only one "type" per block now. Also, you don't need quotes in your OkGoogle query because you aren't using any other delimiter like apostrophe.

Re: Is there a way for nested conditions?

zludany — Tue, 27 Feb 2024 03:03:42 GMT

Thanks man.

I did it in parallel on my way, however it was the hard way figuring out on your own.