I am currently storing my data on the emoncms.org servers.
Since I updated both my Pi's to vlow-write v8.5. The data appears to update graphic displays very infrequently sometimes an hour apart for instance. I assume maybe incorrectly that this is a result of the new software's requirements to run locally on an SD card. All feeds seem to update correctly time interval wise.
I would like to run locally using hdd in the future but I am not sure how I would configure the system so that I can access all the data from 2 possibly 3 Pi's in one place.
If it is the new software or if it isn't can somebody point me in the right direction to get data updating at correct intervals again please?
Seperately
There are instructions to setup and migrate to an hdd but that would require an hdd for each Pi. And therefore I believe the data for each could not be combined to create graphical displays of data which comes from different Pi's.
I did try in the past to run Emoncms on my local machine (a Mac) but I became hopelessly confused very quickly.
My simple logic tells me that with multiple Pi's. Running Emoncms on a local machine would still be the only way to access all the data in one place.
Re: Emoncms.org data updating very infrequently
The interval/update rate to emoncms.org on low-write v8.5 should be no different. Did you update to the low-write v8.5 image? or just upgrade emoncms itself? Are you using emonhub? Emonhub does buffer and send data every 30s but it should buffer data recorded at 10s fine.
Re: Emoncms.org data updating very infrequently
Thanks Trystan, I purchased 2 new sd cards in early Jan from your shop with the software pre loaded. So yes I am using emonhub.
I notice now that when I look at a graphic of my feeds on emoncms.org the info under the graph shows intervals of 120 others have 900. but assuming that those are seconds it doesn't explain why data points are sometimes up to 1 hour apart.
I am really very ignorant of the inner workings of the system but up until around the time that I replaced the SD cards things were fine. However at the time that I changed the cards I also added another Pi and Emontx in a location on the property that could not transmit to my original Pi.
TBH I am not looking at it in a very scientific way but it is clear if I look at older data that the graphs have a lot more data points rather than straight lines running between data points up to an hour apart.
Is there a way that I can look at the data in a way that shows the intervals?
Re: Emoncms.org data updating very infrequently
If you zoom in on the default feed viewer in emoncms to a point where the view interval is 5 to 10 seconds and skip missing is unticked, then click on show csv you should be able to see the missing slots (shown as null) where there should otherwise be datapoints (assuming your nodes are recording at 10s) Here's a screenshot of the CSV view
https://openenergymonitor.org/emon/sites/default/files/exampledata.png
Re: Emoncms.org data updating very infrequently
I think I may have found an issue on emoncms.org in the way the input limiters where set that may have contributed to this issue as Im seeing , I've amended it and will keep an eye on it.
Re: Emoncms.org data updating very infrequently
It seems like the website has some issues. My feeds are not upfating now, for more than half an hour now.
It also occured one or two days ago for several hours during the night.
:-(
Re: Emoncms.org data updating very infrequently
Similar issues being seen by me too - no feed updates for the last hour or so - I was wondering why my solar was stuck on ~500W when it was bright sun outside. EmonTX, GLCD and Nanode are all talking to each other. Nanode reports the inputs being sent okay too but the feeds on emoncms haven't kept up-to-date :(
Re: Emoncms.org data updating very infrequently
Error received just now:
Can't connect to database, please verify credentials/configuration in settings.php
Error message: Too many connections
Re: Emoncms.org data updating very infrequently
I've started a new thread so that the topic of this thread can be separate, there is indeed an issue: https://openenergymonitor.org/emon/node/12240