I'm getting these errors from the Hubitat Dashboard app. How can I get more info to track down the source of the problem?
I'm wondering if that is an attribute in the hub info driver. @thebearmay ?
hmmm could be. 
There was a recent update to that app.... I didn't change the dashboard, but I did update the app through Hubitat Package Manager.
Is the device part of the dashboard device list?
If so, check the device edit page and take a look at the attribute value. I believe the error will occur even if the attribute is not used on the dashboard
yep that was it. 
So does that mean its a but with the current Hub Info Driver?.
I just checked again with HPM and it says I'm up to date. @thebearmay
Ideally it would be good to keep attributes under the 1024, but will let @thebearmay respond to your last question. I don't believe it should stop you using the device and other attributes on your dashboard, you will just see that warning in the logs.
hubUpdateResp hasn’t been part of the driver since 24Nov2021 (was only in there for 1-2 versions) so if you’re seeing that warning you’re not running the current code. I would recommend doing a HPM Repair on the driver to get the latest code, and then turn on the Removed Unused Attributes option - if you are on HE > 2.2.8.141 this will remove the attribute state if it still exists.
4 Likes
Well that's interesting because this is a screen grab directly from the Hub Information Drivers Code that is installed on my Hub. According to HPM and on github, I am running most current code
]
My Hub version is up to date and > 2.2.8.141...
With that said, I did enable the "remove unused attributes" option and I no longer see that attribute as a selection in the dashboard tile attributes list .... so I think that hopefully was all that was needed
1 Like
Yes, everything you mentioned would seem to check out. Basically what happens is you start by using a version of a driver that creates and maintains an attribute and then the developer chooses to remove it from the definition for that driver, as @thebearmay did in this case, but removing it from the driver just stops it from being created, it does not remove it from existing devices that used the earlier version of the code. To remove the old attribute the developer needs to have the driver run a command to remove the attribute, which is what gets called when you turn on the setting to clean them up.
You must have been getting that error for a while then. Discovered that the update notes were being brought back into that attribute and overflowing it so backed it out of the code. I may bring it back in some other form at some time - thinking as a link to the release notes when an update is available.
1 Like
Or you can remove the driver and the virtual device and reinstall, which is what I did when this occurred back when.
2 Likes
