# Heimdall - Let Homey watch over your home **URL:** \ **Category:** Apps\ **Tags:** app, official, security, homey-pro:mini:shs, heimdall\ **Created:** [August 22, 2018, 1:41pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134 "2018-08-22T13:41:20Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Perran83](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/perran83/32/2211_2.png) [@Perran83](https://community.homey.app/u/Perran83)\ **Post date:** [October 3, 2018, 6:40am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/21 "2018-10-03T06:40:06Z")
ok, great. thank you for quick answer. I have not bought cameras yet thats why I ask. =) good work and great app you have developed=) ---
**Author:** ![Ben](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ben/32/12538_2.png) [@Ben](https://community.homey.app/u/Ben)\ **Post date:** [October 3, 2018, 8:15am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/22 "2018-10-03T08:15:41Z")
The xiaomi aqara human body sensors always fall out. Does anyone have any idea how that is possible. I use this in the Heimdall app. Or is this a Xiaomi problem? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 3, 2018, 8:29am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/23 "2018-10-03T08:29:16Z")
@Ben can you explain what you mean with ‘always fall out’? _ **Heimdall** _ ‘listens’ in on the _alarm\_motion_ reports that are generated by the Xiaomi app when it receives information from a device. Does the sensor report movement at all? ---
**Author:** ![Ben](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ben/32/12538_2.png) [@Ben](https://community.homey.app/u/Ben)\ **Post date:** [October 3, 2018, 10:06am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/24 "2018-10-03T10:06:04Z")
> [@DaneedeKruyff](#): > > you explain what you mean with ‘always fall out’? > _ **Heimdall** _ ‘listens’ in on the _alarm\_motion_ reports that are generated by the Xiaomi app when it receives information from a device. Does the sensor report movement at all what I mean by failure is that I currently have two sensors in the room and one in the toilet and one in the garage and one on the landing. The 2 in the room I have no problem with and also not in the toilet. Heimdall recorded everything well except for the one in the garage and overflow. When I have paired it on the landing and garage, everything goes well for a while and heimdall registers everything but after a while nothing is registered by heimdall. I’m going to take out the battery again and again on new pairing everything goes well again and over time I have the same problem again. ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 3, 2018, 2:15pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/25 "2018-10-03T14:15:10Z")
> [@Ben](#): > > what I mean by failure is that I currently have two sensors in the room and one in the toilet and one in the garage and one on the landing. The 2 in the room I have no problem with and also not in the toilet. Heimdall recorded everything well except for the one in the garage and overflow. When I have paired it on the landing and garage, everything goes well for a while and heimdall registers everything but after a while nothing is registered by heimdall. I’m going to take out the battery again and again on new pairing everything goes well again and over time I have the same problem again. Reading that I think you have range/zigbee issues and it’s not something _ **Heimdall** _ has to do with or can fix. ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 4, 2018, 6:56pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/26 "2018-10-04T18:56:42Z")
New version published > ## Version 1.0.22 > > - Added [Last Door](https://github.com/daneedk/com.uc.heimdall/issues/27) functionality > - Split Trigger Delay to 2 separate settings, Arming Delay and Alarm Delay > - Changed Delay range to 0-300 seconds > - Minor layout changes to settings pages The [Last Door](https://github.com/daneedk/com.uc.heimdall/issues/27) functionality will shorten the arming delay when ‘the last door’ is closed to 10 seconds. You don’t have to do anything special to use it, just make sure the _door sensor_ has _ **Delayed Trigger** _ set to **yes** in the settings and you would obviously use a delay setting the _ **Surveillance Mode** _ ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/c/c28f07f54657b03f3efe6abd8e6ac305fd6f01cd.png) Make sure the door is closed when you set your desired _ **Surveillance Mode** _ and just leave through the door, opening and closing is will activate the Last Door functionality which lowers the delay to 10 seconds. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/4/4e04a7ab79c9a3c70b259e16a4801758d34fd625.png) Because this functionality was added the _ **Trigger Delay** _ was split into two separate settings: _ **Arming** _- and _ **Alarm Delay** _, please set them to your desired value in the range 0-300 seconds. ---
**Author:** ![Ben](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ben/32/12538_2.png) [@Ben](https://community.homey.app/u/Ben)\ **Post date:** [October 7, 2018, 10:20am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/27 "2018-10-07T10:20:04Z")
Hi Danee, Si i told one of the sensors worked again for a while and not from the overflow. The last night I see in heimdall that suddenly all the sensors work again but in heimdall it is indicated that the sensors have not sent information in the past 24 hours. You can see that everything works. (See example) ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/f/f02dd7ffe0e4727571e9fcab43f580eb014fecc8.png) ![afbeelding](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/b/b28067c87d1966252e781c4c4b08595839611518.png) With this I want to thank you for the good app ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 7, 2018, 5:44pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/28 "2018-10-07T17:44:31Z")
You’ve stumbled upon a function that will be completed in version 1.0.23. When setting the _ **Surveillance Mode** _ to either armed mode _ **Heimdall** _ will check if sensors have sent an _alarm\_motion_ or _alarm\_contact_ report in the last 24 hours. If a sensor hasn’t reported it will be written to the history and a flow card will be triggered which you can use to be informed about it. ---
**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\ **Post date:** [October 7, 2018, 7:21pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/29 "2018-10-07T19:21:57Z")
To have full usage of the sensor communications, it should also log when the did communicate again, otherwise its half a function. I noticed this also in th Hemdall logs and find it usefull information, but then I also want to know when they communicate again. There are two options, remove this feature or complete it to tell us in the log when sensors did communicate again please. Or create a different and separate monitoring app 😉 This is monitoring of equipment, if you know that a sensor did not communicate for 24 hours, then you can also see that they communicate again. But you need to remember the state of a sensor ( active (reachable/updating) or not active (non reachable/no updates received) and it should survive a reboot of the app and/or the Homey… ---
**Author:** ![M\_a\_r\_c\_o](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_a_r_c_o/32/146_2.png) [@M\_a\_r\_c\_o](https://community.homey.app/u/M_a_r_c_o)\ **Post date:** [October 8, 2018, 6:46am UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/30 "2018-10-08T06:46:25Z")
Is there a flowcard to send the warning to a log and/or to notify me with a notification action card? Is the current warning a real one? Or may be caused by the first installation and a small bug which is mis understood by me and @Ben ? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 9, 2018, 6:56pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/31 "2018-10-09T18:56:22Z")
This functionality is added so a user knows the sensor hasn’t reported for 24 hours, this could be because it’s a motion sensor in a room that wasn’t entered for 24 hours or because it’s a battery operated device where the battery depleted. For the functionality I wrote _ **Heimdall** _ I don’t expect a user to just wait around and check the history over and over again to see if there is communication again but to actively check the sensor why it hasn’t communicated. _ **Heimdall** _ is not a device monitoring app, I merely added this function because Homeys abilities to do this doesn’t really work reliable, if it does this function reliable in a upcoming firmware it may be removed again from _ **Heimdall** _ ---
**Author:** ![stepic7](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stepic7/32/18659_2.png) [@stepic7](https://community.homey.app/u/stepic7)\ **Post date:** [October 18, 2018, 2:17pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/32 "2018-10-18T14:17:43Z")
On trying to implement Heimdall I recently raised a question on the possibility that Heimdall acknowledges the status of doors/windows whether opened/closed Each door/window status is detected by a switch (an input to a Fibaro generic input sensor) However each switch cannot be acknowledged since it does not have the “capability alarm\_contact” in order to be detected by Heimdall So as you suggested I have created Virtual devices to account for an “alarm feature” However no one is detected by Heimdall once giving the definition as the only possible feature available, i.e. “motion detection” which therefore does not work either I think this depends on the fact that “motion detection” is a transient event while the CONTACT detection is a STATUS EVENT > [@Create Virtual device with capability "alarm\_contact"](https://community.homey.app/t/create-virtual-device-with-capability-alarm-contact/1517): > > I need to add a Virtual device with capability alarm\_contact in order to be detected by Heimdall to emulate an ON/OFF switch I tried several no one is acknowledged but in the case the device is Motion detection Use of this device is to pass to Heimdall the info of an Open/Close switch implemented by a flow with the Fibaro binary sensor as explained in the thread: Can anybody help? Do you think is there any possibility to take care of this issue? in the meantime I have also submitted a question to Arjan in github > > > Hello Arjan > I would like to use Heimdall to control the status of doors (open/c…losed) > Each door status is acknowledged by a switch (an input to a Fibaro generic input sensor) > Each switch cannot be acknowledged since it does not have the "capability alarm\_contact" in order to be detected by Heimdall > So as suggested by DaneedeKruyff I have created Virtual devices to account for an "alarm feature" > However no one is detected by Heimdall since ALSO the VD do not have the "alarm feature" > I tried defining the VD with the "motion detection" feature but it does not work as well > I think this depends on the fact that "motion detection" is a transient event while the CONTACT detection is a STATUS EVENT > I wonder this could be accounted for in the definition of a VD > thanks a lot > Stefano to understand whether a VD can be implemented with the “capability alarm\_contact” thanks ---
**Author:** ![vaderag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vaderag/32/150_2.png) [@vaderag](https://community.homey.app/u/vaderag)\ **Post date:** [October 18, 2018, 3:21pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/33 "2018-10-18T15:21:21Z")
I think I missed something here but this is absolutely something I want/need, not because of Heimdall (necessarily) but because sometimes my batteries die or connection lost without me realising… Can you give quick instructions on how I set it up so if any motion sensor has not reported in 24hours I get a notification? Cheers ---
**Author:** ![Wdl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wdl/32/5430_2.png) [@Wdl](https://community.homey.app/u/Wdl)\ **Post date:** [October 18, 2018, 5:45pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/34 "2018-10-18T17:45:35Z")
> [@vaderag](#): > > Can you give quick instructions on how I set it up so if any motion sensor has not reported in 24hours I get a notification? You can build a flow with the trigger “device hasn’t report in 24hr” from the “devices” It will check all the devices you have connected to homey. For filtering I think you can use logic in the “AND” and the “name” tag from the trigger. ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 18, 2018, 6:40pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/35 "2018-10-18T18:40:25Z")
New version published > ## Version 1.0.23 > > - Check if sensors communicated with Homey in the last 24 hours On setting a _ **Surveillance Mode** _ the sensors that are selected for the _ **Armed** _ or _ **Partially Armed** _ mode will be checked when they last reported. If there has not been a _alarm\_motion_ report or _alarm\_contact_ report in the last 24 hours a line will be written to the history: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/4/434e1349a8e9d3402e3b81fded3cd2d5b3dc1aa9.png) The new _ **No information received** _ flow card will also be triggered, with the _Zone_, _Device_, _Last update_ and _Hours card_ you can create a flow to inform you about sensors that need attention. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/d/d8be9dfff5c508133f262409b3ad8293f899641d.jpeg) @vaderag (Version 1.0.24 will have improvements on this new function, it will no longer just look at _alarm\_motion_ or _alarm\_contact_ information but any communication from a sensor) ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 18, 2018, 6:45pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/36 "2018-10-18T18:45:17Z")
> [@Wdl](#): > > You can build a flow with the trigger “device hasn’t report in 24hr” from the “devices” > It will check all the devices you have connected to homey. > For filtering I think you can use logic in the “AND” and the “name” tag from the trigger. Unfortunately that function is not really reliable and that’s the reason I added the _ **Communication Check** _ to _ **Heimdall** _ ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 18, 2018, 6:54pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/37 "2018-10-18T18:54:42Z")
@stepic7 In order to use the Fibaro Binary Sensors in _ **Heimdall** _ as if they are ‘real’ Door/Window sensors you would need to map them to a Virtual Device that has the _alarm\_contact_ capability so it requires support for that in the Virtual Devices app. Until that support is build you could use them as a trigger in the proposed flow I posted in [a previous post](https://community.homey.app/t/134/20) ---
**Author:** ![Willybits](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willybits/32/6094_2.png) [@Willybits](https://community.homey.app/u/Willybits)\ **Post date:** [October 19, 2018, 12:09pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/38 "2018-10-19T12:09:22Z")
Love the App! Here’s a suggestion though, the countdown is now spoken every 5 seconds. Due to this it is hard to use a voice command to turn off the alarm. We have to wait till a countdown is spoken, then quickly say the command and then hope it went well. Would it be an idea to stop announcing the countdown when a user tries to communicate with Homey through voice? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 19, 2018, 7:35pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/39 "2018-10-19T19:35:32Z")
I’d have to look into that. I’m not sure an app can notice when Homey starts listening to a spoken command but think it’s a good idea. Can you create an issue for it on [github](https://github.com/daneedk/com.uc.heimdall/issues) so I have a reminder and you can track progress? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [October 19, 2018, 7:37pm UTC](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134/40 "2018-10-19T19:37:14Z")
@stepic7 @Arie_Laxed I’ve just created a [Pull Request](https://github.com/ArjanKranenburg/virtual-devices/pull/68) on the Virtual Devices app to add support for a Virtual Door/Windows Sensor. [Previous page](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134.md?page=1) [Next page](https://community.homey.app/t/heimdall-let-homey-watch-over-your-home/134.md?page=3)