0.12.0

What's Changed

Features

• Main unit disconnections are detected and DeviceDisconnectedError exception is raised (#147, #148)
• Add support for Python 3.12 (#150)

Read the full changeset and the release milestone.

0.11.0

What's Changed

Features

• Add client.query(q.PANEL) API to retrieve panel details (#140)
• lock() accepts an optional userId to support models that require both the userId and the code (#142)

Bugfixes

• Added debug logs for arm/disarm/lock/unlock actions to simplify the triaging (#144)

Read the full changeset and the release milestone.

0.10.0

What's Changed

Bugfixes

• (#137): InvalidSector and InvalidInput exceptions are replaced by CommandError. This exception is raised when the client fails to arm/disarm the system, or make any time of change. When the system fails, the client logs an error including the response from the API. This solves the issue of assuming what type of error it was.

Testing / Development

• (#136): pre-commit hooks are updated to their latest versions

Read the full changeset and the release milestone.

0.9.2

What's Changed

Bugfixes

• Raise InvalidToken if the token expires while using the lock() method (#134)

Read the full changeset and the release milestone.

0.9.1

What's Changed

Bugfixes

• Prevent a KeyError when inputs, outputs and/or sectors strings are not synchronized with the cloud (#132)

Read the full changeset and the release milestone.

0.9.0

What's Changed

Features

• Add query.OUTPUTS to collect outputs status (#127)
• Add client API to activate or deactivate a given output (#129)
• Parse additional API fields when q.OUTPUTS query is done. This change removes unused keys from q.SECTORS query (#130)

Bugfixes

• Arm and disarm multiple sectors with a single request instead of making one request per sector (#128)

Read the full changeset and the release milestone.

0.8.1

What's Changed

Bugfixes

• Add last_id while polling alerts to get real-time updates (#125)

Read the full changeset and the release milestone.

0.8.0

What's Changed

Client/API

• Add query.ALERTS to query the system via a unified API. You can now query any data just by using query() (#118)
• Response for query.ALERTS queries is now the same as INPUTS and SECTORS (#119)
• Delete unused _filter_data function (#120)

Testing Improvements

• Coveralls reports the actual code coverage (#123)

Breaking Changes

• client. get_status() is replaced by client.query(q.ALERTS)
• The response from client.query(q.ALERTS) is different from before, so you should update your code in case you use it:

# Before
response = {'alarm_led': 0}

# After
response = {0: {"name": "alarm_led", "status": False}}

New Contributors

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

• @xtimmy86x

Read the full changeset and the release milestone.

0.7.0

What's Changed

Client/API

• feat(client): implement get_status() to retrieve the main unit anomalies/alarms/tampering (#116)

Read the full changeset and the release milestone.

0.6.0

What's Changed

Client/API

• feat: IESS Metronet systems are now supported! You can check the documentation to see how to query the right endpoint. (#111)

Breaking Changes

• refactor!: remove AlarmDevice component. The device is now available in the Home Assistant Integration. (#113)

Read the full changeset and the release milestone.