You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing a lot of unavailable time on the b-parasite sensors integrated in Home Assistant:
I am using the latest ble firmware in the b-parasite (as of 2024/04/20 and without any change to default settings). An ESP32 running bluetooth_proxy with ESPHome 2024.4.0 (also without any changes to default settings) and Home Assistant 2024.4.3. The b-parasite and the ESP32 are less than 2m apart so there should not be any transmission problems.
I see a similar behaviour reported in #98, but it seems to be fixed in later HA versions but I am running the latest version and still seeing this. I have to say that another b-parasite running an old firmware with BTHOME v1 paired with another ESP32 does not suffer this problem at all, and it has been running strong for many months.
Anything I can setup/change to mitigate this unavailable times? regards,
The text was updated successfully, but these errors were encountered:
Hi,
I am experiencing a lot of unavailable time on the b-parasite sensors integrated in Home Assistant:
I am using the latest ble firmware in the b-parasite (as of 2024/04/20 and without any change to default settings). An ESP32 running bluetooth_proxy with ESPHome 2024.4.0 (also without any changes to default settings) and Home Assistant 2024.4.3. The b-parasite and the ESP32 are less than 2m apart so there should not be any transmission problems.
I see a similar behaviour reported in #98, but it seems to be fixed in later HA versions but I am running the latest version and still seeing this. I have to say that another b-parasite running an old firmware with BTHOME v1 paired with another ESP32 does not suffer this problem at all, and it has been running strong for many months.
Anything I can setup/change to mitigate this unavailable times? regards,
The text was updated successfully, but these errors were encountered: