Closed GoogleCodeExporter closed 9 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
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:
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:
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
Is this still a problem
Original comment by stephenb...@gmail.com
on 20 Apr 2011 at 6:05
Not sure - my reporting copes with it now ...
Original comment by b...@ticm.com
on 20 Apr 2011 at 6:22
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
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
Is this still problem?
reopen if still bad
Original comment by stephenb...@gmail.com
on 27 Nov 2011 at 4:41
Original issue reported on code.google.com by
b...@ticm.com
on 11 Feb 2011 at 6:16