RE: [weewx-user] Re: No data being recieved by weewx from WMR-918

[Keith Baddock]

I have added the “baudrate” : 9600  to the driver (as looking at the embedded docs in there, which sent me to a link confirming it is 9600 baud)I think this (if it is correct) should be hardcoded rather than configurable as it seems the wmr9x8 will always be 9600 baud, though if this is the default pyserial rate anyway, nothing should need to change! Debugging: Stopped the service.Then ran sudo python3 /usr/share/weewx/weewxd /etc/weewx/weewx.conf  to run from the command line. Should I be seeing anything in the console at all?  Syslog last line indicates  weewx[34003] INFO weewx.engine: Starting main packet loop. So I think it is listening, but not getting anything so looking like a hardware or configuration issue with the serial port on the PC.  And just when I thought I had “upgraded” my PC with RS232   I let it run for 15 minutes, then cancelled, with no loop packets received. I will experiment further with the hardware side – maybe something in BIOS configures the port in some way. Thanks for the help – will let you know how I go, could help some future me! Keith Sent from Mail for Windows From: Tom KefferSent: Sunday, 24 July 2022 7:47 AMTo: weewx-userSubject: Re: [weewx-user] Re: No data being recieved by weewx from WMR-918 Unfortunately, the driver does not let you set the baudrate from the configuration file. If you want to change it, you'll have to go into the code. If you want to do this, starting at line 94 of weewx/driver/wmr9x8.py you'll find this:         self.serialconfig = {            "bytesize": serial.EIGHTBITS,            "parity": serial.PARITY_NONE,            "stopbits": serial.STOPBITS_ONE,            "timeout": None,            "rtscts": 1        } Just add baudrate so it looks like this:         self.serialconfig = {            "bytesize": serial.EIGHTBITS,            "parity": serial.PARITY_NONE,            "stopbits": serial.STOPBITS_ONE,            "timeout": None,            "rtscts": 1,            "baudrate" : 4800        } If that works for you, I'll add the ability to change baudrate through weewx.conf. -tk On Sat, Jul 23, 2022 at 2:37 PM Keith Baddock  wrote:I'll have to investigate how to set the baud rate, as I'm pretty sure the wmr918 is outputting at 9600. It just appears I might not be listening at 9600! I did think that the 11.5k baud was the max the interface could support, but the client software could set it to whatever it needed to suit the device. Running from the command line gives me no visual output. I was expecting to see loop packets too.    Sent from my Galaxy-Tab A 2017 on the Telstra Mobile NetworkGet Outlook for AndroidFrom: weewx-user@googlegroups.com  on behalf of Tom Keffer Sent: Sunday, July 24, 2022 12:21:45 AMTo: weewx-user Subject: Re: [weewx-user] Re: No data being recieved by weewx from WMR-918  Could definitely be a baud rate issue. The driver opens the port using the default pyserial rate, which is 9600, and you seem to be at 115200.  Can you change the port rate to 9600? If not, we can try changing the driver to expect 115200. These things are also easier to diagnose by running weewxd from the command line. Then you can see the LOOP packets coming in. -tk On Sat, Jul 23, 2022 at 4:27 AM Keith  wrote:Jul 23 20:33:14 dragon systemd[1]: Started Run anacron jobs.Jul 23 20:33:14 dragon anacron[9791]: Anacron 2.3 started on 2022-07-23Jul 23 20:33:14 dragon anacron[9791]: Normal exit (0 jobs run)Jul 23 20:33:14 dragon systemd[1]: anacron.service: Succeeded.Jul 23 20:33:26 dragon systemd[1]: Starting LSB: weewx weather system...Jul 23 20:33:26 dragon weewx[9804]:  * Starting weewx weather system weewxJul 23 20:33:26 dragon weewx[9815] INFO __main__: Initializing weewx version 4.8.0Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using Python 3.8.10 (default, Jun 22 2022, 20:18:18) #012[GCC 9.4.0]Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Platform Linux-5.15.0-41-generic-x86_64-with-glibc2.29Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Locale is 'en_AU.UTF-8'Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using configuration file /etc/weewx/weewx.confJul 23 20:33:26 dragon weewx[9815] INFO __main__: Debug is 1Jul 23 20:33:26 dragon weewx[9815] INFO __main__: PID file is /var/run/weewx.pidJul 23 20:33:26 dragon weewx[9818] DEBUG __main__: Initializing engineJul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: Loading station type WMR9x8 (weewx.drivers.wmr9x8)Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: driver version is 3.4.1Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: sensor map is {'barometer': 'barometer', 'pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 'wind_dir', 'windGust': 'wind_gust', 'windGustDir': 'wind_gust_dir', 'windBatteryStatus': 'battery_status_wind', 'inTemp': 'temperature_in', 'outTemp': 'temperature_out', 'extraTemp1': 'temperature_1', 

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Doug Jenkins]

To add to this thread Jan, could you fork this repo and send a link? I am
starting some work on a few enhancements to the wee_extensions and I can
create the proper packaging that weewx expects so that future users of the
driver can install it properly.

