Oregon scientific WMR300 issues

540 views
Skip to first unread message

Markus Benedikt Biewer

unread,
Nov 29, 2017, 3:24:18 AM11/29/17
to weewx-user
I am new to WeeWx and new to Linux as well. I run WeeWx latest version on a Cubietruck running Ubuntu 16.04.3 LTS
I tried to get WeeWx to run with my Oregon Scientific WMR300 but unfortunately I had no success.

I tried to search the weewx user group. After reading that I got in contact with Roland, the author in this thread:

https://groups.google.com/d/topic/weewx-user/YSz_IWnzOjE

Roland said, it is an issue with libusb, but it seems I can not get it fixed without help of the user group here... my knowledge what to do is much too limited.

Is anybody out there willing to help me? I have setup a ssh access okay, even redirected from my LAN to the WAN (in case somebody would be willing to access my cubietruck directly).

Salut from the german/french border,
Markus


Logfile attached:

--
linaro@MyServer:~$ tail -f /var/log/syslog
Nov 29 09:05:37 MyServer weewx[12404]: engine: Loading service weewx.engine.StdReport
Nov 29 09:05:37 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdReport
Nov 29 09:05:37 MyServer weewx[12404]: engine: Starting up weewx version 3.7.1
Nov 29 09:05:37 MyServer weewx[12404]: engine: Station does not support reading the time
Nov 29 09:05:37 MyServer weewx[12404]: wmr300: reading records since ******* N/A *******     (    N/A   )
Nov 29 09:05:37 MyServer weewx[12404]: wmr300: usb failure: [Errno 110] Operation timed out
Nov 29 09:05:37 MyServer weewx[12404]: engine: Main loop exiting. Shutting engine down.
Nov 29 09:05:37 MyServer weewx[12404]: engine: Caught WeeWxIOError: [Errno 110] Operation timed out
Nov 29 09:05:37 MyServer weewx[12404]:     ****  Waiting 60 seconds then retrying...
Nov 29 09:06:13 MyServer rsyslogd-2007: action 'action 10' suspended, next retry is Wed Nov 29 09:07:43 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Nov 29 09:06:37 MyServer weewx[12404]: engine: retrying...
Nov 29 09:06:37 MyServer weewx[12404]: engine: Using configuration file /etc/weewx/weewx.conf
Nov 29 09:06:37 MyServer weewx[12404]: engine: debug is 1
Nov 29 09:06:37 MyServer weewx[12404]: engine: Initializing engine
Nov 29 09:06:37 MyServer weewx[12404]: engine: Loading station type WMR300 (weewx.drivers.wmr300)
Nov 29 09:06:37 MyServer weewx[12404]: wmr300: driver version is 0.18
Nov 29 09:06:37 MyServer weewx[12404]: wmr300: usb info: pyusb_version=1.0.0b2
Nov 29 09:06:37 MyServer weewx[12404]: wmr300: sensor map is {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 'wind_gust'}
Nov 29 09:06:37 MyServer weewx[12404]: wmr300: Found station at bus= device=
Nov 29 09:06:38 MyServer kernel: [298348.444334] usb 3-1: reset full-speed USB device number 2 using sw-ohci
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdTimeSynch
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdTimeSynch
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdConvert
Nov 29 09:06:38 MyServer weewx[12404]: engine: StdConvert target unit is 0x1
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdConvert
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdCalibrate
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdCalibrate
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdQC
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdQC
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.wxservices.StdWXCalculate
Nov 29 09:06:38 MyServer weewx[12404]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=hardware, dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware, windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware
Nov 29 09:06:38 MyServer weewx[12404]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdArchive
Nov 29 09:06:38 MyServer weewx[12404]: engine: Archive will use data binding wx_binding
Nov 29 09:06:38 MyServer weewx[12404]: engine: Record generation will be attempted in 'hardware'
Nov 29 09:06:38 MyServer weewx[12404]: engine: Using archive interval of 300 seconds (specified in weewx configuration)
Nov 29 09:06:38 MyServer weewx[12404]: engine: Use LOOP data in hi/low calculations: 1
Nov 29 09:06:38 MyServer weewx[12404]: manager: Daily summary version is 2.0
Nov 29 09:06:38 MyServer weewx[12404]: engine: Using binding 'wx_binding' to database 'weewx.sdb'
Nov 29 09:06:38 MyServer weewx[12404]: manager: Starting backfill of daily summaries
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdArchive
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdStationRegistry
Nov 29 09:06:38 MyServer weewx[12404]: restx: StationRegistry: Registration not requested.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdStationRegistry
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdWunderground
Nov 29 09:06:38 MyServer weewx[12404]: restx: Wunderground: Posting not enabled.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdWunderground
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdPWSweather
Nov 29 09:06:38 MyServer weewx[12404]: restx: PWSweather: Posting not enabled.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdPWSweather
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdCWOP
Nov 29 09:06:38 MyServer weewx[12404]: restx: CWOP: Posting not enabled.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdCWOP
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdWOW
Nov 29 09:06:38 MyServer weewx[12404]: restx: WOW: Posting not enabled.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdWOW
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.restx.StdAWEKAS
Nov 29 09:06:38 MyServer weewx[12404]: restx: AWEKAS: Posting not enabled.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.restx.StdAWEKAS
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdPrint
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdPrint
Nov 29 09:06:38 MyServer weewx[12404]: engine: Loading service weewx.engine.StdReport
Nov 29 09:06:38 MyServer weewx[12404]: engine: Finished loading service weewx.engine.StdReport
Nov 29 09:06:38 MyServer weewx[12404]: engine: Starting up weewx version 3.7.1
Nov 29 09:06:38 MyServer weewx[12404]: engine: Station does not support reading the time
Nov 29 09:06:38 MyServer weewx[12404]: wmr300: reading records since ******* N/A *******     (    N/A   )
Nov 29 09:06:38 MyServer weewx[12404]: wmr300: usb failure: [Errno 110] Operation timed out
Nov 29 09:06:38 MyServer weewx[12404]: engine: Main loop exiting. Shutting engine down.
Nov 29 09:06:38 MyServer weewx[12404]: engine: Caught WeeWxIOError: [Errno 110] Operation timed out
Nov 29 09:06:38 MyServer weewx[12404]:     ****  Waiting 60 seconds then retrying...

scott arnott

unread,
Nov 29, 2017, 4:50:26 AM11/29/17
to weewx-user
i am having this same problem when running my wmr300 on a raspberry pi hope there is a fix for this have tried everything but still wont read data from the  weather station

scott arnott

unread,
Nov 29, 2017, 5:15:24 AM11/29/17
to weewx-user
this is the error i get on the raspberry pi 

Nov 29 10:13:15 raspberrypi weewx[1868]: wmr300: reading records since ******* N/A *******     (    N/A   )                    
Nov 29 10:13:15 raspberrypi weewx[1868]: wmr300: usb failure: [Errno 110] Operation timed out                                  
Nov 29 10:13:15 raspberrypi weewx[1868]: engine: Caught WeeWxIOError: [Errno 110] Operation timed out                          
Nov 29 10:13:15 raspberrypi weewx[1868]:     ****  Waiting 60 seconds then retrying...                                         
Message has been deleted

Markus Benedikt Biewer

unread,
Nov 29, 2017, 5:38:43 AM11/29/17
to weewx-user
Roland the wrote me a private mail, he wrote that the solution was:

--snip--
- I had to deinstall "libusb" and reinstalled it with an older version (he could not remember the version number, but its in the thread above...)
- I also had to reconfigure apt in a way that libusb does not get updated automatically
--snap--

In his earlier posting here (no data from station, link see above) he also wrote:

