I just upgraded from 2.5.1 to 3.7.1.  I have spent the last week or so 
working out the kinks to get my web pages looking like they did before.  I 
use the Davis Envoy with a ethernet weatherlinkIP data logger and now I see 
"ip-read error: timed out" messages that I didn't see before the upgrade. 
 It appears that the data is coming in and being saved correctly ... just 
that the logger can't keep up all the time.   The database (weewx.sdb) has 
changed a lot (and was automatically converted at first run) so I have had 
to tweak the python programs that I wrote to convert the sqlite data to 
postgresql to be used by my plotting programs I wrote.  The stats.sdb file 
is not used anymore.  All the data is stored in weewx.sdb.

Some settings have been added.  I had a calibration formula for windchill 
that didn't work until I set the SdtWXCalculate entry for windchill to 
prefer_hardware.  I thought that it would have to be set to software but 
that didn't work... after all the  calibration formula is run in software. 
 My mistake. After checking the weewx python code I saw that the 
calibration would only be used if the SdtWXCalculate entry was other than 
software.

I only upgraded because I wanted to refresh the VM install to Debian 
testing and KDE... I run weewx in a VM on my desktop machine which runs 
24/7 anyway.  I had no problems with 2.5.1 so if you aren't into tweaking 
things it might be better to stay at 2.5.1.  

There may be reasons that Tom or others may be able to help determine the 
upgrade path you should take.  Hopefully they will speak up.

...bob


On Thursday, May 11, 2017 at 3:59:45 PM UTC-4, Mikael Djurfeldt wrote:
>
> I currently run WeeWx 2.5.1. Is it safe to upgrade directly to 3.7 are 
> there some versions in between which I should use as stepping stones?
>
> I'm using .deb.
>
> Best regards,
> Mikael
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to