I would fork the repo, but I do not have a BME280 sensor to properly test
the driver.

If it all works, you can send a pull request to the original author and
have it merged.

DDJ

On Sat, Jul 23, 2022 at 5:51 PM Tom Keffer  wrote:

> Something is off. Could you send me the copy of byows_rpi.py you are
> using?
>
>
> On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett  wrote:
>
>> Thank you for your time in responding.
>>
>> It is correct that byows_rpi extension
>>  is mostly just a python file
>> (byows_rpi.py) saved to /usr/share/weewx/user/
>>
>> I have followed the directions at the git repository and have verified
>> with Change Driver 
>> that I've done the appropriate things to weewx.conf as well.
>>
>> When I run either of the commands you listed I receive the same error as
>> before:
>>
>> class ByowsRpi(weewx.drivers.AbstractDevice)
>> NameError: name 'weewx' is not defined
>>
>>
>>
>> On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:
>>
>>> 1, It looks like the byows_pi extension does not use the extension
>>> installer, so weewx has no way of knowing of its existence. This is why it
>>> doesn't show up in the list of available drivers.
>>>
>>> 2. As for running byows_pi directly, you have a slight problem with your
>>> paths. Try either this
>>>
>>> cd /usr/share/weewx
>>> python user/byows_rpi.py
>>>
>>>
>>> or this
>>>
>>> cd /usr/share/weewx
>>> python -m user.byows_rpi
>>>
>>>
>>> -tk
>>>
>>> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett  wrote:
>>>
 I should also note that when I 'sudo wee_config --reconfigure
 --driver=user.byows_rpi --no-prompt' I see the following:

 Using configuration file /home/weewx/weewx.conf
 Driver user.byows_rpi  failed to load: name 'weewx' is not defined

 On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:

> Hey all -
>
> I am trying to install the driver for the Build Your Own Weather
> Station using Raspberry pi (byows_rpi.py)
>
> I have updated weewx-config to include BYOWS. I also have the
> interceptor driver installed.
>
> However, I cannot seem to get the driver to show up under the drivers
> list when I try 'wee_config --list-drivers'.  I show byows_rpi.py under
> /usr/share/weewx/user/
>
> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
> --no-promt' to no avail.
>
> I feel like I've missed a step somewhere about how to actually get the
> system to recognize the driver.
>
> When I try to run the byows_rpi.py via command line from within the
> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following
> error:
>
> class ByowsRpi(weewx.drivers.AbstractDevice)
> NameError: name 'weewx' is not defined
>
> Any guidance would be greatly appreciated!
>
 --
 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/074ed02d-872f-4384-82bf-748449e13ef5n%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/c207e67c-2fb6-4a4c-812d-867387566476n%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/CAPq0zED6%3DO2-mjrfCdB9N%3DkwNoHdoh429f9aeDtw_4KFSVSFMw%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 

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Tom Keffer]

Something is off. Could you send me the copy of byows_rpi.py you are using?


On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett  wrote:

> Thank you for your time in responding.
>
> It is correct that byows_rpi extension
>  is mostly just a python file
> (byows_rpi.py) saved to /usr/share/weewx/user/
>
> I have followed the directions at the git repository and have verified
> with Change Driver 
> that I've done the appropriate things to weewx.conf as well.
>
> When I run either of the commands you listed I receive the same error as
> before:
>
> class ByowsRpi(weewx.drivers.AbstractDevice)
> NameError: name 'weewx' is not defined
>
>
>
> On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:
>
>> 1, It looks like the byows_pi extension does not use the extension
>> installer, so weewx has no way of knowing of its existence. This is why it
>> doesn't show up in the list of available drivers.
>>
>> 2. As for running byows_pi directly, you have a slight problem with your
>> paths. Try either this
>>
>> cd /usr/share/weewx
>> python user/byows_rpi.py
>>
>>
>> or this
>>
>> cd /usr/share/weewx
>> python -m user.byows_rpi
>>
>>
>> -tk
>>
>> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett  wrote:
>>
>>> I should also note that when I 'sudo wee_config --reconfigure
>>> --driver=user.byows_rpi --no-prompt' I see the following:
>>>
>>> Using configuration file /home/weewx/weewx.conf
>>> Driver user.byows_rpi  failed to load: name 'weewx' is not defined
>>>
>>> On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:
>>>
 Hey all -

 I am trying to install the driver for the Build Your Own Weather
 Station using Raspberry pi (byows_rpi.py)

 I have updated weewx-config to include BYOWS. I also have the
 interceptor driver installed.

 However, I cannot seem to get the driver to show up under the drivers
 list when I try 'wee_config --list-drivers'.  I show byows_rpi.py under
 /usr/share/weewx/user/

 I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
 --no-promt' to no avail.

 I feel like I've missed a step somewhere about how to actually get the
 system to recognize the driver.

 When I try to run the byows_rpi.py via command line from within the
 /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following
 error:

 class ByowsRpi(weewx.drivers.AbstractDevice)
 NameError: name 'weewx' is not defined

 Any guidance would be greatly appreciated!