--snip--
After some more digging and testing I came to the conclusion: It is not weewx itself that causes the issue, but the WMR300 driver for some reason. I downgraded to weewx 3.5.0 and everything worked fine. After copying the WMR300 driver files I upgraded again to the latest version and the issue was present again until I copied the driver version 0.10 to the location /usr/share/weewx/weewx/drivers.

So, after all, I have a working configuration :-) Thanks for your support
--snap--

I can understand this procedure but I do not know how to do that at the end. Is anyone willing to show me and scott how the actual steps to do look like?

I tried this wiki also but was not of much help either.

Thanks very much!
Markus

scott arnott

unread,
Nov 30, 2017, 9:04:49 AM11/30/17
to weewx-user
still cant get weewx to read the weather data from the wmr300 have tested it on weather display but relay prefer to use weewx this is the error below i get 

Nov 29 10:13:15 raspberrypi weewx[1868]: wmr300: reading records since ******* N/A ******* ( N/A )
Nov 29 10:13:15 raspberrypi weewx[1868]: wmr300: usb failure: [Errno 110] Operation timed out
Nov 29 10:13:15 raspberrypi weewx[1868]: engine: Caught WeeWxIOError: [Errno 110] Operation timed out
Nov 29 10:13:15 raspberrypi weewx[1868]: **** Waiting 60 seconds then retrying...

Markus Benedikt Biewer

unread,
Dec 1, 2017, 2:11:15 AM12/1/17
to weewx-user
Nobody out there willing to help me and Scott? We seem to have the same problem....

What can we do or try and how?


--

mwall

unread,
Dec 1, 2017, 6:17:39 AM12/1/17
to weewx-user


On Friday, December 1, 2017 at 2:11:15 AM UTC-5, Markus Benedikt Biewer wrote:
Nobody out there willing to help me and Scott? We seem to have the same problem....

What can we do or try and how?


there are some things you can try.  i can walk you through it, but i am rather pressed for time right now (a boat to catch).  will get back to you in a couple of days...
 

Markus Benedikt Biewer

unread,
Dec 4, 2017, 6:42:56 AM12/4/17
to weewx-user
That would be AWESOME and your help is much appreciated.

Salut from France, Markus

--

scott arnott

unread,
Dec 4, 2017, 6:56:12 AM12/4/17
to weewx-user
yes would be good to get some help i have tried different things but still get the same error have tried on linux pc also a raspberry pi and a odroid c1 but still get the same error message but the WMR300 works fine on weather display and WeatherTracker on windows 10 with no problem 

it would be good if someone had a working image for the raspberry pi that  is using a wmr300 that could upload it to a download site 

thanks 

scott arnott

unread,
Dec 6, 2017, 8:19:40 AM12/6/17
to weewx-user
is there anyone running a wmr300 that has any advice how to get it running running om weewx wee cant be the only 2 people that is getting this problem .what is other users with the wmr300 using eg what version of Linux is it running on is it a raspberry pi our pc  and what version of weewx thanks 

Markus Benedikt Biewer

unread,
Dec 6, 2017, 8:59:48 AM12/6/17
to weewx-user
Hi Scott,
I am in contact with Roland (see my first posting in thirs thread) who also had this problem.

https://groups.google.com/d/topic/weewx-user/YSz_IWnzOjE

As I wrote above, he has solved it by downgrading weewx to an older version which changes libusb to a former version and then hinder apt-get to update libusb in the future. Without further help I am not able to do the same which is why i wrote here. Also I think, this is something that should be solved in the current release of weewx package, because if not everyone using a WMR300 will have the same issue in the future.

So the help is not for me and you only but for everyone who is interested to use the current weewx with the Oregon Scientific WMR300 and I desperately hope we can get this solved through the group here.

Salut,
Markus

--

Thomas Keffer

