Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Stopped working #22

Open
dimangi opened this issue Apr 21, 2020 · 10 comments
Open

Stopped working #22

dimangi opened this issue Apr 21, 2020 · 10 comments

Comments

@dimangi
Copy link

dimangi commented Apr 21, 2020

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:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
This is hassio-ruuvitag 0.3.0, terrrrrrrve
@akx
Copy link
Owner

akx commented Apr 21, 2020

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.

@dimangi
Copy link
Author

dimangi commented Apr 21, 2020

RPi 4. I figured the experiences regarding built-in BT are for RPi 3?

@dimangi
Copy link
Author

dimangi commented Apr 25, 2020

Strangely it picked one datapoint in the middle of the night, then silent again. HA version now at 0.108.9.
I’m sort of waiting if an update or something fixes it. Could get a BT dongle, if it was a sure resolution.

@tikkav
Copy link

tikkav commented Apr 25, 2020

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...

@akx
Copy link
Owner

akx commented Apr 25, 2020

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.

@tikkav
Copy link

tikkav commented Apr 26, 2020

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".

@dimangi
Copy link
Author

dimangi commented May 5, 2020

Maybe a stupid question, but does this have anything to do with the bluetooth tracker (being enabled or disabled)?
Bluetooth seems to function, at least the bluetoothctl on ssh. Finds stuff 😊

@dimangi
Copy link
Author

dimangi commented May 13, 2020

Maybe a stupid question, but does this have anything to do with the bluetooth tracker (being enabled or disabled)?
Bluetooth seems to function, at least the bluetoothctl on ssh. Finds stuff 😊

I will answer to me myself ;)
Not sure if this was stupid question or if there is supposed to be a link. But can see that enabling BT tracker seems to make a huge difference. From random readings, I'm now getting consistent readings.

@dimangi
Copy link
Author

dimangi commented Jan 7, 2021

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.
Final resolution in my case was getting a USB extension cable, BT dongle, and disabling the onboard BT chip. Just to get the bluetooth radio closer and behind less obstacles like furniture. One wall seems okay with the dongle I have.

@akx
Copy link
Owner

akx commented Jan 8, 2021

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants