# \[APP\]\[Pro\] Sensor Watchdog – looking for testers

**URL:** <https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462>\
**Category:** Apps\
**Tags:** app, homey-pro, advancedflow\
**Created:** [August 18, 2026, 6:19pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462 "2026-08-18T18:19:04Z")\
**Posts on this page:** 14\
**Page:** 2

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 21, 2026, 2:59pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/21 "2026-08-21T14:59:52Z")

</div>

I installed the new version and reset its settings:

- The Shelly devices are not flagged anymore as silent 👍.
- The two Generic Zigbee devices (dimmable plugs) are still excluded. I am not sure whether Generic Zigbee devices are always excluded or it is just these two.

I generated a new report including only the two generic Zigbee devices (with device IDs `d52` and `d125` that use the `homey:virtualdriverzigbee:driver` driver):

> **Report**
>
> ```auto
> {
> "generatedAt": "2026-08-21T14:45:30.749Z",
> "ready": true,
> "meta": {
> "appVersion": "0.4.3",
> "language": "en",
> "intervalMinutes": 15,
> "discoveryUntil": "2026-08-24T14:44:06.409Z",
> "realtime": {
> "connected": true,
> "delivering": true,
> "missedByEvents": 0,
> "connectedSince": "2026-08-21T14:43:59.500Z",
> "connectAttempts": 1,
> "eventsReceived": 0,
> "eventsPerMinute": 0,
> "availabilityChanges": 0,
> "eventsWithoutAvailable": 0,
> "lastEventAt": null,
> "knownDevices": 138
> }
> },
> "counts": {
> "monitored": 118,
> "verifiable": 118,
> "ok": 111,
> "problems": 7,
> "pending": 0,
> "unverifiable": 0,
> "newAlerts": 0,
> "recovered": 0,
> "lowBattery": 1,
> "groupFailures": 0,
> "newGroupAlerts": 0,
> "skipped": 20,
> "errors": 0
> },
> "groupFailures": [],
> "skipped": [
> {
> "id": "d52",
> "driverId": "homey:virtualdriverzigbee:driver",
> "class": "socket",
> "reason": "excluded",
> "capabilities": [
> "onoff",
> "dim"
> ]
> },
> {
> "id": "d125",
> "driverId": "homey:virtualdriverzigbee:driver",
> "class": "socket",
> "reason": "excluded",
> "capabilities": [
> "onoff",
> "dim"
> ]
> }
> ],
> "overrides": {},
> "devices": [],
> "note": "Enhets- og sonenavn er utelatt med vilje. Enhetene er nummerert d1, d2 …",
> "display": {
> "theme": "light",
> "source": "measured-background",
> "os": "dark",
> "background": "rgb(255, 255, 255)"
> }
> }
> 
> ```

No problem regarding the dark mode; it is not a real issue 😊.

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 21, 2026, 5:13pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/22 "2026-08-21T17:13:37Z")

</div>

Great! Update to 0.4.4 and reset settings and see if the zigbee devices are included

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 21, 2026, 6:16pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/23 "2026-08-21T18:16:04Z")

</div>

Yes, now they are also included in the group of monitored devices! Thanks for the quick fix 👍.

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 27, 2026, 12:14pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/24 "2026-08-27T12:14:03Z")

</div>

Hello Reidar, after letting the app sit for several days and complete its learning cycle, there is one device left reported as ‘lost contact’, while the device is active and receiving updates.

It is a UPS device created by the [Network UPS Tools (NUT)](https://homey.app/a/se.nut/) app, with driver `homey:app:se.nut:ups`.

I extracted the section of the report related to this device:

> **Summary**
>
> ```auto
> 
> {
> "generatedAt": "2026-08-27T11:45:54.093Z",
> "ready": true,
> "meta": {
> "appVersion": "0.4.5",
> "language": "en",
> "intervalMinutes": 15,
> "discoveryUntil": null,
> "realtime": {
> "connected": true,
> "delivering": true,
> "missedByEvents": 0,
> "connectedSince": "2026-08-22T23:27:28.666Z",
> "connectAttempts": 1,
> "eventsReceived": 51805,
> "eventsPerMinute": 8,
> "availabilityChanges": 308,
> "eventsWithoutAvailable": 31,
> "lastEventAt": "2026-08-27T11:45:44.844Z",
> "knownDevices": 146
> },
> "findings": [
> {
> "code": "unavailable",
> "device": "d73",
> "driverId": "homey:app:se.nut:ups",
> "capability": null,
> "evidence": {
> "class": "other",
> "available": false,
> "status": "unavailable",
> "pendingReason": null,
> "rule": "climate",
> "timeoutMinutes": 90,
> "ageMinutes": null,
> "seenAgeMinutes": 40,
> "seenTimeoutMinutes": null,
> "availabilityOnly": false,
> "monitored": [
> "measure_temperature"
> ],
> "staleCapabilities": [],
> "battery": {
> "text": "100%",
> "low": false
> },
> "learning": {
> "observations": 0,
> "medianMinutes": null,
> "p95Minutes": null,
> "maxMinutes": null,
> "observedForHours": 138,
> "confidence": "none"
> },
> "capabilities": [
> {
> "id": "measure_temperature",
> "kind": "periodic",
> "staticKind": "periodic",
> "reclassified": false,
> "looseTimeout": false,
> "observations": 0,
> "longestGapMinutes": null,
> "ageMinutes": null,
> "timeoutMinutes": 90,
> "timeoutSource": "device",
> "provesDeath": false,
> "conditionMet": true,
> "limitDisproved": false,
> "fresh": false,
> "valueChanges": 0,
> "valueUnchangedMinutes": null,
> "maxUnchangedMinutes": null,
> "smallestChange": null,
> "averageChange": null
> }
> ]
> }
> }
> }
> }
> 
> ```

I made a screenshot of the devices capabilities from the Homey Developer Tools. Note that not all provided capabilities are available in my device (so some remain empty):

 ![IMG_2941](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/a/daaba6240b6ae46011ba79aab04a9a28d60553a8.jpeg)

It seems your app focusses only on the UPS’s battery temperature sensor to determine availability, but that capability/sensor is not available in my device. Hence its value will never be updated.

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 28, 2026, 1:34pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/25 "2026-08-28T13:34:12Z")

</div>

Thank you for your feedback 🙂  
I have published a new version. Try to update and please report back 👍

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 28, 2026, 2:06pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/26 "2026-08-28T14:06:08Z")

</div>

When I checked again (before updating) it had the ‘waiting’ status’.

 ![IMG_2945.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/8/282e6d763719a6aa19ea96b2a6eae822706be0cc.jpeg)

After the update to version 0.4.7 the status was unchanged. If I check the ‘Devices’ tab, then de UPS is included in the Maturing section and i seems to be classified as a ‘Temperature/humidity’ sensor.

 ![IMG_2944.PNG](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/1/91737c4a16f585e9aadd3183088d47c51222d260.jpeg)

It has the following info in the report:

> **Report**
>
> ```auto
> {
> "code": "no_timestamp",
> "device": "d73",
> "driverId": "homey:app:se.nut:ups",
> "capability": null,
> "evidence": {
> "class": "other",
> "available": true,
> "status": "pending",
> "pendingReason": "maturing",
> "rule": "climate",
> "timeoutMinutes": 90,
> "ageMinutes": null,
> "signalAgeMinutes": 1,
> "seenAgeMinutes": 0,
> "seenTimeoutMinutes": null,
> "availabilityOnly": false,
> "monitored": [
> "measure_temperature"
> ],
> "staleCapabilities": [],
> "battery": {
> "text": "100%",
> "low": false
> },
> "learning": {
> "observations": 0,
> "medianMinutes": null,
> "p95Minutes": null,
> "maxMinutes": null,
> "observedForHours": 164,
> "confidence": "none"
> },
> "capabilities": [
> {
> "id": "measure_temperature",
> "kind": "periodic",
> "staticKind": "periodic",
> "reclassified": false,
> "looseTimeout": false,
> "observations": 0,
> "longestGapMinutes": null,
> "ageMinutes": null,
> "timeoutMinutes": 90,
> "timeoutSource": "device",
> "provesDeath": false,
> "conditionMet": true,
> "limitDisproved": false,
> "fresh": false,
> "valueChanges": 0,
> "valueUnchangedMinutes": null,
> "maxUnchangedMinutes": null,
> "smallestChange": null,
> "averageChange": null
> }
> ]
> }
> }
> 
> ```

Will the app monitor another capability than measure\_temperature? Because that one will always be null (it is not available on my UPS)?

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 29, 2026, 8:45am UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/27 "2026-08-29T08:45:19Z")

</div>

New version, try to update

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 29, 2026, 10:35am UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/28 "2026-08-29T10:35:49Z")

</div>

Yes, now the device is reported as OK 👍.

It still has the ‘Temperature/humidity’ rule. Should I reset the app or will the app monitor other capabilities though the rule might imply otherwise?

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 29, 2026, 3:08pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/29 "2026-08-29T15:08:53Z")

</div>

New update, try it out. Also you might have to wait some time before the capabilities is updated. You don’t have to reset, it should update itself when your homey receives data from the device

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 29, 2026, 5:20pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/30 "2026-08-29T17:20:09Z")

</div>

The device now shows this:

 ![IMG_2949](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/d/cd6882d93d7e3b31c450182529e8f57cacb0a894.jpeg)

I see the different capabilities listed.

---

<div class="post-metadata">

**Author:** ![Bernhard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bernhard/32/78988_2.png) [@Bernhard](https://community.homey.app/u/Bernhard)\
**Post date:** [August 30, 2026, 6:48am UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/31 "2026-08-30T06:48:14Z")

</div>

Hello Reidar, I’m having issues with the following devices after the latest update.

 ![IMG_1019](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/6/96aeb4a5d64b38036ce58b8291294f4c51ebb3f8.jpeg)

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 30, 2026, 11:49am UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/32 "2026-08-30T11:49:18Z")

</div>

Did you run the learning mode, and applied the suggsetied values? If yes, for how long time did you run the learning mode? I don’t think that the latest update is the reason for this, I assume that the limt is too short. “Cannot be verified” is not the same as “last seen”. “Cannot be verified” means that the sensors data (battery % in this case?) has not changed for 3 days + and that could be normal.

---

<div class="post-metadata">

**Author:** ![Bernhard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bernhard/32/78988_2.png) [@Bernhard](https://community.homey.app/u/Bernhard)\
**Post date:** [August 30, 2026, 12:17pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/33 "2026-08-30T12:17:06Z")

</div>

I have fully completed the three-day learning phase. Earlier this morning, the devices were still marked in red. Now I’ve received the message that all devices could be found again, and everything is back in the green range for me. Thank you very much for your support.

---

<div class="post-metadata">

**Author:** ![Reidar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/reidar/32/121056_2.png) [@Reidar](https://community.homey.app/u/Reidar)\
**Post date:** [August 30, 2026, 12:20pm UTC](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462/34 "2026-08-30T12:20:51Z")

</div>

Thanks to you for testing and feedback 🙂  
I have now uploaded a new version with a minor bug fix and changed the default value for zigbee units.

[Previous page](https://community.homey.app/t/app-pro-sensor-watchdog-looking-for-testers/158462.md?page=1)