Hi Bob- Things seems to be working well, thanks! *I appreciate the effort that goes into coding a driver.* As time allows I hope to look at the code a little. I've done a little protocol work and always found it interesting.
Of course I run with debug = 0, but I was having a little trouble uploading to various public sites, particularly Weather Underground which in my mind can be unreliable at times, so I was trying to debug it. If you look at the timestamps on the debug messages you can see they come fast and furious. From what I read, I thought I could put "debug=0" in the [WS6in1] to quite the driver only, but it seemed not to help. https://www.wunderground.com/dashboard/pws/KPAWASHI69 seems to be mostly OK though my station has disappeared from the map even while data is definately updating. (Makes me chuckle - having worked at IBM for a time.) Not unexpected for that site. On thing I did discover is that, in my mind, the "[[Wunderground]]" section of weewx.conf could be made clearer. The template includes fields for password and api_key, but after some trial an error I found that I had to specify what wunderground calls a "Key" in the password field to authenticate, so both fields are now set to the same value. Seems like a reasonable work-around. Once I get a little more familiar I may make or suggest a change (if only commentary). Thanks Again! Bob On Tuesday, May 31, 2022 at 3:29:21 AM UTC-4 Bob Atchley wrote: > The warning is because the checksum received for a message from the > console that is incorrect - not an issue as the driver simply re-requests > the data. > The DEBUG info is a left over from when I was debugging the driver. Agree > its a bit spammy, but setting the debug flag to 0 in weewx.conf should > remove these messages. > I will look at tidying up the debug messages at sometime in the future ... > > Glad its working, great to have another user > > Bob > > On Tuesday, 31 May 2022 at 00:27:27 UTC+1 [email protected] wrote: > >> @[email protected] >> >> Up and running (mostly). Looks like I'm on the map too (though I >> mis-typed the web site url). location = "Washington/South Strabane, PA" >> >> @Bob Atchley >> Looking forward to looking through the code, but it's working well. >> >> I did notice some startup warnings, like "WARNING user.ws6in1: >> genStartupRecords: bad CRC" >> >> Also when I turned on debug I was getting a slew of >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::got >> my_time: 1653571800 <http://voice.google.com/calls?a=nc,%2B11653571800> >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::gettint >> time >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::got >> my_time: 1653572100 >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::gettint >> time >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::got >> my_time: 1653572400 >> May 30 17:36:19 pi-wx-05 weewx[153046] DEBUG user.ws6in1: decode::gettint >> time >> >> Cheers, and Thanks Guys- >> Bob >> >> On Sunday, May 22, 2022 at 11:07:19 AM UTC-4 [email protected] wrote: >> >>> Hi Bob >>> >>> Your Logia looks to be identical to the Bresser 5-in-1 PC station I use >>> (model 7002571). With it being the PC version (as opposed to the wireless >>> version) you can use Bob Atchley's driver WS6in1. I've been using it since >>> November 2020 and it has worked flawlessly for me. You'll find full details >>> about it on Bob's github page: >>> https://github.com/bobatchley/weewx-ws6in1 >>> >>> In fact I've just checked and indeed the LOWSB510PB is listed. >>> >>> Don't forget to register your station when you setup WeeWX then you will >>> join a select band (currently 11 of us) on the WeeWX map who use the WS6in1 >>> driver ;-) >>> >>> Paul >>> On Saturday, 21 May 2022 at 23:50:37 UTC+1 vince wrote: >>> >>>> You're perhaps overthinking a bit. >>>> >>>> 1. weewx runs as root by default, so there's little gained by making a >>>> non-'pi' user really. As long as your pi is adequately secured (change >>>> the 'pi' password of course) you're probably ok with the default setup. >>>> You could choose to make a different non-privileged user but it gains >>>> little unless you change things to run as that non-privileged user rather >>>> than root, which ups the ante a bit re: permissions to talk to the >>>> hardware >>>> etc. I'd suggest just running the defaults at least initially. >>>> >>>> 2. I don't know why you're messing with setup.cfg at all. If you want >>>> to run a setup.py install, just go with it. It'll put everything under >>>> /home/weewx in one place. All you'll have to do is connect the >>>> public_html tree that will be created under /home/weewx/public_html to >>>> your >>>> webserver. FWIW, I just symlink it. You 'do' need to add a webserver on >>>> a pi since the os doesn't do that automagically for you. I recommend >>>> nginx. >>>> >>>> 3. When you ran 'python3 setup.py install' it should have asked you the >>>> questions needed to populate weewx.conf including which driver to use. >>>> I'd >>>> recommend using the Simulator for starters until you get used to the >>>> software. Once you have that set up you can stop weewx, delete your >>>> archive and public_html contents, reconfigure weewx to the right driver >>>> for >>>> your station, and restart weewx. Unfortunately I don't know anything >>>> about FO stations or if yours is supported or not so I can't help there. >>>> >>>> I think you want to run "sudo /home/weewx/bin/wee_config --reconfigure" >>>> and answer the questions again so it populates weewx.conf appropriately. >>>> >>>> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/14487c5c-5a45-4798-abe7-890d834fe2ecn%40googlegroups.com.
