To be honest, i have had several times that the alarm turned on and I can’t figure out why.
In all flows that enable the alarm, i have cards that write something to the timeline.
The Heimdall log says, turned on by switch.. Unfortunatly, that switch does not have the logs like other devices have.
So it turns on, we where all at home and looked at each other. No idea why 
That sounds like a bug in the mobile app, I suggest logging a ticket at Athom.
@Ronald_Otto Heimdall will not set a Surveillance Mode by itself, this has to be done externally with the Surveillance Mode Switch or a flow. If all your flows have some king of logging but it’s not logged, you’ll have to look into the Surveillance Mode switch.
Is it shared will Homekit perhaps or is it somehow connected to a Virtual Device that might cause this?
Unfortunatelly Athom only included a ‘timeline’ for on/off devices, not for devices that have multiple states, I’ve sent in a feature request for this but no idea if this will ever be built.
Thanks.
I have the Homekt via a virtual button in a flow, it is logged.
I do think someone has thick fingers while using the app. Just can’t find who 
Goodmorning Ronald & Danee,
I had the same situation here, this morning. My wife and I were asleep. And spontaneously Heimdall turned into armed-away mode. I heard the arming countdown sound from the Ring keypad, which woke me up.
I made two diagnostic reports at that moment:
Heimdall aa89e33c-e272-4483-9951-2fe5f1738267
Ring f7303f1b-e84f-4dd6-a3f1-d5a5dbf41fc2
Since I was sleeping, my phone was not in use at that moment. I’m the only one who as the Homey app installed. Beside of the Ring Keypad device, I have no automations which turns Heimdall into Armed-Away mode.
Starts to feel like a real glitch in the matrix.
I to did create a support log and a notification to the developer.
Hope this helps.
This is what the log shows:
2026-09-12T05:34:45.998Z [log] [ManagerDrivers] [Driver:surveillanceModeSwitch] [Device:4f97309b-ba25-4ff2-a6f6-cb0d277ba5bd] Surveillance Mode Switch clicked: armed
2026-09-12T05:34:45.998Z [log] [Heimdall] setSurveillanceMode: armed
2026-09-12T05:34:45.998Z [log] [Heimdall] Arming is delayed: Yes, 180 seconds.
2026-09-12T05:34:45.998Z [log] [Heimdall] setSurveillanceValue in: 180 seconds.
2026-09-12T05:34:46.012Z [log] [Heimdall] checkDeviceState: Guestroom garden door - contact: Closed
And after that all other sensors were checked. That’s a normal looking log, the Heimdall device driver receives a message from Homey the Surveillance Mode was set to Armed, so it goes through the arming routine. If you’re absolutely sure no one touched the Surveillance Mode Switch and you have no flows doing this I suggest you open a ticket at Athom.
Tonight I discovered turning on partial surveillance, closing the homey app (clear from memory), and reopening the app: the surveillance status shows fully armed (armed-away). Testing this behaviour sometimes turned into arming countdown after a short wait.
I will create a ticket at Homey support.
Thanks
@DaneedeKruyff Did you find something in the diagnostic report?
Hi @MRK,
Sorry, I must have missed your previous message.
This is what’s in the log:
2026-08-23T13:40:50.868Z [log] [Heimdall] stateChange:----------------Deursensor garagedeur (Garage begane grond)
2026-08-23T13:40:50.870Z [log] [Heimdall] sensorStateReadable: Geopend
2026-08-23T13:40:50.871Z [log] [Heimdall] Surveillance Mode: partially_armed
2026-08-23T13:40:50.882Z [log] [Heimdall] sourceDeviceFull: true
2026-08-23T13:40:50.885Z [log] [Heimdall] sourceDevicePartial: true
2026-08-23T13:40:50.886Z [log] [Heimdall] sourceDeviceLog: false
2026-08-23T13:40:50.887Z [log] [Heimdall] Alarm is triggered: Yes
2026-08-23T13:40:50.894Z [log] [Heimdall] alarmCounterRunning: true
2026-08-23T13:40:50.900Z [log] [Heimdall] alarmCounterRunning: true
2026-08-23T13:40:50.901Z [log] [Heimdall] alarm is delayed: Yes, 30 seconden
2026-08-23T13:40:50.902Z [log] [Heimdall] ttAlarmCountdown start: 30
2026-08-23T13:40:50.911Z [log] [Heimdall] ttAlarmCountdown: 29
2026-08-23T13:40:51.890Z [log] [Heimdall] stateChange:----------------Bewegingsensor garage zijkant (Garage buitenzijde zijkant)
2026-08-23T13:40:51.891Z [log] [Heimdall] sensorStateReadable: Beweging gedetecteerd
2026-08-23T13:40:51.894Z [log] [Heimdall] Surveillance Mode: partially_armed
2026-08-23T13:40:51.895Z [log] [Heimdall] Alarm is triggered: No
2026-08-23T13:40:52.106Z [log] [Heimdall] ttAlarmCountdown: 28
2026-08-23T13:40:53.113Z [log] [Heimdall] ttAlarmCountdown: 27
2026-08-23T13:40:53.513Z [log] [Heimdall] stateChange:----------------Bewegingssensor garage voorzijde 2 (Garage begane grond)
2026-08-23T13:40:53.514Z [log] [Heimdall] sensorStateReadable: Beweging gedetecteerd
2026-08-23T13:40:53.515Z [log] [Heimdall] Surveillance Mode: partially_armed
2026-08-23T13:40:53.516Z [log] [Heimdall] sourceDeviceFull: true
2026-08-23T13:40:53.517Z [log] [Heimdall] sourceDevicePartial: true
2026-08-23T13:40:53.518Z [log] [Heimdall] sourceDeviceLog: false
2026-08-23T13:40:53.519Z [log] [Heimdall] Alarm is triggered: Yes
2026-08-23T13:40:53.529Z [log] [Heimdall] Device is delayed and there is already an Alarm Counter active.
2026-08-23T13:40:54.200Z [log] [Heimdall] ttAlarmCountdown: 26
2026-08-23T13:40:55.304Z [log] [Heimdall] ttAlarmCountdown: 25
2026-08-23T13:40:56.309Z [log] [Heimdall] ttAlarmCountdown: 24
2026-08-23T13:40:57.320Z [log] [Heimdall] ttAlarmCountdown: 23
2026-08-23T13:40:58.330Z [log] [Heimdall] ttAlarmCountdown: 22
2026-08-23T13:41:00.209Z [log] [Heimdall] ttAlarmCountdown: 21
2026-08-23T13:41:01.367Z [log] [Heimdall] ttAlarmCountdown: 20
2026-08-23T13:41:02.991Z [log] [Heimdall] stateChange:----------------Bewegingsensor garage zijkant (Garage buitenzijde zijkant)
2026-08-23T13:41:03.082Z [log] [Heimdall] sensorStateReadable: Geen beweging gedetecteerd
2026-08-23T13:41:04.605Z [log] [Heimdall] ttAlarmCountdown: 19
2026-08-23T13:41:05.852Z [log] [Heimdall] ttAlarmCountdown: 18
2026-08-23T13:41:07.815Z [log] [Heimdall] ttAlarmCountdown: 17
2026-08-23T13:41:08.856Z [log] [Heimdall] ttAlarmCountdown: 16
2026-08-23T13:41:10.088Z [log] [Heimdall] ttAlarmCountdown: 15
2026-08-23T13:41:11.093Z [log] [Heimdall] ttAlarmCountdown: 14
2026-08-23T13:41:12.162Z [log] [Heimdall] ttAlarmCountdown: 13
2026-08-23T13:41:13.173Z [log] [Heimdall] ttAlarmCountdown: 12
2026-08-23T13:41:14.192Z [log] [Heimdall] ttAlarmCountdown: 11
2026-08-23T13:41:15.206Z [log] [Heimdall] ttAlarmCountdown: 10
2026-08-23T13:41:16.230Z [log] [Heimdall] ttAlarmCountdown: 9
2026-08-23T13:41:17.249Z [log] [Heimdall] ttAlarmCountdown: 8
2026-08-23T13:41:18.293Z [log] [Heimdall] ttAlarmCountdown: 7
2026-08-23T13:41:19.410Z [log] [Heimdall] ttAlarmCountdown: 6
2026-08-23T13:41:20.490Z [log] [Heimdall] ttAlarmCountdown: 5
2026-08-23T13:41:21.560Z [log] [Heimdall] ttAlarmCountdown: 4
2026-08-23T13:41:22.719Z [log] [Heimdall] ttAlarmCountdown: 3
2026-08-23T13:41:23.984Z [log] [Heimdall] ttAlarmCountdown: 2
2026-08-23T13:41:24.716Z [log] [Heimdall] stateChange:----------------Bewegingssensor garage voorzijde 2 (Garage begane grond)
2026-08-23T13:41:24.717Z [log] [Heimdall] sensorStateReadable: Geen beweging gedetecteerd
2026-08-23T13:41:26.042Z [log] [Heimdall] ttAlarmCountdown: 1
2026-08-23T13:41:27.058Z [log] [Heimdall] ttAlarmCountdown: 0
2026-08-23T13:41:27.065Z [log] [Heimdall] alarmCounterRunning: false due to reaching 0
2026-08-23T13:41:27.082Z [log] [Heimdall] Alarm status: activated
2026-08-23T13:41:32.068Z [log] [ManagerDrivers] [Driver:alarmOffSwitch] [Device:37bf297e-9c98-45b9-a0fa-cd63cf6f7366] Alarm button clicked: true
2026-08-23T13:41:32.076Z [log] [Heimdall] Alarm status: deactivated
The first 3 lines show Deursensor Garagedeur is opened while the Surveillance Mode is set to Partially Armed, so the Alarm Countdwon is activated as that mode is configured for a Delayed Alarm.
Next you see the motion sensor on the side is triggerd, but that’s not configured for any mode. After that the motion sensort front side is triggered, that would activate the alarm again, bur since a countdown is active it’s ignored.
After the countdown ends, the alarm is acrivated (3rd line from the bottom) and some 5 seconds later it’s cancelled byclickong the alarm button.
This is just a part of the log, there’s another sequence just like that.
As far as I can see this functions as it should, or am I missing something?
Edit: a lot of this can be seen in the Heimdall log, here’s how to make the log more readable in the Developer Tools: Homey Flow for Web - three Column view [CSS customization] - #2 by DaneedeKruyff
The problem was, the surveillance mode changed to on, while it was off without any action from someone.First lines in the logs
See here: [Device:37bf297e-9c98-45b9-a0fa-cd63cf6f7366] Alarm button clicked: true
2026-08-23T13:41:32.076Z [log] [Heimdall] Alarm status: deactivated
And that is exactly what i had. And i do understand that the first response would be, someone clicked the button thus it turned on. And that might be true but could it be some reset, or check that goes wrong and defaults to activation and logs as button clicked?
Oh and for the people who do not know yet how a community app works, Heimdall is free. The developer does this in his own time and does not work for Homey. So please be patient
Hi @Ronald_Otto,
I’m not sure what you’re refering too, but my last post mentioning MRK has nothing to do with unexpected changing the Surveillance Mode.
If that’s the case, it something happening outside the control of Heimdall, the driver merely reacts on what it receives from Homey and only that.
Pff.. i will take some more coffee.
There are two issues in this thread..
you’re forgiven!
