-
Notifications
You must be signed in to change notification settings - Fork 60
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
RuuviCollector gives up after BT HW error #42
Comments
What hardware & OS are you using? And when this happens, can you see a hcitool and a hcidump process running in addition to the collector process? |
I’m running Raspbian 9.11 on Raspberry Pi 3. The situation is not easy to catch as it happens only once a week or so. But I'll add a process logger to investigate the situation. |
Finally catched this one. Here's output from my ruuvi restart script:
|
Hmm, so it seems neither hcitool nor hcidump crashes/exits when this happens, which makes it hard to reliably detect this error from within the collector as I don't want to add dependencies to dmesg as normal users can't access it on a properly secured system.. either way that'd be a workaround for a problem somewhere else; the real solution would be figuring out why the bluetooth gets those hardware errors. One possible cause for that is a bad power supply that doesn't supply stable enough voltage, as there's almost no voltage regulation on the RPi itself |
Hmm, ok. I could switch to official RP power source and see if this still happens. |
Every time this appears in dmesg, RuuviCollector stops collecting data:
[ke marras 27 20:51:50 2019] Bluetooth: hci0: hardware error 0x43
. The process itself does not crash, it is still there but nothing appears in logs about the situation.The text was updated successfully, but these errors were encountered: