Hubitat Maker API - Device information some info missing

🚧 Developers
1

When using the Maker API to get information from devices, if I pull all the devices with full details, there is some data there for a sensor that is NOT if I pull a sensor directly by ID. Mainly the "date" which we would like to check certain sensors for the last date this device was active. (helpful for sensor that have connectivity issues). Can this be added when you pull the device ID directly?

For example, if I pull it with full details:

/apps/api/9/devices/all?access_token=
...
{
"name": "ES13",
"label": "ES13",
"type": "Zooz ZSE44 Temperature Humidity XS Sensor",
"id": "32",
"date": "2025-05-06T14:01:48+0000",
"model": null,
"manufacturer": null,
"room": "Server",
"capabilities": [
"RelativeHumidityMeasurement",
"Battery",
"TemperatureMeasurement",
"Sensor"
],
"attributes": {
"battery": "100",
"dataType": "NUMBER",
"values": null,
"humidity": "55",
"temperature": "76.7"
},
"commands":
},

But if I pull it by ID specifically, notice the "date" is not there...

/apps/api/9/devices/32?access_token=
{
"id": "32",
"name": "ES13",
"label": "ES13 - Z2.R09",
"type": "Zooz ZSE44 Temperature Humidity XS Sensor",
"room": "Server",
"attributes": [
{
"name": "battery",
"currentValue": 100,
"dataType": "NUMBER"
},
{
"name": "humidity",
"currentValue": 55,
"dataType": "NUMBER"
},
{
"name": "temperature",
"currentValue": 76.7,
"dataType": "NUMBER"
}
],
"capabilities": [
"RelativeHumidityMeasurement",
{
"attributes": [
{
"name": "humidity",
"dataType": null
}
]
},
"Battery",
{
"attributes": [
{
"name": "battery",
"dataType": null
}
]
},
"TemperatureMeasurement",
{
"attributes": [
{
"name": "temperature",
"dataType": null
}
]
},
"Sensor"
],
"commands":

2

The date field is the last event date/time, not the "Last Activity At" date/time as you might see in Device Info. However useful the latter maybe for this purpose, the former would be even less so.

Can't speak to whether this was an intentional omission with certain endpoints (* also won't have it) or intentional, but it's possible this would change your mind. :slight_smile:

You can get this data as part of the data returned with the /hub2/devicesList endpoint against the hub itself (not through Maker API) if that is helpful; no authentication required if you're doing this with an app/driver running on the same hub, though you will if you have Hub Login Security enabled and call it from elsewhere.

3

Thanks for the response. I do understand what that date means, but it's incredibly helpful to monitor (from the outside) passive devices that SHOULD be checking in periodically, but have not for X time. In our case a wireless environmental sensor that hasn't checked in for a few days when they typically at least check in once per day to report their battery health.

This helps us monitor sensors from outside and that they're actively check in and we can check them if needed.

Right now we monitor the attributes of each sensor; battery, temp, humidity, and that works. But if they've not checked in for a long time, all we have is their last readings which won't be helpful.

If we can at least get the date of last activity, that helps us know they are alive..

4

Have you tried doing devices/* instead of devices/all?

5

Device Activity Check does this and provides a cloud link to its (human readable) report. It wouldn’t be difficult to modify the code to add a cloud link to a JSON report if that was more useful.

1 Like