3.3.1

What's Changed

• Fixed an issue with new battery note creation with Python 3.14 - thanks @rtasarz
• Updated German translations via Crowdin - thanks Fischermaen

❤️ Thanks for the huge amount of support shown, if you would like to show your support please

Full Changelog: 3.3.0...3.3.1

3.3.0

What's Changed

• Fixed an issue where entities were not created in HA 2026.2
• Added a new action check_battery_last_replaced where you can raise new battery_notes_battery_not_replaced events for devices that have not had their batteries replaced after a period of days - useful for critical devices that you want to replace annually.
• Check actions now support responses check_battery_last_replaced, check_battery_last_reported, and check_battery_low actions can all optionally return a response with the details as well as raising events. You can disable raising events within the actions if you prefer using responses for different scenarios. Default is to continue raising events so no changes to automations required.
  When Battery Notes was first created action responses did not exist and so events were the only way to use this functionality. I will continue supporting events but response variables gives other options if you prefer to handle the scheduling and actioning for reported devices in one automation.
• Updated Greek and German translations via Crowdin - thanks Thunderstrike116, Fischermaen, and aGr0pp

❤️ Thanks for the huge amount of support shown, if you would like to show your support please

Full Changelog: 3.2.5...3.3.0

3.2.5

What's Changed

• Fixed an issue updating the battery library that prevented discovery
• Removed auto complete on name fields so no more password manager prompts
• Updated Portuguese (Brazilian) and German translations via Crowdin - thanks Hiago and gorischek

❤️ Thanks for the huge amount of support shown, if you would like to show your support please

Full Changelog: 3.2.2...3.2.5

3.2.4

What's Changed

• Fixed an issue updating the battery library that prevented discovery
• Removed auto complete on name fields so no more password manager prompts
• Updated Portuguese (Brazilian) and German translations via Crowdin - thanks Hiago and gorischek

❤️ Thanks for the huge amount of support shown, if you would like to show your support please

Full Changelog: 3.2.2...3.2.4

3.2.3

What's Changed

• Fixed an issue updating the battery library that prevented discovery
• Removed auto complete on name fields so no more password manager prompts
• Updated Portuguese, Brazilian translations via Crowdin - thanks Hiago

❤️ Thanks for the huge amount of support shown, if you would like to show your support please

Full Changelog: 3.2.2...3.2.3

3.2.2

2025 in review

This year saw
📦 15 production releases.
🆕 598 new devices added to the library, thanks for all the contributions.
⬇️ Approximately 28k users of Battery Notes based on downloads.
❤️ 17 supporters across all my open source projects totalling £101.97, thank you all for your support.

I've lots more planned for 2026, if you would like to support my work then please

What's Changed

• Add a new battery percentage template within advanced configuration for a battery note, allowing you to create a battery plus sensor for devices with voltages, binary or textual sensors. If you previously created template helpers for these you can now remove them and add the template directly for easier maintenance. #3552
  The existing battery low template should be considered as legacy, it can still be used if you want more control over when a device is considered low, but the new percentage template will trigger low when it reaches the set threshold so it is not necessary to provide both.
  Example of voltage sensor template with a maximum capacity of 3 volts
  {{ (states('sensor.my_sensor_voltage')|float(0) / 3 * 100) | round(0) }}
  Example of binary low sensor template, returning either 100% or 9%
  {{ 9 if states('binary_sensor.my_sensor_low') == true else 100 }}

• Move some settings for battery notes into a new advanced section.

• Add the name of the battery note device at the top of the second step summary when creating new battery notes. #4081

• Set the last reported when an update is received on devices with only a binary battery low sensor. #3378

• Updated Greek, German, and Dutch translations via CrowdIn - thanks Thunderstrike116, StringSphere, and Hmmbob

Full Changelog: 3.1.0...3.2.2

3.2.1

What's Changed

