a month ago - last edited a month ago
I wrote an automation using YAML on Home.google.com and it used to flash/pulse all my Philips hue lights red and blue and then stay red. Everytime Someone burnt their toast or cooked with too much smoke the routine WOULD Flash the Hue lights red and blue for several minutes and cut off power to the Oven via a contactor powered by a smart plug. . I wrote this automation sometime in mid 2023 and worked perfectly for many months after that. Something happened 2-3 weeks ago and this routine no longer works. Maybe a software update broke the routine? It also turned of the relay connected to smart plug to cut power to my electric stove/oven. One month ago (April 20th 2024?) the automation broke (due to a software update).
Here is a snapshot of the script (partial):
name: Smoke detector lightsS
description: When smoke is detected, flash lights red and blue.
automations:
- starters:
- type: device.state.SensorState
device: Kitchen(KitchenSmokeAlarm) - Kitchen
state: currentSensorStateData.SmokeLevel.currentSensorState
is: high
- type: device.state.SensorState
device: Basement(BasementReal) - Downstairs
state: currentSensorStateData.SmokeLevel.currentSensorState
is: medium
- type: device.state.SensorState
device: Hallway(UpstairHallwaySmokeAlarm) - Basement
state: currentSensorStateData.SmokeLevel.currentSensorState
is: medium
actions:
# Setting color will automatically turn on the lights.
- type: assistant.command.Broadcast
message: There is smoke in the house, Danger.
# No need to add a separate OnOff command.
- type: device.command.ColorAbsolute
devices:
- Living Room Lights - Living Room
color:
name: "red"
- type: time.delay
for: 5sec
- type: device.command.OnOff
devices: Living Room Lights - Living Room
on: false
- type: time.delay
for: 5sec
- type: device.command.ColorAbsolute
devices:
- Living Room Lights - Living Room
color:
name: "blue"
.................
Here is the execution/error log ( from home.google.com script editor console). Right after the Nest smoke alarm went of due to a burnt toast, and the automation to pulse all home lights red and blue should should have been triggered:
Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[0].name] [string_value: "SmokeLevel"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[0].current_sensor_state] [string_value: "smoke detected"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[0].alarm_state] [string_value: "ALARM"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[0].alarm_silence_state] [string_value: "ALLOWED"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[1].name] [string_value: "CarbonMonoxideLevel"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[1].current_sensor_state] [string_value: "no carbon monoxide detected"].
03/05/2024 02:48:21
[INFO] Automation started by: [device not found] because [home.graph.traits.SensorState/current_sensor_state_data[1].raw_value] [float_value: 0.0].
Somehow the Kitchen Nest Protect and other alarms are registering as [Device not Found] instead of KitchenSmokeAlarm or something. This is why lights are not flashing after Nest Protect smoke alarm is triggered, nor is it cutting off power to the electric stove. Please suggest what may have gone wrong. Nest Really needs to integrate their Protect with Google home ecosystem better so that every update does not break it!
