ii libusb-0.1-4:amd64
2:0.1.12-28 amd64userspace USB
programming library
ii libusb-1.0-0:amd64
2:1.0.20-1amd64userspace USB
programming library
hi python-us
Full output of dpkg -l | grep usb is attached for better reading.
Regards,
Roland
Am Donnerstag, 3. November 2016 21:37:56 UTC+1 schrieb mwall:
>
> On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>>
>> I gave it a try, but I had the following errors in the log with debug = 0
I gave it a try, but I had the following errors in the log with debug = 0
Nov 3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach
kernel driver from interface 0: Keine Daten verfügbar
Nov 3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could not
detach kernel drive
Thank you Matthew. 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
vers
Downgrade to python-usb 0.4.3 did not change the behavior. Clean install of
Ubuntu 14.04.5 followed by a clean install of weewx 3.6.1 did not change
the behavior. No I took a brand new Raspberry, put weewx on it, but I have
exactly the same issue. In the past I was running my station on a Raspbe
Here is the output of lsusb -v -d
root@lin01:~# lsusb -v -d 0fde:ca08
Bus 001 Device 006: ID 0fde:ca08 Oregon Scientific
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass
Thanks for your response. If necessary I am willing to downgrade to ubuntu
14.04
I am on Ubuntu 16.04 with Kernel 4.4.0-45-generic
I have
python-usb 1.0.0~b2
libusb-1.0-0 1.0.20-1
libusb-0.1-4 0.1.23-28
2016-10-25 2:38 GMT+02:00 mwall :
> On Monday, October 24, 2016 at 3:01:47 PM UTC-4, Roland E
I found this Thread:
https://groups.google.com/forum/#!msg/weewx-user/FdapyM5Ku0U/c03far_WAQAJ
but the thread is old and I am hoping, the bug mentioned there was fixed.
Am Montag, 24. Oktober 2016 21:01:47 UTC+2 schrieb Roland Ehle:
>
> Hi all,
>
> I have now attached my WMR300 to an Intel NUC r
Hi all,
I have now attached my WMR300 to an Intel NUC running Ubuntu 16.04 LTS.
Unfortunately weewx 3.6.1 is unable to read data from the station.
Apparantly the reason is, that the USB device is reset by the Kernel,
according to the log:
Oct 24 20:57:01 lin01 weewx[932]: engine: Loading stati
Am Montag, 29. August 2016 22:05:11 UTC+2 schrieb mwall:
>
>
>
> On Monday, August 29, 2016 at 3:46:48 PM UTC-4, Roland Ehle wrote:
>>
>> Seems, as if you got it. I have 2 empty entries in the database for
>> pressure and barometer:
>>
>> 1472494380|29.3797991730656|30.1131380980191
>> 14724945
Am Montag, 29. August 2016 21:24:57 UTC+2 schrieb mwall:
>
> roland,
>
> what are the values for pressure and barometer in the database?
>
> sqlite3 /var/lib/weewx/weewx.sdb
> sqlite> select dateTime,pressure,barometer from archive where dateTime >
> 1472256000;
>
> (this timestamp is for 00:00:
Am Montag, 29. August 2016 21:09:34 UTC+2 schrieb mwall:
>
> On Monday, August 29, 2016 at 2:55:46 PM UTC-4, Roland Ehle wrote:
>>
>> Hi all,
>>
>> I am running the current version of weewx on a raspberry Pi with the
>> WMR300 driver. Each time when I restart weewx using the command sudo
>> /et
Hi all,
I am running the current version of weewx on a raspberry Pi with the WMR300
driver. Each time when I restart weewx using the command sudo
/etc/init.d/weewx restart weewx logs very high values for the pressure. I
had 2 restarts today and each time 1025 hPa of pressure were logged, while
13 matches
Mail list logo