unread,
Dec 6, 2017, 9:06:44 AM12/6/17
to weewx-user
Open source depends on a community of people voluntarily offering contributions. You may think this is something that "should be solved," but until someone steps forward to do it, nothing happens. 

Why not give it a try yourself?

-tk

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

Markus Benedikt Biewer

unread,
Dec 6, 2017, 9:19:26 AM12/6/17
to weewx-user
Hi Thomas,
I am not complaining (as Scott does) nor demanding help here and I also tried myself (I have the WMR300 since half a year, then spent some weeks to setup my Linux PC and I have been successful in installing weewx (which makles me kinda proud, as I have no experience at all before with such stuff). I ready through the documentation and tried to follow your docs to change the driver but I did not succeed at this point. Then I contacted Roland, see my first posting, he had the same problem and solved it by downgrading libusb. I am stuck here, could not find postings here that helped. Thats why I asked. I still look for possible solutions and hope mwall's upcoming reply will hopefully help.

I also wrote to let you know (as the creator/maintainer of the weewx package) to solve the problem at the roots as obviously everyone who has a WMR300 expieriences this problem... Just a friendly notification, as we here are all users of weewx (or will come here if in futuire are having the same issue).

I am grateful for any help I can get.

Salut,
Markus

--
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

mwall

unread,
Dec 6, 2017, 9:23:09 AM12/6/17
to weewx-user
scott and markus (and other wmr300 users),

as of dec2017, there are two versions of the wmr300 driver:

1) wmr300 version 0.18 (in the weewx distribution)

2) wmr300x version 0.18nolegacy.05.01a

of course we would like to bring these into a single driver.  the difficult part of that is being able to test all of the permutations.

these are the outstanding issues:

- how to get the initial startup to work with all libusb versions?  the timeouts you see are when the driver cannot get the station to start communication.

- need to incorporate the rain counter changes from 0.18nolegacy.  that version has code that will automatically reset the rain counter - without that reset, one must manually reset the counter since the hardware does not wrap automatically.

- figure out which libusb versions are truly broken.  for example, i experienced problems with libusb 1.0.11 that disappeared when i changed to libusb 1.0.20

- the pyusb version should not matter; the libusb version seems to be the problem

i developed the driver some years ago using a raspberry pi and the legacy libusb.  unfortunately the more recent libusb behave differently.

i no longer have access to that computer or the weather station, so right now i cannot test any changes.

what can you do right now?

- for each configuration you try, be sure to record:
  - the wmr300 driver version
  - the weewx version
  - the libusb version
  - the pyusb version

- try using libusb 0.1 instead of libusb 1.x

- try using the 'nolegacy' driver with libusb 1.x

if we can get a few people with wmr300 stations to do some testing (or give me access to their systems so i can do the testing), then we could consolidate the driver variants.

m

Markus Benedikt Biewer

