2.4.1a1

🚨 Experimental Alpha Build 🚨

Please note that this is an experimental alpha build, intended exclusively for development purposes. It is not suitable for general use. Installing this version without explicit instruction from a developer could lead to malfunctions or issues with your alarm system. Proceed with caution and at your own risk.

DO NOT INSTALL this version unless you have been specifically instructed to do so by a developer.

By proceeding to download or install this alpha release, you acknowledge and accept the risks associated with an experimental build.

Full Changelog: v2.4.0...v2.4.1a1

2.4.0

What's Changed

Features

• Add connection status binary sensor to provide feedback in case of a disconnection (#151)
• Add update_state service that can be used in Lovelace dashboard or in automations, to force alarm updates when scan interval is used (#165)
• Add support for Python 3.12 (#158)

Bugfixes

• The integration keeps the previous known state, to prevent update blips when main unit is disconnected (#150)
• Discard Cloud APIs empty states when main unit connection resets (#153)
• Use async_update_entry when handling config entries (#157)
• Avoid state updates while arming or disarming the alarm (#155)
• Prevent code sensitive data to be logged from services debug logs (#162)
• Automatically refresh integration access token if it's expired (#164)

Dependencies

• Update econnect-python version to 0.12.0 (#167)

Developer Experience

• Disable DEBUG log level when pytest is launched with --verbose argument (#149)
• Use the right Python executable in tox configuration (#163)

Discover the full changeset and the release milestone.

2.3.0

What's Changed

Documentation

• Improved HomeKit configuration docs (#142) - thanks @andr3a88 !

Features

• CommandError exceptions raised from e-Connect Cloud APIs are now handled and logged (#133)
• AlarmDevice queries the panel details. At the moment these details are not exposed to users but they will be available in one of the next minor releases (#135)
• Locking operations (arm and disarm) now expects a userId parameter if the main unit requires it to complete the login. Main units without this requirement are not affected by this change (#136)
• It's now possible to arm and disarm sectors using arm_sectors and disarm_sectors services. Users can pass a single sector or a list of sectors regardless of the modes defined in the configuration (#144)

Bugfixes

• econnect-python logger can now be enabled from the UI using the usual HA debugging process (#127)
• Update deprecated constants that will be removed in future HA versions (2025.1) (#128)
• domain field in the installation flow, is now required and pre-filled with default for users that don't have a vendor domain (#129)
• Forcing a full update after a reconnection is not considered an error anymore, and is now logged as DEBUG (#130)
• CONFIG_SCHEMA is updated to accept internal configurations from config entries (#131)
• experimental settings are enabled again as internal configurations (#138)
• Disarm deactivates only currently activated sectors. This change adds support to users with limited permissions (e.g. multi-areas) (#137)
• Added missing icons for arm_sectors and disarm_sectors services (#145)

Dependencies

• Add async_timeout package used in the AlarmCoordinator (#118)
• Update econnect-python to version 0.11.0 (#132, #136)

Developer Experience

• Include init script to initialize a working development environment with a specific HA version. This change simplifies onboarding for external contributors (#125)
• Update pre-commit hooks versions (#126)
• Use new InvalidData exception imported from newer versions of HA testing platform (#143)

Experimental

These features are incomplete and subject to changes in any versions, so don't use them unless explicitly asked. If you'd like to use an experimental feature, reach out us to better describe your use case!

• HA Alarm Panel can be configured to control only a subset of sectors (#146)

New Contributors

We'd like to extend our gratitude to our new contributors that made their first contribution 🎉

• @andr3a88 in #142

Discover the full changeset and the release milestone.

2.2.1

What's Changed

Bugfixes

• Prevent a Configuration Error when inputs, outputs and/or sectors strings are not synchronized with the cloud (palazzem/econnect-python#132)

Dependencies

• Update econnect-python to version 0.9.1 (#116)

Discover the full changeset and the release milestone.

2.2.0

What's Changed

Bugfixes

• States transition between disarmed and any other state, doesn't glitch anymore to "Armed Away" for a few seconds (palazzem/econnect-python#128)

Features

• Binary sensors alarm_led, tamper_led, and inputs_led are now treated as sensors since they exhibit multiple states: not ready, ready, and partially ready (#99)
• A multi-select UI component now facilitates the sectors configuration (#101)
• The Arm Away state can now be configured via the options configuration page. This update is backward compatible, so if no action is taken, all sectors will be armed as usual (#107).
• The integration collects outputs status using the new entities OutputSwitch (#50)
• It is now possible to activate or deactivate outputs using the new entities OutputSwitch (#110)

Developer Experience

• Provide a Docker compose configuration to spin-up a HA container to test the integration directly with no configurations! (#111)

Testing Improvements

• Enabled socket access for responses version 0.24+ for compatibility (#104).
• Replaced the custom MockConfigEntry with the official hass.MockConfigEntry (#105).
• Increased test coverage for config exceptions and refactored ConfigFlow tests (#102).
• Enhanced test coverage for the OptionsFlow handler (#106).

Dependencies

• Update econnect-python to version 0.9.0 (#113)

Discover the full changeset and the release milestone.

2.1.0

What's Changed

In this version we spent a lot of time refactoring how the integration polling works, and how binary sensors are created. The main goal was to have a way better structure to speed-up features development.

Furthermore, we moved our code coverage from 71% to 86%! This is an important step forward to achieve better integration stability! 🎉

Bugfixes

• Build system now uploads only HACS files to prevent downloading errors (#78)
• Use alerts last_id while polling, to get alerts real-time updates (#97)

Features

• Update econnect-python to 0.8.0 (#92)
• Listed InputSensors entities include only inputs in use (#88)
• Listed SectorSensors entities include only sectors in use (#89)
• Add get_status to retrieve sensor status (#84)

Refactoring

• Split binary sensors in their own entities (#69)
• Add _inventory in AlarmDevice to store all retrieved data (#71)
• Create a view to interact with _inventory (#72)
• Create AlarmCoordinator to separate HA boilerplate from the fetching logic (#74)
• Add device.item to query the inventory (#79)

Testing Improvements

• Initialize automatically alarm_device fixture (#83)
• Add missing tests for binary sensors (#90)
• Write xml code coverage for better coveralls support (#91)
• Ensure unique ids for AlertSensor don't change upon econnect-python changes to avoid breaking changes in the future (#93)

Experimental

These are experimental features, so you should not use them in your production environment.

• Add force_update as experimental setting in YAML configuration (#85)
• Namespace experimental settings under experimental key (#86)

Explore the full changeset and the release milestone.

2.0.1

What's Changed

This hotfix resolves a connection issues when, after a while, the integration stops receiving updates. We highly recommend to update to this version.

Bugfixes

• Force updates when the connection is unstable, so that collectors IDs are reset everytime an update fails (#73)

Explore the full changeset and the release milestone.

2.0.0

What's Changed

This release introduces a breaking change that updates the entity_id for all collected sensors, sectors, and metrics. This alteration became necessary because there was no namespacing in our default Entity IDs, leading to potential future clashes.

If you are upgrading from a 1.0.0 version to 2.x, you must follow our migration guidelines. If not, simply install the integration by downloading it (refer to the bottom of the release notes) or using a HACS custom repository.

Bugfixes

• Use slugify function to generate the entity name as HA expects. This aligns the integration with the latest HA guidelines. (#52)
• Binary sensors and control panels generates a valid Entity ID with a human readable name (#54)

Features

• Add an optional prefix to the control panel and binary sensor entities, so that 2+ systems can be supported in the same HA installation. Fallback to username if not provided (#49) - thanks @xtimmy86x !
• Add system global states to monitor the central unit (#57)
• Support a configurable scan interval to reduce data usage in mobile networks (#58)

Documentation

• Provide documentation to configure this integration in HomeKit (#56, #62) - thanks @syth87 !

Build Process

• All packages are built during the release action instead of using artifacts (#67)

Breaking Changes

• Transitioned the integration to the econnect_metronet namespace. All sensors, sectors, and metrics now have the prefix binary_sensor.econnect_metronet_*. (#64)

New Contributors

We'd like to extend our gratitude to our new contributors that made their first contribution 🎉

• @xtimmy86x
• @syth87

Explore the full changeset and the release milestone.

1.0.0

What's Changed

This release introduces a breaking change that updates the entity_id for all collected sensors, sectors, and metrics. This alteration became necessary because there was no namespacing in our default Entity IDs, leading to potential future clashes.

If you are upgrading from a 0.x version to 1.0.0+, you must follow our migration guidelines. If not, simply install the integration by downloading it (refer to the bottom of the release notes) or use a HACS custom repository.

Bugfixes

• Fixed a bug where transitioning from one state to another (e.g., Home -> Vacation) would update the UI to the "Away" state. (#32)
• Users can now deactivate previously enabled alarm modes (Vacation, Home, Night) by altering the configuration in the integration options page. (#35)
• The build runner now offers a zip package instead of a tar.gz, making the installation on Windows easier. (#39)

Features

• Added HACS support. Now, the integration can be installed using a HACS custom repository. Special thanks to @gervaso! (#31)
• Introduced support for IESS Metronet systems. During installation, you can now choose your system. (#26)
• Incorporated the AlarmDevice component to manage all state transitions and caching. (#28)
• Added "Vacation" mode support. (#34)
• Included Italian translations. (#42)

Documentation

• Refined the installation form and documentation for clearer explanations regarding the domain setting. (#43)
• Updated Elmo/IESS references in the README.md with the latest screenshots. (#46)

Breaking Changes

• Transitioned the integration to the elmo_iess_alarm namespace. All sensors, sectors, and metrics now have the prefix binary_sensor.elmo_iess_alarm_*. (#44)

New Contributors

We'd like to extend our gratitude to a new contributor!

• @gervaso made their inaugural contribution in #31.

Explore the full changeset and the release milestone.

0.2.0

What's Changed

Bugfixes

• _get_descriptions() call is executed in an executor job (6cc75ac)
• device.update() is called after a successful connection (d84bb73)
• Included integration version in the manifest.json (cafb1b4)

Documentation

• Added installation instructions to README

Community Improvements

• Integrated hassfest GitHub actions for integration validation. This ensures the integration is always up to date with the latest HA version (#16)
• Implemented pre-commit hooks for linting and static analysis (#11)
• Added tox for project test matrix (#12)
• Introduced GitHub templates for bug reports, features, and pull requests (#13)
• Provided contribution guidelines (#14)
• Set up GitHub actions for linting, testing, and code coverage CI (#15)
• Refined package structure to enhance testing and building (#10)

Read the full changeset and the release milestone.