agittins / agittins/bermuda

Some beacons jumping a lot between working and "Unknown"

Abierto
#668 13 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
2k
Forks
70
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

iPhones, Apple watches (Private BLE Device) as well as Tesla key seems to work well and predictably.

But now I got three Blue Charm beacons to track the locations of my trash can and they constantly jump between found and "Unknown".

All three trackers are next to each other (on the trashcans). I have a total of 5 ESPhomes with bluetooth proxy.

One device that bothers me the most is "hpwh", it is the closest and shows around 40ft most of the time but shortly after goes to "Unknown".

I have tried increasing the Devtracker timeout to 120s and increasing the Bluecharm's output power to 8dBm ... nothing changed in terms of reliability.

I understand that there are weak signals and varying RSSI values wouldn't surprise me as much, but what is really causing the BLE proxies just jumping to "Unknown" all the time?

Here's an example

Image

In this example you can see that Trashcan Blue is "found" by hpwh which is the closest one but Trashcan Black and Trashcan Green are both as "Unknown". Trashcan Black has instead "vue-utility" which is really far away.

A few seconds later everything will randomly flip again. Note that the trashcans are right next to each other.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.