Re: [weewx-user] Best practice to merge weewx.conf changes on update

['loonsailor' via weewx-user]

"whew.conf: I like that!"

Thanks, autocorrect!
On Tuesday, April 26, 2022 at 4:51:36 PM UTC-7 tke...@gmail.com wrote:

> whew.conf: I like that!
>
> The configuration file really hasn't changed that much in a long time. The 
> biggest change is in how default values are handled, but the old methods 
> will continue to work. There are also options for controlling logging.
>
> You can look through the modern version and see if there's anything that 
> catches your eye, but I doubt it. 
> https://github.com/weewx/weewx/blob/master/weewx.conf
>
>
>
> On Tue, Apr 26, 2022 at 4:31 PM 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> For a long time, I've been sticking with my old whew.conf file, ignoring 
>> the new ones that show up with each update.  It's been several years, and 
>> I'm wondering if / when my old conf file becomes outdated enough that I'm 
>> missing features, or creating problems.  Short of manually updating each 
>> time (error prone!) is there a good way to deal with this?  
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c8fe4910-870f-4689-a14a-cbad6e2e495bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c8fe4910-870f-4689-a14a-cbad6e2e495bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/211316ad-1c59-40d6-a6bc-fefc8fc4fa2fn%40googlegroups.com.

Re: [weewx-user] Best practice to merge weewx.conf changes on update

['loonsailor' via weewx-user]

Thanks.  Just wanted to make sure that I wasn't missing something obvious.

On Tuesday, April 26, 2022 at 5:49:33 PM UTC-7 n0...@n0nb.us wrote:

> * On 2022 26 Apr 18:32 -0500, 'loonsailor' via weewx-user wrote:
> > For a long time, I've been sticking with my old whew.conf file, ignoring 
> > the new ones that show up with each update. It's been several years, and 
> > I'm wondering if / when my old conf file becomes outdated enough that 
> I'm 
> > missing features, or creating problems. Short of manually updating each 
> > time (error prone!) is there a good way to deal with this? 
>
> I think manually is the only way. I use vimdiff which helps me avoid
> omissions and typos but requires knowing at least basic vi editing
> commands. The syntax highlighting makes it easy to spot differences
> between the files and on a line by line basis.
>
> - Nate
>
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9b62efe5-5161-4f96-b214-ac6ee7e7c8cdn%40googlegroups.com.

[weewx-user] Best practice to merge weewx.conf changes on update

['loonsailor' via weewx-user]

For a long time, I've been sticking with my old whew.conf file, ignoring 
the new ones that show up with each update.  It's been several years, and 
I'm wondering if / when my old conf file becomes outdated enough that I'm 
missing features, or creating problems.  Short of manually updating each 
time (error prone!) is there a good way to deal with this? 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c8fe4910-870f-4689-a14a-cbad6e2e495bn%40googlegroups.com.

Re: [weewx-user] Re: Can't get LOOP packets from WiFi logger

['loonsailor' via weewx-user]

rno 104] Connection reset by 
>> peer
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #2; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #3; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got zero 
>> instead
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] 
>> ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded.
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] ERROR 
>> weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe
>>
>> Sep 25 10:53:24 ubu-mini-weather weewx[198474] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>>
>> I'm not sure how often weewx tries these loop reads.  Archive interval is 
>> 10 minutes (both on weewx.conf and in hardware) but these loop reads don't 
>> seem to be synced with that. It only fails once every 2-3 hours, but of 
>> course it shouldn't fail at all.
>>
>> I lengthened the timeouts in the weeWx config, as much as seems 
>> reasonable. tcp_send_delay is now 1.  It was 0.5, and I was getting a lot 
>> more ip-write errors, but I still got one error even with the longer delay. 
>>  I was getting a lot more ip-write errors until I did that, though you can 
>> see that I still got one of those this morning.  Vantage Timeout is now 10 
>> seconds (it defaulted to 6) but I'm not sure that had any effect.
>>
>> I've set the parameters on the WFL very conservatively.  The console 
>> archive interval is 10 minutes, all data exports are disabled (both 
>> individually and the "upload data" on the System setup screen), TCP port == 
>> Pause, Sleep Mode == Disabled.  Web Interface == Enable, but I've been 
>> closing any browser windows that point to it so it doesn't spend time on 
>> web page updates.  Stay Alive was set to "google + gateway", but I just set 
>> it to "disable" to see if that helps. 
>>
>> I suspected that the WiFi communications might be the issue.  the wifi 
>> signal from the WFL is quite weak.  I moved it last night to just a few 
>> feet from a strong AP.  That seems to have reduced the errors, but as you 
>> can see it hasn't stopped them.  FWIW, even when located just 5 feet from 
>> the AP, my AP reports the signal from the WFL at -61dBm, which is quite 
>> low.  I wonder if that's normal for the device.
>>
>> I love the convenience of the WFL, but unless this problem can be solved, 
>> I'm not sure I'd recommend it, and I may return it for the Davis wired 
>> interface.
>>
>> BTW, I sent this as an e-mail to Ryan at Scaled Instruments (from whom I 
>> bought the station and the interface).  He responded instantly, but wasn't 
>> able to help directly.  He forwarded the e-mail to Wojtek, the developer of 
>> the device.  I would have sent him the e-mail, except that there's no 
>> contact information on his web site.  Ryan also promised a full refund if I 
>> can't solve it.  He's been great to deal with.
>>
>> Anybody have any ideas or wisdom?  In any event, I'll update as I learn 
>> more.
>>
>>
>>
>> On Thursday, September 24, 2020 at 11:14:24 AM UTC-7 loonsailor wrote:
>>
>>> I'm still getting the LOOP errors, not every time, so the system does 
>>> work, but more often than I like.  Once every few hours it will exhaust all 
>>> 4 retries and I lose a record.
>>>
>>> I'm continuing to play with some parameters, both in weewx.conf and on 
>>> the WFL.  I'll update when I know more.
>>>
>>> On Thursday, September 24, 2020 at 7:13:57 AM UTC-7 graha...@gmail.com 
>>> wrote:
>>>
>>>> the wifi logger looks attractive, for getting rid of the cable.
>>>> could someone tell me the firmware version of my davis vp2 envoy? i 
>>>> haven’t updated it for a while :-) but my console is older. wifi logger 
>>>> needs vp2 v1.9+.
>>>> wee_device says:
>>>> CONSOLE FIRMWARE:
>>>>   Date: Apr 10 2006
>>>>   Version:  
>>>>
>>>> On 23 Sep 2020, at 9:54 am, 'loonsailor' via weewx-user <
>>>> weewx...@googlegroups.com> wrote:
>>>>
>>>> WiFiLogger 2 <https://wifilogger.net/> (firmware 2.33)
>>>>
>>>>
>>>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f828f81d-d939-4f1c-a45a-7a655708a5a7n%40googlegroups.com.

