-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to work on second load #2669
Comments
This is unlikely an rtl_433 bug. You didn't explain what rtl_433 version you are running (if not git master please update and try again). You didn't explain if you removed/reinserted and if that fixes it, if there's anythign in syslog, and what happens when you use other programs with the dongle. |
I'm running version 22.11 which is the latest release on nixos, I can try master to see if that fixes it. The dongle is in the attic, I don't want to plug it in and out everytime I restart the app. Reboot fixes it so its not a connectivity issue for sure. journalctl gives back this after the app restart:
I recompiled master and tried it again: Got:
which is different than what I was getting before with 22.11. So I rebooted the os again. back to:
Then I restarted the app one more time and:
back to working ??? Can I always make it do the "resetting device ..." step? |
This seems like you have a flaky device, or there is buggy kernel/firmware code. It doesn't seem like an rtl_433 bug. This might be raspberrypi/linux#3060 |
We have seen problems like this before, but we never found a solution. It just seems some devices glitch and only a bus reset gets them back. There are various usb_reset tools if you want something short of a full power-cycle. |
I have had this same issue, and for it happens on Ubuntu 22.04, but not Ubuntu 23.10 and 24.04. Tested with multiple sticks and multiple machines. I now have all machines upgraded, and problem has not returned. |
Using nixos with the following device:
I get the following errors after closing it and running it a second time:
The text was updated successfully, but these errors were encountered: