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

Apps
, ,
21

I installed the new version and reset its settings:

  • The Shelly devices are not flagged anymore as silent :+1:.
  • 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 
{
	"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 :blush:.

22

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

23

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

24

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) app, with driver homey:app:se.nut:ups.

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

Summary 

{
  "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
IMG_29411391×1155 144 KB

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.

25

Thank you for your feedback :slight_smile:
I have published a new version. Try to update and please report back :+1:

26

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

IMG_2945.PNG
IMG_2945.PNG1668×750 133 KB

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
IMG_2944.PNG1668×731 106 KB

It has the following info in the report:

Report 
		{
			"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)?

27

New version, try to update

28

Yes, now the device is reported as OK :+1:.

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?

29

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

30

The device now shows this:

IMG_2949
IMG_29491668×250 30.8 KB

I see the different capabilities listed.

31

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

IMG_1019
IMG_10191613×1116 175 KB

32

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.

33

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.

34

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