I have a nanode rf at home to send data to emoncms.org website. Last month suddenly the graph showed that i have negative consumption. So all the graphs and results for October are wrong. I didn't do any thing on my system at home or on my account in the emoncms website. I'm trying to find out what happened and also i want to see if there is any way to fix it. I tried to export my data to see what happened and i found that for about a minute i had negative values. Please respond if you have any ideas. Thank you!
ps. i have attached a pic and an excel file with my data.
Moved thread here from Emoncms Showcase forum - Moderator, BT
Re: Negative values on Emoncms
same happend to mee a while ago...
its when you reboot and it cant get the time from internet... it then defaults to 1970... and this backstep in time causes it to report negative....
the negative will slowly go towards positive....
Re: Negative values on Emoncms
Your problem is a very similar to this one: http://openenergymonitor.org/emon/node/5995
Re: Negative values on Emoncms
Suddenly since the previous weekend, some of my input last update and in feeds Updated fields using PHPFINA became negative (-1443855111s ago) . Some other sensor values using update with valid times.
The system time on raspi is UTC +2 .
In webpage Account the timezone is set to UTC+2.
Normal data displays for the positive update time of certain sensors are painted.
For the negative update times , no data is displayed.
I have read the FAQ but cannot find a reason for this behavior.
I am using emoncms v 8.3.5 on a read-only Raspberry Pi to forward data (no local storage) to the EMONCMS website.
Can anyone please help me?
Thanks in advance
Re: Negative values on Emoncms
it's probably the same thing as i was seeing due to daylight saving time
http://openenergymonitor.org/emon/node/11473
i also noticed all graphs use the browser's timezone instead of the timezone specified in the user settings page this cause display bugs (after the daylight saving time problem) like display the same day twice on the x axis of bargraphs instead, it does however display correct data. i'm using v9.0 though so not sure if it's at all related but i'm fairly certain if it happend since last weekend it's due to daylight saving time