Fyi for those who are interested...

The kernel change/fix was recently back-ported Red Hat Enterprise Linux 9 / 
Rocky Linux 9.  As of 5.14.0-687.41.1.el9_8.x86_64 the udev rules patch was 
NOT necessary.  As of 5.14.0-687.53.1.el9_8.x86_64 it IS necessary.

As of weewx 5.5.2 from the weewx repo (weewx-5.5.2-1.el9.src.rpm) I see the 
fix in /etc/weewx/udev/weewx.rules, so its just a matter of copying this 
file to /etc/udev/rules.d/60-weewx.rules and installing it.

All good now.  So ends 2 days of rooting around in the muck and chasing a 
kernel induced weewx crash.  Inconveniently for me, the newer kernel got 
installed along with a motherboard replacement.  Tail chase, not aided by a 
bunch of AI bogus debugging and hack suggestions.

Thanks Jens,
cjn

On Saturday, April 18, 2026 at 10:30:42 PM UTC-7 Mike Book wrote:

> Just wanted to chime in and say thanks to Jens Jensen and Tom Keffer. 
>
> Once tom pointed out where the file path was I was able to input Jens 
> information in. This was a fresh Pi OS install and the most recent version 
> too. It worked flawlessly and I'm very happy.
>
> Once again Thank you.
>
> On Tuesday, April 14, 2026 at 5:55:30 PM UTC-4 Vince Skahan wrote:
>
>> oops thanks. The old thing where the file can be in /etc or /usr or 
>> either with one taking precedence gets me all the time. Sigh.
>>
>> On Tuesday, April 14, 2026 at 2:10:20 PM UTC-7 Tom Keffer wrote:
>>
>>> Just a small correction: both the package installers, and the pip script 
>>> "setup-daemon.sh", install the WeeWX udev rule in 
>>> */usr/lib/udev/rules.d/60-weewx.rules*
>>>
>>>
>>> On Tue, Apr 14, 2026 at 1:54 PM Vince Skahan <[email protected]> wrote:
>>>
>>>> Mike  - you have some misconceptions....
>>>>
>>>>    - /etc/weewx/udev contains 'template' files that come with weewx 
>>>>    which you can choose to install if needed
>>>>    - editing in /etc/weewx/udev just updates the template file.  It 
>>>>    doesn't affect how the os works
>>>>
>>>>
>>>>    - /etc/udev/rules.d is the operating system's directory for that 
>>>>    subsystem
>>>>    - weewx does not install anything there by default since 
>>>>    customization there is not needed for all configurations
>>>>
>>>> So in your case you'd need to:
>>>>
>>>>    - edit the template file weewx comes with to add the additional 
>>>>    stuff Jens mentioned
>>>>    - then 'copy' it into place via "sudo cp 
>>>>    /etc/weewx/udev/weewx.rules /etc/udev/rules.d/60-weewx.rules"
>>>>    - and then run a couple commands to make the file take 
>>>>    effect.....or simply reboot the pi which is easier I suspect.
>>>>
>>>> If you do a google search for 'installing udev file debian' and look at 
>>>> the AI generated help it will explain further.
>>>>
>>>> Lastly -  raspi os and ubuntu are both debian-based so they operate the 
>>>> same.  No need to switch your os.
>>>>
>>>> On Sunday, April 12, 2026 at 11:38:19 PM UTC-7 Mike Book wrote:
>>>>
>>>>> I gave Jens Jensen fix a try and it didn't work.
>>>>>
>>>>> What I found is the rules file path  /etc/udev/rules.d/60-weewx.rules did 
>>>>> not exist. I looked for anything with that and I found nothing. The only 
>>>>> rules I could find with were in the weexwx etc folder and was named 
>>>>> weewx.rules. There was nothing started with the name 60. I did try adding 
>>>>> their code into weewx.rules and it didn't make any change. 
>>>>>
>>>>> At this time I rolled back to an older version of Pi Os. 
>>>>>
>>>>> I'm running Pi now but this could potentially just be folders that get 
>>>>> creatted in Ubuntu and not Pi.
>>>>>
>>>>> I will try and Ubuntu install on a different date.
>>>>>
>>>>> On Monday, April 13, 2026 at 1:25:29 AM UTC-4 Mike Book wrote:
>>>>>
>>>>>> Thank you so much for that detailed information. With this I can feel 
>>>>>> better updating my Pi to the newest software and give it ago.
>>>>>>
>>>>>> I'm sure many will appreciate this whole heartedly.
>>>>>>
>>>>>> On Sunday, April 12, 2026 at 7:38:46 PM UTC-4 Tom Keffer wrote:
>>>>>>
>>>>>> Thank you, Jens, for not only a very comprehensive summary, but also 
>>>>>> a solution!
>>>>>>
>>>>>> On Sun, Apr 12, 2026 at 3:59 PM 'Jens Jensen' via weewx-user <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>> FYI, I was able to fix this with help of gemini & a udev rule 
>>>>>> addition (which I'll look into getting a PR into weewx repo). Gemini's 
>>>>>> summary & fix:
>>>>>>
>>>>>> This summary covers why Acurite weather stations (and similar 
>>>>>> non-standard HID devices) recently stopped working on Linux systems like 
>>>>>> Ubuntu 24.04 and how to fix it.
>>>>>> ------------------------------
>>>>>> *Technical Summary: Acurite USB Connectivity Fix**The Issue*
>>>>>>
>>>>>> After updating to recent Linux kernels (specifically 6.2 and newer, 
>>>>>> found in Ubuntu 24.04+), users found that *WeeWX* or other weather 
>>>>>> software could no longer communicate with Acurite base stations (Vendor 
>>>>>> ID 
>>>>>> 0x24c0, Product ID 0x0003). The device would show up in lsusb, but 
>>>>>> no data would flow, and the system often reported "Resource busy" or 
>>>>>> "Timeout" errors.
>>>>>> *The Cause: Firmware Non-Compliance*
>>>>>>
>>>>>> The hardware firmware in many Acurite consoles is technically 
>>>>>> "broken." It provides a *USB HID Descriptor* that is malformed 
>>>>>> (specifically, it declares two descriptors but only provides one, 
>>>>>> leading 
>>>>>> to the error Warning: Descriptor too short).
>>>>>> *The Reason: Kernel Evolution*
>>>>>>
>>>>>> Previously, the Linux kernel was "permissive." It would ignore these 
>>>>>> minor firmware errors and allow the device to function. However, 
>>>>>> starting 
>>>>>> around early 2023, the kernel's HID subsystem was updated to be 
>>>>>> *stricter* for security and stability reasons.
>>>>>>
>>>>>>    - 
>>>>>>    
>>>>>>    When the modern kernel sees the malformed descriptor, it fails 
>>>>>>    the "probe" of the device.
>>>>>>    - 
>>>>>>    
>>>>>>    The usbhid driver then "hangs onto" the device in an error state, 
>>>>>>    preventing user-space drivers (like WeeWX's Python driver) from 
>>>>>> claiming 
>>>>>>    the interface.
>>>>>>    
>>>>>> *The Resolution: Udev Unbinding*
>>>>>>
>>>>>> The fix involves a specific udev rule that performs two tasks:
>>>>>>
>>>>>>    1. 
>>>>>>    
>>>>>>    *Permission Granting:* Grants the weewx user group permission to 
>>>>>>    access the raw USB character device.
>>>>>>    2. 
>>>>>>    
>>>>>>    *Driver Unbinding:* Automatically tells the kernel to "let go" of 
>>>>>>    the device (unbind) the moment it is plugged in. This prevents 
>>>>>>    the usbhid driver from locking the device in its failed state, 
>>>>>>    leaving it "free" for WeeWX to communicate with directly via 
>>>>>>    libusb.
>>>>>>    
>>>>>> ------------------------------
>>>>>> *The Fix*
>>>>>>
>>>>>> Modify existing acurite rules:
>>>>>>
>>>>>> /etc/udev/rules.d/60-weewx.rules
>>>>>>
>>>>>> *Paste the following content:*
>>>>>> # 1. Grant permissions to the weewx group 
>>>>>> SUBSYSTEM=="usb", ATTRS{idVendor}=="24c0", ATTRS{idProduct}=="0003", 
>>>>>> MODE="0664", GROUP="weewx" 
>>>>>> # 2. Force the kernel to unbind the hid-generic driver so it doesn't 
>>>>>> "lock" the station 
>>>>>> SUBSYSTEM=="usb", ATTRS{idVendor}=="24c0", ATTRS{idProduct}=="0003", 
>>>>>> ACTION=="add", RUN+="/bin/sh -c 'echo $kernel > 
>>>>>> /sys/bus/usb/drivers/usbhid/unbind || true'"
>>>>>>
>>>>>> My Notes: section 2 is the new thing here which seems to fix it. 
>>>>>>
>>>>>> *Apply the changes:*
>>>>>> sudo udevadm control --reload-rules 
>>>>>> sudo udevadm trigger 
>>>>>> # Then restart WeeWX 
>>>>>> sudo systemctl restart weewx 
>>>>>> My Notes: There appear to be other ways to fix this, e.g. 
>>>>>> via usbhid.quirks kernel options, etc, but this udev rules change 
>>>>>> appears 
>>>>>> to be the cleanest, easiest way, and probably easy to incorporate the 
>>>>>> fix 
>>>>>> into weewx itself.
>>>>>>
>>>>>> -Jens
>>>>>> On Thursday, March 12, 2026 at 6:54:52 PM UTC-5 Mike Book wrote:
>>>>>>
>>>>>> Well thank for the insight but I will still leave ubuntu updates off. 
>>>>>> I have clearly seen a few other posts with the same issue after updating 
>>>>>> to 
>>>>>> Ubuntu with not much of a fix. Considering this computer doesn't run 
>>>>>> anything vital to me I also don't care if it updates.
>>>>>>
>>>>>> On Thursday, March 12, 2026 at 7:43:51 PM UTC-4 John Smith wrote:
>>>>>>
>>>>>> To be honest I have no idea why my copy of 24.04.3 LTS failed. It was 
>>>>>> in the middle of installing when I had a message window popup stating 
>>>>>> that 
>>>>>> the installed failed.
>>>>>>
>>>>>>
>>>>>> That could have been a corrupt image or the USB/CD/DVD that wasn't 
>>>>>> written to or couldn't be read from properly, but when you said that 
>>>>>> version broke the driver I thought you meant it installed fully.
>>>>>>  
>>>>>>
>>>>>> I think when I get back home tonight I will disable updates just in 
>>>>>> case.
>>>>>>
>>>>>>
>>>>>> That isn't a good strategy when there is bugs that get a high CVE 
>>>>>> score, especially if the severity is up around 10.
>>>>>>
>>>>>> Setting hold on packages is less risky as only those packages won't 
>>>>>> update.
>>>>>>
>>>>>> On Fri, 13 Mar 2026 at 05:10, Mike Book <[email protected]> wrote:
>>>>>>
>>>>>> To be honest I have no idea why my copy of 24.04.3 LTS failed. It was 
>>>>>> in the middle of installing when I had a message window popup stating 
>>>>>> that 
>>>>>> the installed failed. Asked me to send the report but I passed on it. So 
>>>>>> I 
>>>>>> don't believe it was a kernel issue. 
>>>>>>
>>>>>> Since I found my old previous installation media I knew that worked 
>>>>>> previously so just went with that. 
>>>>>>
>>>>>> Like stated I'm running desktop. Any time there is an update I get a 
>>>>>> window saying a update is available and I just pass on it. I think when 
>>>>>> I 
>>>>>> get back home tonight I will disable updates just in case.
>>>>>>
>>>>>> On Thursday, March 12, 2026 at 3:48:33 AM UTC-4 John Smith wrote:
>>>>>>
>>>>>> I couldn't find an ISO of 24.04.3 LTS that would work when installing
>>>>>>
>>>>>>
>>>>>> Was it just a kernel issue?
>>>>>>
>>>>>> If so wouldn't you just install an older kernel package and then use 
>>>>>> apt-mark hold to stop it from being upgraded? 
>>>>>>
>>>>>> On Thu, 12 Mar 2026 at 15:20, Mike Book <[email protected]> wrote:
>>>>>>
>>>>>> Thank you to everyone that assisted.
>>>>>>
>>>>>> My weather station is officially back up and running.
>>>>>>
>>>>>> Here is the fix just for those in the future that might be having the 
>>>>>> same problem.
>>>>>>
>>>>>> For starters Ubuntu 24.04.4 LTS kills the Acurite driver. It appears 
>>>>>> 25.10 does the same thing.
>>>>>>
>>>>>> I couldn't find an ISO of 24.04.3 LTS that would work when 
>>>>>> installing. I only guessed this would work from looking around on the 
>>>>>> forums. There is a live server version of 24.04.3 that might work but I 
>>>>>> haven't verified that. I also don't like server version too much. I 
>>>>>> prefer 
>>>>>> the usage of a GUI.
>>>>>>
>>>>>> I ended up getting lucky and finding my original flash drive that I 
>>>>>> used two years ago. This drive had the Ubuntu 24.04.2 LTS ISO installed 
>>>>>> on 
>>>>>> it. I went ahead and gave this a try. My installation of Ubuntu went 
>>>>>> without any hiccups.
>>>>>>
>>>>>> That being said, once Ubuntu installed I followed the Debian install 
>>>>>> on weewx website. After that was done I got some insufficient permission 
>>>>>> errors with weewx. This isn't a weewx problem and there was no need for 
>>>>>> me 
>>>>>> to go down the rabbit hole of creating udevs and such. When weewx 
>>>>>> installs 
>>>>>> it creates a bunch of groups and with Ubuntu any group policy that is 
>>>>>> made 
>>>>>> a complete restart is needed.
>>>>>>
>>>>>> I restarted the computer and checked the HTML path and sure if enough 
>>>>>> the Index.HTML file was there. I proceeded to edit my config file to get 
>>>>>> up 
>>>>>> and running on CWOP.
>>>>>>
>>>>>> My weather station is now live and showing data.
>>>>>>
>>>>>> Again, thanks to all of those that helped, it was much appreciated.
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 4:46:33 PM UTC-4 Mike Book wrote:
>>>>>>
>>>>>> Thank you friend,
>>>>>>
>>>>>> I have it downloading now. I also got a desktop version of 22.04.5 
>>>>>> which resembles exactly how I remember my desktop looking before 
>>>>>> updating 
>>>>>> the current software.
>>>>>>
>>>>>> I will try it later tonight to see if it works.
>>>>>>
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 3:31:08 PM UTC-4 Tom Keffer wrote:
>>>>>>
>>>>>> My apologies. I missed that point.
>>>>>>
>>>>>> Just use the same URL, except substitute 24.04.3 for 24.04.4:
>>>>>>
>>>>>>
>>>>>> https://ubuntu.com/download/server/thank-you?version=24.04.3&architecture=amd64&lts=true
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>> On Wed, Mar 11, 2026 at 11:41 AM Mike Book <[email protected]> 
>>>>>> wrote:
>>>>>>
>>>>>> yes but it appears this version is the version that kills the Acurite 
>>>>>> driver. Was looking to get 24.04.3 which I had last year and had never 
>>>>>> updated.
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 2:26:15 PM UTC-4 Tom Keffer wrote:
>>>>>>
>>>>>> Until 26.04 comes out, that's the current "Long Term Support" 
>>>>>> version. You can find it on their download page: 
>>>>>> https://ubuntu.com/download/server
>>>>>>
>>>>>> On Wed, Mar 11, 2026 at 10:54 AM Mike Book <[email protected]> 
>>>>>> wrote:
>>>>>>
>>>>>> Since it was mentioned that there has been issues with acurite 
>>>>>> drivers from newer Linux distros it has occurred to me that is more than 
>>>>>> likely the issue.
>>>>>>
>>>>>> When I first installed my weather station in 2025 Ubuntu 24.04.4 had 
>>>>>> not been released. I'm pretty sure I was running 24.04.3 and I took a 
>>>>>> look 
>>>>>> through the forums and it appears the consensus was to install that 
>>>>>> version 
>>>>>> of Ubuntu.
>>>>>>
>>>>>> Problem is I moved recently and can't find the original USB drive I 
>>>>>> used to install Ubuntu.
>>>>>>
>>>>>> I've tried getting the ISO direct from Ubuntu but that hasn't helped. 
>>>>>> I'm wondering if anyone knows where I can get the amd64 iso for 24.04.3. 
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 12:11:47 PM UTC-4 Pablo Sanchez wrote:
>>>>>>
>>>>>> I use openSUSE Tumbleweed. I installed weewx using the pip method - 
>>>>>> https://weewx.com/docs/5.3/quickstarts/pip/
>>>>>>
>>>>>> It works great!
>>>>>>
>>>>>> I should probably update the OS as it has been 50 odd days since my 
>>>>>> last update. :) 
>>>>>> --- pablo 
>>>>>>
>>>>>> On 2026-03-11 12:04, Mike Book wrote:
>>>>>>
>>>>>> I thank you for that but I have searched the forums for my exact 
>>>>>> errors and everything that is listed has not worked. 
>>>>>>
>>>>>> I recently got openSUSE installed to try that but it won't install.
>>>>>> mike@mint:~> sudo rpm --import https://weewx.com/keys.html 
>>>>>> [sudo] password for root:  
>>>>>> mike@mint:~> curl -s https://weewx.com/suse/weewx.repo | \ 
>>>>>> >     sudo tee /etc/zypp/repos.d/weewx.repo 
>>>>>> [weewx] 
>>>>>> name=weewx 
>>>>>> baseurl=http://weewx.com/suse/weewx/suse$releasever_major 
>>>>>> enabled=1 
>>>>>> gpgcheck=1 
>>>>>> mike@mint:~> sudo zypper install weewx 
>>>>>> Error building the cache: 
>>>>>> [weewx|http://weewx.com/suse/weewx/suse20260308] Failed to retrieve 
>>>>>> new repository metadata. 
>>>>>> History: 
>>>>>> - [weewx|http://weewx.com/suse/weewx/suse20260308] Repository type 
>>>>>> can't be determined. 
>>>>>> Warning: Skipping repository 'weewx' because of the above error. 
>>>>>> Some of the repositories have not been refreshed because of an error. 
>>>>>> Loading repository data... 
>>>>>> Reading installed packages... 
>>>>>> 'weewx' not found in package names. Trying capabilities. 
>>>>>> No provider of 'weewx' found. 
>>>>>> Resolving package dependencies... 
>>>>>> Nothing to do. 
>>>>>> mike@mint:~> 
>>>>>>
>>>>>> This is all I got. I'm not sure what could be wrong here.
>>>>>>
>>>>>> To the previous. I understand nothing much has changed on Weewx which 
>>>>>> I get but something isn't right.
>>>>>>
>>>>>> If its not Ubuntu distro then that makes sense but I'm pretty sure I 
>>>>>> never updated my distro previously until the SDD crash and it worked 
>>>>>> fine. 
>>>>>>
>>>>>> If its a distro issue then some guidance would be great. Again 
>>>>>> searched the forums and not finding much that helps.
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 11:53:55 AM UTC-4 p q wrote:
>>>>>>
>>>>>> There's a problem with the more recent Linux versions and the USB 
>>>>>> Acurite interface. Search this forum for conversations about it.
>>>>>>
>>>>>> On Wed, Mar 11, 2026 at 8:35 AM Tom Keffer <[email protected]> wrote:
>>>>>>
>>>>>> While things like logging have changed, the guts of the Acurite 
>>>>>> driver has not changed since v3.9.2 in early 2019.
>>>>>>
>>>>>> When you updated your copy of Ubuntu, did it change the version of 
>>>>>> Python? There have been some problems with pyusb and Python 12.
>>>>>>
>>>>>> On Wed, Mar 11, 2026 at 7:18 AM Mike Book <[email protected]> wrote:
>>>>>>
>>>>>> Oh I'm not even getting the HTML file.
>>>>>>
>>>>>> Weewx won't make that file if it isn't collecting any data. Since I'm 
>>>>>> currently getting absolutely nothing for the data thus no file.
>>>>>>
>>>>>> This is version 5.3 that I was installing. My last system that worked 
>>>>>> was on the same Ubuntu OS but I was using weewx 5.1.
>>>>>>
>>>>>> Not sure if there is a problem with Weewx.
>>>>>>
>>>>>> Currently I'm attempting to install an openSUSE system and going to 
>>>>>> try installing that way. Hopefully it will work.
>>>>>>
>>>>>> On Wednesday, March 11, 2026 at 10:14:27 AM UTC-4 Steven Hulse wrote:
>>>>>>
>>>>>> Hi Mike, 
>>>>>>
>>>>>> I'm experiencing a similar issue after an update to 5.3 in Linux 
>>>>>> Mint. Did you check the web page that comes with Weewx? I looked at 
>>>>>> mine, 
>>>>>> and it is gathering data, so that's a way you can test to see if it's 
>>>>>> still 
>>>>>> working. My problem is that it's not publishing to Weatherunderground 
>>>>>> anymore. Is that what you are experiencing (not publishing)?
>>>>>>
>>>>>> On Tuesday, March 10, 2026 at 10:10:45 AM UTC-6 Mike Book wrote:
>>>>>>
>>>>>> Hey all, 
>>>>>>
>>>>>> At one point weewx was working just fine for me. I had an issue with 
>>>>>> the PC and had to update with a fresh install of Ubuntu.
>>>>>>
>>>>>> I have no idea what is wrong here but with the new install and 
>>>>>> following the debian install tutorial to the tee I'm getting USB errors 
>>>>>> on 
>>>>>> weewx.
>>>>>>
>>>>>> ● weewx.service - WeeWX
>>>>>>      Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
>>>>>> preset: enabled)
>>>>>>      Active: active (running) since Tue 2026-03-10 11:51:36 EDT; 7min 
>>>>>> ago
>>>>>>        Docs: https://weewx.com/docs
>>>>>>    Main PID: 6217 (python3)
>>>>>>       Tasks: 2 (limit: 8004)
>>>>>>      Memory: 16.9M (peak: 17.3M)
>>>>>>         CPU: 327ms
>>>>>>      CGroup: /system.slice/weewx.service
>>>>>>              └─6217 python3 /usr/share/weewx/weewxd.py 
>>>>>> /etc/weewx/weewx.conf
>>>>>>
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> weewx.engine: 'pyephem' detected, extended almanac data is available
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> __main__: Starting up weewx version 5.3.1
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> weewx.manager: Starting backfill of daily summaries
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> weewx.manager: Empty database
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: INFO 
>>>>>> weewx.engine: Starting main packet loop.
>>>>>> Mar 10 11:57:37 weatherstation-ThinkCentre-M715q weewxd[6217]: ERROR 
>>>>>> weewx.drivers.acurite: Failed attempt 1 of 10 to get LOOP data: [Errno 
>>>>>> 5] 
>>>>>> Input/Output Error
>>>>>> Mar 10 11:58:07 weatherstation-ThinkCentre-M715q weewxd[6217]: ERROR 
>>>>>> weewx.drivers.acurite: Failed attempt 2 of 10 to get LOOP data: [Errno 
>>>>>> 5] 
>>>>>> Input/Output Error
>>>>>> Mar 10 11:58:37 weatherstation-ThinkCentre-M715q weewxd[6217]: ERROR 
>>>>>> weewx.drivers.acurite: Failed attempt 3 of 10 to get LOOP data: [Errno 
>>>>>> 5] 
>>>>>> Input/Output Error
>>>>>> Mar 10 11:59:07 weatherstation-ThinkCentre-M715q weewxd[6217]: ERROR 
>>>>>> weewx.drivers.acurite: Failed attempt 4 of 10 to get LOOP data: [Errno 
>>>>>> 5] 
>>>>>> Input/Output Error
>>>>>>
>>>>>> This is the error I'm getting.
>>>>>>
>>>>>> When I list my USB devices I do see the weather station.
>>>>>>
>>>>>> weatherstation@weatherstation-ThinkCentre-M715q:~$ lsusb
>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>>> Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
>>>>>> Bus 002 Device 003: ID 2357:012d TP-Link Archer T3U [Realtek 
>>>>>> RTL8812BU]
>>>>>> Bus 002 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
>>>>>> Bus 002 Device 005: ID 24c0:0003 Chaney Instrument Model 01036 
>>>>>> weather center
>>>>>> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>>>>
>>>>>> Oddly enough my weather station is not a 01036 it is an 02064. Like 
>>>>>> stated this was working a day ago until the PC problems.
>>>>>>
>>>>>> When I put the USB devices as a tree this is what I see.
>>>>>>
>>>>>> lsusb -t
>>>>>> /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/1p, 
>>>>>> 480M
>>>>>> /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 
>>>>>> 480M
>>>>>>     |__ Port 001: Dev 005, If 0, Class=Human Interface Device, 
>>>>>> Driver=[none], 1.5M
>>>>>>     |__ Port 004: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
>>>>>>         |__ Port 001: Dev 003, If 0, Class=Vendor Specific Class, 
>>>>>> Driver=rtw88_8822bu, 480M
>>>>>>         |__ Port 003: Dev 004, If 0, Class=Human Interface Device, 
>>>>>> Driver=usbhid, 12M
>>>>>>         |__ Port 003: Dev 004, If 1, Class=Human Interface Device, 
>>>>>> Driver=usbhid, 12M
>>>>>> /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 
>>>>>> 5000M
>>>>>>
>>>>>> Also, the 02064 doesn't have the USB modes to select. This 
>>>>>> automatically ports to USB 4 I think per weewx hardware information. 
>>>>>> That 
>>>>>> will not be something I can change.
>>>>>>
>>>>>> Any guidance would be appreciated.
>>>>>> Thanks
>>>>>> Mike
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/4e2db14c-0af0-4684-8a1e-da75c77a3e64n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/4e2db14c-0af0-4684-8a1e-da75c77a3e64n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBHs%3DY5FutDxs2L89TxVWnv8JU39_C4rpsuDx2tt_2ARA%40mail.gmail.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBHs%3DY5FutDxs2L89TxVWnv8JU39_C4rpsuDx2tt_2ARA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> Peter Quinn
>>>>>> (415)794-2264
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/0f43d730-53d9-46a8-9375-c564c0d0f0d3n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/0f43d730-53d9-46a8-9375-c564c0d0f0d3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/d0a6d8d9-10bf-43ea-909a-6434adea9c26n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/d0a6d8d9-10bf-43ea-909a-6434adea9c26n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/26942ed5-672d-4970-b8b9-c4f5cf1f7545n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/26942ed5-672d-4970-b8b9-c4f5cf1f7545n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/0a528d2d-3230-4427-981b-f8f64f572839n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/0a528d2d-3230-4427-981b-f8f64f572839n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/fc51a438-3d62-4a36-91d4-0d2e1d998456n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/fc51a438-3d62-4a36-91d4-0d2e1d998456n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>>
>>>>>> To view this discussion visit 
>>>>>> https://groups.google.com/d/msgid/weewx-user/42556611-bcb6-427d-b422-7791b4cda576n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/weewx-user/42556611-bcb6-427d-b422-7791b4cda576n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>>
>>> To view this discussion visit 
>>>> https://groups.google.com/d/msgid/weewx-user/20a903d8-8994-4fbd-bf5c-10e2b957db0bn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/20a903d8-8994-4fbd-bf5c-10e2b957db0bn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/307cfc21-19f9-4d0f-a662-0d8e42ab6f29n%40googlegroups.com.

Reply via email to