-
-
Notifications
You must be signed in to change notification settings - Fork 7
Stopped working #22
Comments
Which hardware platform are you running on? According to comments in #18 using an USB BT dongle may work better than the RPi internal BT, for instance. |
RPi 4. I figured the experiences regarding built-in BT are for RPi 3? |
Strangely it picked one datapoint in the middle of the night, then silent again. HA version now at 0.108.9. |
Similar issues with Intel NUC and BT dongle. I'm getting few datapoints very randomly. It works (kind of) few hours and then no datapoint what so ever for next 20-24 hours. This behavior keeps repeating... |
As some anecdata, I'm using a NUC and an Asus BT dongle, admittedly not hass-ruuvitag but the underlying https://github.com/akx/ruuvidriver library... aside from the NUC in general going into some sort of perätila now and then it works fine. |
BT interface is indeed ending up to some sort of weird state. Reseting BT interface seems to help for a while. Dongle I'm using is reported as "Broadcom Corp. BCM20702A0 Bluetooth 4.0". |
Maybe a stupid question, but does this have anything to do with the bluetooth tracker (being enabled or disabled)? |
I will answer to me myself ;) |
Another answer to myself. Had nothing to do with the tracker. BT is very sensitive distance and obstacles. Weirdly the results vary a lot when the signal is weak. |
Glad you found a solution! For what it's worth, I had a terrible time with my NUC's built-in BT and I bought the cheapest Asus dongle which turned out to work way better. |
Addon worked just fine for about an hour, then stopped working. Reboot, reinstall, reset settings, no effect. Doesn't log any devices, seems dead.
Meanwhile, the ruuvitag shows up just fine on other devices.
HassOS 3.13
Log:
The text was updated successfully, but these errors were encountered: