Minor changes related to connection handling:

• Allow keep-alive timer to be set to 0 to disable it (via the Advanced settings).
• Prevent disconnect processing from happening multiple times for the same disconnection.
• Disconnect from the EVL if the login handshake fails to complete.
• Changed reconnection timer to use an exponential backoff instead of a fixed 30s.

Uno panel update:

This release adds additional capabilities for Uno panels based on new firmware updates.

The following additions have been made for Uno panels:

• Support for arming the system in both away and stay modes.
• Switch entities to bypass zones. This must be turned on in the Advanced settings of the integration.
• Partition status codes updated to match changes in firmware (previous firmware used Honeywell codes).
• Partition trouble status exposed (AC present, battery trouble, system trouble, bell trouble).

Thanks for @zim514, @tamorgen, @andredigenova, @deliverer33 and others for beta testing the changes as I don't own an Uno panel myself.

Thanks also to @chelming for contributing some Lovelace examples for the integration.

Full Changelog: v1.0.0...v1.1.0

Changes:

• Updated partition status codes to match what the 124 is sending.
• Fixed panic alarm buttons not working due to the TPI command being incorrectly formatted.
• Added missing TPI error response codes.
• Debug TX logging was not including the full command data.

A new 1.0.123 firmware is now available for Uno panels which allows additional capabilities to be exposed by this integration. This release includes the following additions:

• Support for arming the system in both away and stay modes.
• Switch entities to bypass zones. This must be turned on in the Advanced settings of the integration.

The firmware update also includes additional status information for the panel (AC failure, bell trouble, etc.) but support for that will be added to this integration in a future release.

Full Changelog: v1.0.0...v1.1.0-uno-beta1

Changes:

Alarm code handling

The default alarm code is now configured on the alarm_control_panel_entity itself rather than via this integration per the discussion here. The alarm code in envisalink_new is still honoured if present but will log warnings. To set the default alarm code, select the alarm control panel entity and then click the gear in the top right to edit its settings and fill in the Default code value with your alarm code.

Zone / Partition Assignments

Added the ability to assign zones to their respective partitions. This is done via Configuration->Partition Assignments.

• Zones not explicitly assigned will be defaulted to the lowest partition configured (typically 1)
• All zone attributes now include a partition attribute
• DSC Zone bypass switches will now send the bypass command to the correct partition on the EVL panel (#113)

Additional changes

• Added a configuration option (Configuration->Advanced->Code required to arm) to control the value of code_arm_required for DSC panels. Thanks to @bassdr for the PR inspiring these changes.
  • Depending on the DSC panel setup, a code may or may not be required.
  • This is not exposed for Honeywell panels as they always require a code for arming.
• Added a new configuration option (Configuration->Advanced->Show Keypad) to control when the alarm keypad is shown in the UI. This allows for the hiding of the keypad in cases where it is not desired (e.g., for arming).
• The integration has been renamed to EyezOn to better reflect support for additional devices such as the UNO products.
• Changed the exposed alarm state from PENDING to ARMING when the alarm is in the exit delay state.
• Fixed deprecation warning (#162)
• The Configuration->Advanced->Panic type setting is now a drop down instead of a freeform text field (thanks to @bassdr for the contribution).

Full Changelog: v0.9.6...v1.0.0

Changes

• #165: Fixed issue with the chime switch entity not using the new default alarm code mechanism.
• Fixed an issue with the translations not working properly for selectors in the Advanced settings.

Changes:

Alarm code handling

The default alarm code is now configured on the alarm_control_panel_entity itself rather than via this integration per the discussion here. The alarm code in envisalink_new is still honoured if present but will log warnings.

Added a configuration option (Configuration->Advanced->Code required to arm) to control the value of code_arm_required for DSC panels.

• Depending on the DSC panel setup, a code may or may not be required.
• This is not exposed for Honeywell panels as they always require a code for arming.

Added a new configuration option (Configuration->Advanced->Show Keypad) to control when the alarm keypad is shown in the UI. This allows for the hiding of the keypad in cases where it is not desired (e.g., for arming).

Thanks to @bassdr for the PR inspiring these changes.

Zone / Partition Assignments

Added the ability to assign zones to their respective partitions. This is done via Configuration->Partition Assignments.

• Zones not explicitly assigned will be defaulted to the lowest partition configured (typically 1)
• All zone attributes now include a partition attribute
• DSC Zone bypass switches will now send the bypass command to the correct partition on the EVL panel (#113)

Additional changes

• The integration has been renamed to EyezOn to better reflect support for additional devices such as the UNO products.

• Changed the exposed alarm state from PENDING to ARMING when the alarm is in the exit delay state.

• Fixed deprecation warning (#162)

• The Configuration->Advanced->Panic type setting is now a drop down instead of a freeform text field (thanks to @bassdr for the contribution).

Full Changelog: v0.9.6...v1.0.0-beta1

Changes:

• #156: Fixed knock on from previous changes to Night mode handling. If a Honeywell system was configured to use Instant for night mode then the alarm panel would incorrectly show Armed Home instead of Armed Night.

Changes:

• #154: Added detection of Envisalink 4 UNO STANDALONE devices.

Bug fixes:

• #146: Both Honeywell and DSC were previously tracking Night mode strictly based on a zero-entry-delay state.
  • Honeywell now tracks night mode using the 4th bit in the beep field from a virtual keypad update (thanks to @Dilbert66 for this info).
  • DSC now tracks night mode based on mode 3 (ZERO-ENTRY-STAY) from a 652 (Partition Armed) update.