Hi,
I am monitoring trends of my heat pump vs external temperature on a daily basis.
I am using for both a simple bargraph visualization with 86400 interval using directly temperature measured and power measured.
Both feeds are REALTIME PHPFINA.
The behaviour of temperature visualization is odd and unpredictable. In fact this visualization is, unfortunately, totally useless.
Any guess ?
Thanks,
Emiliano.
Re: Emoncms Bargraph issue
Emilliano, please sort out your screenshot above!
Paul
Re: Emoncms Bargraph issue
Screenshot fixed (I hope) Paul.
Any guess for the real issue ?
Thanks.
Re: Emoncms Bargraph issue
The screenshot is still blank for me, can you upload it to site here? Can you describe the problem your seeing in more detail too?
Re: Emoncms Bargraph issue
Mmmm ... here the screenshot as a link:
http://image.forumcommunity.it/8/3/4/8/2/3/5/1424596402.png
Basically bargraph of temperature is showing "random" values.
Re: Emoncms Bargraph issue
I think whats happening here is that your pulling out the temperature at a spot point every 24 hours rather than the average temperature for the day which is what I think your after? You cant get averages of underlying data with the PHPFina feed engine but you can with PHPFiwa (fixed interval with averaging). If your running this on a raspberrypi with the low write sd card version of emoncms PHPFiwa is not available unfortunately as it writes to the disk more often wearing the SD card out. Are you running the SD card emoncms?
Re: Emoncms Bargraph issue
I am using emoncms.org
But why one PHPFINA feed is working and the other one is not ?
Re: Emoncms Bargraph issue
Anyway is there a way to change Feed Engine for an existing feed ?
I have 1 year of data I'd prefer to not loose.
Re: Emoncms Bargraph issue
No I'm afraid not at the moment, there is further reading here about the recommended feed types to use.
As the present graph is not suitable for your needs, you could plot the existing data using a Rawdata chart, which is probably better than nothing, but not ideal.
Sometimes when a mistake like this has been made, it's less painful in the long term to lose the historical data and start afresh!
Paul