[BETA] Device Details Display Utility

In delving into the way that device drivers are constructed for HE I found myself bouncing from page to page to wrap my head around the details particularly if I was trying to look at 2 or more devices. To speed up my analysis I wrote a series of small apps, that I finally decided to consolidate into one slightly bigger one that gave me all of the details about a device in one place. The current working result is at:

https://raw.githubusercontent.com/thebearmay/hubitat/main/apps/deviceCharacteristics.groovy

App provides a quick way to get a listing of capabilities, attributes (summary and detail on type and current values), commands implemented (summary, and details on parameters and types), and device specific data.

12 Likes

Very similar to to GetAttributeApp, but with more details:

Hadn’t seen that before, but there are some similarities at the first layer.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

Just found this handy little info app, never knew it existed! Thanks.

1 Like

Trying to list all physical devices (75+) for my records. Works fine for the display, but fails for the report. Error messae and log file:


What hub platform version are you on? It is trying to run a replace on a Boolean data type, which is odd. I wonder if something changed on a recent platform that broke it.

I'm on 2.4.0.151. It is a list of device information from the details page. Line 243 is trying to replace a \ character.

The problem is that is trying to run replace on a Boolean (true/false) which obviously you cannot replace characters on a Boolean value. There would need to be more logging to determine what is happening exactly.

Oh I think I see.... its going through the device data, and assuming they are all strings. May need to add a check in there to verify the data type before attempting the replace. You must have some devices with true/false values in the device data, which is odd I have never seen anyone do that before.

App is overdue for a rewrite, but I'll take a look and see if I can do a quick patch to correct this issue.

2 Likes

Found the 4 devices that caused the error. Adding any one of them causes the error.
Zooz ZEN05 LR, Zooz ZEN05, an old Zooz double plug and a HomeSeer Floodlight Sensor.
Can paste the details if that would help.

A snapshot of details area of one would help make sure I'm testing appropriately. Thanks.

Detail displays
New ZEN05 LR


child device

HomeSeer Floodlight Sensor

Old Zooz double plug

child device

Did the screenshots help? If not would it help to create a version with logging capabilities for me to run to figure out which data that's causing the problem?

I pushed up a new version late last night that should correct that issue.

Works great. I especially like that the report is pushed to a URL on the hub.
Could you do that for your other reports? Like the Rule References Rule Table app.

Shouldn't be hard to do, I'll look at it.