ANNOUNCING VERSION 3 OF THE DSC/ENVISALINK DRIVER
I’m pleased to make available the next iteration of this driver that includes several enhancements as requested by the community, as well as some fixes to known issues.
This is a NEW driver and therefore will not automatically replace your existing driver. This is so YOU have control over when to upgrade, since it will be disruptive to your existing setups. For example, when you are ready to move to the new driver, you will be required to create all new panel and zone devices. This will in turn require you to redo any automations you have.
Your existing V2 driver will continue to run normally and I’ll not even remove it from the channel for a few months. So you can decide when you are ready to move to the V3 driver.
Version 3 Enhancements
- Clean-up of known annoyances in V2 driver (field labels, button issues, etc.)
- Ability to initiate PGM1, PGM2, PGM3, PGM4 commands from automations
- Fixes to instant arm commands
- Partition status distinction between regular armed and instant-armed states (@7522)
- Know who in the household last armed/disarmed the system
- addition of last-armed user field in panel device; user names are configured in new device Setting option
- Enhanced trouble condition information
- addition of trouble type field in panel device to specifically indicate Battery, Bell, AC Power Lost, etc. trouble conditions
- Improved notification and recovery of Envisalink connection loss
- addition of periodic Envisalink connection monitoring: poll frequency in minutes can be configured in primary panel device settings; if Envisalink connection found not to be active, then all devices will be set to offline status and partition status set to ‘Offline’, enabling automation triggers.
Additional information is available in the driver README file on github.
A special thank-you goes out to @BobR for his ideas on enhancements and willingness to test the driver out before I released it.
Installation
Before proceeding, you will need to delete any existing V2 panel and zone devices, and remove the V2 driver.
You can install the V3 driver from my shared projects channel. Enroll your hub if not already, and choose to install the “Envisalink 3.0” driver.
For the remaining steps please refer to the README instructions.
If you follow my instructions carefully you should be back up and running within a matter of minutes (not including re-creating any automations you need).