Thank you kindly good sir 
I shall install the test version and give it a go 
Hi Rick @Rick_D
Been using it for a few hours now, and the difference is night and day better… and the fix for the pause on my iPhone works beautifully. Greatly appreciated. Thank you kindly good sir
Thank you Andy for reporting
have a nice evening
(version is life now)
Hi Marcus, thanks again for the screenshots - hopefully both are fixed in v1.9.52:
The number jumping back - a real bug: the settings auto-save re-filled the form, so if you cleared a field and paused for a moment, the old value popped back in while you were still typing. A field you’re typing in is no longer overwritten.
The timeline and the delay - the delay does apply to the timeline, but the entries are written ~3 seconds after the event, so their timestamps alone were misleading: two entries 1 s apart with a 10 s delay just means the Airco was down for ~11 s. To make this obvious, the “available again” entry now says how long the device was down, e.g. “Airco (after 11 s)”. Outages shorter than your delay don’t show up at all. If it still reports more than you’d like, raise the delay (30-60 s works well for devices that drop for a few seconds) and check the Airco’s Details for a per-device delay, which overrides the global one.
P.S. sry not using the timeline myself (i work with log messages and notifications so the whole timeline stuff is not tested by myself → happy for feedback there)
Hi Rick,
Thanks for your quick response.
I will try 60s and see how that works.
Great job!
Good morning Rick.
Feature request. Any chance to make an option for watchdog to stop monitoring? I find that during the night because of some flows I have doing a restart of apps, homey backups and updates, a lot of nuisance timeline messages are generated. For me a time window in which Watchdog operates would be a great solution.
There is a flowcard to pause a device but that’s just one device. I would like Watchdog to stop monitoring all together during the night.
Hi Marcus
Before I build anything big, could you first try what’s already there? It might be enough for your nightly restarts and backups:
Try this first (Settings → Automatic scan / Default thresholds):
- Delay before “unavailable” counts - a device only counts as unavailable once it has stayed unreachable for that long, so a restart or backup that’s over in a few minutes never shows up (not in the timeline, the log, the triggers or the virtual device). You can set it in minutes, globally or per device under Details.
- Wait after app start (minutes) - after an app restart (e.g. from your night flows) the first automatic scan waits this long, which avoids a burst of false “not reporting” flags while everything is still settling.
Could you give those a go for a few nights (e.g. the unavailable delay at 10-15 minutes) and tell me whether it’s enough? The catch is that both are global, so the delay also applies during the day.
If that’s not enough, here’s what I could add:
- Quiet hours for the timeline - a switch plus “from / to” (e.g. 23:00 - 06:00) for the timeline only. It’s the only thing Watchdog writes that you can’t gate with your own flows (triggers, the widget and the virtual device can all be used with time conditions in a flow). No timeline entries during that window; monitoring keeps running underneath, so the widget, counters, log and Flow triggers stay correct. Downside: entries in the window are dropped, not queued - a problem that starts at 03:00 and is still there in the morning gets no timeline entry (it’s still in the widget / log / virtual device). I could add a single catch-up entry when the window ends if you’d want that.
- A real “pause everything” switch (or Flow cards “Pause Watchdog / Resume Watchdog”, so you could tie it to your backup flows). That’s a lot more work, and ongoing problems could be reported as “new” again when it resumes - so I’d only go there if the other options aren’t enough.
kr
Rick
EDIT: Watchdog needs some fine-tuning for your setup - I’d strongly suggest playing with the global and individual settings so you don’t need workarounds: fix the root cause, not the symptoms.
You could always create a Flow to to Disable the Device Watchdog app at your desired time, and then Re-enable it in the morning, which would effectively achieve what you are requesting with already existing native Flow cards, requiring no changes to the app:
This is similar to what I do with the Flow Checker app when I disable all my camera alerts Flows while I am out in my garden to prevent getting spammed with alerts that a lot of Flows have been Disabled, and then again when they are re-enabled when I come back in and re-enable all the camera alerts Flows.
Hope this is helpful
It would be nice if the Pause flow card included a time of day setting as well as date, similar to what you graciously added to the settings, and perhaps add an all devices option at the same time… that would solve @Marcus_Bitterling problem and preserve the recommendations stats. (Thank you kindly good sir 
for adding the time to the Pause BTW, it’s been a game changer!)
Good idea, thanks! If Marcus needs more than the settings, I’d rather build **one global “Pause Watchdog”** (until a date + time, or for X hours, plus a resume card) than pause every device individually - the statistics would keep running, since realtime updates are still recorded while paused. Let’s see first how he gets on with the delay settings.
A global pause for X time/until time would be useful for when you are making big device changes or performing maintenance that is likely to set off a whole bunch of alerts (like a regular battery changing session for numerous battery powered end devices/sensors)
I have a bunch of devices that use AA/AAA batteries, so use rechargeable batteries and regularly swap them out for fully charged, while I recharge the used ones.
Please try out the new test Version 
1.9.53 with flow card, 1.9.54 with Global setting will follow
Not in 1.9.54 (that one is the global pause in the Devices tab) - but good point. Two things for the next version: the variable card already accepts a time since 1.9.51 (type 2026-11-05 14:30), I just never mentioned it on the card, so I’ll fix the label and hint. And I’ll add a new “Pause device until date and time” card with a date picker plus a time picker (the old card stays as it is, so your existing flows keep working).
Outstanding! Thank you kindly good sir Most graciously appreciated
I use the advanced flow one myself after you added it at my earlier request, for devices I turn off power to when I’m not home… but I know not everyone likes to use advanced flows
I’ll try the first two options. I’ve set unreachable delay to 600 seconds and after restart app to 300. Let’s see how this works out. Thanks!