unread,
Dec 6, 2017, 2:53:35 PM12/6/17
to weewx-user
I wrote you a private mail, I hope you have received it? I can give you a SSH access to my instattion, which might be easier in terms of time (although I won't learn sth)... Just let me know....

Salut,
Markus

--

scott arnott

unread,
Dec 7, 2017, 2:42:43 AM12/7/17
to weewx-user
finally got it working with using this driver and adding it to /usr/share/weewx/weewx/drivers i also added this below into the weewx config file 

[WMR300]
    # This section is for WMR300 weather stations.
    
    # The station model, e.g., WMR300A
    model = WMR300
    
    # The driver to use:
    driver = weewx.drivers.wmr300

   history_clear_pct = 5

    debug_decode=0
    debug_history=0
    debug_rain=1
# Set debug_backend to 0 for default lib
# 1 for libusb0
# 2 for libusb1
# 3 for openusb
# 4 for ?
    debug_backend=0
wmr300.py

Miguel Iniesta

unread,
Dec 7, 2017, 5:36:55 AM12/7/17
to weewx-user
Hello Markus,

Ubuntu 16.04 seems to have a libusb1 version which does not work with either WMR300 driver. I tried without success.
Debian 9 and WMR300x is working fine. According to some users, Raspbian (based on Debian 9) and WMR300x works also fine.
You can find more information in this thread:
https://groups.google.com/forum/?hl=en#!searchin/weewx-user/misc%7Csort:date/weewx-user/zten3pSm3M0/qvYVy8jQBwAJ

Regards,

Alberto Sánchez

unread,
Dec 26, 2017, 8:07:51 AM12/26/17
to weewx-user
I am testing new mwall driver 0.19RC1 (Thanks a lot mwall). But I have problems with it:

Dec 26 14:01:28 raspberrypi weewx[2333]: ****    File "/usr/share/weewx/weewx/drivers/wmr300.py", line 1230, in get_history
Dec 26 14:01:28 raspberrypi weewx[2333]: ****      self.finish_history()
Dec 26 14:01:28 raspberrypi weewx[2333]: ****    File "/usr/share/weewx/weewx/drivers/wmr300.py", line 1129, in finish_history
Dec 26 14:01:28 raspberrypi weewx[2333]: ****      self.station.write(cmd)
Dec 26 14:01:28 raspberrypi weewx[2333]: ****    File "/usr/share/weewx/weewx/drivers/wmr300.py", line 1465, in write
Dec 26 14:01:28 raspberrypi weewx[2333]: ****      return self._write(buf)
Dec 26 14:01:28 raspberrypi weewx[2333]: ****    File "/usr/share/weewx/weewx/drivers/wmr300.py", line 1458, in _write
Dec 26 14:01:28 raspberrypi weewx[2333]: ****      sent = self.handle.interruptWrite(Station.EP_OUT, buf, self.timeout)
Dec 26 14:01:28 raspberrypi weewx[2333]: ****  USBError: could not detach kernel driver from interface 0: No data available
Dec 26 14:01:28 raspberrypi weewx[2333]: ****  Exiting.



thanks

Alberto Sánchez

unread,
Dec 26, 2017, 8:28:51 AM12/26/17
to weewx-user
If I restart weewx It works well.

mwall

unread,
Dec 26, 2017, 12:38:33 PM12/26/17
to weewx-user
On Tuesday, December 26, 2017 at 8:07:51 AM UTC-5, Alberto Sánchez wrote:
I am testing new mwall driver 0.19RC1 (Thanks a lot mwall). But I have problems with it:


fixed at commit e43e033 

it looks like we must ignore usb non-errors and usb timeouts for all reads and writes

m

Alberto Sánchez

unread,
Dec 26, 2017, 1:06:24 PM12/26/17
to weewx-user
Thanks!!! I will test as soon as possible and I will inform here.

mwall

unread,
Dec 31, 2017, 11:24:32 AM12/31/17
to weewx-user
On Tuesday, December 26, 2017 at 1:06:24 PM UTC-5, Alberto Sánchez wrote:
Thanks!!! I will test as soon as possible and I will inform here.

wmr300 version 0.19rc2 has been running reliably now on armhf ubuntu 16.04.03


dpkg --list | grep usb
ii  libusb-0.1-4:armhf 2:0.1.12-28 armhf   userspace USB programming library
ii  libusb-1.0-0:armhf 2:1.0.20-1 armhf    userspace USB programming library
ii  python-usb         1.0.0~b2-2 all      USB interface for Python
ii  usbutils           1:007-4    armhf    Linux USB utilities


feedback from users with these systems would be helpful:


any x86_64 systems
any armel systems
python-usb 0.4.x
libusb-0.1 (no libusb-1.x installed) 
libusb-1.0.11 (ships with debian 7) 

you can download the driver directly from github:


this incorporates cameron's history flushing and handles usb non-errors and timeouts.  there is not yet any known method for automatically resetting the rain counter, but this driver will make a log entry once each day if the rain counter has reached its maximum value.

if anyone has been able to use software to reset the rain counter, please do some usb captures of the process and post them to weewx-user so that we can incorporate that into the driver.

thanks to all of the wmr300 owners who have helped make this driver possible!

m

Alberto Sánchez

unread,
Jan 1, 2018, 10:58:46 AM1/1/18
to weewx-user
Hi mwall,

I am testing rc2 driver, this is mi configuration

pi@raspberrypi:~ $ dpkg -l | grep usb
ii  libusb-0.1-4:armhf                    2:0.1.12-25                               armhf        userspace USB programming library
ii  libusb-1.0-0:armhf                    2:1.0.19-1                                armhf        userspace USB programming library
ii  libusbmuxd2:armhf                     1.0.9-1                                   armhf        USB multiplexor daemon for iPhone and iPod Touch devices - library
ii  python-usb                            0.4.3-1                                   armhf        USB interface for Python
ii  usb-modeswitch                        2.2.0+repack0-2                           armhf        mode switching tool for controlling "flip flop" USB devices
ii  usb-modeswitch-data                   20150115-1                                all          mode switching data for usb-modeswitch
ii  usbutils                              1:007-2                                   armhf        Linux USB utilities


And I have this error when I restart my raspberry:

pi@raspberrypi:~ $ sudo /etc/init.d/weewx status -l
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since Thu 1970-01-01 01:00:40 CET; 48 years 0 months ago
  Process: 581 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)

