Odd thing. If I leave the Dashboard open in a tab, and then go work in another tab, when I return to the tab with the Dashboard open, it is unresponsive. If I open the dashboards again, it then loads fine. This isn't right away. Not sure the time, but I could guess it's about an hour later.
I'm using Chrome Version 83.0.4103.34 (Official Build) beta (64-bit)
192.168.0.166 is my hub where HubiGraph lives, whereas 192.168.0.127 is my hub where the Dashboard is.
Chrome sleeps it’s tabs when you “background them”. There is a way to disable that through chrome://flags
When I access the URL given in the app the directly data is current. However when checking the dashboard icon it is stuck at the time I create it. I reread the instruction and I don't think I missed anything. I double checked the URL and changed the refresh rate in the chart settings (not the issue I know, but just tried it).
Is there something I missed, or anything else I should try to get the dashboard chart to update?
EDIT: never mind I checked back again and now it is updating
I wouldn't do that... it will chew up RAM until non remains free and potentially crash chrome and/or computer.
did anybody check if charts work for values below zero?
For example, if I wanna use my solar panels and electricity usage to compare them, sometimes production is higher than consumption that will create negative values.
Also most people outside the US and increasingly more people inside the US using celsius, so freezer temperature is below zero and winter temperatures also.
also, charts are already implemented in
somehow using Hubitat cloud.
Did you check if something can be used in this project?
even if there is not too much taxing on Local hub still cloud option can be interesting since hubs computing power isn't really stellar
I didn't "check" but my aeotec meter reported -1.118 on the "power" state and it was displayed correctly (multiple times)
Time for those with day jobs to lose some sleep tonight! That's right. Line Graphs now support AS MANY LINES AS YOU WANT. I asked my son to implement 2 lines while at work. He, being the overachiever that he is, used his COVID-19 quarantine time to implement "UNLIMITED" attributes on one graph. Just remember, with great power....
Also removed Sensor limitation. Line Graphs can now built with any device type
Updated code is HERE. Hopefully I did not screw up the commit. Some pointers:
After updating the devices and attributes, please revisit the "Configure Graph" page. Make sure your selections are correct. Remember: Each line has its own color and thickness settings because ... my son is an overachiever.
Thanks to my son (Alden) for his hard work today on behalf of our laziness (because no other group of people would go through so much trouble to avoid flicking a switch). Enjoy
This is awesome! Thank you and tell your son great job!
This is fantastic! You do know the next question though.....
Any way to implement filtering the graph view via selection when using the key?
OK so I am feeling dumb here. I don't have a "HTML virtual device", at least not by that name. I tried searching, and scrolling through alphabetically.
I went to "Devices" tab, and clicked "Add Virtual Device". From there, I am stuck.
It’s in the GitHub repo for this app. As HTML Device (html,groovy)
Just an fyi, I got rid of my dashboards tiles and created a link tile. The link you put in is the same HTML you put in the graph tile. It gives a full size webpage.
Thanks.
It wasn't clear in the instructions I guess. It said "Install 3 FILES" in step 5 and I did that. I don't see anywhere before you just start installing the app and building graphs etc where it mentions installing the DRIVER. Maybe I am blind?
@thomas.c.howard May I suggest that step 5 should say "Install 3 app codes and 1 driver code"
Just a guess, but when the OP was written there probably were three files in the GitHub repo. One driver and two apps. That’s still how this graphing solution works.
But at some point the child app that now says “legacy” in the name probably became redundant.
Wait, so what is "hubigraphs.groovy". I installed that too. Is that redundant also?
And one more thing while I am making suggestions.
Graphs were working, but timelines give me an error. "Endpoint creation failed".
Apparently OAuth needs to be enabled in hubigraph_line_graph.groovy AND hubigraph_time_line.groovy.
That should also be added to step 6.
Sorry it’s late and I can’t count apparently 
. The “legacy” child app presumably doesn’t do anything that's required for the app to work. I never even installed it.
You need a driver, the parent app, and the two child apps if you want to create both line and timeline graphs.
I guessed the Legacy App was just that. But you threw me off when you said 2 apps and 1 driver.
Thanks for clearing that up.
Download the Hubitat app
