search

nebgor / sma-bluetooth

Automatically exported from code.google.com/p/sma-bluetooth
0 stars 0 forks source link

Daylight Saving Time (DST) not considered #58

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. download daily data with sma-bluetooth into MySQL DB
2. download same data using SMA's sunny explorer
3. Compare

What is the expected output? What do you see instead?
data from sma-bluetooth is 1 hour ahead -> e.g. current peak from 8:00 in sunny 
explorer is matched with current peak at 9:00 in sma-bluetooth

What version of the product are you using? On what operating system?
0.15
arch linux

Please provide any additional information below.

Original issue reported on code.google.com by joel.hat...@gmail.com on 15 Dec 2011 at 11:08

GoogleCodeExporter commented 9 years ago 
Hi,

I have had similar problems.  In my case the problem was that the inverter's 
time/timezone/DST setting was wrong.  I have sma-bluetooth on Linux, Sunny 
Explorer on Windows and a Sunny Beam which can't do Adelaide time all fighting 
for what the time and timezones are.

sma-bluetooth's 'setting' of the time as it collects data does not seem to 
stick, whereas there is a specific procedure to set the inverter time in Sunny 
Explorer.  Sunny Explorer tells you what the inverter time is in the bottom 
right hand corner - set it if it is wrong.

I fiddled around with it a lot until I've gotten it to work, and now I just 
hold my breath until Daylight Saving finishes :(

Original comment by djkammer...@gmail.com on 22 Dec 2011 at 2:36