Help: [motion_detection_event_in_progress] is not supported by device

[BritinLA]

I have the new ADT+ system and have a few of their new motion sensors.

I am trying to turn on lights when motion is detected. The sensors appear in the Google home app and are addressable in the script editor. I started by creating an automation in the Google Home app but it did not work, so I went to the script editor. 

automations:
  - starters:
      - type: device.state.MotionDetection
        device: Master bedroom sensor motion - Master bedroom
        state: motionDetectionEventInProgress
        is: true

 The problem is, when I click Validate it give the following error:
[motion_detection_event_in_progress] is not supported by device

How can this be as the script editor is auto populating the fields in the script and it is literally the only option I have? I have validated that the sensors detect motion because in the ADT app I can see them triggering and event. 

Any advice would be greatly appreciated. 

[JPNC]

I have the same issue. It was working before, but now I get the same error.

[BritinLA]

Just bumping in to see if there is an update or advice from anyone on the Google team?

[BritinLA]

Bumping again as nobody seems to want to engage and it is still a problem! 

[ssjblur]

it's killing meeeeee

[jginder]

Why is this error suddenly breaking my working automation script? Come on, Google, speak up!

[oscanada12]

Same issue here. Tying to turn off lights after no motion detection. Google!!!!

[oscanada12]

I got it to turn of when motion is detected like this - EDIT: This works when motion is detected from a Google Nest Camera. Not 3rd party sensor as OP requires.

automations:
- starters:
- type: device.event.MotionDetection
device: Kitchen - Kitchen
condition:
type: time.between
after: SUNRISE
before: SUNSET
actions:
- type: device.command.OnOff
devices:
- Kitchen Island Light - Kitchen
on: true

My problem now is that I can't turn the lights off after no motion is detected. That's where i need to check the state via: motionDetectionEventInProgress but have the same problem as you.

[Skyjetty]

I also had it working for one day yesterday with a delay of 5min before it turned off.  I never got the motion not detected to work.   This is trivial automation stuff in other platforms why can't Google get it right...   

[BritinLA]

How does this work with the motion sensor, there are no triggers.

[oscanada12]

My apologies. I am using a google nest cam for motion detection and not a sensor. Regardless, same issue as you for checking state.

[Skyjetty]

I had it working for one day then it stopped working and I can't get it to work again.  
Now I just see a message like this. 

[PersonDetection] is off for this camera. Turn it on in camera settings in the Google Home app.

But it's NOT off...   

[oscanada12]

I solved it - the trick was to stop using Google. Platform going downhill.

[Skyjetty]

What did you do instead?   Are you still using the Nest Camera as the motion detection? 

[oscanada12]

Switched to UniFi + home assistant. I am able to do all that plus a lot more. Put up all my Google hardware for sale. Google is clearly piling a lot of resources into AI and Gemini and a lot of others teams are likely understaffed now. I don’t expect any of this to be fixed for a long time which is why I decided to pull the plug.

[Skyjetty]

So you got rid of your Nest Cameras as well or are they working in home assistant now?  

I may need to do the same thing soon.  

[zhudson]

You can have them added into HomeAssistant, I just recently did this via following this article here and by watching the attached video: Google Nest - Home Assistant. 

While I haven't had a chance to create any automations in HA with Nest devices, I can say my Nest Cameras in HA have a black thumbnail as shown in this Github issue.

I'm personally going to start considering getting off of the platform as well, especially since I already have a UniFi network. 

[Skyjetty]

What is the advantage of the UniFi network?

[zhudson]

Bit of an open ended question but I'll narrow it down to simply security camera's since this is the topic of this thread. Feel free to investigate Ubiquiti/UniFi Security more if you are interested. 

1. Local storage for recordings (no cloud storage fee's)
2. More streamlined & reliable integration and with Home Assistant (UniFi Video / Protect)
3. Single pane of glass for users who already have a UniFi network

I will mention that their cameras are going to require POE. So if you don't have a POE switch, then this is something to consider not buying unless you want to change/upgrade your network.

[avetis]

I think I found a sort of a workaround solution. Delete ALL ZONES in your nest battery cam. Turn on people detection. Use your computer to login to home.google.com.  From there, create an automation (can't edit automation created on mobile device). Then DO NOT use the motion detected, instead use person detection. Here's the script I used: 

# ------------------------------------------------------------------------------------------ #
# Lines starting with “#” are comments and will be ignored by the automation.
# Indentation determines hierarchy within the script.
# Visit g.co/home/script-editor-docs for full documentation.
# ------------------------------------------------------------------------------------------ #

metadata:
name: Backyard Lights Person # Choose a short name that summarizes important starters and actions, like “Sunset lights”.
description: Scripted automation # Write a detailed description that includes everything the automation does, like “At sunset, on weekdays, close blinds, turn on lights to 50%, and play the sunset playlist on certain speakers.”

automations:
# “starters” and “actions” are required; “conditions” are optional.
# Use Ctrl + Space to see autocomplete suggestions.

# ---- STARTERS ---- #
# Starters describe events that will start the automation.
# To add more than one starter, duplicate the "- type" section under "starters".
# If you add multiple starter events, any one of them happening will start the automation.
starters:
- type: device.event.PersonDetection # A person has been detected by the camera.
device: Backyard camera - Backyard

# ---- CONDITIONS ---- #
# Conditions are optional. Delete this section if it’s empty.
# Conditions will prevent an automation from starting if the conditions aren’t met.
# See g.co/home/script-editor-docs for documentation about how to use logical operators like “and”, “or”, and “not”.
condition:
type: time.between
# Optional. 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)
before: sunrise
# Optional. 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)
after: sunset
# Optional. Days of the week to apply condition on.
weekdays:
- MON
- TUE
- WED
- THU
- FRI
- SAT
- SUN

# ---- ACTIONS ---- #
# Actions will start when a starter event takes place and all conditions are met.
# Actions will start in the order they appear in the script and with any delay specified.
# To add more than one action, duplicate the "- type" section under "actions".
actions:
- type: device.command.OnOff # Turn the device on or off.
# Whether to turn the device on or off.
on: true
devices: Backyard Lights - Backyard

[Skyjetty]

So you can't use Zones?