graphs are working again, maybe something in cloud is down.. what about the messages coming out in the logging. don't see that is in the code and debugging is NOT on. thanks
Hoping that someone can point me in the right direction with something that should be fairly simple, but I can't get my head around it?
All I'm trying to do is create a graph plotting time (x) and temperature (y). Probably with say, 5 minute intervals.
I'd also like to see when a switch is on or off.
The purpose of this is to see the front room temperature and when my smart trv switches on or off (it's not really a smart trv, it's an actuator so just has simple on/off status).
I can never seem to produce anything visual that makes sense.
Easy? Depends. To start, I would set up a Time Graph that graphs the temperature. Assign it to the left axis. Then add your switch. HubiGraph allows setting state to a value. I would assign it to the right axis and set on to 100 and 0 to off. That should give you the display I think you want.
Just a quick note to say I've been waiting for an app like this! So nice to be able to graph data without having to go to huge extremes like trying to use node red!
Also a note to say there seems to be a bug with the legend. I turned it on for one graph and then turned it off and it won't remove the legend from the graph. Also, turning the background of the legend to transparent doesn't actually change the background color.
Thanks for the praise (and bug). I have a running bug list that I am going to address right after I release HubiWeather. I have decided to separate my graphing product from my Weather Product… Stay tuned….
Also, not sure if this has been mentioned and/or if it's a limitation of the google charts you're using but it would be nice to label a line on a graph with the name of the device that line is charting.
same thing intermittantly and on top of that automations stop working.. it appears that the jobs to rebuild the data archives offline storage are too hard on the hub.. problems started cropping up after i turned that on.. For now disabled that option again..
Any idea to my question why we cannot use the normal attributes in the devices that go back much more than the 30 your are using now?
@kahn-hubitat The answer to your questions really relies ALOT on how much data and how often you are storing data. I use this (LTS) on a 1200 point graph. How many points are you trying to save. Saving the data should not stop automations….
As for using history vs state… the fetch tends to be much slower in my experience; Also, although State is limited to 30 by default, history is limited to 100…not much difference in my book…
If you want similar behavior, just up state to 100 on those devices and you’ll get more data points
@djh_wolf, to figure out what is going on, could you use the browser debugger and look at the errors being given by the Java Script in the console? Step 4/4 is caused by JS errors. It could be an undefined option or loss of connection to internet. It could be missing data (I.e. zero events in the timeframe).
Thanks upped the couple of important weather devices to 100 now.. will see if that works ok without bogging the hub down when the graph load fails for some reason..
new to HE. I loaded hubigraph and it's showing up in my apps code section. I have no idea how to begin using it. I want to be able to graph some temp sensors over time as a start. Is there a simple 'click here. type this' how to so i can get started?
Welcome. When you say "loaded Hubigraph", I assume you used Package Manager? If so, as mentioned by @thebearmay add the App. Then I would recommend starting with a Time Graph for your purposes. You'll select you devices and some basic options. There are ALOT of options (I blame user requests for that ). Just post questions as you hit walls and we'll get you through. I believe HubiGraphs is fairly easy to use, but requires a bit of configuration if you want a fancy graph.
@djh_wolf. Thanks for the attempt. If the hub required a reboot, Hubigraphs could have done something bad, but to be honest the code is fairly straight forward. You are not "saving" too many events, so i don't see that Hubigraphs is causing the issue. BUT if you have any other data points, please let us know in the forum.
Has anyone else experienced weird issues with graphing the thermostat set point from an ecobee thermostat? I had my graph set up to show the set point along side the sensor temperatures over a certain time period. I also had long term storage enabled. Everything was working great, then this morning the graph got stuck on the 4/4 loading page. I took a look at the long term storage event counts of each device and it showed that the temperature sensors each had hundreds of points (I'm sampling every couple minutes) but the set point attribute only had 5 points. Hence why it was stuck on the 4/4 load screen since there would be a whole bunch of 0 data points trying to plot for the set point compared to the hundreds of sensor data points.
The device event log for the ecobee thermostat set point does indeed show very few data points recorded. Not sure if there's much I can do about this really, but wondering if anyone else has run into this issue.
Thanks again for this fantastic app! My infant daughter appreciates the adjustments made possible through the temperature monitoring