Version 2.1.1

Bugfixes:

• Fixed error caused by integration not being able to be set up.
• Removed Binary sensors that caused redundant API calls and thus booked the API key.
• Added method to update API key in the Options / Configure instead of having to redo the setup.

Removals:

• The binary sensors for the bypass states have been removed and replaced with switches.

Version 2.1.0

Bugfixes:

• Fixed power sensor bug created in version 2.0.9.

Version 2.0.9

Bugfixes:

• Fixed the error some users had with the double setup/ config entry issue.

Features:

• Added switches for bypassing zones and toggling PGM's that are set to latch.

For full documentation and new features check the README

Version 2.0.8

Bugfixes:

• Fixed the error some users had with the PGM's when it was not set up in the Olarm App.

Version 2.0.7

Release changes

• Improved logging.
• Improved error handling
• Does not flood logs when not in debug mode.

Version 2.0.6

Features

1. Added description to config flow.

Version 2.0.4

Bugfixes:

1. Fixed issue where PGM would break the entire config, due to setup reporting more PGMs than there actually are on the alarm.
2. Fixed an Issue where some users would not see a code popup for their alarm actions.

Full Changelog: version.2.0.3...version2.0.4

Version 2.0.3

Bugfixes:

1. Fixed Keyerror if the user did not set up up the alarm code as per instructions.
2. Fixed duplicate sensors if config for Zone Numbers in the Olarm App has not been configured properly.

Version 2.0.2

Bugfixes:

1. Fixed DictKeyError when checking config entry.
2. Fixed errors due to space in the device name.

Version 2.0.0

Bugfixes:

1. Fixed DictKeyError inheriting from the wrong parent class.
2. Added extra checks to prevent wrongly configured PGMs and utility keys to break the integration.
3. Fixed where DeviceType would break integration if not set in the Olarm App.

Features added:

1. Ability to change and configure the integration without the need to redo the setup. (Note that you will probably need to restart or reload the integration afterwards for the new settings to take effect.