I'm still waiting for a re-occurrence. Hopefully one of us catches it here soon.
INPUT NEEDED:
I'm trying to think of the best way to get the data that's in the app to elsewhere within the system. Right now, variable links are the only way to do so.
The problems:
- Hub variables don't scale very well, in part because they can't automatically be created so the user must make each one and then link them.
- I thought about dumping the table data into a variable to display the table in a dashboard tile. Hub variables are limited to <256 characters and the table it definitely bigger than that.
- I thought about creating a child device with an attribute for the table (like @thebearmay has done with the Hub info driver) but, again, the table is too large and parts of the HTML are blocked by the Dashboards app itself.
- I could create a child virtual device that correlates to each "row" in the table, but, again, this doesn't scale very well.
- I could create a child virtual device that houses an attribute for each table entry. I think this would be the most cumbersome to code (if it's even possible) and would likely result in a disaster of a device page.
So, I'm looking to see if anyone has any other ideas. No matter how far fetched, I'm open to ideas. Never know what might trigger the "ah-ha" moment.
