topic Re: Conditions codes from script editor stoped working in Home Automation

Conditions codes from script editor stoped working

Ran_Shemesh — Thu, 01 Aug 2024 19:00:18 GMT

Hey everyone,

I'm having trouble with conditions in the Script editor. I used to have 3 automations that worked perfectly based on time of day and device status, but they suddenly stopped without any error message.

Here is an example for the triggers

- starters: - type: time.schedule # Required. Time to schedule automation. Accepts either clock time (10:00:00 AM, with seconds optional, or in a 24 hour format), or 'sunrise' or 'sunset', with an optional offset ('sunrise+10m', for instance) at: 21:30 # HH:MM (24 hours format). Adjust time as needed # Optional. Days of the week to run automation on. weekdays: - MON - TUE - WED - THU - FRI - SAT - SUN condition: type: and # "AND" together two or more conditionals conditions: - type: device.state.OnOff # The basic on and off functionality for any device that has binary on and off, including plugs and switches as well as many future devices. state: on # Whether a device with an on/off switch is on or off. <code>true</code> if the device is on, <code>false</code> if the device is off. [available operators: is, isNot] is: true device: curved lamp - Living Room

Has anyone else encountered this issue? Any suggestions on how to fix it?

Thanks in advance!

Re: Conditions codes from script editor stoped working

webnibbler — Sun, 04 Aug 2024 12:00:28 GMT

Just from the YAML provided in your post there appears to be only one condition for your AND where there should at least two. Was this just missed in the copy and paste?

Re: Conditions codes from script editor stoped working

Ran_Shemesh — Sun, 04 Aug 2024 13:07:40 GMT

This is how it was and worked.

So if I want to have time and divce state, what should be the conditions?

Re: Conditions codes from script editor stoped working

OpethNJ — Tue, 06 Aug 2024 04:26:05 GMT

Except you have one condition listed along with an AND statement.

That might be the confusion as the AND statement covers the CONDITIONS and not a CONDITION and STARTER

Re: Conditions codes from script editor stoped working

Ran_Shemesh — Tue, 06 Aug 2024 07:54:53 GMT

I tried this:

starters: - type: time.schedule at: 21:31 weekdays: - MON - TUE - WED - THU - FRI - SAT - SUN condition: type: and conditions: - type: time.between before: sunrise+60min after: 21:30 weekdays: - MON - TUE - WED - THU - FRI - SAT - SUN - type: device.state.OnOff state: on is: true device: curved lamp - Living Room

But this is still not working..

Re: Conditions codes from script editor stoped working

webnibbler — Tue, 06 Aug 2024 15:48:21 GMT

Try adding an ACTION at the end

actions: type: device.command.OnOff on: true devices: curved lamp - Living Room

Re: Conditions codes from script editor stoped working

Ran_Shemesh — Sun, 11 Aug 2024 15:07:43 GMT

There is actions after the triggers, but the triggers are not working.

I want that my actions will start once it’s a time of the day and a specific light is on. And for some reason I can’t manage to get that.

Re: Conditions codes from script editor stoped working

Ran_Shemesh — Tue, 13 Aug 2024 11:16:21 GMT

I tried this but it's not working as well:(

starters: - type: device.state.OnOff device: curved lamp - Living Room state: on is: true condition: type: and conditions: - type: device.state.OnOff state: on is: true device: Ceiling light - Living Room - type: time.between after: 21:30 actions: - type: device.command.OnOff on: true devices: Table lamp - Living Room

Re: Conditions codes from script editor stoped working

Asterix1 — Mon, 31 Mar 2025 13:39:31 GMT

Was this resolved? It suddenly stopped working today for me.

Re: Conditions codes from script editor stoped working

Ran_Shemesh — Tue, 01 Apr 2025 07:31:43 GMT

No:(
I can't find a way to fix it.
I tried many variations, even asking ChatGPT, but nothing worked

Re: Conditions codes from script editor stoped working

Asterix1 — Wed, 02 Apr 2025 03:06:39 GMT

I managed to resolve my issue. It was due to my tuya virtual switch (i use it to set away mode to stop the automations) not communicating properly with google home (or the other way around).

I recreated the virtual switch using google home playground and ithe conditions are working again.