# \[APP\]\[Pro\]\[SHS\] Device Watchdog - Battery, connectivity & staleness monitoring for all your devices

**URL:** https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537
**Category:** Apps
**Created:** [July 24, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537 "2026-07-24T10:54:46Z")
**Posts on this page:** 20
**Page:** 3

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 1, 2026, 8:13pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/41 "2026-08-01T20:13:06Z")

</div>

Which version are you running now? You need \>= 1.8.4.

E.g. From my setup. Only works if the value is provided by the app.

 ![105389](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/6/56bbdfc960ee06bf9e53678de461ae8b4b48ecce.png)

if you’re missing the information, please provide me with the following details

- developer tools
- Web API Playground
- Homey.devices.getDevice({ id: “” })
- the values regarding the energyObj

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/5/d5b6861323f1ee087b98750331ec764f6f9d0a68.png)

in my example:

```auto
"energyObj":{
"W":NULL,
"batteries":[
0:string"CR2032"
],1 item

```

or wherever you see the information you’re missing 🙂

---

<div class="post-metadata">

### Author: ![4x4\_Pete](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/4x4_pete/32/113286_2.png) [@4x4\_Pete](https://community.homey.app/u/4x4_Pete)
#### Post date: [August 2, 2026, 1:04am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/42 "2026-08-02T01:04:09Z")

</div>

> [@Rick\_D](#):
>
> Under a device’s “Details”, set “Paused until” to a date - the device is skipped entirely (like “not monitored”) until then, and automatically resumes on the very next scan once the date passes. No reminder needed, no manual re-enabling.

Could you make a then card to do this via flow?

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 2, 2026, 6:10am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/43 "2026-08-02T06:10:25Z")

</div>

Yes, added since - three new Flow cards for this:

**And:** “A specific device is paused” - check whether a device currently has an active pause.

**Then:**

- “Pause device until date” - device picker + a native date picker.
- “Pause device until date (variable)” - same thing, but the date is a text field so you can drop in a token or a Homey Logic variable instead of a fixed date, for a computed/dynamic pause date.
- “Resume device” - clears an active pause early, so it’s monitored again right away instead of waiting for the date.

All in the latest test version: 🔗 [Install Test version](https://homey.app/a/com.rickd.devicewatchdog/test/)

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 2, 2026, 7:51am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/44 "2026-08-02T07:51:55Z")

</div>

Am on 1.9.0.  
Yes some devices do not provide battery information. Am having issues with some Aqara devices but here we are talking about devolo heater devices that do have battery information like:

```auto
"energyObj":{
   "W":NULL,
     "batteries":[
       0:string"AA",
       1:string"AA"
],2 items

```

A devolo door sensor has no battery info too:

```auto
"energyObj":{
"W":NULL,
"batteries":[
0:string"CR123A"
],1 item

```

Aqara temp sensors with battery info are displayed:

```auto
"energyObj":{
"W":NULL,
"batteries":[
0:string"CR123A"
],1 item

```

Looks identical

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 2, 2026, 8:36am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/45 "2026-08-02T08:36:06Z")

</div>

Found it - real bug on my end. Turns out the battery type is reliably populated in `energyObj.batteries`, not `energy.batteries` (which I was reading) - checked against real devices, and `energy.batteries` was empty for the large majority even when `energyObj.batteries` had the correct value. Fixed in 1.9.3.

Also added a manual override for cases where Homey genuinely has nothing (sounds like your Aqara devices might be in that camp) - under a device’s “Details”, there’s now a free-text “Battery type (manual)” field. Whatever you type there shows up instead of the auto-detected value, both in the widget and the details view. Leave it empty and it keeps using auto-detection.

🔗 [Install Test version](https://homey.app/a/com.rickd.devicewatchdog/test/)

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 2, 2026, 8:44am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/46 "2026-08-02T08:44:10Z")

</div>

Fast reaction on a sunday morning. Where battery info available it‘s now displayed.  
Thanks

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 2, 2026, 8:57am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/47 "2026-08-02T08:57:51Z")

</div>

Had a quick time slot 🙂 please continue to report improvements. Can’t test them all since I don’t own all the different sensors 😁

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 6, 2026, 5:02am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/48 "2026-08-06T05:02:52Z")

</div>

**Update (v1.9.5):**

- New: three “any device” condition cards — _Any device is unavailable / is not reporting / has low battery_ — no device picker needed, handy for flows hung off the summary triggers where you don’t know in advance which device tripped it.

As always, happy to hear what’s working and what isn’t 🙂

🔗 [Install Test version](https://homey.app/a/com.rickd.devicewatchdog/test/)

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 8, 2026, 8:52am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/49 "2026-08-08T08:52:50Z")

</div>

Was looking at my zwave sirene. Homey app had a popup. Something like: haven‘t seen the device a long time. Couldn‘t then open the device. Tried a „test“ with device watchdog. As the device is under: not watched no indication wether the test worked or not. Looks like it did. Only I get only an okay when the device is on the watched list. Is it possible to get an okay on test when device is on the not watched list?

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 8, 2026, 3:03pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/50 "2026-08-08T15:03:11Z")

</div>

Thx for the input. Just shipped v1.9.6 with a small addition: the Test button now shows a clear “✓ Reachable” (or the error) directly on the button itself for a couple of seconds after every test — regardless of whether the device is on the monitored list or not. Should give you the confirmation you were missing on that sirene.

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 8, 2026, 4:17pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/51 "2026-08-08T16:17:06Z")

</div>

Thanks. Works.  
Just noticed when a device is on the not monitored the search function does not find it.

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 8, 2026, 5:12pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/52 "2026-08-08T17:12:20Z")

</div>

They are → they are just under “nicht überwacht” (see below). At least in my setup they are. Or you have a filter active 🙂

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/e/8eea1f40eab465fc52b173acb96dcae58918356a.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/a/4a86888a2c86ed9f2952c75a12a6a519d162e99a.png)

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 8, 2026, 5:31pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/53 "2026-08-08T17:31:13Z")

</div>

You are correct, they are under not monitored. I asumed when having selected all devices the search does include the not monitored ones too. Presently I have to remember to search 2 places. A bit confusing, or?

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 8, 2026, 5:43pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/54 "2026-08-08T17:43:14Z")

</div>

Will fix it next time online 🙂

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 8, 2026, 6:58pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/55 "2026-08-08T18:58:48Z")

</div>

That message now only appears when a search truly has zero results anywhere.

While I was in there, I also made search results easier to actually see: any zone group containing a match now auto-expands as you type, instead of leaving you to click open a collapsed zone to find what you just searched for.

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 10, 2026, 1:08pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/56 "2026-08-10T13:08:35Z")

</div>

Just had to restart my homey and watchdog tells me thirty something devices are not reporting. Now down to 9 devices. Any idea. Maybe wait a while after a restart bevor a scan starts?  
Had a look at the last seen time stamp. After 18 min all have one. Started several scans via widget still some are not talking?

 ![IMG_4034](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/f/9fee806889790994da07d25ea62523d9f8af7af9.jpeg)