Jan 01 01:00:40 raspberrypi systemd[1]: Started LSB: weewx weather system.
Jan 01 16:49:11 raspberrypi weewx[882]: engine: Using configuration file /etc/weewx/weewx.conf
Jan 01 16:49:11 raspberrypi weewx[882]: engine: Loading station type WMR300 (weewx.drivers.wmr300)
Jan 01 16:49:11 raspberrypi weewx[882]: wmr300: driver version is 0.19rc2
Jan 01 16:49:11 raspberrypi weewx[882]: wmr300: usb info: pyusb_version=0.4.x
Jan 01 16:49:11 raspberrypi weewx[882]: wmr300: sensor map is {'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill'... 'extraD
Jan 01 16:49:11 raspberrypi weewx[882]: wmr300: history limit is 20%
Jan 01 16:49:12 raspberrypi weewx[882]: import of driver failed: Connection timed out (<class 'usb.USBError'>)
Jan 01 16:49:12 raspberrypi weewx[882]: engine: Unable to load driver: Connection timed out
Jan 01 16:49:12 raspberrypi weewx[882]: ****  Exiting...


After that, if I restar weewx it works well.

Thank you very much and happy new year!

mwall

unread,
Jan 1, 2018, 11:05:59 AM1/1/18
to weewx-user
alberto,

thank you for testing!

please try the attached wmr300-0.19rc3.py

m


wmr300-0.19rc3.py

Alberto Sánchez

unread,
Jan 2, 2018, 11:36:24 AM1/2/18
to weewx-user
Hi mwall.

I am testing RC3 and it works well! The previous error has been corrected.

Thank you very much!

Alberto Sánchez

unread,
Jan 17, 2018, 2:50:36 PM1/17/18
to weewx-user
15 days without any error.

Thanks.

Sam Walton

unread,
Feb 26, 2018, 7:05:28 AM2/26/18
to weewx-user
Hi Mwall,

Thanks for the driver. I've installed driver wmr300-0.19rc3 on my Ubuntu pi tonight and it is working well! 

Have you or anyone else noticed that WU is not displaying wind direction at the top? It seems to be recording it in the history and also on the weewx local site but not WU. I did not have this problem running Weewx on Raspbian before. 

Attached is some debug logs and I've noticed that rapid fire isn't sending the direction logs all the time.

The Weatherstation is: Oregon Scientific WMR300

Thanks again

Sam
syslog_debuglvl2.txt
Reply all
Reply to author
Forward
0 new messages