Hello Felix,
first, many thanks, this update brought so many useful features, like multi graph, posting data from LAN! This is HUGE, big step up!
- The only thing I would see as being useful if it was in is some kinda color picker for multigraph (which by the way I can't thank you enough for it)
This though would need to change file in userMetric.. so I don't know, is it double? - Another thing is, edit multi graph as it, select which metrics you would like to see. Instead you have to delete it and create is again (unless I don't see where to do this)
- Cross node multi graph? use metric1 and 2 from node A and metric5 from node B (something for future version?)
Another thing I've found is:
- I've put speedtest to node 17
- I then moved the old usermetric and db to gateway
- node 17 was not in it then
- I couldn't added back 17, it said it was already existing
- deleted the db files for 17
- still couldn't add it, it still existed
Maybe it would come up in ~5min after speed test would be done
Thing of beauty and joy forever!
(https://i.imgur.com/xUkc68Z.png)
Glad you like it,
So you figured out the colors?
Basically if you want a specific color, it has to be defined in that metric's graph object, you can see how its done for various existing graphs.
Color picker? I thought this was pretty hard to achieve but ... keep dreaming maybe something will come of it :)
Dynamically pick/hide metrics in multigraph .. yes i wanted this too but .. it will have to be a future version. I think its acceptable for now since in most cases you'd pick the 2-3 metrics you really care for and then it never really changes.
Cross node multigraph? It will be done at some point, future version. It would be a major paradigm shift in some ways and how the front end list is shown, etc. One problem is with legends and crowding of so much data in 1 graph.
Let me know if there is still a problem with the speed-test data migration.
Yes of course I figured it out, line and fillColor, just so many colors to choose from and so many metrics I can get :)
I thought it is not trivial, maybe if there was limited set of predefined colors, would that be any easier? I will also look into this
And while we are at multigraphs, perhaps allow to have >1 multigraph per node. Temperature vs humidity and heating power vs temperature (for future version :))
QuoteIt would be a major paradigm shift in some ways and how the front end list is shown, etc. One problem is with legends and crowding of so much data in 1 graph.
Perhaps, but it might net have to be. Front end can still be like this. Just add one after the other (if nothing else for beta version, to see how that would work). Legends you could also add max of 4 (I don't know if you would need it even 2, since you can always drag your pointer to graph to see value and which one is it), then you don't even need to show it anymore, it is expected that you know or can check what you are looking at.
I understand, this can be a problem for mobile devices, but PCs have big screens and you can fit a lot of data on it.
QuoteLet me know if there is still a problem with the speed-test data migration.
Will check again later today
Quote from: LukaQ on May 09, 2019, 11:44:12 PM
And while we are at multigraphs, perhaps allow to have >1 multigraph per node. Temperature vs humidity and heating power vs temperature (for future version :))
That was my intent when I started coding it, then realized how much of a complication it would be, and thought it's a better idea to start with 1 only per node and see later if it's feasible to have multiple. "1" step at a time.
Hello, Mr. Felix
At first, I want to thank You for this great projects (Moteino, IoT_Gateway..)
I follow Your site lowpowerlabs, about 2 years and I make a few custom Moteinos (by Yours DIY Moteino tutorial) and Gateway on RPi3.
Now, when released new Gateway v9.0.0, I make a decision to translate GUI to Slovenian language (My family not speaking English..) and I don`t now if this is legal (but I use Gateway translation for My own)_ I just modified index.html and userMetrics.
I ordered a MightyHat in Your shop, to enable UPS function for Gateway.
If You would make in GUI (index.html) some subpage for ground_floor, 1st_floor, garage.. for separating nodes?
With respects, SLO_Rock
SLO_Rock,
Thanks for the feedback and compliments, much appreciated, and glad you like the app.
I think you're asking the same question as Luka above - about the ability of grouping nodes together in some way.
At some point I think I will do it, just nothing planned for release right now, I have other pressing things I need to work on at the moment.
Also, regarding other languages - I can only officially support English going forward, I don't think that will change, but its commendable that you took it upon yourself to translate the UI for your family.
Felix,
This issue happened last week but I just thought it was something I did wrong.. now out of the blue it happened again.
Pulling up the UI on my phone I noticed the icon changed on my DoorBell mote.. clicking on it I noticed that under the Type: field there was no type selected.. I had to re-select the type. Last week when it happened it was my SumpPump and Garage mote that this same thing happened. see attached
I am aware of a bug which causes the TYPE to be re-assigned if the TYPE is sent out by the mote.
But this seems a little different.
Anyway I will have a fix in the next version, I see nothing like this on my end so I think it's resolved.
If you want to do it now, you can replace this piece of code in gateway.js:
//handle TYPE metric
if (metric == 'TYPE') {
nodetype = metricsDef.determineValue(matchingMetric, tokenMatch);
if (metricsDef.motes[nodetype] && existingNode.type !== nodetype) {
existingNode.type = nodetype;
existingNode.icon = metricsDef.motes[nodetype].icon || existingNode.icon;
}
continue;
}
Well the change to gateway.js did not help the issue I'm having.
Is it possible to use httpendpoint to update RF nodes? I have been using an "api" js add-on to provide an interface to homekit, but it's not very stable due to the need to query the dB all the time. It would be great if this functioned like an API, so I could query status of the garagemote and even initiate an open/close command. Is that possible, or can I only interface with httpendpoint nodes?
At this point you certainly can append data to any node with the HTTP endpoint.
So a "node" can receive data from an RF node (by its ID) and/or through the HTTP endpoint (to that same ID).
If the ID is not specified then a new node with the IP address would be created as ID.
I'd like to give it a try. Does it still work on only Raspberry Pi 2?
Works fine on Pi3
Pi2 is pretty old, someone just reported (https://lowpowerlab.com/forum/pi-gateway/getting-err_connection_refused-with-clean-install/) having some issues getting the app to run.
I haven't tried it on a Pi2 in a long time, not even sure if I have one around.
The console output during setup should be watched carefully for any errors especially for the nginx install and the more finicky node packages like node-serial which were always problematic between Pi versions and OS releases.
PS @WhiteHare nice to see you around!
Felix, for next improvement, could you add option to graph two nodes in one graph. Example would be: sensor1 = node 2, sensor2 = node 3. Then have options to graph both, let's say you would want to compare indoor and outdoor temp and see relation
Duable?
And how do you use same scale for two metrics in multi-graph?
I have also found I problem, where I can't have 5 metrics on one node, if I have 6, last one does not appear and none of the previous ones don't update anymore
last thing I've added is Flow : { name:Flow', regexp:/\bFlw\:([\d\.]+)\b/i,
value:'',
duplicateInterval:3600,
unit:'m3/h',
pin:1,
graph:1,
graphOptions: {legendLbl:'m3/h',
lines: { steps: false, lineWidth:1 },
colors:['#326'],
//yaxis: { tickSize: 0.2},
series: { curvedLines: { active: true, apply: true, nrSplinePoints: 1},
lines: { show: true, fill: true, fillColor: "rgba(205, 80, 105, 0.3)" },
points: { show: false, fill: false },
autoMarkings: { enabled: true, showMinMax: true, showAvg: true, minMaxAlpha: 0.3, lineWidth: 1, avgcolor: "rgb(255, 0, 0)"},
}
}
},
Yes dual nodes on 1 graph is planned, it will take time, no ETA yet, sorry about that.
I will take a look at this if I find some time.
IMO 6 graphs is a LOT of data (too much possibly) to load on 1 graph. The issue is when you have 1000 data points in view for each. The Pi does extremely well with the aggregation algorithm but I personally have not tried it with more than 3-4 graphs, its so much data it's barely readable.
The thing is, I don't want to plot them all, didn't even try, I just want to log them, 6 separate metrics for one node (this specific one). I'm only talking about logging, no relation to graphs
And for 5 metrics, I can do that, if I try to have 6, whole gateway "stops". I graph only 3 not more.
If I remove 6th from the userMetrics (6th for this node, I have many more altogether), it starts to work again.
And this is via HTTPendpoint, this node, not over serial (RFM)
Felix (or anyone), can you tell me how versioning works for the gateway code? When I look at the github repository is says that v8.11.1 is the latest release. But "Gateway V9 Released" and accompanying release notes was an entry on the LowPowerLab home page dated May 8, 2019 and I saw a reference to v9.1.0 on this page https://lowpowerlab.com/guide/gateway/fail2ban/ (https://lowpowerlab.com/guide/gateway/fail2ban/) a few days ago. But I can't find any relevant changes in the github repository that details what's different in the code between v9.0.0 and v.9.1.0. Also, other than what's in the 2019 announcement, is any change log maintained? As the gateway is further developed it would really be nice to know what all has changed.
I appreciate the question. Sorry i haven't put more time into docs. Yes it is actively developed.
I am working on the 9.1 release. It's a major release with lots of important changes, fixes, optimizations, and some nice goodies IMO.
I will release a blog when this is ready and will put up more documentation on the github release.
I did not make a 9.0 release. Basically 9.0 is the head of the repository as it is published now, and would include all commits since last release. I will see if I can do that quickly before the 9.1 release, for completeness sake.
UPDATE: A 9.0 release was made here (https://github.com/LowPowerLab/RaspberryPi-Gateway/releases). There is also a V9.0 blog release (https://lowpowerlab.com/2019/05/08/gateway-v9-released/) with the change/new feature log.
That would be great Felix. Much appreciated!