topic Script editor validating; no errors, but not running certain routines in Home Automation

Script editor validating; no errors, but not running certain routines

chaybee — Thu, 25 Jan 2024 22:04:43 GMT

This has happened a few times. The latest script which was validated and activated does not work in which a Wyze door sensor is open for 5 minutes to announce on 2x google Hubs that the door is open. Here it is (generated by the "help me write a script") section:

metadata:
name: Laundry open for 5 min
description: When the door is open for 5 min announce on display
automations:
- starters:
- type: device.state.OpenClose
device: Laundry garage door - Laundry Room
state: openPercent
is: 100
for: 5min
actions:
- type: assistant.command.Broadcast
devices:
- Beach Room display - Beach Room
- Basement Hub - Basement
message: The laundry room door has been open for 5 minutes

Are there some things that are being validated but just aren't supported? I doesn't even have to be an announcement on the hubs; I just need to figure out a way to alert me AFTER 5 MINUTES that the door is still open In 2 different areas of the house.

Re: Script editor validating; no errors, but not running certain routines

salbando — Fri, 26 Jan 2024 14:58:25 GMT

I would suggest that you open the script and click on "View execution logs" (the clock looking thing with the circular arrow around it). See if it says anything like "Starter check: conditions met". After you see what is happening, try a different starter condition other than "is". For example, you might try "greaterThan" and choose zero. It might trigger for anything other than a closed door.

Re: Script editor validating; no errors, but not running certain routines

chaybee — Fri, 26 Jan 2024 18:55:57 GMT

Thanks for the suggestion! I tried this and it did not work. I first tried to do the routine physically, nothing at all. Would not show any information in the logs. I then hit enter on the routine to start it on my PC. It immediately did the announcement on the hubs part, therefore, I can only assume that even though the script is permitting me to enter the sensor as the trigger, it is not recognizing it which leads me to believe it is built into the code somewhere but Google has yet to implement support. This coincides with the actual Home app in which sensors started showing up and you can seemingly start an automation with them however, once you click next there are no options to move forward.