Re: [weewx-user] Re: Can't get LOOP packets from WiFi logger

['loonsailor' via weewx-user]

I suspected that the WiFi communications might be the issue.  the wifi 
signal from the WFL is quite weak.  I moved it last night to just a few 
feet from a strong AP.  That seems to have reduced the errors, but as you 
can see it hasn't stopped them.  FWIW, even when located just 5 feet from 
the AP, my AP reports the signal from the WFL at -61dBm, which is quite 
low.  I wonder if that's normal for the device.

I love the convenience of the WFL, but unless this problem can be solved, 
I'm not sure I'd recommend it, and I may return it for the Davis wired 
interface.

BTW, I sent this as an e-mail to Ryan at Scaled Instruments (from whom I 
bought the station and the interface).  He responded instantly, but wasn't 
able to help directly.  He forwarded the e-mail to Wojtek, the developer of 
the device.  I would have sent him the e-mail, except that there's no 
contact information on his web site.  Ryan also promised a full refund if I 
can't solve it.  He's been great to deal with.

Anybody have any ideas or wisdom?  In any event, I'll update as I learn 
more.



On Thursday, September 24, 2020 at 11:14:24 AM UTC-7 loonsailor wrote:

> I'm still getting the LOOP errors, not every time, so the system does 
> work, but more often than I like.  Once every few hours it will exhaust all 
> 4 retries and I lose a record.
>
> I'm continuing to play with some parameters, both in weewx.conf and on the 
> WFL.  I'll update when I know more.
>
> On Thursday, September 24, 2020 at 7:13:57 AM UTC-7 graha...@gmail.com 
> wrote:
>
>> the wifi logger looks attractive, for getting rid of the cable.
>> could someone tell me the firmware version of my davis vp2 envoy? i 
>> haven’t updated it for a while :-) but my console is older. wifi logger 
>> needs vp2 v1.9+.
>> wee_device says:
>> CONSOLE FIRMWARE:
>>   Date: Apr 10 2006
>>   Version:  
>>
>> On 23 Sep 2020, at 9:54 am, 'loonsailor' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>> WiFiLogger 2 <https://wifilogger.net/> (firmware 2.33)
>>
>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e17c0c83-80f1-4e26-b483-8246e701ad0fn%40googlegroups.com.

[weewx-user] Re: Extension to read purpleAir data via json?

['loonsailor' via weewx-user]

Thanks, Vince.  I had a look at the extension and it was very helpful. 
 I've written a python program to get and parse the json for the station, 
but haven't turned it into a weewx extension, and don't know if / when I 
will.  I used to be a professional coder, but that was some decades ago. 
 The coding isn't a barrier for me - I haven't done much Python, but that's 
not such a biggie - but GitHub is totally new and mysterious!

On Wednesday, September 23, 2020 at 1:06:40 PM UTC-7 vince wrote:

> On Wednesday, September 23, 2020 at 12:03:21 PM UTC-7, loonsailor wrote:
>>
>> I'd like to add air quality to my weewx data.  There is a purple air 
>> sensor very near to me, but it's not mine and I don't have lan access to 
>> it.  It does report to purpleair.com, and I can read the data from there 
>> in json format.  I thought I remembered seeing that somebody had done an 
>> extension to read from purple air.com, instead of accessing the sensor 
>> directly, but I can't find it now.  Does it exist, or was I imagining it?
>
>
> I have an extension at https://github.com/vinceskahan/weewx-purpleair 
> that you can probably tweak a little to do this.
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9aadfa4-5082-4839-9db4-437b9d23ee87n%40googlegroups.com.

Re: [weewx-user] Re: Can't get LOOP packets from WiFi logger

['loonsailor' via weewx-user]

I'm still getting the LOOP errors, not every time, so the system does work, 
but more often than I like.  Once every few hours it will exhaust all 4 
retries and I lose a record.

I'm continuing to play with some parameters, both in weewx.conf and on the 
WFL.  I'll update when I know more.

On Thursday, September 24, 2020 at 7:13:57 AM UTC-7 graha...@gmail.com 
wrote:

> the wifi logger looks attractive, for getting rid of the cable.
> could someone tell me the firmware version of my davis vp2 envoy? i 
> haven’t updated it for a while :-) but my console is older. wifi logger 
> needs vp2 v1.9+.
> wee_device says:
> CONSOLE FIRMWARE:
>   Date: Apr 10 2006
>   Version:  
>
> On 23 Sep 2020, at 9:54 am, 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
> WiFiLogger 2 <https://wifilogger.net/> (firmware 2.33)
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/60e16b46-5dec-45df-aa39-af6991385a45n%40googlegroups.com.

[weewx-user] Extension to read purpleAir data via json?

['loonsailor' via weewx-user]

I'd like to add air quality to my weewx data.  There is a purple air sensor 
very near to me, but it's not mine and I don't have lan access to it.  It 
does report to purpleair.com, and I can read the data from there in json 
format.  I thought I remembered seeing that somebody had done an extension 
to read from purple air.com, instead of accessing the sensor directly, but 
I can't find it now.  Does it exist, or was I imagining it?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32275c47-dceb-4ad9-be8b-55a5416b7fa3n%40googlegroups.com.

[weewx-user] Re: Can't get LOOP packets from WiFi logger

['loonsailor' via weewx-user]

Charlie, thanks for posting this!  I'm switching from my ancient vantage 
pro, connected via lantronix serial<->ethernet to a shiny new vantage pro 2 
with the WiFiLogger 2  (firmware 2.33).  I ran into 
the same problem:

Sep 22 10:56:59 ubu-mini-weather weewx[178549] INFO weewx.manager: Starting 
backfill of daily summaries

Sep 22 10:57:00 ubu-mini-weather weewx[178549] INFO weewx.engine: Starting 
main packet loop.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #1; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #2; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #3; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #4; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP max tries (4) exceeded.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] INFO weewx.engine: Main loop 
exiting. Shutting engine down.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] CRITICAL __main__:   
Waiting 60 seconds then retrying...
After several frustrating hours of trying to fix it, I searched the forum 
and found your post.  Sure enough, changing the WiFiLogger configuration 
Setup > System > General Settings > TCP Port to Pause (there was no 
"auto-pause") fixed the problem, and it's running great now.  Going through 
the log, I still find a couple of the loop errors, but they're rare now, 
and the retry gets it right.

A couple of checklist items for anybody else doing this.  The weewx config 
items are all in the Vantage section of weewx.conf.  The wfl items are set 
using a browser to access the web server built into the wfl.

   - Make sure the WiFiLogger (wfl) port number (setup->wiFi setup->tcp 
   port settings, default 2)  matches weewx.conf items tcp_port and port. 
Actually, the "port" item is probably not used, but I just set them both.
   - Make sure the wfl is at a fixed ip address on your lan, and that 
   weewx.conf "host" is set to that address.  You can fix the IP address 
   either in your router (preferable, IMHO) or on the wfl itself (Setup->WiFi 
   Setup->Connect to Router->Advanced Options).
   - I'm using loop type 2 (loop_request = 2 in weewx.conf), but I'm not 
   sure this matters.
   - Make sure the archive intervals match.  In weewx.conf it's 
   archive_interval in the StdArchive section.  On the wfl it's Setup->Weather 
   Station Setup->Set Archive Interval, BUT the units are seconds in 
   weewx.conf, minutes in wfl.  So, mine are 10 minutes on the wfl, 600 in 
   weewx.conf.
   
I haven't had it running for long, but it's very nice to have a wireless 
connection to the Davis console, and to stick my old Lantronix on a shelf.

Thanks again for posting the fix, Charlie.
On Sunday, November 25, 2018 at 7:40:18 PM UTC-8 cfor...@gmail.com wrote:

>
> On Saturday, November 24, 2018 at 7:37:26 PM UTC-5, cfor...@gmail.com 
> wrote:
>>
>> WeeWx sees the WiFi logger and can get the archive packets, but not the 
>> LOOP packets. It always times out. 
>>
>
> It looks like the time out problems were caused by the TCP settings of the 
> WiFiLogger, not weewx.
>
> I know this isn't a WiFiLogger forum, but in the interest of anyone that 
> stumbles upon this same problem here's how I fixed things: In the 
> WiFiLogger I changed Setup > System > General Settings > TCP Port to 
> Auto-Pause. This is with WiFiLogger firmware 1.23. The timeout problems now 
> seem to be gone and weewx can get the LOOP packets as normal.
>
>
>
> Charlie
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/95d9b830-a255-4b73-b25e-2113b67ba237n%40googlegroups.com.

Re: [weewx-user] Can't update weewx from 3.8.0.1 (Ubuntu / Cheetah)

['loonsailor' via weewx-user]

Yeah, I know that I could have delved deeper and made it all work on Ubuntu 
18.04, but I kind of wanted to move to 20.04 anyway, so after playing with 
it for a while I tried the upgrade.  Now it just works, no issues.

Thanks for the input.

On Thursday, August 27, 2020 at 4:59:53 PM UTC-7 gjr80 wrote:

> Ah, here it is 
> <https://groups.google.com/g/weewx-user/c/GdlSK3vTvYE/m/4aGctnQxBAAJ>.
>
> Gary
>
> On Friday, 28 August 2020 at 09:02:46 UTC+10 gjr80 wrote:
>
>> @tkeffer Can’t lay my hands on your previous posts to check,  but this 
>> isn’t one of those quirks where if you install from the wrong directory pip 
>> picks up a config file it shouldn’t and installs to a location that the 
>> system can’t later find?
>>
>> Gary
>>
>> On Friday, 28 August 2020 at 08:46:52 UTC+10 loonsailor wrote:
>>
>>> I'm on Ubuntu 18.04LTS, which is based on Debian 10 (/etc/debian_version 
>>> = buster/sid).  So, I would have thought that it should be there.  Anyway, 
>>> I did install it with pip3:
>>>
>>>  $pip3 install cheetah3
>>>
>>>  ...
>>>
>>>  Successfully installed cheetah3-3.2.5
>>>
>>> and it still won't allow me to install the python3 version of weewx
>>>
>>>  $ sudo apt-get install weewx
>>>
>>>  ...
>>>
>>>  Some packages could not be installed. This may mean that you have
>>>
>>>  requested an impossible situation or if you are using the unstable
>>>
>>>  distribution that some required packages have not yet been created
>>>
>>>  or been moved out of Incoming.
>>>
>>>  ...
>>>
>>>  The following packages have unmet dependencies:
>>>
>>>   weewx : Depends: python3-cheetah but it is not installable
>>>
>>>  E: Unable to correct problems, you have held broken packages.
>>>
>>>
>>> So, I'm not sure what's happening.  Well, I think I'll use this an 
>>> excuse to update to ubuntu 20.04LTS.  Maybe the problem will fix itself 
>>> with the OS upgrade.
>>>
>>>
>>>
>>> On Thursday, August 27, 2020 at 12:08:58 PM UTC-7 tke...@gmail.com 
>>> wrote:
>>>
>>>> Don't know what you mean by "the same error message," but 
>>>> python3-cheetah is not available on all operating systems. In particular, 
>>>> it is not available on Debian 9 systems. In that case, you need to use 
>>>> pip3 
>>>> to install.
>>>>
>>>> On Thu, Aug 27, 2020 at 11:09 AM 'loonsailor' via weewx-user <
>>>> weewx...@googlegroups.com> wrote:
>>>>
>>>>> Well, I thought I had, but apparently not.  Talk about a rookie 
>>>>> mistake!  (Doh!)  After the update, the python2 version updates properly 
>>>>> to 
>>>>> v4.1.1.  But, the python3 version (switched by 'wget -qO - 
>>>>> http://weewx.com/apt/weewx-python3.list | sudo tee 
>>>>> /etc/apt/sources.list.d/weewx.list', then another apt-get update) still 
>>>>> gives me the same error message , as does an attempted install of 
>>>>> python3-cheetah.
>>>>>
>>>>> On Thursday, August 27, 2020 at 9:55:13 AM UTC-7 blu...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Did you do a “sudo apt-get update”?
>>>>>>
>>>>>> On Aug 27, 2020, at 9:45 AM, 'loonsailor' via weewx-user <
>>>>>> weewx...@googlegroups.com> wrote:
>>>>>>
>>>>>> I'm trying to update my weewx installation.  When I use the python2 
>>>>>> version, 'apt-get install weewx' gets me 'weewx is already the newest 
>>>>>> version (3.8.0-1).'.  I know that we're up to 4.x.  So I try the python3 
>>>>>> version.  That gets me the following:
>>>>>>
>>>>>>
>>>>>> $ sudo apt-get install weewx
>>>>>> Reading package lists... Done
>>>>>> Building dependency tree   
>>>>>> Reading state information... Done
>>>>>> Some packages could not be installed. This may mean that you have
>>>>>> requested an impossible situation or if you are using the unstable
>>>>>> distribution that some required packages have not yet been cr

Re: [weewx-user] Can't update weewx from 3.8.0.1 (Ubuntu / Cheetah)

['loonsailor' via weewx-user]

I'm on Ubuntu 18.04LTS, which is based on Debian 10 (/etc/debian_version = 
buster/sid).  So, I would have thought that it should be there.  Anyway, I 
did install it with pip3:

 $pip3 install cheetah3

 ...

 Successfully installed cheetah3-3.2.5

