Version 2.3.2

Bugfixes

• Made code and integration compatible with Home Assistant 2024.10
• Thanks @zAAmpie

Please Note
I no longer have an Olarm device connected to my alarm system, so will not be able to test this release.

Version 2.3.1

Bugfixes
Made code and integration compatibe with Home Assistant 2024.6
Fixed config_flow (ui setup) not working for some users)

Version 2.3.0

Improvements:
Added static entity ID to resolve the issue if a zone is renamed, that there is a new sensor created.

Bugfixes
Fix for Home Assistant 2024.6 where it will not start:

Please note:
Please note that there now may not be the correct info for each Olarm Service under the services tab. There will also now no longer be the fill example data.

Version 2.2.9

Improvements:
Added static entity ID to resolve the issue if a zone is renamed, that there is a new sensor created.

Version 2.2.8

Bugfixes:
Improved API limiter config.

Added Support
Now supports minor_version added in Home-Assistant version 2024.1.

Version 2.2.6

Should fix JSON not selializable when trying to install.
Follow zone number as unique_id and not zone name. (This allows the zones to be renamed in the Olarm App or on the ALarm panel and have the same entity id.

Version 2.2.5

Added sensor to show which zone triggered the alarm.
Full Changelog: version2.2.4...version2.2.5

Version 2.2.4

Added triggering the armed response radio via Home Assistant if the radio is triggered via a PGM.
Full Changelog: version2.2.3...version2.2.4

Version 2.2.3

Fixed icons to use sensor types first then name.

What's Changed

• Fixed icons to use sensor type first, then name by @Cha0s2nd in #74

New Contributors

• @Cha0s2nd made their first contribution in #74

Full Changelog: version2.2.2...version2.2.3

version2.2.2

Bugfixes:

• Fixed the Alarm Control Panel not updating its state after the coordinator update.