HA 2025.2.0 requires Bermuda 0.7.3 or later!

[agittins]

A quick note that the new HA release of 2025.2.0 has some nice improvements in the bluetooth integration, which older versions of Bermuda will freak out about and you'll find your scanners not picking up the right Areas for devices (this is mainly because Bermuda needs to use non-API methods to get the data it needs, so the HA project has no way of knowing if they'll make changes that break Bermuda).

So... if you're running HA 2025.2.0 or later, make sure you update to Bermuda 0.7.3 or later for the full avocado on toast experience.

Thanks to @tbrasser for the heads-up on this, as well as @jkpe and @bmatheny for their input - much appreciated! 😁

[Wheemer]

Really appreciate the work you guys are doing on this. It's been a pleasure to be able to consolidate things and not have separate espresense devices needed.

[Tvojm100]

Hi, is the combination of this HA version and the Bermuda version the only fix for 'unknown' area?

I have the latest Bermuda integration, but assuming this alone would not help the issue, as I still get the unknown state the majority of time.

Unfortunately I am unable to upgrade to this version of HA, as it breaks a functionality of an unrelated integration.

[benniPe]

Hi,
I have running HA 2025.2.0 and Bermuda 0.7.3 but i still get the "unknown" issue.

When restart HA it works for just a few minutes

[agittins]

Newer versions of Bermuda will work ok on any currently available release of HA from mid 2024 onwards. Which is to say, the bugs in current Bermuda releases are due to Bermuda alone, not to HA 😅

It's possible that you are getting "unknown" because one or more of your proxies (or, especially, a local bt adaptor) don't have an area assigned to them. The next version of Bermuda has changes that will raise a repair issue and also set the area sensor to "invalid area - scannername" to make it clear why it's happening if it detects that to be the case.

The current RC (release candidate, sort of like a beta) of Bermuda includes these changes already, along with fixes and improvements to the smoothing which will improve the "twitchiness" of area switching. I'm expecting to make a full release in the next several hours to include all of this 👍🏼

@benniPe I expect that this next release will directly fix your issue, as your case (sensor works for a bit, then goes unknown and stays that way until a restart) is exactly one of the bugs that is fixed.

@Tvojm100 if the next release doesn't resolve your issue (or prompt you how to repair it) please raise an issue, and include a "download diagnostics" and a screenshot of a recent history (Go into the history tool on the sidebar, choose "+add device" and choose a Bermuda device. You can narrow the time range to the interesting bits. The screenshot only needs to include the top two graphs which should be the bars showing area, home/away etc and the graph showing distances). That should help me work out what might be going on for you - but hopefully this next release will sort it 👍🏽

[Tvojm100]

@agittins

Thanks for the thorough reply.

The one thing I did not previously adjust was the BLE beacon settings on my phone (Samsung S24 Plus). I am using the HA companion app and increased the 'advertise mode' to 3Hz and 'transmit power' from ultra low to low.

This seemed to have made a significant difference. The only unknowns now, 'seem' to be where I am out of range from any scanner.

I am obviously sacrificing some battery by doing the above, so wondering if this is the most optimal configuration overall (?). I'll look out for beta/RC/other releases.

I have standard ESP32 WROOM as scanners (not sure how to identify the exact model).

Wondering if others with the same phone are experiencing this? Mind you, I get the same results for the Samsung S21 too. Again, changing the companion app settings, seems to have vastly improved area detection.

One thing that would be useful is being able to limit the max area range value per scanner and not just globally. Some of my rooms are close to each and the scanners are placed as far apart as can be, but it can sometimes wrongly detect which I am area I am in.

[benniPe]

The new HA 2025.2.1 is running and there is no "unknown" issue anymore....👍🏻😄

Im happy
@agittins thank you very much