That’s the exact same behaviour I have as well. When just checking the status of the Surveillance (even though I know for sure it’s deactivated), it changes to fully armed without me touching anything. I’ve created a ticket at Homey support and Bas mentioned that the ticket was escalated to the Homey Development team. We’re now about 10 days further but I didn’t get any further news. I have this behaviour on two different Android phones. This does not happen when using an Android tablet or the web-based interface.
(I just also experienced that the Surveillance Mode switched is opened it selects the topmost option in the list and executes the action that’s supposed to happen when that option is selected, that’s surely a bug in the (iOS) app and outside the control of Heimdall)
Yeah, I’ve now seen this happen on multiple apps. My Ozonos app uses the same picker type capability and it also happened to me in the Peblar app whenchecking the charge mode for my car. This definitely is an app problem, and not limited to Android as I’m using iOS.
The bug in the picker is fixed in app version 10.1.2 according to the changelog in Testflight. Not sure when it hits the app stores but I expect it to be soon™️
I’ve been developing HeimConnect, an independent iPhone app for Homey and Heimdall, and I’m looking for a small group of 5–10 testers to try it through Apple TestFlight.
Check your security status and arm, partially arm or disarm Heimdall.
View recent alarm information, log entries and selected devices.
Use the iPhone widget and an Apple Watch app.
The app supports Dutch, English, German, French, Spanish and Italian, and includes a built-in help section to guide you in your setup.
You’ll need an iPhone with iOS 17+ and a Homey with Heimdall installed and configured. Apple Watch is optional and requires watchOS 10+.
I’m especially interested in how setup and everyday use work on different Homey configurations. Feedback on translations and the Watch app is welcome too!
This is a beta that controls your real security system, so please test actions at a suitable moment. Keep your existing Homey alarm notifications configured—HeimConnect doesn’t provide its own alarm push notifications for this test.
First of all, thanks for Heimdall. I’m using it with a frient Intelligent Keypad (KEYZB-110) on Homey Pro and the integration is working very well.
I would like to create a separate Heimdall user with their own PIN, but have that user/PIN enabled only during specific recurring time windows.
Outside those periods, the PIN should simply be invalid and unable to disarm the system.
I can see that every Heimdall user already has an Enabled switch in the Users settings, so essentially what I need is a way to automate that switch.
Would it be possible to add Heimdall Flow actions such as:
Enable user [user] Disable user [user]
This could then be combined with Homey’s date/time conditions to create scheduled or temporary access for cleaners, guests, maintenance staff, etc.
Alternatively, is there currently a safe way to change a user’s Enabled status through HomeyScript or Heimdall’s API?
It would also be very useful if Heimdall could expose the user name as a Flow tag when a keypad user arms or disarms the system, allowing different users’ actions to be logged or used in automations.
I would prefer to keep the keypad in Heimdall mode, as the whole alarm setup is currently working reliably.
Is there currently any way to achieve this that I may have missed?
Thanks a lot for your help and for developing Heimdall.
I’m a long term user of Heimdall (in my three homes). I’m super happy with the functions. I just got in to a new “issue”.
I have about 45 Shelly Door/Windows BLE sensors - they works fine in general. Shelly have created a new Homey app - everything works nice and the sensors/Homey are detecting opening of doors/windows nicely.
The issue is the sensors are not showing up in the Heimdall any more. The support team for the Shelly app says; “You will have to contact Heimdall such that they can add support for alarm_open because that is the one we are using currently”. Sadly the Shelly App team have changed the how the sensor values are presented.
Is there any chance getting the Heimdall app to detect sensors with “alarm_open” as well as current alarm_contact? I think there is a lot of Shelly devices used by the homey community.
Small question, I’ve been searching for a list of the return values in the tag of the “The alarm is deactivated” WHEN card. The info tooltip popup says the way the alarm is deactivated is returned in the Source tag, but I can’t find a list of possible values anywhere? I want to test if the deactivation was by flow or by the “Turn Off” button on the Surveillance device card in the app, is this possible please? Thank you kindly
Thanks, glad you like it. I’m not able to look into that currently, if you want to know it fast, make a flow that writes the tag to the timeline and try the different methods to disarm. That will definitely get you the correct texts.
@SteAlk Please test this version and let me know if this works for you. I have no Shelly devices, nor other devices that use the alarm_open capability so it’s impossible for me to test this.
That’s weird indeed… I have other sensors connected via both Zigbee and Matter over Thread/WiFi that show up in the device list just fine. It is only the LWR02 Matter over Thread sensor that is missing.
I have tried restarting the Heimdall and Lafaer apps on my Homey… and I have tried running a repair of the LWR02. The Lafaer iOS app can find the sensor okay. And it works just fine with the Lafaer Homey app and advanced flows that it triggers. I also tried deleting the device and re-adding it, and replaced all the flow cards… but it still doesn’t show up in the Heimdall app Devices list
This version is now live in the Homey App Store. Devices that report their state through the alarm_open capability can now be used in Heimdall, so they can be added to your surveillance setup just like your other sensors.
The update has been running as a test version for a while without issues, so it’s now available to everyone.
I’ve had a look at the Diagnostics Report, no errors there. I guess it’s because of the use of occupancy_sensor capability instead of alarm_motion which Heimdall looks at.
I don’t understand how it is working for @DirkG perhaps he has included the sensor at an earlier app version where it did support alarm_motion. (just guessing here, only thing I can think of.
Anyways, I’ll see if it’s possible to add the occupancy_sensor capability in Heimdall. For now please have a look at the FAQ for a workaround:
Q: I have a device that doesn’t have the alarm_motion capability, can I still use it with Heimdall?