>>> --
>>> 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/074ed02d-872f-4384-82bf-748449e13ef5n%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/c207e67c-2fb6-4a4c-812d-867387566476n%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/CAPq0zED6%3DO2-mjrfCdB9N%3DkwNoHdoh429f9aeDtw_4KFSVSFMw%40mail.gmail.com.

Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

[Tom Keffer]

Unfortunately, the driver does not let you set the baudrate from the
configuration file. If you want to change it, you'll have to go into the
code. If you want to do this, starting at line 94 of weewx/driver/wmr9x8.py
you'll find this:

self.serialconfig = {
"bytesize": serial.EIGHTBITS,
"parity": serial.PARITY_NONE,
"stopbits": serial.STOPBITS_ONE,
"timeout": None,
"rtscts": 1
}

Just add baudrate so it looks like this:

self.serialconfig = {
"bytesize": serial.EIGHTBITS,
"parity": serial.PARITY_NONE,
"stopbits": serial.STOPBITS_ONE,
"timeout": None,
"rtscts": 1,
"baudrate" : 4800
}

If that works for you, I'll add the ability to change baudrate through
weewx.conf.

-tk

On Sat, Jul 23, 2022 at 2:37 PM Keith Baddock 
wrote:

> I'll have to investigate how to set the baud rate, as I'm pretty sure the
> wmr918 is outputting at 9600. It just appears I might not be listening at
> 9600! I did think that the 11.5k baud was the max the interface could
> support, but the client software could set it to whatever it needed to suit
> the device. Running from the command line gives me no visual output. I was
> expecting to see loop packets too.
>
> Sent from my Galaxy-Tab A 2017 on the Telstra Mobile Network
> Get Outlook for Android 
> --
> *From:* weewx-user@googlegroups.com  on
> behalf of Tom Keffer 
> *Sent:* Sunday, July 24, 2022 12:21:45 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: No data being recieved by weewx from
> WMR-918
>
> Could definitely be a baud rate issue. The driver opens the port using the
> default pyserial rate, which is 9600, and you seem to be at 115200.
>
> Can you change the port rate to 9600? If not, we can try changing the
> driver to expect 115200.
>
> These things are also easier to diagnose by running weewxd from the
> command line. Then you can see the LOOP packets coming in.
>
> -tk
>
> On Sat, Jul 23, 2022 at 4:27 AM Keith  wrote:
>
> Jul 23 20:33:14 dragon systemd[1]: Started Run anacron jobs.
> Jul 23 20:33:14 dragon anacron[9791]: Anacron 2.3 started on 2022-07-23
> Jul 23 20:33:14 dragon anacron[9791]: Normal exit (0 jobs run)
> Jul 23 20:33:14 dragon systemd[1]: anacron.service: Succeeded.
> Jul 23 20:33:26 dragon systemd[1]: Starting LSB: weewx weather system...
> Jul 23 20:33:26 dragon weewx[9804]:  * Starting weewx weather system weewx
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Initializing weewx
> version 4.8.0
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using Python 3.8.10
> (default, Jun 22 2022, 20:18:18) #
> 012[GCC 9.4.0]
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Platform
> Linux-5.15.0-41-generic-x86_64-with-glibc2.29
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Locale is 'en_AU.UTF-8'
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using configuration file
> /etc/weewx/weewx.conf
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Debug is 1
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: PID file is
> /var/run/weewx.pid
> Jul 23 20:33:26 dragon weewx[9818] DEBUG __main__: Initializing engine
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: Loading station type
> WMR9x8 (weewx.drivers.wmr9x8)
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: driver
> version is 3.4.1
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: sensor map
> is {'barometer': 'barometer', '
> pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 'wind_dir',
> 'windGust': 'wind_gust', 'windG
> ustDir': 'wind_gust_dir', 'windBatteryStatus': 'battery_status_wind',
> 'inTemp': 'temperature_in', 'outTe
> mp': 'temperature_out', 'extraTemp1': 'temperature_1', 'extraTemp2':
> 'temperature_2', 'extraTemp3': 'tem
> perature_3', 'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5',
> 'extraTemp6': 'temperature_6'
> , 'extraTemp7': 'temperature_7', 'extraTemp8': 'temperature_8',
> 'inHumidity': 'humidity_in', 'outHumidit
> y': 'humidity_out', 'extraHumid1': 'humidity_1', 'extraHumid2':
> 'humidity_2', 'extraHumid3': 'humidity_3
> ', 'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5',
> 'extraHumid6': 'humidity_6', 'extraHumid7':
>  'humidity_7', 'extraHumid8': 'humidity_8', 'inTempBatteryStatus':
> 'battery_status_in', 'outTempBatteryS
> tatus': 'battery_status_out', 'extraBatteryStatus1': 'battery_status_1',
> 'extraBatteryStatus2': 'battery
> _status_2', 'extraBatteryStatus3': 'battery_status_3',
> 'extraBatteryStatus4': 'battery_status_4', 'extra
> BatteryStatus5': 'battery_status_5', 'extraBatteryStatus6':
> 'battery_status_6', 'extraBatteryStatus7': '
> battery_status_7', 'extraBatteryStatus8': 'battery_status_8',
> 'inDewpoint': 'dewpoint_in', 'dewpoint': '
> dewpoint_out', 'dewpoint0': 'dewpoint_0', 'dewpoint1': 'dewpoint_1',
> 'dewpoint2': 'dewpoint_2', 'dewpoin
> t3': 

Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

[Keith Baddock]

I'll have to investigate how to set the baud rate, as I'm pretty sure the 
wmr918 is outputting at 9600. It just appears I might not be listening at 9600! 
I did think that the 11.5k baud was the max the interface could support, but 
the client software could set it to whatever it needed to suit the device. 
Running from the command line gives me no visual output. I was expecting to see 
loop packets too.

Sent from my Galaxy-Tab A 2017 on the Telstra Mobile Network
Get Outlook for Android

From: weewx-user@googlegroups.com  on behalf of 
Tom Keffer 
Sent: Sunday, July 24, 2022 12:21:45 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

Could definitely be a baud rate issue. The driver opens the port using the 
default pyserial rate, which is 9600, and you seem to be at 115200.

Can you change the port rate to 9600? If not, we can try changing the driver to 
expect 115200.

These things are also easier to diagnose by running weewxd from the command 
line. Then you can see the LOOP packets coming in.

-tk

On Sat, Jul 23, 2022 at 4:27 AM Keith 
mailto:keithbadd...@gmail.com>> wrote:
Jul 23 20:33:14 dragon systemd[1]: Started Run anacron jobs.
Jul 23 20:33:14 dragon anacron[9791]: Anacron 2.3 started on 2022-07-23
Jul 23 20:33:14 dragon anacron[9791]: Normal exit (0 jobs run)
Jul 23 20:33:14 dragon systemd[1]: anacron.service: Succeeded.
Jul 23 20:33:26 dragon systemd[1]: Starting LSB: weewx weather system...
Jul 23 20:33:26 dragon weewx[9804]:  * Starting weewx weather system weewx
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Initializing weewx version 
4.8.0
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using Python 3.8.10 (default, 
Jun 22 2022, 20:18:18) #
012[GCC 9.4.0]
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Platform 
Linux-5.15.0-41-generic-x86_64-with-glibc2.29
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Locale is 'en_AU.UTF-8'
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Debug is 1
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: PID file is /var/run/weewx.pid
Jul 23 20:33:26 dragon weewx[9818] DEBUG __main__: Initializing engine
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: Loading station type 
WMR9x8 (weewx.drivers.wmr9x8)
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: driver version is 
3.4.1
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: sensor map is 
{'barometer': 'barometer', '
pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 'wind_dir', 
'windGust': 'wind_gust', 'windG
ustDir': 'wind_gust_dir', 'windBatteryStatus': 'battery_status_wind', 'inTemp': 
'temperature_in', 'outTe
mp': 'temperature_out', 'extraTemp1': 'temperature_1', 'extraTemp2': 
'temperature_2', 'extraTemp3': 'tem
perature_3', 'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5', 
'extraTemp6': 'temperature_6'
, 'extraTemp7': 'temperature_7', 'extraTemp8': 'temperature_8', 'inHumidity': 
'humidity_in', 'outHumidit
y': 'humidity_out', 'extraHumid1': 'humidity_1', 'extraHumid2': 'humidity_2', 
'extraHumid3': 'humidity_3
', 'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5', 'extraHumid6': 
'humidity_6', 'extraHumid7':
 'humidity_7', 'extraHumid8': 'humidity_8', 'inTempBatteryStatus': 
'battery_status_in', 'outTempBatteryS
tatus': 'battery_status_out', 'extraBatteryStatus1': 'battery_status_1', 
'extraBatteryStatus2': 'battery
_status_2', 'extraBatteryStatus3': 'battery_status_3', 'extraBatteryStatus4': 
'battery_status_4', 'extra
BatteryStatus5': 'battery_status_5', 'extraBatteryStatus6': 'battery_status_6', 
'extraBatteryStatus7': '
battery_status_7', 'extraBatteryStatus8': 'battery_status_8', 'inDewpoint': 
'dewpoint_in', 'dewpoint': '
dewpoint_out', 'dewpoint0': 'dewpoint_0', 'dewpoint1': 'dewpoint_1', 
'dewpoint2': 'dewpoint_2', 'dewpoin
t3': 'dewpoint_3', 'dewpoint4': 'dewpoint_4', 'dewpoint5': 'dewpoint_5', 
'dewpoint6': 'dewpoint_6', 'dew
point7': 'dewpoint_7', 'dewpoint8': 'dewpoint_8', 'rain': 'rain', 'rainTotal': 
'rain_total', 'rainRate':
 'rain_rate', 'hourRain': 'rain_hour', 'rain24': 'rain_24', 'yesterdayRain': 
'rain_yesterday', 'rainBatt
eryStatus': 'battery_status_rain', 'windchill': 'windchill'}
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.drivers.wmr9x8: Opened up serial 
port /dev/ttyS0
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading service 
weewx.engine.StdTimeSync
h
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: StdConvert target unit is 
0x1
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading service 
weewx.engine.StdConvert
Jul 23 20:33:26 dragon weewx[9818] DEBUG 

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Jan Bennett]

Thank you for your time in responding.

It is correct that byows_rpi extension 
 is mostly just a python file 
(byows_rpi.py) saved to /usr/share/weewx/user/

I have followed the directions at the git repository and have verified with 
Change 
Driver  that I've done 
the appropriate things to weewx.conf as well.

When I run either of the commands you listed I receive the same error as 
before:

class ByowsRpi(weewx.drivers.AbstractDevice)
NameError: name 'weewx' is not defined



On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:

> 1, It looks like the byows_pi extension does not use the extension 
> installer, so weewx has no way of knowing of its existence. This is why it 
> doesn't show up in the list of available drivers.
>
> 2. As for running byows_pi directly, you have a slight problem with your 
> paths. Try either this
>
> cd /usr/share/weewx
> python user/byows_rpi.py
>
>
> or this
>
> cd /usr/share/weewx
> python -m user.byows_rpi
>
>
> -tk
>
> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett  wrote:
>
>> I should also note that when I 'sudo wee_config --reconfigure 
>> --driver=user.byows_rpi --no-prompt' I see the following:
>>
>> Using configuration file /home/weewx/weewx.conf
>> Driver user.byows_rpi  failed to load: name 'weewx' is not defined
>>
>> On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:
>>
>>> Hey all - 
>>>
>>> I am trying to install the driver for the Build Your Own Weather Station 
>>> using Raspberry pi (byows_rpi.py)
>>>
>>> I have updated weewx-config to include BYOWS. I also have the 
>>> interceptor driver installed.
>>>
>>> However, I cannot seem to get the driver to show up under the drivers 
>>> list when I try 'wee_config --list-drivers'.  I show byows_rpi.py under 
>>> /usr/share/weewx/user/
>>>
>>> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi 
>>> --no-promt' to no avail.
>>>
>>> I feel like I've missed a step somewhere about how to actually get the 
>>> system to recognize the driver.
>>>
>>> When I try to run the byows_rpi.py via command line from within the 
>>> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following 
>>> error:
>>>
>>> class ByowsRpi(weewx.drivers.AbstractDevice)
>>> NameError: name 'weewx' is not defined
>>>
>>> Any guidance would be greatly appreciated!
>>>
>> -- 
>> 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/074ed02d-872f-4384-82bf-748449e13ef5n%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/c207e67c-2fb6-4a4c-812d-867387566476n%40googlegroups.com.

Re: [weewx-user] installation and configuration of weewx-saratoga

[Tom Keffer]

I don't know anything about the Saratoga extensions, but I do know how to
add a column to the database: use wee_database with the --add-column
 option:

*wee_database --add-column=windrun*


That may, or may not, help your problem. It's possible that the Saratoga
extension requires wind to be present.

On Sat, Jul 23, 2022 at 1:47 AM Alessandro Battini <
alessandro.batt...@gmail.com> wrote:

> Hi all, I'm trying to install and configure the weewx-saratoga plugin, but
> after the installation process, once I restart the weewx service I'm
> getting this error in the log :
>
> Database OperationalError exception: no such column: windrun
>
> After some search it should be an issue with my DB that is not updated and
> does not contains the windrun column, but I did not found any indication on
> how to fix this issue.
>
> Not sure if it's relevant but currently the station does not have a wind
> server and thus no wind data is present.
>
> Thank in advance,
> Alessandro.
>
> --
> 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/2dcf5455-4ea5-46f2-aa53-269ce5057fb0n%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/CAPq0zEC7k38kV_1LtYtZoghyyrZEUgu7o-9h0eDSmf6BA-3uzA%40mail.gmail.com.

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Tom Keffer]

1, It looks like the byows_pi extension does not use the extension
installer, so weewx has no way of knowing of its existence. This is why it
doesn't show up in the list of available drivers.

2. As for running byows_pi directly, you have a slight problem with your
paths. Try either this

cd /usr/share/weewx
python user/byows_rpi.py


or this

cd /usr/share/weewx
python -m user.byows_rpi


-tk

On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett  wrote:

> I should also note that when I 'sudo wee_config --reconfigure
> --driver=user.byows_rpi --no-prompt' I see the following:
>
> Using configuration file /home/weewx/weewx.conf
> Driver user.byows_rpi  failed to load: name 'weewx' is not defined
>
> On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:
>
>> Hey all -
>>
>> I am trying to install the driver for the Build Your Own Weather Station
>> using Raspberry pi (byows_rpi.py)
>>
>> I have updated weewx-config to include BYOWS. I also have the interceptor
>> driver installed.
>>
>> However, I cannot seem to get the driver to show up under the drivers
>> list when I try 'wee_config --list-drivers'.  I show byows_rpi.py under
>> /usr/share/weewx/user/
>>
>> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
>> --no-promt' to no avail.
>>
>> I feel like I've missed a step somewhere about how to actually get the
>> system to recognize the driver.
>>
>> When I try to run the byows_rpi.py via command line from within the
>> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following
>> error:
>>
>> class ByowsRpi(weewx.drivers.AbstractDevice)
>> NameError: name 'weewx' is not defined
>>
>> Any guidance would be greatly appreciated!
>>
> --
> 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/074ed02d-872f-4384-82bf-748449e13ef5n%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/CAPq0zEB-Kuj98uMP8cDJPhXutyZaS4WOruGfxeLO8k9AH_mhTw%40mail.gmail.com.

