To give a bit of information on what is coming next. The stable release above is partly to get everything in place ready for some more significant changes in the pipeline. Including:
New emonhub configuration user interface, removing the need to configure emonhub.conf directly GitHub - emoncms/config at nodes_ui. This includes functionality to calibrate a connected emonPi or serial connected emonTx from the interface and removes the need to hard code RFM node decoders in the emonhub.conf that we ship by default. This development integrates with work @Robert.Wall has been doing on new firmware for OpenEnergyMonitor hardware nodes.
Further development of the component manager to include the ability to install and remove modules/components. The installation process will involve a relatively easy process of looking through a list of modules that are available but not installed and clicking ‘install’.
I will post more detailed posts on each of these soon.
I upgraded just now on a lightly used emonPi. So far everything looks good, except that the inputs view is blank. The inputs are there and are feeding the, err, feeds correctly. I can graph data for the last hour without interruption and the feeds data shows last updated within the last minute for everything.
Hello @zag sounds like a browser cache issue, could you try doing a full page reload on the inputs page? What browser are you using? Can you see if there are any errors showing in your browser console?
(Firefox > application menu > Web developer > browser console)
Yep, it was the browser. I did a full page reload and it came up fine. I had a look in the console and I didn’t see anything from this page before or after loading.
@TrystanLea
Thank you – it works and is pretty cool.
And it finds a close by value if there is not a value at the exact specified time.
As far as I can make out (using phptimeseries) – it finds the nearest PRIOR time with a feed value UNLESS the specified time is less than 5 secs before the FOLLOWING time with a feed value.
That’s a bit of a mouthful … so an example …
Time=1600775170, Actual Value=85, FOUND Value=85
Time=1600775180 Actual Value=null, FOUND Value=85
Time=1600775190 Actual Value=null, FOUND Value=85
Time=1600775195 ~~~~~~~~~, FOUND Value=85
Time=1600775196 ~~~~~~~~~, FOUND Value=84
Time=1600775200 Actual Value=84, FOUND Value=84
I’ve stumbled across the answer - it’s necessary to express the UNIX times in milliseconds !
However that is inconsistent with the case when just seeking a single value.
And I found no reference to milliseconds on the Feed API Help page.
The only example on the page with an actual time (Insert multiple data points) shows UNIX time in secs
We are running V10.4 and have a dashbaord running in chrome after a few hours on the screen we a error with only the option to reload. the old version of Emoncms was ok
Hello @Pukka do you know what version you where running before the update or roughly how long ago that you last updated? Im not aware of significant changes that should affect this. There was a series of threads on similar issues last year but I think they were resolved Long term, always on Emoncms dashboard stability testing
