v0.6.8 - The HelpMeHelpYou release
This release is focussed on providing more useful diagnostics and quality-of-life improvements for fresh installs.
📈 SITREP
The Config dialog now shows a summary of how many Bluetooth scanners and Bluetooth devices Bermuda can see in the system, and how many of those have been seen in the last 10 seconds. This helps you know if the bluetooth backend is working and sending through data, which is something to which HA doesn't always give the best visibility. I've also added some help text in the "Configure Devices" setup page.
🔍 Diagnostics
Bermuda also now has a "Download Diagnostics" item in its options menu, which will give you a json file containing heaps of potentially useful diagnostic information, in json format. This data is "redacted" meaning it should not contain any of your MAC addresses. However, rather than just replacing them with asterisks or similar, it creates a per-file-consistent moniker for each address which will make troubleshooting easier by enabling cross-referencing between entries, without disclosing actual addresses. The idea is to create something safe for you to upload to a github issue that's still informative enough for me to analyse - but you might find it an excellent tool for your own troubleshooting as well.
🔢 Like a Version
Display of the integration version number should now be fixed, with the integration's version number (hopefully!) showing up in the main Bermuda page in HA. I won't know for sure if that works until github processes this release, but fingers crossed! 🤞🏼
📜 Signs of Wikiness
There have also been recent changes to the Wiki (yes, there's a wiki!) with advice on how to keep database sizes down and some initial guidance on troubleshooting.
🆘 Call for help
A few people have experienced serious performance issues unrelated to the recent async changes. At this stage I think that another integration is creating tens of thousands of "new" bluetooth records in HA's backend, and this is causing those systems to get bogged down as Bermuda tries to process them all. In one case, over 60 thousand devices were showing up - Bermuda automatically purges so it only keeps about a thousand of the most recent entries, but these entries kept being flagged up as new.
If you've experienced something similar, or might have an idea of which integration(s) might be causing this I'd love to hear from you so I might try and replicate the issue locally. #234
Ch-ch-ch-Changes
- feat: Diagnonstics and Redaction support @agittins (#239)
- feat: Show active device and scanner count in configure @agittins (#240)
- chore: fix versioning in release zip and HACS settings @agittins (#244)
- feat: Add full bt-manager data to diagnostics, with redactions @agittins (#245)
📦 Dependencies
- chore(deps): update pip requirement from <24.1,>=23.2.1 to >=24.1.1,<24.2 @dependabot (#224)
- chore(deps): bump ruff from 0.4.8 to 0.5.0 @dependabot (#223)
- chore(deps): bump pip from 24.0 to 24.1.1 in /.github/workflows @dependabot (#222)
- chore(deps): bump softprops/action-gh-release from 2.0.5 to 2.0.6 @dependabot (#217)
- chore(deps): bump flake8 from 7.0.0 to 7.1.0 in /.github/workflows @dependabot (#216)
- chore(deps): bump ruff from 0.5.0 to 0.5.1 @dependabot (#231)
- chore(deps): bump pip from 24.1.1 to 24.1.2 in /.github/workflows @dependabot (#230)
- chore(deps): bump actions/setup-python from 5.1.0 to 5.1.1 @dependabot (#237)
- chore(deps): bump ruff from 0.5.1 to 0.5.2 @dependabot (#242)
