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

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