data lags one hour? - Githubissues

nebgor / sma-bluetooth

Automatically exported from code.google.com/p/sma-bluetooth

0 stars 0 forks source link

data lags one hour? #14

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

I've noticed that for some reason - and I admit I've been too lazy to look. The 
data in the database is always one hour behind...

Last run using -v -d gave a final output of..
11/2/2011 14:09:35  total=13545342230331392.000 Kwh current=0 Watts togo=0 i=11 
crc=1073874040

looking at the db though..

2011-02-11 13:00:00 | 3000TL   | 2100085423 |         2160 |    6029.798 | NULL 
               | 0000-00-00 00:00:00 |

Cheers

Bret

Original issue reported on code.google.com by b...@ticm.com on 11 Feb 2011 at 6:16

GoogleCodeExporter commented 8 years ago

It works on the computer time is correct, especially timezone.

What timezone are you in? If non daylight saving such as qld I may have a 
request for a scan from you.

Original comment by stephenb...@gmail.com on 12 Feb 2011 at 3:18

GoogleCodeExporter commented 8 years ago

I'm in WA, session log attached
Second issue noted... date error

Original comment by b...@ticm.com on 12 Feb 2011 at 3:45

Attachments:

session.log

GoogleCodeExporter commented 8 years ago

Re ran this with an older build - see attached session log
Looks like it might be an error in the timestamp calc..

Original comment by b...@ticm.com on 12 Feb 2011 at 3:48

Attachments:

session.log

GoogleCodeExporter commented 8 years ago

I'll have a look at the time on the inverter. It may be an issue. Use Sunny 
Explorer ( if you have it) and go into options and see what it says the time 
is. It definitely looks like a daylight saving time issue.

Original comment by stephenb...@gmail.com on 13 Feb 2011 at 6:12

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Is this still a problem

Original comment by stephenb...@gmail.com on 20 Apr 2011 at 6:05

GoogleCodeExporter commented 8 years ago

Not sure - my reporting copes with it now ...

Original comment by b...@ticm.com on 20 Apr 2011 at 6:22

GoogleCodeExporter commented 8 years ago

Yes it is actually. However in reverse for me. The data in the database is 2 
hours ahead of what is reported. The clocks on the inverter are synced with the 
computer, when i look at the output of smatool it also reports the correct 
value but it gets stored in the database with a difference of 2 hours.

I also did notice this when running sma tool with -d:

utc=2011-08-24 05:08 local=2011-08-24 07:08 diff 2 hours

Original comment by Blokker.1999@gmail.com on 24 Aug 2011 at 5:13

GoogleCodeExporter commented 8 years ago

Found the cause of mine. The SQL is on a remote machine in a different 
timezone. Somewhy the times get translated to that timezone. After changing the 
remote machine to the same time zone the reported times are correct.

Original comment by Blokker.1999@gmail.com on 24 Aug 2011 at 8:13

GoogleCodeExporter commented 8 years ago

Is this still problem?

reopen if still bad

Original comment by stephenb...@gmail.com on 27 Nov 2011 at 4:41

Changed state: Done