Thanks Bernardino, Paul! Good idea about the clickable legend, I will try and do that. I was thinking that it would be quite nice to have the statistics: min, max, mean, watt hours, stdev shown in a box when you hover on each feed in the legend but wasn’t quite sure how to detect the feed being hovered over but that should be part of the show/hide code in the multigraph thanks to Chaveiro.
Happy to merge a pull request with the menu great!
Happy to remove the id from the legend, I will look into making the tag selectable.
I see your point on sorting the number of feeds in a hierarchy via tags in the sidebar, I reckon that will be the more complicated one to implement… i might have to come back to that one.
Mixing bars and plots is cool, here is a quick example of a graph (I can now save and embed etc) of the cpu temperature of a Pi installed at a site where the PV inverter is overheating and cooking everything in the plant room including my monitor, so it’s something I check frequently until they fix the overheating.
It would be nice to have some bar width control once we start playing with daily totals etc, The “fill” box isn’t utilized with bars, perhaps that could be also toggle “filling” the report period (not quite 100%, perhaps 90% to provide gaps) to toggle “line bars” or fill out to “interval bars” eg 1 day or 1 hour for the job at hand?
Great, yes I was wondering whether to make it possible to select different interval periods for each feed. So that its possible to add a daily bargraph but then have a higher resolution temperature feed overlayed, It could then size the bars to the interval of the feed… quite a bit of work to implement though.
I have enabled the toggling of series, I see now its done by jquery.flot.togglelegend.min.js. Which is not quite as easy to then adapt for showing statistics as I suggested above, so might leave that for now.
Personally I find it very useful and feel I would be lost without it, Having looked through some of my multigraphs I use it a fair bit (I have lots of graphs some with some without tags). When graphing a group of items with the same tag or items that only appear once in any account it is preferable to omit the tag as it is ugly, confusing and takes up screen/graph real estate. But equally there are times when it is absolutely vital they are there eg 12 feeds called temperature isn’t much use without the tags to say what area/rooms they are.
Does it prevent other things from working? or is it just the work involved? I think many (myself, very much included) would appreciate the choice and the effort made to provide that.
I would just like to avoid having a graph called “Area1” (could be a room or a building etc) with a legend saying
Area1 Lights power
Area1 Heating power
Area1 Ventilation power
Area1 temperature
etc etc
I have some tags like “RE_block_2_room_4” and “Main_block_DB3_L1” so things could get ugly quite quickly.
If they cannot be toggled I guess it would have to be always included, but that does seem like a big step backwards IMO, sorry!
EDIT - Love the toggling of series though
At first using the cpu_temp example above it would resize each time I toggled cpu_temp_max but not the other 2, discovered that setting the max scale sorted that issue, I had previously edited min scale to get rid of dead graph area but left max at auto. Works perfectly when both min scale and max scales are set.
Not sure if related to this addition, but during the last 2 days I have problems creating dashboards. Almost every type of visualization I add is red with the “Not configured or Authentication not valid” message. At first it only applied to Multigraphs, but this morning I cannot seem to add any graph at all.
Granted, I am not a super user, but I have managed to cobble together some dashboards in the past without any issues. I did a search on the community forum before posting here and did not find any others having the same or similar issues.
I have just checked this and can confirm your suspicions, it is this module that is preventing any other visualization from being configured correctly.
@TrystanLea, I have just tried adding a random selection of visualizations to a new dashboard and while the red box appears after selecting a vis’ configuring it does not allow it to display, even if saved and then “view” the vis’ appears unconfigured.
I tried removing the graphs Module and all was restored and working correctly. I then re-cloned the graphs module and lost the issue returned. Although removing or adding the module alone doesn’t change anything unless the page is refreshed so it is something that is loaded when the page gets loaded. The only noticeable difference to that page with or without the module installed is the addition of the “graph” option at the top of the visualization selection dropdown.
I previously had the graph module installed for a couple of months at least and had not noticed any problem before updating yesterday,
when we “Show CSV output” the 9x cpu_temp_max and 9x cpu_temp_min values are listed alongside the first 9 cpu_temp datapoints, appearing to give them timestamps spanning 2hrs not 8days.
.
EDIT - I have just noticed something that maybe of value, the number of datapoints and the timestamps seem to be driven by the first selected item on the table ie the top one, using the same example again, by deselecting the yellow cpu_temp trace in the lefthand panel and reselecting it so it effectively moves from the top to the bottom of the table, I now ONLY have the first 9 datapoints of each feed (data subset) included in the CSV output and they are 86400 secs apart.
IMO you should keep it on the work area, I would certainly like to be able to find the feed id, if you remove it could you provide a tooltip/hoverover? There again should it remain visible for assisting users that provide screendumps? I think keep it!
ID access is something I have been meaning to bring up in a general sense too. The old processlist edit page used to include the input ID at the head of the page, now it seems there is no way to obtain an input id without using a input/list api call or adding a “+input” to a processlist and getting the id from hovering over the shorthand processlist buttons on the input page.
And in contrast the feeds page prominently shows all feedids in the 1st column and also sorts by feedid too, so lists become very confused once you start retrospectively adding feeds at a later date. the default sort order should be based on feed name (within the tag groups) and perhaps the column display order should be Name first.
I would like to see less focus on feedids on the feeds page without losing them altogether like the inputs, and bring back the inputid in a discreet but logical location.
EDIT - Sorry slid a bit off topic there, maybe I should start a new thread about the general use of ids and their visibility (or lack of)
Would you consider putting the graph selector & save functions at the top of the feed list pane? the graph selector & save box is a fixed size that will be needed on most visits to the page and some users will only have short feed lists, some of us though have quite long feed lists, look at the size of the scroll bar handle for the left pane in this screendump.
Do you see the same issue when creating a multigraph?
This type of issue has been mentioned before with colour picking in some browsers and I do not recall the outcome, If it is not unique to the graphs module/page we should move this discussion another thread to keep on topic.
@TrystanLea - Sorry but I found another bug, when using the right hand axis, the legend is not right. the screenshot below is the same 3 feeds but the right boxes are selected rather than the left.
