08-19-2017, 11:31 AM
Sorry for the pleathora of questions regarding the v2 drivers and 5.+ system.  I'm late to the game upgrading my system and feel like perhaps I missed out on the explainations. That being said.....
With the v1 Elk driver, I had a trigger on the AreaArm1 field.  This field changed with the arm status of the system.  So when I armed the system "Away" or "Vacation" or "Disarm", my CQC system would react to that and change thermostat set points, power on/off devices, etc.
With the V2 Elk driver, I don't see this field anymore.  Furthermore, I don't even see a way to add a trigger to the Area fields in the client side driver.  You can add triggers for the individual zones, but not an area.
Is there a method to accomplish what I was doing with the V1 driver with the V2 driver?  Currently I still have the V1 driver installed so that my triggers continue to work.  But obviously that is a little overkill and it would be nice to get rid of the duplicate driver.
Thanks!
With the v1 Elk driver, I had a trigger on the AreaArm1 field.  This field changed with the arm status of the system.  So when I armed the system "Away" or "Vacation" or "Disarm", my CQC system would react to that and change thermostat set points, power on/off devices, etc.
With the V2 Elk driver, I don't see this field anymore.  Furthermore, I don't even see a way to add a trigger to the Area fields in the client side driver.  You can add triggers for the individual zones, but not an area.
Is there a method to accomplish what I was doing with the V1 driver with the V2 driver?  Currently I still have the V1 driver installed so that my triggers continue to work.  But obviously that is a little overkill and it would be nice to get rid of the duplicate driver.
Thanks!
Brian - a long time user that rarely messes with the system now
BlueIris and IP cameras for CCTV
Incredible PBX for home phone
Other systems used:
SageTV w/ cablecard tuner & multiple extenders for viewingBlueIris and IP cameras for CCTV
Incredible PBX for home phone