> **list of last seen timestamps**
>
> ```auto
> 
> Script started at: 10.08.2026 15:11:03,403
> Devolo PS_2 - vor 00:00:11 Std
> Nous P2 - vor 00:00:11 Std
> Nous P1 - vor 00:00:11 Std
> H_Mari.Zi - vor 00:00:29 Std
> H_Arb.Zi 1 - vor 00:00:38 Std
> H_Schla.Zi. 2 - vor 00:00:51 Std
> DP5 - vor 00:00:57 Std
> H_Arb.Zi 2 - vor 00:00:59 Std
> NP5 - vor 00:01:03 Std
> Aqara plug 2 - vor 00:01:04 Std
> Arb.Zi OG H1 3 - vor 00:01:07 Std
> NP1 - vor 00:01:08 Std
> Wandschalter H1 4 - vor 00:01:30 Std
> QB1 - vor 00:01:48 Std
> NP7 - vor 00:02:14 Std
> Aqara Temp 14 - vor 00:02:14 Std
> NP6 - vor 00:02:25 Std
> H_Wohn.Zi - vor 00:02:38 Std
> Aqara Temp 12 - vor 00:02:42 Std
> H_Wohn.Zi. 2 - vor 00:02:51 Std
> NP3 - vor 00:02:54 Std
> Devolo PS_1 - vor 00:03:08 Std
> H_EssZi. 2 - vor 00:03:17 Std
> Heizkörperthermostat - vor 00:03:23 Std
> Schlafzi. OG H1 2 - vor 00:03:26 Std
> H_Schlaf-Zi - vor 00:03:26 Std
> H_Kevin.Zi - vor 00:03:34 Std
> Licht Wz. OG - vor 00:03:42 Std
> Aqara Temp 10 - vor 00:03:49 Std
> Aqara Temp 6 - vor 00:04:17 Std
> DP3 - vor 00:04:31 Std
> NP2 - vor 00:04:35 Std
> Flood sensor Dach - vor 00:05:18 Std
> Wall Plug 5 - vor 00:05:26 Std
> BM 3 - vor 00:06:06 Std
> Aqara doorS1 - vor 00:06:26 Std
> Aqara Temp 5 - vor 00:08:48 Std
> Aqara Temp 1 - vor 00:09:22 Std
> LF - vor 00:09:31 Std
> FP1 - vor 00:10:04 Std
> RaumTh_2 - vor 00:10:33 Std
> Fibaro_SS2 1 - vor 00:10:59 Std
> Aqara Temp 2 - vor 00:15:05 Std
> Aqara Temp 11 - vor 00:15:21 Std
> Fibaro 2 (S1) - vor 00:17:57 Std
> Sirene - vor 00:18:06 Std
> FP2 - vor 00:18:13 Std
> Wall Plug 4 - vor 00:18:13 Std
> Aqara plug 1 - vor 00:18:13 Std
> Aqara plug 4 - vor 00:18:13 Std
> Aqara plug 3 - vor 00:18:14 Std
> DP1 - vor 00:18:36 Std
> Tür Eingang - vor 00:18:36 Std
> DoorS_6o - vor 00:18:36 Std
> DoorS_1 - vor 00:18:36 Std
> Tür Balkon - vor 00:18:36 Std
> BM 5 - vor 00:18:36 Std
> BM 2 - vor 00:18:36 Std
> BM 4 - vor 00:18:36 Std
> FP3 - vor 00:18:40 Std
> BM 1 - vor 00:18:47 Std
> 
> ```

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 10, 2026, 3:30pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/57 "2026-08-10T15:30:05Z")

</div>

Thanks for the detailed report, that’s really useful. Two separate things going on there:

**The initial burst (30+ → 9):** Right after a Homey restart, the app’s own device cache isn’t fully settled yet when the first scan runs - that’s very likely what caused the temporary spike, exactly your own suspicion. Just shipped v1.9.8 with a new setting: “Wait after app start (minutes)” (default 2 min) - delays only that very first automatic scan after a restart, giving things time to settle first. Manual scans and every later scan are unaffected.

**The remaining 9:** Looking at your screenshot, most of those (window/door sensors, the flood sensor, rain sensor) show “last update” from days or even months ago (e.g. 23.3. for the flood sensor) - that’s unrelated to the restart, they’re just event-driven sensors that haven’t had a reason to send a new value in a while. Not a bug, just how event-driven devices work - see the FAQ entry on “not reporting” for more on that.

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 16, 2026, 8:13am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/58 "2026-08-16T08:13:52Z")

</div>

Think you can record in your log when you detect a device became available again? Would love to see some positiv entries too. 😉 That leads me to my next question. How many entries or how long do you keep the log?

---

<div class="post-metadata">

### Author: ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)
#### Post date: [August 16, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/59 "2026-08-16T15:33:13Z")

</div>

Thanks again for the feedback - v1.9.9 added exactly that: the log now shows recoveries too (“device available again” / “reporting again” / “battery no longer low”), green icon right next to the problem entries. Also fixed a small related thing while testing this: the log tab wasn’t refreshing itself while the settings page was already open - it now reloads every time you switch to it (v1.9.10).

---

<div class="post-metadata">

### Author: ![SingKT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/singkt/32/173226_2.png) [@SingKT](https://community.homey.app/u/SingKT)
#### Post date: [August 17, 2026, 7:53am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/60 "2026-08-17T07:53:27Z")

</div>

The improvments are partly working. I have a zigbee xiaomi doorsensor that was flagged and reported in the log as not reporting. It defenitely works now, it’s also no more flagged. Even after a manual scan no good record in the log. 2 other devices have their 2 records.

[Previous page](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537.md?page=2)

[Next page](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537.md?page=4)
