[weewx-user] Re: NOOB Questions on "Installation using setup.py" on Raspberry Pi

2022-05-25 Thread radi...@gmail.com
OK - I think I got connected and allowed part of the log to be captured.  
Time to do more reading...

I read in the Logia manual that when plugged into a USB port, the console 
pulls some power via USB.  So I wanted to check for undervoltage with dmesg 
and noticed this when plugging in the console:

[356628.885042] usb 1-1.3: new full-speed USB device number 10 using dwc_otg
[356629.001467] usb 1-1.3: New USB device found, idVendor=1941, 
idProduct=8021, bcdDevice= 0.00
[356629.001511] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[356629.001536] usb 1-1.3: *Product: CCLEL C8488*
[356629.001558] usb 1-1.3: Manufacturer: Silicon Laboratories Inc.
[356629.001580] usb 1-1.3: SerialNumber: CCLEL c8488
[356629.024144] hid-generic 0003:1941:8021.001B: hiddev97,hidraw3: USB HID 
v1.11 Device [Silicon Laboratories Inc. CCLEL C8488] on 
usb-3f98.usb-1.3/input0

This would seem to confirm Bob Atchley's in comment in 
https://github.com/bobatchley/weewx-ws6in1 that the Logia is likely 
manufactured by CCL Electronics.

I've found dmseg to be helpful for a number of things, including what the 
OS "thinks" about a USB device plugged into a port as it tried to make it 
accessible.

Cheers,
Bob

Looks promising!

On Wednesday, May 25, 2022 at 10:50:03 AM UTC-4 radi...@gmail.com wrote:

