C8 .166
I have read multiple threads on this and I know it's harmless but....
I haven't had this in years and at 05:30 this morning 2 of my Dashboards, which are almost identical, started this nonsense.
I have Tile Master and Tile Builder running with no changes at 5 am 
They all report around 400 char length; Tiile Master uses Bitly so that's well under as well.
Just curious how to get more granular as the log just gives the Dashboard ID.
I guess just disable tiles with the most infomation and re-enable/watch logs?
Tile Builder won’t publish tiles greater than 1,024, those will go to file or endpoint. But there is an option to load rooms css for better tile rendering. If you have done that it will generate that error as it is bigger than 1,024.
I had a look and only Hub Info and Owntrack pushed updates yesterday.
I don't have Hub Info attributes on my Dash so I thought it might be OT as there is a lot on that tile.
I deleted OT , Tile master, Tile Builder and a WebCore tile.
Nothing but HE supplied single device tiles and on every refresh I get the error.
So I really doubt it's anyones code that chamged at 05:30.
I did a reboot but maybe I'll repair the DB this time.
Attribute alertDescrFull size of attribute > 1024 characters
> This driver just recently added an attribute called 'alertDescrFull'. It concatenates the full weather alert descriptions of up to 10 weather alerts sourced from OpenWeatherMaps. In most cases the text in this attribute will be greater than the 1,024 character limit imposed on dashboard tiles. The intent of this attribute is to allow the user to do text searches in Rule Machine or WebCoRE and trigger off of those results. This attribute was never intended to be used in tiles.
1 Like
Unfortunately the mere presence of an attribute > 1,024 in a device that is added to a dashboard will trigger this error, even if the attribute is not placed on the dashboard itself.
I agree that a warning, not an error, is shown in the logs for the dashboard. There is no error or warning shown for the driver. Hubitat would need to give the user an option on what level of logging it shows (Error, Warning, Info, Trace) in the dashboard app to correct this.
