This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official CommunityApp SDK2
[APP] Heimdall - Let Homey watch over your home.
This discussion has been closed.
Comments
How many devices do you see in the devices overview on the settings page?
This screenshot shows the devices in Heimdall: Zigbee doorsensors and Z-wave Aeotec Multi Sensors 6
And here you see two added doorsensors (node 4 and 5), that don't show up:
What would you like me to do?
Did you try scrolling the devices overview? (The viewport is 9 devices high, any number over 9 sensors requires scrolling)
If that is not the problem, please download the app, run it from a term/cmd session and wait for the log to show:
2018-03-13 16:29:35 [log] [Heimdall] Enumerating devices done.
Please post the log above that here.But guess what; I had to scroll down to see the two latest additions :-)
I did not see a scroll box/handle.... sorry!
So, all is working!
In the flow that is trigger by the alarm the sirene goes on and again off after 5 minutes. But when there is a alarm trigger it does not goes off again, because the alarm is still active (of course).
So I installed a new flow that unsets the alarm after 5 minutes. But obviously that flow should first check whether there is no trigger active for the alarm. What is the easiest way to do this? I do not want to check all devices seperately.
If you want to switch off your Sirene but want it to be activated again when a new trigger (movement or door opened) is generated you will have to make sure Heimdall will accept this as a new trigger -> the previous Alarm will have to be cleared.
This can be done by using the Deactivate the alarm action card in the same flow (perhaps with a slight delay) as where you turn the Sirene on and off.
This way any new trigger will be seen as a new trigger and will activate the The alarm is activated trigger card. If you combine this with a low Disable motion alarm after/Motion Alarm Cancelation (the description varies per brand) timer on the sensors this will very likely give you a new activation of the flow that fires the Sirene.
Please do keep in mind that this will result in a unreliable display of the Alarm state! So decide for yourself if you want to do this!
I'd rather be informed by a push message so I can take appropriate actions and then deactivate the alarm state manually on my phone than having that done in a flow. That way the next trigger will still activate the Sirene and I'm aware the alarm went off.
Version 1.0.7
The new condition cards enable you to evaluate if an Arming coundown or Alarm countdown is active in your flows:
@vaderag
know we know that the fibaro v2 door sensors are having a tamper issue.
is there anything what i can do because now i'm getting an alarm in the middle of the night and there is nothing wrong accept the tamper iseu.
However, this also happend last night;
While there wasn't a motion detected message up front, wich makes sense because there was nobody (at least i hope haha)
Could this be a heimdall thing or should i search in the Fibaro corner?
Latest version of Heimdall and homey 1.5.8 stable
The setting Do not log deactivating of sensors (Log het deactiveren van een sensor niet) is available for that.
I've added a setting to make tampering detection optional
Version 1.0.8
Tampering detection is now optional through the new setting: Listen to tampering reports from sensors
@ikenzo66
I will test it tonight and hoppe its not gone wake me up:)
thanks .
I suggest you read the first and second post from this thread, it will help you understand what Heimdall can do.
It’s being worked on, We’re not in a state to give any predictions when it will be available.