> @Bob Atchley - Thanks!  Not confusing (to me) at all!  ;-)
>
> Very helpful- particularly the Wiki links.  My usage of GitHub has been 
> very limited from what I now see for WeeWX, so I'll have to do some 
> exploring.  I've used Wikis often but was unaware GitHub has such a rich 
> capability.
>
> Thanks Again-
> Bob
>
> On Monday, May 23, 2022 at 1:12:29 PM UTC-4 Bob Atchley wrote:
>
>> And just as a slight addendum to your original post ...
>>
>> I personally choose to run weewx as a non privileged user.  Its 
>> relatively simple to set up but the user does need to be in the www-data 
>> group to interface with the web server (assuming the web server is local) 
>> and needs permission to read/write to the usb see:
>> https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user
>>
>> I use systemd to start/stop the weewx service and you need to add the 
>> user name into the [service] part of the configuration e.g.
>> User= myUser  
>> Group=myUser
>> Again the brilliant weewx Wiki has some stuff on using systemd see:
>> https://github.com/weewx/weewx/wiki/systemd
>>
>> But as Vince says no need to do this, the default works out of the box 
>> ... but it can be done.  I found it useful while developing the WS6in1 
>> driver.
>>
>> Hope this helps rather than confuses
>>
>> Bob
>>
>>
>>
>> On Sunday, 22 May 2022 at 19:52:13 UTC+1 radi...@gmail.com wrote:
>>
>>> @vince - Yeah, overthinking is likely...
>>>
>>> My intent was to install WeeWX "out of the box" and get it up and 
>>> running, to get familiar with it  (quite possibly reinstall using one of 
>>> the other methods later thinking that might ease updates).  I ran into GPIO 
>>> access issues when trying to manipulate them through a web page a while 
>>> ago, so I planned to stick with "pi" initially.  I confess when I saw 
>>> /home/weewx mentioned several times, I *assumed *this implied a user.  
>>> Nowhere does it say this that I recall, so not a valid assumption.  (A 
>>> little sys admin bias perhaps.)  I've used Apache on most of my Pis, having 
>>> failed to get nginx to run at one time, and having used Apache for some 
>>> time.  I do have a hosted server which will be the target for observations 
>>> eventually.
>>>
>>> "*Why mess with setup.cfg?*"  The short answer is 
>>> https://weewx.com/docs/setup.htm says "To specify an install location 
>>> different from the default /home/weewx, modify the parameter home in 
>>> the setup.cfg file." Again, I didn't want to create a weewx user (my 
>>> assumption), and didn't understand the implications of what one chooses for 
>>> home.
>>>
>>> I did note that the code has to run under root / sudo.  Eventually I'll 
>>> run it under systemd (using root).
>>>
>>> I'll try wee_config --reconfigure when I get back to it.  Helpful tip, 
>>> thanks!
>>>
>>>
>>> @paul...@gmail.com 
>>>
>>> When researching what station to buy I did note Bob Atchley's driver but 
>>> didn't have the Logia model number on hand at the time.  Amazingly it does 
>>> match!  I was looking for a USB-connected station, and they are getting 
>>> harder to find it seems.  Appreciate the pointer to his git, and knowing 
>>> that you've had good success with it.  (With Cumulus I had written a 
>>> separate watchdog process because the comms were dropping fairly often.)
>>>
>>> I had planned on registering once I was up and running - so we'll be 
>>> 12!  ;-)
>>>
>>> Thanks Folks- Very favorable experience with my first post to the forum!
>>> Bob
>>>
>>> On Sunday, May 22, 2022 at 11:07:19 AM UTC-4 paul...@gmail.com wrote:
>>>
 Hi Bob

 Your Logia looks to be identical to the Bresser 5-in-1 PC station I use 
 (model 

Re: [weewx-user] Problem with weewx-airlink

2022-05-25 Thread 'John Kline' via weewx-user
You’re getting this because the timestamp is bad:
'ts': 85460

The specific message: user.airlink: last_report_time must be time since boot: 
85441 seconds.
is worded that way because I found airlink was reporting time since reboot 
(rather than time since epoch).  I observed this behavior until the airlink 
started reporting concentrations.  I specifically check for pm1 to determine 
this state.  In the case below, pm_1 is missing ('pm_1': None).

I wouldn’t try to get this running in weewx until you have good data.  In a 
browser, go to:
http:///v1/current_conditions

You need a good timestamp to show up here (e.g., right now, "ts": 1653499667) 
and good concentrations (rather than None); e.g., "pm_1": 5.16

Since it’s finding no valid concentrations, you are seeing the message “Could 
not get concentrations from any source.”

John

> On May 25, 2022, at 8:24 AM, anc...@gmail.com  wrote:
> 
> Hi guys,
> I just installed for the first time a Davis Airlink and I want to integrate 
> it in WeeWX with which my Davis VP2 already works. I followed the 
> instructions on the weewx-airlink page, but for some reason it is not working 
> . Here is some log:
> 
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85441, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85446 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7, 
> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4, 
> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85446, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in 
> 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> collect_data: Attempt to fetch from: 192.168.0.196 failed: 
> HTTPConnectionPool(host='192.168.0.196', port=80): Max retries exceeded with 
> url: /v1/current_conditions 

Re: [weewx-user] Problem with weewx-airlink

2022-05-25 Thread Doug Jenkins
My guess since you do not see the device in weatherlink.com is that it is
not reporting correctly on the network.


1.  First see if you can open your web browser to the api of the airlink
device.

for example: http://xxx.xxx.xxx.xxx/v1/current_conditions
You should see JSON data returned.

2. Also check the APi Documentation from Davis (Introduction | AirLink
Local API (weatherlink.github.io)
 about how the
device works on a network. From their documentation, AirLink devices
advertise their presence on the local network using DNS Service Discovery
 over multicast DNS (mDNS)
. These technologies are also known as
Zeroconf or Bonjour or Avahi.

I have a weewx-airlink device and I followed this guide using the driver
with success. Please let me know if you have any questions.



if not,

On Wed, May 25, 2022 at 11:24 AM anc...@gmail.com  wrote:

> Hi guys,
> I just installed for the first time a Davis Airlink and I want to
> integrate it in WeeWX with which my Davis VP2 already works. I followed the
> instructions on the weewx-airlink page
> , but for some reason
> it is not working . Here is some log:
>
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> last_report_time must be time since boot: 85441 seconds.  Record: {'data':
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions':
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5,
> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4,
> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None,
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None,
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None,
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None,
> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time':
> 85441, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None,
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error':
> None}
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> last_report_time must be time since boot: 85446 seconds.  Record: {'data':
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions':
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7,
> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4,
> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None,
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None,
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None,
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None,
> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time':
> 85446, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None,
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error':
> None}
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager:
> Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager:
> Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in
> 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> collect_data: Attempt to fetch from: 192.168.0.196 failed:
> 

[weewx-user] Problem with weewx-airlink

2022-05-25 Thread anc...@gmail.com
Hi guys,
I just installed for the first time a Davis Airlink and I want to integrate 
it in WeeWX with which my Davis VP2 already works. I followed the 
instructions on the weewx-airlink page 
, but for some reason it 
is not working . Here is some log:

May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Could not get concentrations from any source.
May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
{'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
[{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 
'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time': 
85441, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
None}
May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Could not get concentrations from any source.
May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
last_report_time must be time since boot: 85446 seconds.  Record: {'data': 
{'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions': 
[{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7, 
'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4, 
'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None, 
'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 
'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time': 
85446, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
None}
May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Could not get concentrations from any source.
May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in 
'weewx.sdb'
May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
collect_data: Attempt to fetch from: 192.168.0.196 failed: 
HTTPConnectionPool(host='192.168.0.196', port=80): Max retries exceeded 
with url: /v1/current_conditions (Caused by 
ConnectTimeoutError(, 'Connection to 192.168.0.196 timed out. (connect timeout=2)')).
May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Could not get concentrations from any source.
May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:21 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:23 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:25 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
Found no concentrations to insert.
May 25 16:11:26 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
last_report_time must be time since boot: 85460 seconds.  Record: {'data': 
{'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85460, 'conditions': 
[{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.2, 'hum': 26.8, 
'dew_point': 53.2, 'wet_bulb': 60.4, 

[weewx-user] Re: NOOB Questions on "Installation using setup.py" on Raspberry Pi

2022-05-25 Thread radi...@gmail.com
@Bob Atchley - Thanks!  Not confusing (to me) at all!  ;-)

Very helpful- particularly the Wiki links.  My usage of GitHub has been 
very limited from what I now see for WeeWX, so I'll have to do some 
exploring.  I've used Wikis often but was unaware GitHub has such a rich 
capability.

Thanks Again-
Bob

On Monday, May 23, 2022 at 1:12:29 PM UTC-4 Bob Atchley wrote:

> And just as a slight addendum to your original post ...
>
> I personally choose to run weewx as a non privileged user.  Its relatively 
> simple to set up but the user does need to be in the www-data group to 
> interface with the web server (assuming the web server is local) and needs 
> permission to read/write to the usb see:
> https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user
>
> I use systemd to start/stop the weewx service and you need to add the user 
> name into the [service] part of the configuration e.g.
> User= myUser  
> Group=myUser
> Again the brilliant weewx Wiki has some stuff on using systemd see:
> https://github.com/weewx/weewx/wiki/systemd
>
> But as Vince says no need to do this, the default works out of the box ... 
> but it can be done.  I found it useful while developing the WS6in1 driver.
>
> Hope this helps rather than confuses
>
> Bob
>
>
>
> On Sunday, 22 May 2022 at 19:52:13 UTC+1 radi...@gmail.com wrote:
>
>> @vince - Yeah, overthinking is likely...
>>
>> My intent was to install WeeWX "out of the box" and get it up and 
>> running, to get familiar with it  (quite possibly reinstall using one of 
>> the other methods later thinking that might ease updates).  I ran into GPIO 
>> access issues when trying to manipulate them through a web page a while 
>> ago, so I planned to stick with "pi" initially.  I confess when I saw 
>> /home/weewx mentioned several times, I *assumed *this implied a user.  
>> Nowhere does it say this that I recall, so not a valid assumption.  (A 
>> little sys admin bias perhaps.)  I've used Apache on most of my Pis, having 
>> failed to get nginx to run at one time, and having used Apache for some 
>> time.  I do have a hosted server which will be the target for observations 
>> eventually.
>>
>> "*Why mess with setup.cfg?*"  The short answer is 
>> https://weewx.com/docs/setup.htm says "To specify an install location 
>> different from the default /home/weewx, modify the parameter home in the 
>> setup.cfg 
>> file." Again, I didn't want to create a weewx user (my assumption), and 
>> didn't understand the implications of what one chooses for home.
>>
>> I did note that the code has to run under root / sudo.  Eventually I'll 
>> run it under systemd (using root).
>>
>> I'll try wee_config --reconfigure when I get back to it.  Helpful tip, 
>> thanks!
>>
>>
>> @paul...@gmail.com 
>>
>> When researching what station to buy I did note Bob Atchley's driver but 
>> didn't have the Logia model number on hand at the time.  Amazingly it does 
>> match!  I was looking for a USB-connected station, and they are getting 
>> harder to find it seems.  Appreciate the pointer to his git, and knowing 
>> that you've had good success with it.  (With Cumulus I had written a 
>> separate watchdog process because the comms were dropping fairly often.)
>>
>> I had planned on registering once I was up and running - so we'll be 12!  
>> ;-)
>>
>> Thanks Folks- Very favorable experience with my first post to the forum!
>> Bob
>>
>> On Sunday, May 22, 2022 at 11:07:19 AM UTC-4 paul...@gmail.com 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.   

Re: [weewx-user] Davis Data Logger - Issue

2022-05-25 Thread WindnFog
A powered hub makes it just as bad, and possibly worse, Tom.  But, with 
your "more forgiving" Vantage driver, it is far better than before.  So I 
am quite willing to live with it as it is.  

As mentioned in the same thread, I removed my cron job that calls a 
program, and I'm using the tags you recommended based on the NOAA 
generation template.  That's a far better approach.

- Paul VE1DX
On Wednesday, May 18, 2022 at 9:38:17 PM UTC-3 Graham Eddy wrote:

> i reported earlier that i got a burst of weewx restarts by vantage driver 
> when my extra vp2 station (wireless temp) battery started reporting low (i 
> hadn’t noticed until this thread started). tom’s new retry patch not 
> applied. this happened a second time recently viz. burst of restart 
> activity when extra station reported low battery. nothing to do with power 
> supplies or reboots, i am more inclined to point to an envoy or data 
> logger/usb firmware bug (they are more than 15yo).
> (it is possible this firmware bug could lead to phantom battery low 
> reports; i think more likely they were genuine battery low events driving 
> the error)
>
> sadly this extra wireless vp2 station has just been borked - it was under 
> water for a week in 2010 floods (i mounted it higher after that :-) but a 
> few days ago couldn’t survive 2-3 tonnes of tree branch crushing it on 
> rocks. it will be replaced by a much much cheaper ecowitt remote temp probe 
> (i run dual vp2/gw1000)
>
> On 19 May 2022, at 1:09 am, Paul Dunphy  wrote:
>
> Whatever it is, it's related to RPis talking to a Davis Logger via 
> USB. I have a couple of powered USB hubs lying around. I can try putting 
> one of them on in the next day or so . . . now that you mention it, I never 
> had any trouble with an RPi 3. However, it did/does manifest itself on 
> three different RPi 4s. I'll report back when I have results using a 
> powered hub.
>
> - Paul VE1DX
>
> On 2022-05-18 11:14 a.m., Tom Keffer wrote:
>
> I don't know that it's a "timing issue," but it could certainly be a power 
> issue. 
>
> The USB power supplies for many RPis can be barely adequate. In 
> particular, the RPi 4 uses a lot of power. It doesn't take much for the 
> power to sag, resulting in errors.
>
>
>   >snip<
>
> -- 
> 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/9d5bf73c-2c97-fd8b-6a14-06dfbeb751d3%40gmail.com
>  
> 
> .
>
>
>

-- 
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/89dc2f8f-67fa-4858-b519-92166e1bc70bn%40googlegroups.com.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Graham Eddy
i can power down, pull it apart, put the batteries in backwards. how do i reset 
it?
(and why would wee_device be failing to reconfigure ch2 but work successfully 
otherwise?)

> On 25 May 2022, at 8:13 pm, gjr80  wrote:
> 
> Doesn't leave many options. Can't power down/reset the envoy?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
> data logger is in an envoy
> 
> 
>> On 25 May 2022, at 7:25 pm, gjr80 > > wrote:
>> 
> 
>> Can't you set transmitter IDs manually via the console?
>> 
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/C6DEC2F7-0B3B-4FD4-ACD7-661727422852%40geddy.au.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread gjr80
Doesn't leave many options. Can't power down/reset the envoy?

Gary

On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:

> data logger is in an envoy
>
> On 25 May 2022, at 7:25 pm, gjr80  wrote:
>
> Can't you set transmitter IDs manually via the console?
>
> Gary
>
> On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:
>
>> QC is filtering out the bad values, but weewx server is currently 
>> resetting after 4 failed retries on regular basis while the phantom station 
>> haunts the vp2. there is no radio signal being transmitted to provide the 
>> extraTemp1 values, it is just a figment of data logger’s imagination. the 
>> phantom battery-low apparently from the ex-station stopped yesterday, but 
>> the data logger is still reporting the extraTemp1 despite my (failed) 
>> wee_device instruction just now to desist
>>
>> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ 
>> error.
>> then i do ‘wee_device —info’ and it reports ch2 still enabled
>> so it is not just a case of resetting memory/power
>>
>> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
>> (vp2 firmware is from 2004. lately weewx has been resetting whenever the 
>> (now ex-) extra station reported low battery, so this bogus extraTemp1 
>> value upsetting weewx is kinda understandable → i need to turn all vestiges 
>> of the (ex-) extra station off)
>>
>> On 25 May 2022, at 5:53 pm, Stephen Hocking  wrote:
>>
>> Given such a whacko figure, perhaps under the [[Corrections]] section 
>> under [StdCalibrate], or more suitably, something under [StdQC].
>>
>> On Wed, 25 May 2022 at 17:45, Graham Eddy  wrote:
>>
>>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at 
>>> ch1) has carked it (crushed in tree fall). it exists no more; it is not 
>>> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
>>> about 150 C (not bad for a river!) every few seconds, how do i disable this 
>>> phantom?
>>>
>>> i tried (*with weewx not running*) ‘wee_device 
>>> --set-transmitter-type=2,10’ to set ch2 to none, but all i get is an 
>>> error ‘No  received from Vantage console’, and it continues 
>>> reporting the phantom when i start weewx again. how can i stop this phantom?
>>> cheers
>>>
>>> -- 
>>> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>>
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>>
>>
>>
>> -- 
>> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>>  
>> 
>> .
>>
>>
>>
> -- 
> 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/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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/a8eed4cd-5995-448f-9922-cd2628f88e24n%40googlegroups.com.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Graham Eddy
data logger is in an envoy

> On 25 May 2022, at 7:25 pm, gjr80  wrote:
> 
> Can't you set transmitter IDs manually via the console?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:
> QC is filtering out the bad values, but weewx server is currently resetting 
> after 4 failed retries on regular basis while the phantom station haunts the 
> vp2. there is no radio signal being transmitted to provide the extraTemp1 
> values, it is just a figment of data logger’s imagination. the phantom 
> battery-low apparently from the ex-station stopped yesterday, but the data 
> logger is still reporting the extraTemp1 despite my (failed) wee_device 
> instruction just now to desist
> 
> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
> then i do ‘wee_device —info’ and it reports ch2 still enabled
> so it is not just a case of resetting memory/power
> 
> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
> (vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
> ex-) extra station reported low battery, so this bogus extraTemp1 value 
> upsetting weewx is kinda understandable → i need to turn all vestiges of the 
> (ex-) extra station off)
> 
> 
>> On 25 May 2022, at 5:53 pm, Stephen Hocking > > wrote:
>> 
> 
>> Given such a whacko figure, perhaps under the [[Corrections]] section under 
>> [StdCalibrate], or more suitably, something under [StdQC].
>> 
>> On Wed, 25 May 2022 at 17:45, Graham Eddy > > wrote:
>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at 
>> ch1) has carked it (crushed in tree fall). it exists no more; it is not 
>> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
>> about 150 C (not bad for a river!) every few seconds, how do i disable this 
>> phantom?
>> 
>> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
>> set ch2 to none, but all i get is an error ‘No  received from Vantage 
>> console’, and it continues reporting the phantom when i start weewx again. 
>> how can i stop this phantom?
>> cheers
>> 
>> -- 
>> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>>  
>> .
>> 
>> 
>> -- 
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>> 
>> 
>> -- 
>> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>>  
>> .
> 
> 
> -- 
> 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/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%40googlegroups.com
>  
> .

-- 
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/D38AF7A8-8AC0-4A50-8F49-F98A595EFEF3%40geddy.au.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread gjr80
Can't you set transmitter IDs manually via the console?

Gary

On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:

> QC is filtering out the bad values, but weewx server is currently 
> resetting after 4 failed retries on regular basis while the phantom station 
> haunts the vp2. there is no radio signal being transmitted to provide the 
> extraTemp1 values, it is just a figment of data logger’s imagination. the 
> phantom battery-low apparently from the ex-station stopped yesterday, but 
> the data logger is still reporting the extraTemp1 despite my (failed) 
> wee_device instruction just now to desist
>
> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
> then i do ‘wee_device —info’ and it reports ch2 still enabled
> so it is not just a case of resetting memory/power
>
> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
> (vp2 firmware is from 2004. lately weewx has been resetting whenever the 
> (now ex-) extra station reported low battery, so this bogus extraTemp1 
> value upsetting weewx is kinda understandable → i need to turn all vestiges 
> of the (ex-) extra station off)
>
> On 25 May 2022, at 5:53 pm, Stephen Hocking  wrote:
>
> Given such a whacko figure, perhaps under the [[Corrections]] section 
> under [StdCalibrate], or more suitably, something under [StdQC].
>
> On Wed, 25 May 2022 at 17:45, Graham Eddy  wrote:
>
>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at 
>> ch1) has carked it (crushed in tree fall). it exists no more; it is not 
>> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
>> about 150 C (not bad for a river!) every few seconds, how do i disable this 
>> phantom?
>>
>> i tried (*with weewx not running*) ‘wee_device 
>> --set-transmitter-type=2,10’ to set ch2 to none, but all i get is an 
>> error ‘No  received from Vantage console’, and it continues 
>> reporting the phantom when i start weewx again. how can i stop this phantom?
>> cheers
>>
>> -- 
>> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>>  
>> 
>> .
>>
>
>
> -- 
>
>   "I and the public know
>   what all schoolchildren learn
>   Those to whom evil is done
>   Do evil in return"  W.H. Auden, "September 1, 1939"
>
>
>
> -- 
> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>  
> 
> .
>
>
>

-- 
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/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%40googlegroups.com.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Stephen Hocking
An alternative might be to use a different driver - does rtl_433 pick up
its transmissions? If so, using the SDR driver could work, and you wouldn't
have weewx resetting after failed USB comms.

On Wed, 25 May 2022 at 18:18, Graham Eddy  wrote:

> QC is filtering out the bad values, but weewx server is currently
> resetting after 4 failed retries on regular basis while the phantom station
> haunts the vp2. there is no radio signal being transmitted to provide the
> extraTemp1 values, it is just a figment of data logger’s imagination. the
> phantom battery-low apparently from the ex-station stopped yesterday, but
> the data logger is still reporting the extraTemp1 despite my (failed)
> wee_device instruction just now to desist
>
> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
> then i do ‘wee_device —info’ and it reports ch2 still enabled
> so it is not just a case of resetting memory/power
>
> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
> (vp2 firmware is from 2004. lately weewx has been resetting whenever the
> (now ex-) extra station reported low battery, so this bogus extraTemp1
> value upsetting weewx is kinda understandable → i need to turn all vestiges
> of the (ex-) extra station off)
>
> On 25 May 2022, at 5:53 pm, Stephen Hocking 
> wrote:
>
> Given such a whacko figure, perhaps under the [[Corrections]] section
> under [StdCalibrate], or more suitably, something under [StdQC].
>
> On Wed, 25 May 2022 at 17:45, Graham Eddy  wrote:
>
>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at
>> ch1) has carked it (crushed in tree fall). it exists no more; it is not
>> transmitting. my vp2 data logger is faithfully reporting a phantom value of
>> about 150 C (not bad for a river!) every few seconds, how do i disable this
>> phantom?
>>
>> i tried (*with weewx not running*) ‘wee_device
>> --set-transmitter-type=2,10’ to set ch2 to none, but all i get is an
>> error ‘No  received from Vantage console’, and it continues
>> reporting the phantom when i start weewx again. how can i stop this phantom?
>> cheers
>>
>> --
>> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>> 
>> .
>>
>
>
> --
>
>   "I and the public know
>   what all schoolchildren learn
>   Those to whom evil is done
>   Do evil in return"  W.H. Auden, "September 1, 1939"
>
>
>
> --
> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
> 
> .
>
>
> --
> 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/F4510CA0-CFDC-4855-A336-6A1FCED46B72%40geddy.au
> 
> .
>


-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"W.H. Auden, "September 1, 1939"

-- 
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/CA%2BxzKjAMvAVCmnd9fGDeaB_%3D%3D1yvyxhJGtvU_%3D_o14sjR2AnpA%40mail.gmail.com.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Graham Eddy
QC is filtering out the bad values, but weewx server is currently resetting 
after 4 failed retries on regular basis while the phantom station haunts the 
vp2. there is no radio signal being transmitted to provide the extraTemp1 
values, it is just a figment of data logger’s imagination. the phantom 
battery-low apparently from the ex-station stopped yesterday, but the data 
logger is still reporting the extraTemp1 despite my (failed) wee_device 
instruction just now to desist

i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
then i do ‘wee_device —info’ and it reports ch2 still enabled
so it is not just a case of resetting memory/power

weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
(vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
ex-) extra station reported low battery, so this bogus extraTemp1 value 
upsetting weewx is kinda understandable → i need to turn all vestiges of the 
(ex-) extra station off)

> On 25 May 2022, at 5:53 pm, Stephen Hocking  wrote:
> 
> Given such a whacko figure, perhaps under the [[Corrections]] section under 
> [StdCalibrate], or more suitably, something under [StdQC].
> 
> On Wed, 25 May 2022 at 17:45, Graham Eddy  > wrote:
> my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
> has carked it (crushed in tree fall). it exists no more; it is not 
> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
> about 150 C (not bad for a river!) every few seconds, how do i disable this 
> phantom?
> 
> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
> set ch2 to none, but all i get is an error ‘No  received from Vantage 
> console’, and it continues reporting the phantom when i start weewx again. 
> how can i stop this phantom?
> cheers
> 
> -- 
> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>  
> .
> 
> 
> -- 
>   "I and the public know
>   what all schoolchildren learn
>   Those to whom evil is done
>   Do evil in return"  W.H. Auden, "September 1, 1939"
> 
> 
> -- 
> 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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>  
> .

-- 
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/F4510CA0-CFDC-4855-A336-6A1FCED46B72%40geddy.au.


Re: [weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Stephen Hocking
Given such a whacko figure, perhaps under the [[Corrections]] section under
[StdCalibrate], or more suitably, something under [StdQC].

On Wed, 25 May 2022 at 17:45, Graham Eddy  wrote:

> my old vantage pro2’s additional wireless temp station at ch2 (iss is at
> ch1) has carked it (crushed in tree fall). it exists no more; it is not
> transmitting. my vp2 data logger is faithfully reporting a phantom value of
> about 150 C (not bad for a river!) every few seconds, how do i disable this
> phantom?
>
> i tried (*with weewx not running*) ‘wee_device --set-transmitter-type=2,10’
> to set ch2 to none, but all i get is an error ‘No  received from
> Vantage console’, and it continues reporting the phantom when i start
> weewx again. how can i stop this phantom?
> cheers
>
> --
> 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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
> 
> .
>


-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"W.H. Auden, "September 1, 1939"

-- 
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/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com.


Re: [weewx-user] Logging

2022-05-25 Thread Mark Fraser

On 24/05/2022 09:58, gjr80 wrote:
You have nothing to apologise over, you did exactly the right thing. Was 
just pointing out that the operation of log_success is independent of 
the logging system being used and in the case of a driver or service 
such as you are using using log.debug() is more appropriate.


Gary


Thanks Gary, that's been changed. Is it worth testing to see if the 
version of weewx installed can use the new logging system first as in 
https://github.com/matthewwall/weewx-windy/blob/master/bin/user/windy.py ?


--
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/d9d2103c-b70b-a0d3-cda1-7ca8f6fa5d84%40gmail.com.


[weewx-user] vp2 - how to disable ch2?

2022-05-25 Thread Graham Eddy
my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
has carked it (crushed in tree fall). it exists no more; it is not 
transmitting. my vp2 data logger is faithfully reporting a phantom value of 
about 150 C (not bad for a river!) every few seconds, how do i disable this 
phantom?

i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
set ch2 to none, but all i get is an error ‘No  received from Vantage 
console’, and it continues reporting the phantom when i start weewx again. how 
can i stop this phantom?
cheers

-- 
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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au.