All of the sudden these events started appearing in the log. It started after making changes to a driver, however I'm baffled as to why... app 35 is Dashboard. Not a specific one, but the Dashboard parent app. This driver has no dashboards.
Thank you. I did read those, and found that I could work around it by disabling drivers until it stops... but since this started happening after I updated a driver I'd rather fix the source.
Problem: my driver doesn't have a notificationText attribute... so this appears to be coming from something responding to a Rule action based on my driver one supposes. So I'm looking for some way to narrow down which app is generating the event.
@bravenel all of these issues (the above ones and this one) have the common need to know where it's coming from. Can you get this error tweaked to indicate what is the source of the attribute which it has issues with?
Please re-read this thread. This has all of the answers to you questions. I could re-type them but this is faster.
The problem is one of your devices has an attribute over 1024 characters and that device is selected to be accessed by a dashboard app. Not displayed necessarily, just accessed. All the devices are loaded when the dashboard is.
It's right there in your logs. A device has this attribute and it is over 1024 characters. it doesn't have to be displayed on a dashboard, just toggled on as being available to add to that one. What devices do you have that have the attribute "notificationText"?
It is whatever dashboard app35 is. You can click on the WARN button and it should launch the dashboard app. not the dashboard itself, just the app for it.
35 is the dashboard parent. All of my dashboard apps are 3-digit numbers.
Here's some more timeline events with only built-in drivers and the Zooz driver. There's zero activity related to my driver here, and yet these started happening after an update to my driver.
app:352020-04-04 02:49:46.145 pm warnExcluded attribute notificationText size of attribute > 1024 characters
dev:3252020-04-04 02:49:44.127 pm infoPower Strip - LR Side Table energyDuration is 74.49 Days
dev:3252020-04-04 02:49:44.105 pm infoPower Strip - LR Side Table energy is 9.66 kWh
dev:3302020-04-04 02:49:44.098 pm infoLR Power Strip P5 - Controller Charging Station energyDuration is 74.49 Days
dev:3302020-04-04 02:49:44.029 pm infoLR Power Strip P5 - Controller Charging Station energy is 0.98 kWh
dev:3292020-04-04 02:49:43.991 pm infoLR Power Strip P4 - Ionic Pro energyDuration is 74.49 Days
dev:3292020-04-04 02:49:43.901 pm infoLR Power Strip P4 - Ionic Pro energy is 1.65 kWh
dev:3282020-04-04 02:49:43.834 pm infoLR Power Strip P3 - empty energyDuration is 74.49 Days
dev:3282020-04-04 02:49:43.584 pm infoLR Power Strip P3 - empty energy is 2.44 kWh
dev:3272020-04-04 02:49:43.455 pm infoLR Power Strip P2 - Physically Blocked energyDuration is 74.49 Days
dev:3262020-04-04 02:49:43.250 pm infoLR Power Strip P1 - Google Home energyDuration is 74.49 Days
dev:3272020-04-04 02:49:43.242 pm infoLR Power Strip P2 - Physically Blocked energy is 0.36 kWh
app:352020-04-04 02:49:43.122 pm warnExcluded attribute notificationText size of attribute > 1024 characters
dev:3262020-04-04 02:49:42.959 pm infoLR Power Strip P1 - Google Home energy is 4.23 kWh
dev:3252020-04-04 02:49:42.692 pm infoPower Strip - LR Side Table power is 5.5 W
dev:3302020-04-04 02:49:42.506 pm infoLR Power Strip P5 - Controller Charging Station power is 0 W
dev:3282020-04-04 02:49:42.336 pm infoLR Power Strip P3 - empty power is 3.1 W
dev:3292020-04-04 02:49:42.295 pm infoLR Power Strip P4 - Ionic Pro power is 0 W
dev:3272020-04-04 02:49:42.069 pm infoLR Power Strip P2 - Physically Blocked power is 0 W
dev:3262020-04-04 02:49:42.064 pm infoLR Power Strip P1 - Google Home power is 2.4 W
app:352020-04-04 02:49:38.116 pm warnExcluded attribute notificationText size of attribute > 1024 characters
dev:1052020-04-04 02:49:36.218 pm infoAeotec Switch6 power is 0.000 W
dev:1052020-04-04 02:49:36.117 pm infoAeotec Switch6 energy is 7.381 kWh
dev:1052020-04-04 02:49:36.113 pm infoAeotec Switch6 energyDuration is 305.79 Days
dev:1052020-04-04 02:49:36.015 pm infoAeotec Switch6 current is 0.000 A
dev:1052020-04-04 02:49:35.982 pm infoAeotec Switch6 voltage is 120.898 V
#1 apps don't have attributes. #2 you know what attributes the Hubitat drivers have since they follow the standard device capabilities described in the docs. So, I'm willing to bet this is coming from a custom driver.
#2 you can see what attributes your device have by clicking on them, can't you?
Think about it for a second.....the attributes name is notificationText. What devices do have that do notifications? Start with those. But you have a device that has that attribute because it is over 1024 characters.
I will say it again since you don't seem to be listening. There is a device on your system that has that attribute and that attribute has text in it and that text is longer than 1024 characters. So, when the dashboard app tries to load all the attributes for the devices within the dashboard, it can't load this one because it is too long.
Something is sending notifications to your phone that are over 1024 characters long. Or did...and the attribute is too long for the dashboard. You have to clear the attribute by sending another notificaiton.
I have nothing sending notifications to phones. I don't use that feature at all. How would I clear an attribute of something I don't do?
I found the attribute on the phone device, but there is no clearAttribute() feature available to me AFAIK. What's also interesting is there is no code to send anything to this phone, and yet that attribute currently contains nearly a week's worth of the Abode device logs.
I also don't understand why this started appearing after my driver update... on the dashboard parent. I have confirmed FYI that none of my dashboard apps have all devices enabled, nor have my Abode driver's device selected. So I have correlation that makes absolutely zero sense for causation
I think this is memory corruption or something else going on here.