and it still won't allow me to install the python3 version of weewx

 $ sudo apt-get install weewx

 ...

 Some packages could not be installed. This may mean that you have

 requested an impossible situation or if you are using the unstable

 distribution that some required packages have not yet been created

 or been moved out of Incoming.

 ...

 The following packages have unmet dependencies:

  weewx : Depends: python3-cheetah but it is not installable

 E: Unable to correct problems, you have held broken packages.


So, I'm not sure what's happening.  Well, I think I'll use this an excuse 
to update to ubuntu 20.04LTS.  Maybe the problem will fix itself with the 
OS upgrade.



On Thursday, August 27, 2020 at 12:08:58 PM UTC-7 tke...@gmail.com wrote:

> Don't know what you mean by "the same error message," but python3-cheetah 
> is not available on all operating systems. In particular, it is not 
> available on Debian 9 systems. In that case, you need to use pip3 to 
> install.
>
> On Thu, Aug 27, 2020 at 11:09 AM 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Well, I thought I had, but apparently not.  Talk about a rookie mistake! 
>>  (Doh!)  After the update, the python2 version updates properly to v4.1.1.  
>> But, the python3 version (switched by 'wget -qO - 
>> http://weewx.com/apt/weewx-python3.list | sudo tee 
>> /etc/apt/sources.list.d/weewx.list', then another apt-get update) still 
>> gives me the same error message , as does an attempted install of 
>> python3-cheetah.
>>
>> On Thursday, August 27, 2020 at 9:55:13 AM UTC-7 blu...@gmail.com wrote:
>>
>>> Did you do a “sudo apt-get update”?
>>>
>>> On Aug 27, 2020, at 9:45 AM, 'loonsailor' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
>>> I'm trying to update my weewx installation.  When I use the python2 
>>> version, 'apt-get install weewx' gets me 'weewx is already the newest 
>>> version (3.8.0-1).'.  I know that we're up to 4.x.  So I try the python3 
>>> version.  That gets me the following:
>>>
>>>
>>> $ sudo apt-get install weewx
>>> Reading package lists... Done
>>> Building dependency tree   
>>> Reading state information... Done
>>> Some packages could not be installed. This may mean that you have
>>> requested an impossible situation or if you are using the unstable
>>> distribution that some required packages have not yet been created
>>> or been moved out of Incoming.
>>> The following information may help to resolve the situation:
>>> The following packages have unmet dependencies:
>>>   weewx : Depends: python3-cheetah but it is not installable
>>>   E: Unable to correct problems, you have held broken packages.
>>>
>>> I've tried to install Cheetah, but I get this:
>>>
>>> $ sudo apt-get install python3-cheetah
>>>
>>> Reading package lists... Done
>>>
>>> Building dependency tree   
>>>
>>> Reading state information... Done
>>>
>>> Package python3-cheetah is not available, but is referred to by 
>>> another package.
>>>
>>> This may mean that the package is missing, has been obsoleted, or
>>>
>>> is only available from another source
>>>
>>> E: Package 'python3-cheetah' has no installation candidate
>>>
>>> I did the alternate installation ('pip3 install cheetah3').  That 
>>> succeeds, but I still can't install a python3 version of weewx, with the 
>>> same error message. What am I missing?
>>>
>>> (ubuntu 18.04LTS, python v2.7.17, python3 v 3.6.9)
>>>
>>>
>>> -- 
>>> 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 weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/04098d72-909f-4f7b-a4f3-8a92efe6c6f4n%40googlegroups.com
>>>  
>>> &

Re: [weewx-user] Can't update weewx from 3.8.0.1 (Ubuntu / Cheetah)

['loonsailor' via weewx-user]

Well, I thought I had, but apparently not.  Talk about a rookie mistake! 
 (Doh!)  After the update, the python2 version updates properly to v4.1.1. 
 But, the python3 version (switched by 'wget -qO - 
http://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list', then another apt-get update) still 
gives me the same error message , as does an attempted install of 
python3-cheetah.

On Thursday, August 27, 2020 at 9:55:13 AM UTC-7 blu...@gmail.com wrote:

> Did you do a “sudo apt-get update”?
>
> On Aug 27, 2020, at 9:45 AM, 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
> I'm trying to update my weewx installation.  When I use the python2 
> version, 'apt-get install weewx' gets me 'weewx is already the newest 
> version (3.8.0-1).'.  I know that we're up to 4.x.  So I try the python3 
> version.  That gets me the following:
>
>
> $ sudo apt-get install weewx
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
>   weewx : Depends: python3-cheetah but it is not installable
>   E: Unable to correct problems, you have held broken packages.
>
> I've tried to install Cheetah, but I get this:
>
> $ sudo apt-get install python3-cheetah
>
> Reading package lists... Done
>
> Building dependency tree   
>
> Reading state information... Done
>
> Package python3-cheetah is not available, but is referred to by 
> another package.
>
> This may mean that the package is missing, has been obsoleted, or
>
> is only available from another source
>
> E: Package 'python3-cheetah' has no installation candidate
>
> I did the alternate installation ('pip3 install cheetah3').  That 
> succeeds, but I still can't install a python3 version of weewx, with the 
> same error message. What am I missing?
>
> (ubuntu 18.04LTS, python v2.7.17, python3 v 3.6.9)
>
>
> -- 
> 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 weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/04098d72-909f-4f7b-a4f3-8a92efe6c6f4n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/04098d72-909f-4f7b-a4f3-8a92efe6c6f4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3a21d584-0831-4853-a1fe-ccbd3e9d6278n%40googlegroups.com.

[weewx-user] Can't update weewx from 3.8.0.1 (Ubuntu / Cheetah)

['loonsailor' via weewx-user]

I'm trying to update my weewx installation.  When I use the python2 
version, 'apt-get install weewx' gets me 'weewx is already the newest 
version (3.8.0-1).'.  I know that we're up to 4.x.  So I try the python3 
version.  That gets me the following:

$ sudo apt-get install weewx
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
  weewx : Depends: python3-cheetah but it is not installable
  E: Unable to correct problems, you have held broken packages.

I've tried to install Cheetah, but I get this:

$ sudo apt-get install python3-cheetah

Reading package lists... Done

Building dependency tree   

Reading state information... Done

Package python3-cheetah is not available, but is referred to by another 
package.

This may mean that the package is missing, has been obsoleted, or

is only available from another source

E: Package 'python3-cheetah' has no installation candidate

I did the alternate installation ('pip3 install cheetah3').  That succeeds, 
but I still can't install a python3 version of weewx, with the same error 
message. What am I missing?

(ubuntu 18.04LTS, python v2.7.17, python3 v 3.6.9)


-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/04098d72-909f-4f7b-a4f3-8a92efe6c6f4n%40googlegroups.com.

[weewx-user] Re: Advice on moving to new station hardware (prob ecowitt or ambinent)

['loonsailor' via weewx-user]

After all the useful input, I just ordered a Vantage Pro 2 from Scaled 
Instruments.  They've got a great price for them right now.  Also, at his 
suggestion I ordered a WiFiLogger 2.  I'll post later about how that works 
out.

Thanks to all for the advice and wisdom.

On Tuesday, August 25, 2020 at 1:15:40 PM UTC-7 loonsailor wrote:

> Thanks for the input everyone.  The reason I was considering a different 
> brand than Davis is connectivity.  Currently, my old Vantage console has an 
> option added to it which provides a serial output, which goes to a 
> Lantronix serial-ethernet server box (necessary because the station is too 
> far from the weewx computer to allow for the console to plug into the 
> computer directly).  My weewx.conf includes the following:
>
>  type = ethernet
>
> # If the connection type is serial, a port must be specified:  
>
>  port = 3001
>
> # If the connection type is ethernet, an IP Address/hostname is 
> required:
>
> host = 192.168.198.202
> It works fine, but the idea of a more "modern" station / console that has 
> wifi built in seemed more appealing.  Also, I can't tell from the Davis web 
> site if the connectivity I'm using now would still work identically with a 
> new Vantage Pro 2, or if there's an option I'd need, or ???  How do most 
> people here connect them?
>
> Also, since I want to add air quality sensors, it was unclear to me 
> whether that had to hook that in through my primary station, or if it could 
> be entirely separate.  If I stay with Davis, then buy either a PurpleAir or 
> a sensor+GW1000, is weewx fine with reading them both into the same db?
>
> BTW, Ambient quoted me a 2-month wait for the ultrasonic system, and it 
> sounds like Ecowitt won't sell me one in the US (they haven't confirmed 
> that to me yet) so it looks like that's not an option.
>
>
> On Monday, August 24, 2020 at 12:44:49 PM UTC-7 vince wrote:
>
>> On Monday, August 24, 2020 at 11:48:27 AM UTC-7, loonsailor wrote:
>>>
>>> I need a replacement for my 25-year-old Vantage Pro (original, not +) 
>>> and am considering either the Ecowitt 2551 or the 2553 or the Ambient 
>>> equivalents.   
>>>
>>
>> With a 25 history with Davis gear, why would you change vendors ?
>>
>> I'll also add a WH41 and a WH43 (or ambient equivalents) ar quality 
>>> sensors.
>>>
>>  
>> Easy - you can add a PurpleAir now and integrate it pretty easily into 
>> weewx. 
>>
>>
>>>1. Getting the air quality sensors set up is a stage-2 sort of 
>>>project for me, and I understand that it’s not completely 
>>> straightforward, 
>>>because there is no dedicated PM2.5 field in the standard DB.  
>>>
>>>
>> Not true as of weewx v4 which has air quality elements in the new default 
>> bigger (ie, 'wview-extended') schema, so that is actually pretty 
>> straightforward now.
>>
>> All comes down the usual price/size/look+feel/supportability things that 
>> only you can quantify.
>>
>> It might be worth contacting Davis support to see if your existing 
>> console+logger can be used with a Vue or VP2 sensor suite.  You can get a 
>> Vue sensor suite very inexpensively if you look at places like Scaled 
>> Instruments and Scientific Sales.  Heck a Vue sensor suite is only $165 or 
>> so. A complete VP2 sensor suite is $320 or so.
>>
>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3655954f-7bed-450f-92fc-16524c46f343n%40googlegroups.com.

[weewx-user] Re: Advice on moving to new station hardware (prob ecowitt or ambinent)

['loonsailor' via weewx-user]

Thanks for the input everyone.  The reason I was considering a different 
brand than Davis is connectivity.  Currently, my old Vantage console has an 
option added to it which provides a serial output, which goes to a 
Lantronix serial-ethernet server box (necessary because the station is too 
far from the weewx computer to allow for the console to plug into the 
computer directly).  My weewx.conf includes the following:

 type = ethernet

# If the connection type is serial, a port must be specified:  

 port = 3001

# If the connection type is ethernet, an IP Address/hostname is 
required:

host = 192.168.198.202
It works fine, but the idea of a more "modern" station / console that has 
wifi built in seemed more appealing.  Also, I can't tell from the Davis web 
site if the connectivity I'm using now would still work identically with a 
new Vantage Pro 2, or if there's an option I'd need, or ???  How do most 
people here connect them?

Also, since I want to add air quality sensors, it was unclear to me whether 
that had to hook that in through my primary station, or if it could be 
entirely separate.  If I stay with Davis, then buy either a PurpleAir or a 
sensor+GW1000, is weewx fine with reading them both into the same db?

BTW, Ambient quoted me a 2-month wait for the ultrasonic system, and it 
sounds like Ecowitt won't sell me one in the US (they haven't confirmed 
that to me yet) so it looks like that's not an option.