• Add a new battery percentage template within advanced configuration for a battery note, allowing you to create a battery plus sensor for devices with voltages, binary or textual sensors. If you previously created template helpers for these you can now remove them and add the template directly for easier maintenance. #3552
  The existing battery low template should be considered as legacy, it can still be used if you want more control over when a device is considered low and will not be removed, but the new percentage template will trigger low when it reaches the set threshold so it is not necessary to provide both.
  Example of voltage sensor template with a maximum capacity of 3 volts
  {{ (states('sensor.my_sensor_voltage')|float(0) / 3 * 100) | round(0) }}
  Example of binary low sensor template, returning either 100% or 9%
  {{ 9 if states('binary_sensor.my_sensor_low') == true else 100 }}

• Move some settings for battery notes into a new advanced section.

• Add the name of the battery note device at the top of the second step summary when creating new battery notes. #4081

• Set the last reported when an update is received on devices with only a binary battery low sensor. #3378

• Updated Greek, German, and Dutch translations via CrowdIn - thanks Thunderstrike116, StringSphere, and Hmmbob

Full Changelog: 3.1.0...3.2.1

3.2.0

What's Changed

• Add a new battery percentage template within advanced configuration for a battery note, allowing you to create a battery plus sensor for devices with voltages, binary or textual sensors. If you previously created template helpers for these you can now remove them and add the template directly for easier maintenance. #3552
  The existing battery low template should be considered as legacy, it can still be used if you want more control over when a device is considered low and will not be removed, but the new percentage template will trigger low when it reaches the set threshold so it is not necessary to provide both.
  Example of voltage sensor template with a maximum capacity of 3 volts
  {{ (states('sensor.my_sensor_voltage')|float(0) / 3 * 100) | round(0) }}
  Example of binary low sensor template, returning either 100% or 9%
  {{ 9 if states('binary_sensor.my_sensor_low') == true else 100 }}

• Move some settings for battery notes into a new advanced section.

• Add the name of the battery note device at the top of the second step summary when creating new battery notes. #4081

• Set the last reported when an update is received on devices with only a binary battery low sensor. #3378

• Updated Greek, German, and Dutch translations via CrowdIn - thanks Thunderstrike116, StringSphere, and Hmmbob

Full Changelog: 3.1.0...3.2.0

3.1.0

What's Changed

• Rate limit battery_reported updates to once per hour, if the battery level has not changed. If you had a device that was updating frequently it would add a lot of additional data to the recorder.
• Add the integration name onto discovered devices panels, making identification easier.
• Add a fallback on retrieving the library updates if Cloudflare R2 storage fails for any reason.
• Updated Polish and Italian translations via Crowdin, thanks mrwogu and lorlis respectively.

Full Changelog: 3.0.4...3.1.0

3.0.4

What’s Changed

⚠️ Important
The way Battery Notes associate with a device has had to change due to a change within Home Assistant.
You will still see your battery note entities within the device page and they work exactly the same, but you will not see Battery Notes listed in the integrations at the top.
You can edit a battery note for a device by going into the Battery Notes integration, choosing the device and configuring it there.
A Battery Note no longer has entities itself, but you can still see all the entities, grouped by device, by clicking on the xx entities just under the Battery Notes service within the integration page.

If you are using the offical blueprints you will need to reimport them to be able to modify device filters due to this change, new blueprints available here. or just click the three dots and reimport against each Battery Notes blueprint from the settings/blueprints screen.

Global settings are now configurable via the UI, the configuration.yaml for battery notes is no longer required and is migrated into the integrations settings. You will get a repair raised once this happens and can manually remove the battery_notes section from configuration.yaml.

New features
The Device name attribute will now be the name set within the battery note rather than the source device/entity. This allows you to override the name making it more meaningful for notifications.

When creating new entity associated battery notes the battery note title will be device name - entity name, aiding easier identification.

Improved Home Assistant start up speed, Battery Notes will now wait before performing discovery on startup.

Bug fixes
Fixed discovery issue with certain library entries with multiple hardware versions.
Fix issue deleting a battery note after deleting its source.

Other changes
Migrate to UV for dev environment - thanks to @EVWorth for a lot of effort on this.
Updated Greek translations - thanks Thunderstrike116 via Crowdin