We have moved at community.getvera.com

Author Topic: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB  (Read 362634 times)

Offline Floor61

  • Newbie
  • *
  • Posts: 15
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #225 on: December 01, 2011, 09:20:39 am »
Florin - I can confirm that it does work on the 10SE as I have one.

Thanks for the heads up.  I was able to get general status updates to show, i.e. it will show READY, STAY, AWAY, etc...but I don't get zone-specific faults.  I.e. Fault - Zone 4, etc.  Should it show those as well?

Offline mcvflorin

  • Administrator
  • Hero Member
  • *****
  • Posts: 1755
  • Karma: +11/-3
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #226 on: December 01, 2011, 10:16:38 am »
If you have a newer plugin version (2.4+) then you must add the zones in the Cheat Sheet, and the plugin will create a device for each zone in the Cheat Sheet.

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #227 on: December 01, 2011, 10:20:48 am »

AFAIK insecure and unsecured have different meanings:
Quote from: Wiktionary
insecure = not secure
unsecured = not secured
In this case I meant not secure storage.
Insecure = not secure (when referring to feelings and emotions)
Unsecured = not secure / not secured (when referring to protection)


Quote
You can enable DebugMode and look into the logs to find what's happening, or give me the logs to investigate.
Code: [Select]
50 12/01/11 9:49:31.896 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0100000110000000----],001,[f70000008001000c2c000000000000],"ARMED ***AWAY***** ALL SECURE **"'. <0x2d536680>
50 12/01/11 9:49:31.897 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: ARMED_AWAY, CHIME_MODE <0x2d536680>
50 12/01/11 9:49:31.898 luup_log:180: (VistaAlarmPanel::getPartitionState) Got Alarm='None' for partition 1 (device #189). <0x2d536680>
50 12/01/11 9:49:31.898 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Armed' for partition 1 (device #189). <0x2d536680>
50 12/01/11 9:49:31.899 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='Armed' for partition 1 (device #189). <0x2d536680>



52 12/01/11 9:49:43.055 0x5b 0x30 0x31 0x30 0x30 0x30 0x30 0x30 0x31 0x31 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x2d 0x2d 0x2d 0x2d 0x5d 0x2c 0x30 0x30 0x31 0x2c 0x5b 0x66 0x37 0x30 0x30 0x30 0x30 0x30 0x30 0x38 0x30 0x30 0x31 0x30 0x30 0x30 0x63 0x32 0x63 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x5d 0x2c 0x22 0x41 0x52 0x4d 0x45 0x44 0x20 0x2a 0x2a 0x2a 0x41 0x57 0x41 0x59 0x2a 0x2a 0x2a 0x2a 0x2a 0x20 0x41 0x4c 0x4c 0x20 0x53 0x45 0x43 0x55 0x52 0x45 0x20 0x2a 0x2a 0x22 ([0100000110000000----],001,[f70000008001000c2c000000000000],"ARMED ***AWAY***** ALL SECURE **") <0x2d536680>
50 12/01/11 9:49:43.056 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0100000110000000----],001,[f70000008001000c2c000000000000],"ARMED ***AWAY***** ALL SECURE **"'. <0x2d536680>
50 12/01/11 9:49:43.057 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: ARMED_AWAY, CHIME_MODE <0x2d536680>
50 12/01/11 9:49:43.057 luup_log:180: (VistaAlarmPanel::getPartitionState) Got Alarm='None' for partition 1 (device #189). <0x2d536680>
50 12/01/11 9:49:43.058 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Armed' for partition 1 (device #189). <0x2d536680>
50 12/01/11 9:49:43.058 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='Armed' for partition 1 (device #189). <0x2d536680>

JOD.
I'm sorry, my responses are limited. You must ask the right questions.

Offline mcvflorin

  • Administrator
  • Hero Member
  • *****
  • Posts: 1755
  • Karma: +11/-3
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #228 on: December 01, 2011, 10:35:16 am »
As I can see from the logs you posted, indeed it works OK. But to find why it gives the no keypad error message, you must watch the logs during the plugin startup. Look for a message that looks like this:
(VistaAlarmPanel::getKeypadPartitions) Got these addresses: ..., for partition 1.

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #229 on: December 01, 2011, 11:25:25 am »
Code: [Select]
50 12/01/11 11:05:45.577 luup_log:180: Honeywell Ademco Vista Alarm Panel Plugin version 2.41 <0x2b491680>
50 12/01/11 11:05:45.578 luup_log:180: (VistaAlarmPanel::getDebugMode) Debug mode disabled. <0x2b491680>
50 12/01/11 11:05:45.579 luup_log:180: (VistaAlarmPanel::getNumPartitions) Number of partitions = 1. <0x2b491680>
50 12/01/11 11:05:45.592 luup_log:180: (VistaAlarmPanel::getKeypadPartitions) Got these addresses: 31, for partition 1. <0x2b491680>
50 12/01/11 11:05:45.593 luup_log:180: (VistaAlarmPanel::getStoreMode) Secure store disabled. <0x2b491680>
50 12/01/11 11:05:45.594 luup_log:180: (VistaAlarmPanel::getTtl) TTL = 60. <0x2b491680>
50 12/01/11 11:05:45.600 luup_log:180: (VistaAlarmPanel::getCheckConnectionDelay) Check connection delay = 180. <0x2b491680>
50 12/01/11 11:05:45.602 luup_log:180: (VistaAlarmPanel::main) SUCCESS: Startup successful. <0x2b491680>
50 12/01/11 11:05:45.989 luup_log:219: Honeywell Ademco Vista Alarm Panel Plugin version 2.41 <0x2b491680>
50 12/01/11 11:05:45.990 luup_log:219: (VistaAlarmPanel::getDebugMode) Debug mode disabled. <0x2b491680>
50 12/01/11 11:05:45.991 luup_log:219: (VistaAlarmPanel::getNumPartitions) Number of partitions = 1. <0x2b491680>
50 12/01/11 11:05:45.995 luup_log:219: (VistaAlarmPanel::getKeypadPartitions) Got these addresses: , for partition 1. <0x2b491680>
50 12/01/11 11:05:45.995 luup_log:219: (VistaAlarmPanel::getKeypadPartitions) ERROR: No keypad for partition 1. Terminate. <0x2b491680>
50 12/01/11 11:05:48.977 luup_log:180: (VistaAlarmPanel::processIncoming) ERROR: Invalid message. <0x2d1b1680>
50 12/01/11 11:09:47.180 luup_log:180: Honeywell Ademco Vista Alarm Panel Plugin version 2.41 <0x2b685680>
50 12/01/11 11:09:47.181 luup_log:180: (VistaAlarmPanel::getDebugMode) Debug mode enabled. <0x2b685680>
50 12/01/11 11:09:47.182 luup_log:180: (VistaAlarmPanel::getNumPartitions) Number of partitions = 1. <0x2b685680>
50 12/01/11 11:09:47.182 luup_log:180: (VistaAlarmPanel::appendPartitions) Appending partition #1. <0x2b685680>
50 12/01/11 11:09:47.183 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #1. <0x2b685680>
50 12/01/11 11:09:47.193 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #2. <0x2b685680>
50 12/01/11 11:09:47.194 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #3. <0x2b685680>
50 12/01/11 11:09:47.195 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #4. <0x2b685680>
50 12/01/11 11:09:47.196 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #5. <0x2b685680>
50 12/01/11 11:09:47.197 luup_log:180: (VistaAlarmPanel::appendZones) Appending zone #6. <0x2b685680>
50 12/01/11 11:09:47.204 luup_log:180: (VistaAlarmPanel::getChildDevices) Partition 1 device number = 189. <0x2b685680>
50 12/01/11 11:09:47.205 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #1 device number = 221, name = 'Zone #1 - . <0x2b685680>
50 12/01/11 11:09:47.206 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #2 device number = 222, name = 'Zone #2 - . <0x2b685680>
50 12/01/11 11:09:47.206 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #3 device number = 223, name = 'Zone #3 - . <0x2b685680>
50 12/01/11 11:09:47.207 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #4 device number = 224, name = 'Zone #4 - . <0x2b685680>
50 12/01/11 11:09:47.207 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #5 device number = 225, name = 'Zone #5 - . <0x2b685680>
50 12/01/11 11:09:47.208 luup_log:180: (VistaAlarmPanel::getChildDevices) Zone #6 device number = 226, name = 'Zone #6 - . <0x2b685680>
50 12/01/11 11:09:47.208 luup_log:180: (VistaAlarmPanel::getKeypadPartitions) Got these addresses: 31, for partition 1. <0x2b685680>
50 12/01/11 11:09:47.209 luup_log:180: (VistaAlarmPanel::getStoreMode) Secure store disabled. <0x2b685680>
50 12/01/11 11:09:47.210 luup_log:180: (VistaAlarmPanel::getTtl) TTL = 60. <0x2b685680>
50 12/01/11 11:09:47.213 luup_log:180: (VistaAlarmPanel::getCheckConnectionDelay) Check connection delay = 180. <0x2b685680>
50 12/01/11 11:09:47.215 luup_log:180: (VistaAlarmPanel::main) SUCCESS: Startup successful. <0x2b685680>
50 12/01/11 11:09:47.570 luup_log:219: Honeywell Ademco Vista Alarm Panel Plugin version 2.41 <0x2b685680>
50 12/01/11 11:09:47.571 luup_log:219: (VistaAlarmPanel::getDebugMode) Debug mode disabled. <0x2b685680>
50 12/01/11 11:09:47.571 luup_log:219: (VistaAlarmPanel::getNumPartitions) Number of partitions = 1. <0x2b685680>
50 12/01/11 11:09:47.575 luup_log:219: (VistaAlarmPanel::getKeypadPartitions) Got these addresses: , for partition 1. <0x2b685680>
50 12/01/11 11:09:47.575 luup_log:219: (VistaAlarmPanel::getKeypadPartitions) ERROR: No keypad for partition 1. Terminate. <0x2b685680>
50 12/01/11 11:09:50.601 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = ' <0x2d3a5680>
50 12/01/11 11:09:50.601 luup_log:180: (VistaAlarmPanel::processIncoming) ERROR: Invalid message. <0x2d3a5680>
50 12/01/11 11:09:54.678 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:09:54.678 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:09:54.680 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:09:54.681 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:09:54.681 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:09:54.683 luup_log:180: (VistaAlarmPanel::addFaultedZone) Set zone #1 to tripped. <0x2d3a5680>
50 12/01/11 11:09:58.686 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:09:58.686 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:09:58.688 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:09:58.689 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:09:58.689 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:02.696 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:02.697 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:02.699 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:02.700 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:02.701 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:06.726 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:06.726 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:06.728 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:06.729 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:06.729 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:10.776 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:10.777 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:10.779 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:10.780 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:10.781 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:14.836 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:14.837 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:14.839 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:14.840 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:14.840 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:16.997 luup_log:180: (VistaAlarmPanel::ttlCountdownTimer) Zone #1 TTL = 55 <0x2b685680>
50 12/01/11 11:10:17.000 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:17.126 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:17.127 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:19.786 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:19.787 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:19.789 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:19.790 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:19.790 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:22.926 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:22.927 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:22.929 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:22.929 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:22.930 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:24.108 luup_log:0: startTime = 805; currentTime = 1110; endTime = 2315 <0x2b485680>
50 12/01/11 11:10:24.112 luup_log:0: startTime = 100; currentTime = 1110; endTime = 2345 <0x2b485680>
50 12/01/11 11:10:26.926 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:26.927 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:26.929 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:26.929 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:26.930 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:29.110 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.113 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.118 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.121 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.159 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:29.159 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:29.215 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.219 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.222 luup_log:180: (VistaAlarmPanel::ttlCountdownTimer) Zone #1 TTL = 55 <0x2b685680>
50 12/01/11 11:10:29.225 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:29.415 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:29.416 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:29.696 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:29.696 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:29.865 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:29.866 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:30.095 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:30.095 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:30.335 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:30.335 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:30.575 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:30.575 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:31.025 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:31.026 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:31.029 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:31.029 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:31.030 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:31.738 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:31.975 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:31.975 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:32.005 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:32.205 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '!Sending...done'. <0x2d3a5680>
50 12/01/11 11:10:32.206 luup_log:180: (VistaAlarmPanel::processIncoming) Drop message. <0x2d3a5680>
50 12/01/11 11:10:34.736 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:34.736 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:34.739 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:34.739 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:34.740 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:38.146 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:38.147 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:38.148 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:38.149 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:38.149 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:42.398 luup_log:180: (VistaAlarmPanel::processIncoming) Incoming data = '[0001000110000000----],001,[f70000008001000028000000000000],"FAULT 01 ZONE 01                "'. <0x2d3a5680>
50 12/01/11 11:10:42.399 luup_log:180: (VistaAlarmPanel::getStatusFlags) Active flags: CHIME_MODE <0x2d3a5680>
50 12/01/11 11:10:42.401 luup_log:180: (VistaAlarmPanel::getPartitionState) Got ArmMode='Disarmed' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:42.401 luup_log:180: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='NotReady' for partition 1 (device #189). <0x2d3a5680>
50 12/01/11 11:10:42.402 luup_log:180: (VistaAlarmPanel::addFaultedZone) Zone #1 TTL = 60 <0x2d3a5680>
50 12/01/11 11:10:43.215 luup_log:180: (VistaAlarmPanel::ttlCountdownTimer) Zone #1 TTL = 55 <0x2b685680>
50 12/01/11 11:10:43.219 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:43.233 luup_log:180: (VistaAlarmPanel::sendStar) Send '*' to partition 1. <0x2b685680>
50 12/01/11 11:10:43.240 luup_log:111: Received: unknowncommand 14 <0x2cfa5680>

JOD.
I'm sorry, my responses are limited. You must ask the right questions.

Offline mcvflorin

  • Administrator
  • Hero Member
  • *****
  • Posts: 1755
  • Karma: +11/-3
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #230 on: December 01, 2011, 11:54:31 am »
I see 2 alarm panel devices: 180 and 219.

Which means that installing the plugin creates another device, which is normal behavior. Sorry for giving you erroneous information.

Please delete device 219, because this is the one that doesn't work.

(Note to self: verify the information you post.)

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #231 on: December 01, 2011, 01:14:19 pm »
HAHA.... It's just a bump in the road.
I just posted some erroneous info on the beta forum then.... Because I didn't see that a new device was created, now I see it, along with the unpinned zone devices!. Sweet.

I'll go revise the post and then delete the device.

JOD.

*Edit. Deleted device #219  & #220 and the error has cleared.
« Last Edit: December 01, 2011, 01:42:26 pm by JOD »
I'm sorry, my responses are limited. You must ask the right questions.

Offline dratifk

  • Sr. Newbie
  • *
  • Posts: 41
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #232 on: December 01, 2011, 02:29:40 pm »
Working great. Thank you for your hard work. I appreciate you answering what may seem stupid and basic questions.

Offline wseverino

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 854
  • Karma: +0/-0
  • Da Man, Da Myth, Da Legend - in his own mind!
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #233 on: December 01, 2011, 02:54:52 pm »
I don't know if anyone noticed this.....but when one of the child devices / security sensors created from the cheat sheet trips the tripped variable does not get reset to 0 when the faulted zone is cleared.
My ZWave Network: Too friggin big to list.....

Offline shep29

  • Sr. Newbie
  • *
  • Posts: 39
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #234 on: December 02, 2011, 03:10:18 pm »
Anyone with a Vista 10-SE panel getting "Check" 09" errors at their keypads? My alarm went off as a result in the middle of the night and freaked everybody out. This seems to have started when I upgraded to 2.41 but not 100% sure. According to the manual, a "Check 09" error happens when the control panel loses communication with the wireless receiver, which in my case is located inside my 6160RF keypad, which is hard-wired to the panel. It may be unrelated but its coincidental and so I thought I'd post it. I even replaced the keypad and ran new wire from the panel. Thoughts anyone before I rip this panel out and put in a 20P?

Offline waynebrady

  • Full Member
  • ***
  • Posts: 110
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #235 on: December 02, 2011, 03:32:27 pm »
I am also noticing this.

I don't know if anyone noticed this.....but when one of the child devices / security sensors created from the cheat sheet trips the tripped variable does not get reset to 0 when the faulted zone is cleared.

Offline mathewss

  • Sr. Newbie
  • *
  • Posts: 29
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #236 on: December 02, 2011, 11:58:00 pm »
Anyone with a Vista 10-SE panel getting "Check" 09" errors at their keypads? My alarm went off as a result in the middle of the night and freaked everybody out. This seems to have started when I upgraded to 2.41 but not 100% sure. According to the manual, a "Check 09" error happens when the control panel loses communication with the wireless receiver, which in my case is located inside my 6160RF keypad, which is hard-wired to the panel. It may be unrelated but its coincidental and so I thought I'd post it. I even replaced the keypad and ran new wire from the panel. Thoughts anyone before I rip this panel out and put in a 20P?

 To answer your question.
   I do not recall any issue of a customer reporting this fault and I have a fair number of people using the AD2USB on SE panels.
Lets record as much info for your event that way if anyone else does I can answer that question differently next time : )

Please post the following to my support queue general@support.nutech.com.

 Your hardware and firmware version.
 Plugin logs during the time 10-20 minutes prior and ending with the time where the event was cleared. 
 What steps were necessary to clear the problem?
 Any other information that you think may be pertinent would be helpful.

@ mcvflorin I will cc you on the ticket and send you the same details for your records.
 
 Thanks @ everyone.
 Sean Mathews
 CTO @ NuTech dot com

Offline JOD

  • Hero Member
  • *****
  • Posts: 1973
  • Karma: +4/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #237 on: December 04, 2011, 01:06:33 pm »
@mcvflorin,

After upgrading to 2.41, all my scenes relating to the alarm panel events are void of triggers.
Armed Night, Armed Stay, Armed Instant, Not Ready, Ready, Armed, Stay Instant, Disarmed and most importantly Alarm.

I no longer see my panel device #180 & the partition #189 when viewing triggers.
Therefore, scene setup based on an alarm event or panel status is not possible.

JOD.

*Edit. In addition, using the child devices as triggers, I'm seeing a toggle of tripped and untripped every few minutes.
Zone 5 Untripped 12/4/2011 5:51:23 P.M.
Zone 5 Tripped 12/4/2011 5:50:08 P.M.
Zone 5 Untripped 12/4/2011 5:49:35 P.M.
Zone 5 Tripped 12/4/2100 5:47:44 P.M.
Zone 5 Untripped 12/4/2011 5:45:20 P.M.
Zone 5 Tripped 12/4/2011 5:43:50 P.M.
Zone 5 Untripped 12/4/2011 5:36:20 P.M.
Zone 5 Tripped 12/4/2011 5:33:52 P.M.
Zone 5 Untripped 12/4/2011 5:32:26 P.M.
Zone 5 Tripped 12/4/2011 5:31:39 P.M.
 

« Last Edit: December 04, 2011, 06:08:31 pm by JOD »
I'm sorry, my responses are limited. You must ask the right questions.

Offline mcvflorin

  • Administrator
  • Hero Member
  • *****
  • Posts: 1755
  • Karma: +11/-3
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #238 on: December 06, 2011, 10:34:00 am »
I don't know if anyone noticed this.....but when one of the child devices / security sensors created from the cheat sheet trips the tripped variable does not get reset to 0 when the faulted zone is cleared.

Not even after some time? Usually it takes up to TTL seconds for the Tripped variable to be cleared.

@ mcvflorin I will cc you on the ticket and send you the same details for your records.

Thanks.

After upgrading to 2.41, all my scenes relating to the alarm panel events are void of triggers.

But can you create a new scene and use the triggers? I have a suspicion that this isn't plugin related.

*Edit. In addition, using the child devices as triggers, I'm seeing a toggle of tripped and untripped every few minutes.

What do the all knowing logs say? :)
« Last Edit: December 06, 2011, 10:46:02 am by mcvflorin »

Offline waynebrady

  • Full Member
  • ***
  • Posts: 110
  • Karma: +0/-0
Re: Honeywell Ademco Vista Alarm Panels Plugin via AD2USB
« Reply #239 on: December 12, 2011, 01:30:16 am »
Is it possible to get sensor trips when armed? I usually arm my house at night, but I still want to get some of my motion sensors to trip so I can create a scene to turn on lights.