On Monday, August 24, 2020 at 12:44:49 PM UTC-7 vince wrote:

> On Monday, August 24, 2020 at 11:48:27 AM UTC-7, loonsailor wrote:
>>
>> I need a replacement for my 25-year-old Vantage Pro (original, not +) and 
>> am considering either the Ecowitt 2551 or the 2553 or the Ambient 
>> equivalents.   
>>
>
> With a 25 history with Davis gear, why would you change vendors ?
>
> I'll also add a WH41 and a WH43 (or ambient equivalents) ar quality 
>> sensors.
>>
>  
> Easy - you can add a PurpleAir now and integrate it pretty easily into 
> weewx. 
>
>
>>1. Getting the air quality sensors set up is a stage-2 sort of 
>>project for me, and I understand that it’s not completely 
>> straightforward, 
>>because there is no dedicated PM2.5 field in the standard DB.  
>>
>>
> Not true as of weewx v4 which has air quality elements in the new default 
> bigger (ie, 'wview-extended') schema, so that is actually pretty 
> straightforward now.
>
> All comes down the usual price/size/look+feel/supportability things that 
> only you can quantify.
>
> It might be worth contacting Davis support to see if your existing 
> console+logger can be used with a Vue or VP2 sensor suite.  You can get a 
> Vue sensor suite very inexpensively if you look at places like Scaled 
> Instruments and Scientific Sales.  Heck a Vue sensor suite is only $165 or 
> so. A complete VP2 sensor suite is $320 or so.
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/61629519-cdd1-4512-ad34-1e60e997e7c8n%40googlegroups.com.

[weewx-user] Advice on moving to new station hardware (prob ecowitt or ambinent)

['loonsailor' via weewx-user]

