I will be adding a siren on / off actions based on the Heimdall status. I have already tested that he siren starts. However, what I don’t want to test empirically is to find out how long the siren will run before it stops by itself, if at all.
Assuming it will not stop by itself, is there a way to turn the siren off after x minutes? For example with a flow?
The information Heimdall uses is read from Homey itself, not from the actual sensor(s). (So it could be Homey is not aware of the sensor’s actual status) I’d like to see a log to see if I can find out what goes wrong:
Could you please stop and start Heimdall, next perform the actions that lead to your problem and after that send me a diagnostics report?
Recently I moved in to my new home. Within the range of the geofence is a road that leads me to the highway. So this happens:
Pim is leaving
(30-60 seconds later) Pim is at home (because I drive on the road behind my house)
(10 seconds later) Pim is leaving
This triggers Homey (and Heimdall) to arm - disarm - and arm again. Same happens with the light flows at home.
Unfortunately you can not define a geofence range in the Homey app so if you want to keep using a geofence to set the Surveillance Mode you will have to look at an alternative.
You could try installing the Locative app on your phone and setup webhooks on entering and leaving your defined geofence. Next add some flows to receive and process the webhooks, more information can be found here: IOS Presence app (locative)
(I’m not sure if Locative is available on Android but if not I’m sure someone can mention an Android equivalent)
Set up check-in via MacroDroid to the Homey to: I also use a separate account for each user on the Homey, so I can see who is present per person. Then you can also use flows like first home and last gone which are standard in the Homey. Start by creating a flow with a webhook on the Homey to set your presence: [Flow MacroDroid home&away] Details of the flow map. I even use a space in the name: [Webhook car…