02-22-2024 01:55 PM
Hi all
I am curious to see if anyone has experience with a good sensor that:
1. Alerts to duration of a door being opened, not just just on action (open/close)
2. Preferably does not require a hub for Home integration.
I have scoured the interwebs and just cannot find much that meets even the first requirement. The original Wyze sensors did this, but now the newer sensors require a hub . And also, with the several recent security snafus on their part, I am not interested in adding them back into my network.
Thanks!
02-24-2024 02:13 PM
I am interested in this too. I'd like to receive a notification if the garage door stays open for more than, say, 5 minutes. I am not seeing an obvious way of doing this. With a more complete programming language, I could simply wait 5 minutes and then check the status of the door.
There is one possibility. An automation may be able to trigger another automation, and the second automation may refuse to start when its condition is not met. I haven't tried this yet and I am not sure that it will work.
02-25-2024 08:16 PM
statement was that you didnt want another hub but Native device registration into Google Home isnt there yet. So you work with what you can.
From a Google Home Script Editor perspective you can control timing in your STARTER with "for" and or "suppressFor".
Within ACTIONS you can also set timers there .
You could also leverage multiple STARTERS to get some control that way.
After that its easy to get notification. This section of script is from a larger script I have running in my apt. I do a check for the open close state of the door at 60 seconds and 90 seconds. Keep in mind that 90 means 30 seconds after the first 60 second check.
metadata:
name: Kitchen 3.0
description: check to see if the Fridge or Freezer door has been left open , announce and alert. TOD check then turn on lights.
automations:
###
# Fridge Check 1
###
- starters:
- type: device.state.OpenClose
state: openPercent
is: 100
device: AQCS Fridge - Kitchen
for: 1min
actions:
- type: assistant.command.Broadcast
message: Check the fridge door
devices:
- Living Room Display - Living Room
###
# Fridge Check 2
###
- starters:
- type: device.state.OpenClose
state: openPercent
is: 100
device: AQCS Fridge - Kitchen
for: 90sec
actions:
- type: assistant.command.Broadcast
message: Refridgerator door is still open
devices:
- Living Room Display - Living Room
- Bedroom display - Bedroom
- type: home.command.Notification
title: Check the Fridge
body: Fridge Door has been open for 1 minute.
members: #GOOGLE HOME MEMBER EMAIL
02-25-2024 09:16 PM
Thank you OpethNJ, I had not noticed the for clause in the starter event. Using it solves my problem, and I believe it solves the OP's problem too.
04-12-2024 02:52 PM
Do you frequently get false alerts, especially if say the door is opened and closed rapidly, say around 30 seconds (not super fast like 1 sec)? That's been my problem. The activity log sometimes shows missing door closed event, but even when it does capture the door close the announcement often fires anyway after the set delay.
07-08-2024 08:46 AM
I often get false alarms too, with Ikea Parasoll door sensor. Is there a more robust way to write the automation? If my starter is door opening and has 'for: 10min', could i then have a test that whether the door really still is open before notification? I tried adding a condition but it did not help:
metadata:
name: notify if front door is left open
description: notify if front door open for more than 10 min
automations:
starters:
type: device.state.OpenClose
device: Etuovi - Entryway
state: openPercent
is: 100
for: 600sec
condition:
type: device.state.OpenClose
device: Etuovi - Entryway
state: openPercent
is: 100
actions:
type: home.command.Notification
title: Front door was left open
body: Front door has been open for more than 10min