Re: [weewx-user] Re: No data being recieved by weewx from WMR-918

[Tom Keffer]

Could definitely be a baud rate issue. The driver opens the port using the
default pyserial rate, which is 9600, and you seem to be at 115200.

Can you change the port rate to 9600? If not, we can try changing the
driver to expect 115200.

These things are also easier to diagnose by running weewxd from the command
line. Then you can see the LOOP packets coming in.

-tk

On Sat, Jul 23, 2022 at 4:27 AM Keith  wrote:

> Jul 23 20:33:14 dragon systemd[1]: Started Run anacron jobs.
> Jul 23 20:33:14 dragon anacron[9791]: Anacron 2.3 started on 2022-07-23
> Jul 23 20:33:14 dragon anacron[9791]: Normal exit (0 jobs run)
> Jul 23 20:33:14 dragon systemd[1]: anacron.service: Succeeded.
> Jul 23 20:33:26 dragon systemd[1]: Starting LSB: weewx weather system...
> Jul 23 20:33:26 dragon weewx[9804]:  * Starting weewx weather system weewx
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Initializing weewx
> version 4.8.0
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using Python 3.8.10
> (default, Jun 22 2022, 20:18:18) #
> 012[GCC 9.4.0]
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Platform
> Linux-5.15.0-41-generic-x86_64-with-glibc2.29
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Locale is 'en_AU.UTF-8'
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using configuration file
> /etc/weewx/weewx.conf
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Debug is 1
> Jul 23 20:33:26 dragon weewx[9815] INFO __main__: PID file is
> /var/run/weewx.pid
> Jul 23 20:33:26 dragon weewx[9818] DEBUG __main__: Initializing engine
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: Loading station type
> WMR9x8 (weewx.drivers.wmr9x8)
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: driver
> version is 3.4.1
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: sensor map
> is {'barometer': 'barometer', '
> pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 'wind_dir',
> 'windGust': 'wind_gust', 'windG
> ustDir': 'wind_gust_dir', 'windBatteryStatus': 'battery_status_wind',
> 'inTemp': 'temperature_in', 'outTe
> mp': 'temperature_out', 'extraTemp1': 'temperature_1', 'extraTemp2':
> 'temperature_2', 'extraTemp3': 'tem
> perature_3', 'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5',
> 'extraTemp6': 'temperature_6'
> , 'extraTemp7': 'temperature_7', 'extraTemp8': 'temperature_8',
> 'inHumidity': 'humidity_in', 'outHumidit
> y': 'humidity_out', 'extraHumid1': 'humidity_1', 'extraHumid2':
> 'humidity_2', 'extraHumid3': 'humidity_3
> ', 'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5',
> 'extraHumid6': 'humidity_6', 'extraHumid7':
>  'humidity_7', 'extraHumid8': 'humidity_8', 'inTempBatteryStatus':
> 'battery_status_in', 'outTempBatteryS
> tatus': 'battery_status_out', 'extraBatteryStatus1': 'battery_status_1',
> 'extraBatteryStatus2': 'battery
> _status_2', 'extraBatteryStatus3': 'battery_status_3',
> 'extraBatteryStatus4': 'battery_status_4', 'extra
> BatteryStatus5': 'battery_status_5', 'extraBatteryStatus6':
> 'battery_status_6', 'extraBatteryStatus7': '
> battery_status_7', 'extraBatteryStatus8': 'battery_status_8',
> 'inDewpoint': 'dewpoint_in', 'dewpoint': '
> dewpoint_out', 'dewpoint0': 'dewpoint_0', 'dewpoint1': 'dewpoint_1',
> 'dewpoint2': 'dewpoint_2', 'dewpoin
> t3': 'dewpoint_3', 'dewpoint4': 'dewpoint_4', 'dewpoint5': 'dewpoint_5',
> 'dewpoint6': 'dewpoint_6', 'dew
> point7': 'dewpoint_7', 'dewpoint8': 'dewpoint_8', 'rain': 'rain',
> 'rainTotal': 'rain_total', 'rainRate':
>  'rain_rate', 'hourRain': 'rain_hour', 'rain24': 'rain_24',
> 'yesterdayRain': 'rain_yesterday', 'rainBatt
> eryStatus': 'battery_status_rain', 'windchill': 'windchill'}
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.drivers.wmr9x8: Opened up
> serial port /dev/ttyS0
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service
> weewx.engine.StdTimeSynch
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading
> service weewx.engine.StdTimeSync
> h
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service
> weewx.engine.StdConvert
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: StdConvert target
> unit is 0x1
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading
> service weewx.engine.StdConvert
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service
> weewx.engine.StdCalibrate
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading
> service weewx.engine.StdCalibrat
> e
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service
> weewx.engine.StdQC
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading
> service weewx.engine.StdQC
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service
> weewx.wxservices.StdWXCalculate
> Jul 23 20:33:26 dragon weewx[9818] INFO weewx.wxservices: StdWXCalculate
> will use data binding wx_bindin
> g
> Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.manager: Daily summary
> version is 

[weewx-user] Re: Install user.byows_rpi driver?

[Jan Bennett]

I should also note that when I 'sudo wee_config --reconfigure 
--driver=user.byows_rpi --no-prompt' I see the following:

Using configuration file /home/weewx/weewx.conf
Driver user.byows_rpi  failed to load: name 'weewx' is not defined

On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:

> Hey all - 
>
> I am trying to install the driver for the Build Your Own Weather Station 
> using Raspberry pi (byows_rpi.py)
>
> I have updated weewx-config to include BYOWS. I also have the interceptor 
> driver installed.
>
> However, I cannot seem to get the driver to show up under the drivers list 
> when I try 'wee_config --list-drivers'.  I show byows_rpi.py under 
> /usr/share/weewx/user/
>
> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi 
> --no-promt' to no avail.
>
> I feel like I've missed a step somewhere about how to actually get the 
> system to recognize the driver.
>
> When I try to run the byows_rpi.py via command line from within the 
> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following 
> error:
>
> class ByowsRpi(weewx.drivers.AbstractDevice)
> NameError: name 'weewx' is not defined
>
> Any guidance would be greatly appreciated!
>

-- 
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/074ed02d-872f-4384-82bf-748449e13ef5n%40googlegroups.com.

[weewx-user] Re: BYOWS_RPi

[Jan Bennett]

What would be a direction to take if you don't see the byows_rpi driver 
listed?

On Friday, December 6, 2019 at 12:06:40 AM UTC-7 Theeuwes wrote:

>
> Hi michael
>>
>
>   I am not a so good with software but i can try to help you , i got it 
> running after a few  days of try and error
>
>   do you see  the BYOWS rpi in the drivers list ( sudo wee_config 
> --list-drivers )
>
>   Theeuwes
>

-- 
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/5941dbe8-36ee-4935-8f42-097147874096n%40googlegroups.com.

[weewx-user] Install user.byows_rpi driver?

[Jan Bennett]

Hey all - 

I am trying to install the driver for the Build Your Own Weather Station 
using Raspberry pi (byows_rpi.py)

I have updated weewx-config to include BYOWS. I also have the interceptor 
driver installed.

However, I cannot seem to get the driver to show up under the drivers list 
when I try 'wee_config --list-drivers'.  I show byows_rpi.py under 
/usr/share/weewx/user/

I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi 
--no-promt' to no avail.

I feel like I've missed a step somewhere about how to actually get the 
system to recognize the driver.

When I try to run the byows_rpi.py via command line from within the 
/usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following 
error:

class ByowsRpi(weewx.drivers.AbstractDevice)
NameError: name 'weewx' is not defined

Any guidance would be greatly appreciated!

-- 
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/b7833121-755a-4fa2-a3a4-8a5285e40f99n%40googlegroups.com.

[weewx-user] Re: No data being recieved by weewx from WMR-918

[Keith]

Jul 23 20:33:14 dragon systemd[1]: Started Run anacron jobs.
Jul 23 20:33:14 dragon anacron[9791]: Anacron 2.3 started on 2022-07-23
Jul 23 20:33:14 dragon anacron[9791]: Normal exit (0 jobs run)
Jul 23 20:33:14 dragon systemd[1]: anacron.service: Succeeded.
Jul 23 20:33:26 dragon systemd[1]: Starting LSB: weewx weather system...
Jul 23 20:33:26 dragon weewx[9804]:  * Starting weewx weather system weewx
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Initializing weewx 
version 4.8.0
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using Python 3.8.10 
(default, Jun 22 2022, 20:18:18) #
012[GCC 9.4.0]
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Platform 
Linux-5.15.0-41-generic-x86_64-with-glibc2.29
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Locale is 'en_AU.UTF-8'
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: Debug is 1
Jul 23 20:33:26 dragon weewx[9815] INFO __main__: PID file is 
/var/run/weewx.pid
Jul 23 20:33:26 dragon weewx[9818] DEBUG __main__: Initializing engine
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: Loading station type 
WMR9x8 (weewx.drivers.wmr9x8)
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: driver 
version is 3.4.1
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.drivers.wmr9x8: sensor map is 
{'barometer': 'barometer', '
pressure': 'pressure', 'windSpeed': 'wind_speed', 'windDir': 'wind_dir', 
'windGust': 'wind_gust', 'windG
ustDir': 'wind_gust_dir', 'windBatteryStatus': 'battery_status_wind', 
'inTemp': 'temperature_in', 'outTe
mp': 'temperature_out', 'extraTemp1': 'temperature_1', 'extraTemp2': 
'temperature_2', 'extraTemp3': 'tem
perature_3', 'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5', 
'extraTemp6': 'temperature_6'
, 'extraTemp7': 'temperature_7', 'extraTemp8': 'temperature_8', 
'inHumidity': 'humidity_in', 'outHumidit
y': 'humidity_out', 'extraHumid1': 'humidity_1', 'extraHumid2': 
'humidity_2', 'extraHumid3': 'humidity_3
', 'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5', 'extraHumid6': 
'humidity_6', 'extraHumid7':
 'humidity_7', 'extraHumid8': 'humidity_8', 'inTempBatteryStatus': 
'battery_status_in', 'outTempBatteryS
tatus': 'battery_status_out', 'extraBatteryStatus1': 'battery_status_1', 
'extraBatteryStatus2': 'battery
_status_2', 'extraBatteryStatus3': 'battery_status_3', 
'extraBatteryStatus4': 'battery_status_4', 'extra
BatteryStatus5': 'battery_status_5', 'extraBatteryStatus6': 
'battery_status_6', 'extraBatteryStatus7': '
battery_status_7', 'extraBatteryStatus8': 'battery_status_8', 'inDewpoint': 
'dewpoint_in', 'dewpoint': '
dewpoint_out', 'dewpoint0': 'dewpoint_0', 'dewpoint1': 'dewpoint_1', 
'dewpoint2': 'dewpoint_2', 'dewpoin
t3': 'dewpoint_3', 'dewpoint4': 'dewpoint_4', 'dewpoint5': 'dewpoint_5', 
'dewpoint6': 'dewpoint_6', 'dew
point7': 'dewpoint_7', 'dewpoint8': 'dewpoint_8', 'rain': 'rain', 
'rainTotal': 'rain_total', 'rainRate':
 'rain_rate', 'hourRain': 'rain_hour', 'rain24': 'rain_24', 
'yesterdayRain': 'rain_yesterday', 'rainBatt
eryStatus': 'battery_status_rain', 'windchill': 'windchill'}
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.drivers.wmr9x8: Opened up 
serial port /dev/ttyS0
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSync
h
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.engine: StdConvert target 
unit is 0x1
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrat
e
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Jul 23 20:33:26 dragon weewx[9818] INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_bindin
g
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.manager: Daily summary 
version is 4.0
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCa
lculate
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTyp
es
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Jul 23 20:33:26 dragon weewx[9818] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressu
reCooker
Jul 23 

[weewx-user] No data being recieved by weewx from WMR-918

[Keith]

I'm moving my WMR-918 weather station off a "well past it" Windows 7 PC 
onto a "not quite past it" PC running Ubuntu 20.04.4 LTS and trying to get 
it working with weewx.

The WMR-918 was definitely sending data to VWS on the old PC prior to the 
relocation, so I know it and the cable are still OK.
On the Ubuntu PC I had to add a DB-9 connector with cable to the 
motherboard, so there may be a chance that is where the problem is, or 
there is some issues with enabling the serial port.

weewx was installed using the deb installation method, and seems to launch 
OK but does not appear to generate any loop data,

Serial Port appears to be there, not sure if I need to do some kind of 
config on it, eg 9600 baud?
 dmesg | grep tty
[0.065487] printk: console [tty0] enabled
[0.242012] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 
16550A

Anything obvious I've missed, known tricks with this weather station?
Log to follow.
Thanks,
keith





-- 
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/e9f96bd6-9d60-41ce-a6fb-498d478b2c0en%40googlegroups.com.

[weewx-user] installation and configuration of weewx-saratoga

[Alessandro Battini]

Hi all, I'm trying to install and configure the weewx-saratoga plugin, but 
after the installation process, once I restart the weewx service I'm 
getting this error in the log :

Database OperationalError exception: no such column: windrun

After some search it should be an issue with my DB that is not updated and 
does not contains the windrun column, but I did not found any indication on 
how to fix this issue.

Not sure if it's relevant but currently the station does not have a wind 
server and thus no wind data is present.

Thank in advance,
Alessandro.

-- 
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/2dcf5455-4ea5-46f2-aa53-269ce5057fb0n%40googlegroups.com.