I need a replacement for my 25-year-old Vantage Pro (original, not +) and 
am considering either the Ecowitt 2551 or the 2553 or the Ambient 
equivalents.  I'll also add a WH41 and a WH43 (or ambient equivalents) ar 
quality sensors.  I've got a 25 year database of weather (started on wView) 
and I'm eager to keep it going.  A couple of questions:


   1. How does the ultrasonic anemometer compare to the one in the 
   mechanical ones in accuracy, reliability, and expected longevity?
   2. Of course, I will want to connect the new station to weeWx.  I see 
   that there is a new pull driver for the GW1000. Is it worth getting the 
   GW1000 for that purpose, or can I use the new driver with the console 
   included with the stations?
   3. Is the maximum range from station to console the same for GW1000 and 
   the included console?
   4. One of the things I like about my ancient Vantage Pro is that there 
   is a 2-week memory in the station console.  If my linux server goes down 
   for any reason, upon startup weeWX will recapture the data that it missed 
   and populate the DB accordingly.  Very nice!  Is there any equivalent with 
   the stations / consoles that I’m considering?
   5. Getting the air quality sensors set up is a stage-2 sort of project 
   for me, and I understand that it’s not completely straightforward, because 
   there is no dedicated PM2.5 field in the standard DB.  Still, though I’ll 
   worry about that implementation a bit later, I’d like to plan for it.  With 
   that in mind, is there any reason to prefer the Ambient or the Ecowitt?  If 
   I’m picking up the data with weeWx, how does it get into one of the public 
   air quality maps?  Or, should I consider getting a PurpleAir instead?  I 
   know it’s pricier, but if there’s a good reason to go that way I’m open to 
   it.  

Any advice will be eagerly, gratefully accepted.  Thanks, in advance.


-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/07ce6fe1-5682-4780-9e82-ac43ca987a5dn%40googlegroups.com.

Re: [weewx-user] Re: Can't use my wview database

['loonsailor' via weewx-user]

Well, it took ~20 hours for wee_database --fix-strings to munge my old 
wview_archive.sdb on my little 1.6GHz Celeron (which, not so long ago, 
would have been a supercomputer!), but it worked!  To merge that data with 
the data from weewx for the last month, I opened weewx.sdb with sqlite3 and 
.dumped the archive table into a file, edited that file to get rid of the 
lines that packaged it as a transaction and created the table, then opened 
my newly repaired wview database and added the data that I had just dumped 
by .read.  Then I renamed my newly merged database, including all the data 
from both dbs, but only the archive table, to weewx.sdb, crossed my 
fingers, and restarted weewx.  Voila, it all works!  Took <5 minutes to 
build the new day summaries, etc.  And my site 
 now has data back to 2006.  

Thanks for all the help!  I'm looking forward to working with weewx.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Can't use my wview database

['loonsailor' via weewx-user]

I'm running it now with check-strings.  Taking a long time.  
Extrapolating out, looks like it could be 24 hours or so for 11 years of 
data (537K records).  Is that normal?  (1.6 GHz Celeron N3150, 4GHz ram)

Also, once its done (assuming it works) I was planning on merging the last 
month of data that weewx has gathered with the repaired wiew database using 
"DB Browser for SQLite", by exporting the records from weewx.sdb and then 
importing into the wview archive, both of which the browser does as text, 
then renaming the wview database weewx.sdb and restarting it.  Anything 
wrong with that plan?


On Wednesday, January 24, 2018 at 11:43:54 PM UTC-8, gjr80 wrote:
>
> On Thursday, 25 January 2018 16:15:03 UTC+10, loonsailor wrote:
>>
>> It's getting late. so I'll try this in the morning.
>>
>
> Generally a good idea to manipulate a database with a clear head (and 
> eyes) :)
>
> Gary
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Can't use my wview database

['loonsailor' via weewx-user]

Thanks, Gary.  It's getting late. so I'll try this in the morning.  Once 
again, thanks for your help!

On Wednesday, January 24, 2018 at 10:07:04 PM UTC-8, gjr80 wrote:
>
> Some answers below, as usual it's not just a simple yes/no.
>
> Gary
>
> On Thursday, 25 January 2018 15:41:48 UTC+10, loonsailor wrote:
>>
>> If I am to modify /etc/weewx/weewx.conf, I should stop weewx, back up 
>> weewx.conf, make the changes you suggest to it, and run wee_database.
>>
>
> Normal rule of thumb is that if you make changes to weewx.conf you need 
> to stop/start weeWX for the changes to take effect. That is true for weeWX, 
> but in this case we are running wee_database which will be run as a 
> completely separate process to weeWX. Also, since wee_database will only 
> be accessing your wview_archive_fixit.sdb database, weeWX could continue 
> to run and wee_database could be run on wview_binding and there would be 
> no database contention (assuming of course that weeWX is running using a 
> binding other than wview_binding for storing archive data). So chances 
> are you could leave weeWX running. I would play it safe though and stop 
> weeWX while running wee_database. 
>  
>
>>   If all goes as planned, I will then have a fixed archive, which I can 
>> go ahead and combine with my existing weewx archive (I've been running it 
>> for about a month now), put it in place, go back to the backed up .conf 
>> file, and restart weewx.  Is that right?
>>
>
> By way of 'backed up .conf file' do you mean mean weewx.conf as it was 
> before you added the wview binding? If so it does not matter, there is no 
> need to revert to a backed weewx.conf just becasue you added the wview 
> binding and now want to revert your weewx.conf. You can have dozens of 
> bindings defined in weewx.conf and weeWX will only use the one you define 
> at the data_binding config option in [StdArchive] for saving archive data 
> (you may well have other extensions installed that may use other bindings 
> for accessing data in other databases but these woudl be defined elsewhere) 
>
> But yes after running --fix-strings on your wview data you should have an 
> archive that you can merge with your weeWX data, of course providing that 
> the problem with your wview data was in fact null strings in numeric fields.
>
>
>> BTW, what does weewx do when there are multiple databases defined in 
>> .conf?  If I leave the existing archive, and add the new one as 
>> wview_archive_sqlite, what does that mean to weewx?
>>
>
> I guess the above comment already answered this, weeWX doesn't care about 
> unused bindings/databases defined in weewx.conf, weeWX only uses those it 
> is told to use any others are ignored. So leaving the existing archive data 
> binding ([[wx_binding]] I expect) and the new one will not be a problem, 
> the only issue is a cosmetic one of housekeeping; after doing this numerous 
> times (for whatever reason) you might end up with a lot of unused, 
> confusing junk in weewx.conf.
>  
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Can't use my wview database

['loonsailor' via weewx-user]

OK, I'm feeling a bit dense, so let me see if I understand.  If I am to 
modify /etc/weewx/weewx.conf, I should stop weewx, back up weewx.conf, make 
the changes you suggest to it, and run wee_database.  If all goes as 
planned, I will then have a fixed archive, which I can go ahead and combine 
with my existing weewx archive (I've been running it for about a month 
now), put it in place, go back to the backed up .conf file, and restart 
weewx.  Is that right?

BTW, what does weewx do when there are multiple databases defined in 
.conf?  If I leave the existing archive, and add the new one as 
wview_archive_sqlite, what does that mean to weewx?

Thanks.

