v0.4.0

Updates:

• Entity names for when adding a device via the UI now follow HA guidelines. However, if importing via configuration.yaml, the names in the configuration are preserved.
• When importing from configuration.yaml, derive the device name from the partition info. If only one partition is defined, use that. If multiple parittions are defined, use the lowest numbered one. If no partitions are defined, use the default.
• Disallow adding the same device multiple times.
• Added validation to the options flow to prevent configuring an invalid zone or partition specification.
• Improvements to startup process in cases where it's not possible to connect to the EVL device.
• Added the ability to update hostname, user and password via the "Configure" button.
• Password and alarm code should now no longer be logged when debug logging is enabled.

v0.3.5

• Fixed issue with timing on periodic zone timer dumps and keep-alive to ensure they fire on schedule.
• Keypress sequences on Honeywell systems are issued as multiple commands to the EVL. Added change to ensure that they are sent in sequence and that no other commands can get inserting in the middle of the sequence.

v0.3.4

Fixed an issue with zone updates not working properly for Honeywell systems.

v0.3.3

Commands issued to the EVL that timeout will now trigger a reconnect under the assumption that the EVL has become unresponsive (as they are prone to do).

v0.3.2

• Fixed issue with Honeywell login flow that could prevent it completing the login process
• Added a timeout on the read loop and adjusted some logging to help track down the system sometimes becoming unresponsive.

v0.3.1

Fixed bug in EVL command parser which truncated the data portion if it contained a comma.

v0.3.0

IMPORTANT

This release contains some fairly intrusive changes to how commands from the EVL are processed. Earlier re-work of the network handling revealed some possible issues with how the existing processing of inbound commands was done so I felt it needed to be addressed.

The biggest part of the changes are in the Honeywell code. I do not have a Honeywell system but started building a mock EVL server to test the changes against and they work against it but it is far from complete nor did I have the ability to validate that it behaves exactly like a real EVL on a Honeywell system.

I would appreciate any feedback on this release from folks with a Honeywell system.

v0.2.2

Fixed issue with alarm panel entity not being created on Honeywell systems.

v0.2.1

Updates include:

• Fixed bug where login to the EVL would fail if the a numeric password was used.
• Cleaned up a bit of error handling in pyenvisalink (exposed by the above issue).
• Changed the default "arm_night" mode on Honeywell systems to use <code>33 instead of <code>7 as the latter is "Instant" mode. Also added an option in the UI to change the behaviour back to "Instant" mode to maintain the old behaviour for those wishing it.

v0.2.0

Fixes for #3

• Import of zone/partition information from configuration.yaml should now deal with non-contiguous numbers.
• Zones with a leading 0 (e.g. 08) will now import correctly.
• When configuring via the UI, it is now possible to specify a zone and partition list to make your system rather than simply a "number of zones/partitions" value. More info in the README.

IMPORTANT

There are schema changes in this release so it is highly recommended you upgrade using the following steps:

1. Go to Settings->Devices & Service section and delete any envisalink_new devices you have added.
2. Download this release via HACS
3. Restart Home Assistant Core.

If you are using configuration.yaml for your setup, once you restart HA it should automatically re-import the configuration and setup the device.