patrick, 0) what happens when you run when the reset is commented out?
1) do you have some other software running that is claiming the station? what does 'ps aux' tell you? 2) are you running weewx as root? 3) is the log from running weewx directly or as a daemon? 4) is the log you posted with the reset or without the reset in te923.py? (it looks like it is with reset) 5) please post the following info: os, udev, libusb, pyusb *uname -a*Linux feta 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux *cat /etc/issue*Raspbian GNU/Linux 7 *dpkg -l | grep udev*ii libgudev-1.0-0:armhf 175-7.2 armhf GObject-based wrapper library for libudev ii libudev0:armhf 175-7.2 armhf libudev shared library ii udev 175-7.2 armhf /dev/ and hotplug management daemon *dpkg -l | grep libusb*ii libusb-0.1-4:armhf 2:0.1.12-20+nmu1 armhf userspace USB programming library ii libusb-1.0-0:armhf 2:1.0.11-1 armhf userspace USB programming library *dpkg -l | grep python-usb*ii python-usb 0.4.3-1 armhf USB interface for Python try forcing the kernel to release the station: option 1: unload the hid kernel module. *warning!* this will make any mouse, keyboard, or other usb hid device stop functioning! sudo rmmod usbhid option 2: try to get usbhid to release just the station sudo bash -c "echo -n XXX > /sys/bus/usb/drivers/usbhid/unbind" where XXX is something like 2-1:1.0 - it is the usb device number for your station. you can see them all at /sys/bus/usb/devices. the easiest way to figure out the number for your station is to ls /sys/bus/usb/devices before your station is plugged in, then again after you plug in the station. after you do either option 1 or option 2, start weewx and see if you still get the 'device or resource busy' failure. the 'device or resource busy' message typically indicates one of these conditions: a) there is another process running that has claimed the usb device, e.g., another instance of weewx or some modem software b) the kernel has claimed the device, typically via usbhid, and the calls to release it in the driver code are not working c) the user running weewx does not have permission to claim the usb device (more often this is 'permission denied') d) the usb reset is invoked in the driver after claiming the interface, which causes the driver to release its claim of the interface m -- 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. For more options, visit https://groups.google.com/d/optout.