On Wednesday, January 24, 2018 at 9:27:32 PM UTC-8, gjr80 wrote:
>
> Yep, the correct wee_database syntax 
>  will be a good 
> start :) You can't pass wee_database the database name directly, what you 
> need to do is define a data binding in a .conf file (might as well use 
> weewx.conf) that uses your database and then use the --binding option 
> with wee_database to tell wee_database which binding (and hence database) 
> to use. When you define a binding you (may) also need to define a database 
> under [Databases]. So if you define [[wview_binding]] and 
> [[wview_archive_sqlite]] in weewx.conf as follows:
>
> [DataBindings]
> 
>
> [[wview_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = wview_archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.wxmanager.WXDaySummaryManager
>
> [Databases]
> 
>
> [[wview_archive_sqlite]]
> database_name = wview-archive-fixit.sdb
> database_type = SQLite
>
> you should be able to use the following command:
>
> $ wee_database --fix-strings --binding=wview-binding
>
> Gary
>
>
> On Thursday, 25 January 2018 15:06:56 UTC+10, loonsailor wrote:
>>
>> I've finally returned from travelling, and I'm trying to get this 
>> resolved.  When I run wee_database, I get the following result:
>>
>> jerry@ubu-mini-weather:~/Wview$ wee_database --fix-strings wview-archive-
>> fixit.sdb 
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_database", line 793, in 
>> main()
>>   File "/usr/bin/wee_database", line 133, in main
>> config_path, config_dict = weecfg.read_config(options.config_path, 
>> args)
>>   File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
>> config_dict = configobj.ConfigObj(config_path, file_error=True)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
>> __init__
>> self._load(infile, configspec)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in 
>> _load
>> raise error
>> configobj.ConfigObjError: Parsing failed with several errors.
>> First error at line 2.
>> I get the exact same errors when I run with --check-strings, 
>> --fix-strings, or no switch at all.  Before I go slogging through code, and 
>> suggestions where I might start on resolving this?
>>
>> Thanks!
>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Can't use my wview database

['loonsailor' via weewx-user]

I've finally returned from travelling, and I'm trying to get this 
resolved.  When I run wee_database, I get the following result:

jerry@ubu-mini-weather:~/Wview$ wee_database --fix-strings wview-archive-
fixit.sdb 
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 793, in 
main()
  File "/usr/bin/wee_database", line 133, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 2.
I get the exact same errors when I run with --check-strings, --fix-strings, 
or no switch at all.  Before I go slogging through code, and suggestions 
where I might start on resolving this?

Thanks!

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Can't use my wview database

['loonsailor' via weewx-user]

I've got weewx running great on my shiny new ubuntu box, but I haven't been 
able to start it from my wview database, with 11 years of data.  I copy 
wview-archive.sdb to /var/lib/weewx/weex.sdb and start weewx, but it dies 
immediatlely, with the following in syslog:

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: engine: Archive will use data 
binding wx_binding

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: engine: Record generation 
will be attempted in 'hardware'

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: engine: Using archive 
interval of 600 seconds (specified by hardware)

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Jan 10 18:41:22 ubu-mini-weather weewx[5090]: manager: Starting backfill of 
daily summaries

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: engine: Caught unrecoverable 
exception in engine:

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   unsupported operand 
type(s) for +=: 'float' and 'unicode'

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   Traceback (most 
recent call last):

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/engine.py", line 865, in main

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   engine = 
engine_class(config_dict)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/engine.py", line 77, in __init__

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   
self.loadServices(config_dict)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/engine.py", line 141, in loadServices

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
config_dict))

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/engine.py", line 491, in __init__

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   
self.setup_database(config_dict)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/engine.py", line 604, in setup_database

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   _nrecs, _ndays 
= dbmanager.backfill_day_summary() # @UnusedVariable

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/manager.py", line 1454, in backfill_day_summary

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   
day_accum.addRecord(rec, 
weight=weight)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/accum.py", line 242, in addRecord

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   func(self, 
record, obs_type, add_hilo, weight)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/accum.py", line 301, in add_value

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   
self[obs_type].addSum(val, 
weight=weight)

Jan 10 18:41:23 ubu-mini-weather weewx[5090]: File 
"/usr/share/weewx/weewx/accum.py", line 88, in addSum

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   self.sum += 
val

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   TypeError: 
unsupported operand type(s) for +=: 'float' and 'unicode'

Jan 10 18:41:23 ubu-mini-weather weewx[5090]:   Exiting.


I've tried a couple of different database snapshots, always with the same 
result.  It quits very quickly, so the problem is not deep into the file 
(which is about 86MB). 

Where should I start looking?

Thanks! 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

Thanks, that did it!  Actually, I'm not sure whether it was the "port" or 
the "tcp_port" parameter in weewx.conf, so I changed both.  I'm up and 
running!  It barfed on importing my 15 years or so of data from wview, but 
that's a problem for another day, and I won't have a chance to dig into it 
for a couple of weeks.

Thanks again for all the help!  What a nice way to enter a new community.

On Wednesday, December 27, 2017 at 6:16:56 PM UTC-8, Tom Keffer wrote:
>
> The "host" line should just  be the IP address: no port.
>
> The "port" line should be the port.
>
> you're combining the two as "host".
>
> So, you want
>
> [Vantage]
>   type = ethernet
>   host = 192.168.198.202
>   port = 3001
>
> -tk
>
> On Wed, Dec 27, 2017 at 6:05 PM, 'loonsailor' via weewx-user <
> weewx...@googlegroups.com > wrote:
>
>> Thanks for this.  I was really excited.  Tried it, but it doesn't work.  
>> Specifically, here is the log file:
>>
>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Dec 27 18:00:32 ubu-mini-weather weewx[10902]:...done.
>> Dec 27 18:00:32 ubu-mini-weather systemd[1]: Started LSB: weewx weather 
>> system.
>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: vantage: Socket error 
>> while opening port 2 to ethernet host 192.168.198.202.
>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: import of driver failed: [
>> Errno 111] Connection refused ()
>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Unable to load 
>> driver: [Errno 111] Connection refused
>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]:   Exiting...
>>
>>
>>
>> The serial port converter wants to use socket 3001.  Worked fine in 
>> wview, so I chaged the socket address in weewx.conf to be 
>> 192.168.198.202:3001.  Then, I get the following:
>>
>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: vantage: Socket error 
>> while opening port 2 to ethernet host 192.168.198.202:3001.
>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: import of driver failed: [
>> Errno -2] Name or service not known ()
>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Unable to load 
>> driver: [Errno -2] Name or service not known
>> Dec 27 17:31:29 ubu-mini-weather weewx[10658]:...done.
>>
>> So, I'm not sure how to tell it to open the correct socket on the 
>> lantronix.  I'll have a look at the code, but any ideas?
>>
>> Thanks
>>
>> On Wednesday, December 27, 2017 at 11:03:43 AM UTC-8, Chris Alemany wrote:
>>
>>> Hi loonsailor,
>>>
>>> I have been using a serial to ethernet interface for years as well (with 
>>> the wview software).  I moved to weewx recently and after some digging 
>>> realized the support for serial-ethernet is there, just not documented up 
>>> front.
>>>
>>> Just go through the regular install process and when you get into the 
>>> weewx.conf file below is what I am using for my Serial-Ethernet bridge.  
>>> Exactly what I used for wview all this time.  Worked on the first try.
>>>
>>> Good luck!
>>>
>>> [Vantage]
>>> # This section is for the Davis Vantage series of weather stations.
>>> 
>>> # Connection type: serial or ethernet 
>>> #  serial (the classic VantagePro)
>>> #  ethernet (the WeatherLinkIP)
>>> type = ethernet
>>> 
>>> # If the connection type is serial, a port must be specified:
>>> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
>>> # /dev/ttyUSB0 is a common USB port name
>>> # /dev/ttyS0   is a common serial port name
>>> #   BSD:
>>> # /dev/cuaU0   is a common serial port name
>>> port = /dev/ttyUSB0
>>> 
>>> # If the connection type is ethernet, an IP Address/hostname is 
>>> required:
>>> host = 192.168.1.101
>>> 
>>> ##
>>> # The rest of this section rarely needs any attention. 
>>> # You can safely leave it "as is."
>>> ##
>>> 
>>> # Serial baud rate (usually 19200)
>>> baudrate = 19200
>>> 
>>> # TCP port 

[weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

Thanks for this.  I was really excited.  Tried it, but it doesn't work.  
Specifically, here is the log file:

Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Dec 27 18:00:32 ubu-mini-weather weewx[10902]:...done.
Dec 27 18:00:32 ubu-mini-weather systemd[1]: Started LSB: weewx weather 
system.
Dec 27 18:00:32 ubu-mini-weather weewx[10917]: vantage: Socket error while 
opening port 2 to ethernet host 192.168.198.202.
Dec 27 18:00:32 ubu-mini-weather weewx[10917]: import of driver failed: [
Errno 111] Connection refused ()
Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Unable to load driver
: [Errno 111] Connection refused
Dec 27 18:00:32 ubu-mini-weather weewx[10917]:   Exiting...



The serial port converter wants to use socket 3001.  Worked fine in wview, 
so I chaged the socket address in weewx.conf to be 192.168.198.202:3001.  
Then, I get the following:

Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Dec 27 17:31:29 ubu-mini-weather weewx[10673]: vantage: Socket error while 
opening port 2 to ethernet host 192.168.198.202:3001.
Dec 27 17:31:29 ubu-mini-weather weewx[10673]: import of driver failed: [
Errno -2] Name or service not known ()
Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Unable to load driver
: [Errno -2] Name or service not known
Dec 27 17:31:29 ubu-mini-weather weewx[10658]:...done.

So, I'm not sure how to tell it to open the correct socket on the 
lantronix.  I'll have a look at the code, but any ideas?

Thanks

On Wednesday, December 27, 2017 at 11:03:43 AM UTC-8, Chris Alemany wrote:
>
> Hi loonsailor,
>
> I have been using a serial to ethernet interface for years as well (with 
> the wview software).  I moved to weewx recently and after some digging 
> realized the support for serial-ethernet is there, just not documented up 
> front.
>
> Just go through the regular install process and when you get into the 
> weewx.conf file below is what I am using for my Serial-Ethernet bridge. 
>  Exactly what I used for wview all this time.  Worked on the first try.
>
> Good luck!
>
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
> 
> # Connection type: serial or ethernet 
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP)
> type = ethernet
> 
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
> port = /dev/ttyUSB0
> 
> # If the connection type is ethernet, an IP Address/hostname is 
> required:
> host = 192.168.1.101
> 
> ##
> # The rest of this section rarely needs any attention. 
> # You can safely leave it "as is."
> ##
> 
> # Serial baud rate (usually 19200)
> baudrate = 19200
> 
> # TCP port (when using the WeatherLinkIP)
> tcp_port = 4660
> 
> # TCP send delay (when using the WeatherLinkIP):
> tcp_send_delay = 0.5
> 
> # The id of your ISS station (usually 1). If you use a wind meter 
> connected
> # to a anemometer transmitter kit, use its id
> iss_id = 1
> 
> # How long to wait for a response from the station before giving up (in
> # seconds; must be greater than 2)
> timeout = 4
> 
> # How long to wait before trying again (in seconds)
> wait_before_retry = 1.2
> 
> # How many times to try before giving up:
> max_tries = 4
> 
> # The driver to use:
> driver = weewx.drivers.vantage
>
>
>
> On Tuesday, December 26, 2017 at 9:57:39 PM UTC-8, loonsailor wrote:
>>
>> My old computer, on which I've been running view for many years, has 
>> died.  I'd like to switch over to weewx, but I'm not sure if it will 
>> support my hardware.  I'm running an original vantage pro.  The console has 
>> a serial port, which I've connected to my LAN with a Lantronix 
>> serial-ethernet interface, an older version of this 
>>  one.  I can't move 
>> the console near my computer, because the wireless won't handle the walls 
>> and the distance.  So, I have uncertainty on two levels - the old Vantage 
>> Pro (not the newer + version), and the connection via a serial-ethernet 
>> interface.  Can I make this work, or do I need to rethink the whole thing?
>>
>> Thanks
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.co

[weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

I forgot to mention - running under Ubunto 17.10.

On Tuesday, December 26, 2017 at 9:57:39 PM UTC-8, loonsailor wrote:
>
> My old computer, on which I've been running view for many years, has died. 
>  I'd like to switch over to weewx, but I'm not sure if it will support my 
> hardware.  I'm running an original vantage pro.  The console has a serial 
> port, which I've connected to my LAN with a Lantronix serial-ethernet 
> interface, an older version of this 
>  one.  I can't move 
> the console near my computer, because the wireless won't handle the walls 
> and the distance.  So, I have uncertainty on two levels - the old Vantage 
> Pro (not the newer + version), and the connection via a serial-ethernet 
> interface.  Can I make this work, or do I need to rethink the whole thing?
>
> Thanks
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

My old computer, on which I've been running view for many years, has died. 
 I'd like to switch over to weewx, but I'm not sure if it will support my 
hardware.  I'm running an original vantage pro.  The console has a serial 
port, which I've connected to my LAN with a Lantronix serial-ethernet 
interface, an older version of this 
 one.  I can't move 
the console near my computer, because the wireless won't handle the walls 
and the distance.  So, I have uncertainty on two levels - the old Vantage 
Pro (not the newer + version), and the connection via a serial-ethernet 
interface.  Can I make this work, or do I need to rethink the whole thing?

Thanks

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.