i seen in the Wiki that the plugin supports PGM, but is disabled by default in the code. Does anyone know how to enable it in the code? I have a two wire smoke detector that connects to PGM02, and I was hoping there was someway to have the plugin recognize PGM02 as a fire zone. I did see a topic on this forum suggesting using a relay, but the suggested fix will not work for me as all my hardwired zones are already used (I have a 1616). Any help is appreciated.
The PGM is an output, not a Zone. When configured in a 2-Wire Smoke setup, the Panel is supposed to report a [Panel-level] Vendor code of 631 code when the issue is detected, and a 632 code when it’s restored.
These appear to be Panel-level events, so you’d need to trigger on that event specifically (Advanced Scenes), and IIRC I’m not 100% Panel-level Vendor-codes are working at the moment…
Anyhow I’ve not tested the end-to-end interaction, so you’ll need to start by checking at your end that your 2-Wire Smoke setup is actually reporting the 631/632 Vendor codes (using Verbose logging, and looking at the logs) before any further steps are taken.
Guessed thanks. I did a test and had the log logging events. somewhere around here is when i triggered it (shorted the wires), and immediately the alarm panel lit up fire and started alarming
09/30/14 19:06:29.577 Device_Variable::m_szValue_set device: 219 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: VendorStatusCode was: 510 now: 631 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f177680>
06 09/30/14 19:06:29.579 Device_Variable::m_szValue_set device: 219 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: VendorStatus was: Keypad LED State now: Aux Input Alarm Set #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f177680>
06 09/30/14 19:06:29.580 Device_Variable::m_szValue_set device: 219 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 variable: AuxInputAlarm was: EMPTY now: 1 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f177680>
06 09/30/14 19:06:30.084 Device_Variable::m_szValue_set device: 226 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatusCode was: 650 now: 654 #hooks: 0 upnp: 0 v:0xe2da38/NONE duplicate:0 <0x2f177680>
06 09/30/14 19:06:30.085 Device_Variable::m_szValue_set device: 226 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatus was: Ready now: Alarm #hooks: 0 upnp: 0 v:0xe2d128/NONE duplicate:0 <0x2f177680>
06 09/30/14 19:06:30.087 Device_Variable::m_szValue_set device: 226 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: Alarm was: None now: Active #hooks: 1 upnp: 0 v:0xce0998/NONE duplicate:0 <0x2f177680>
So looks like it sent a 631. let me know if the above was what you were looking for, as I am new to this Vera stuff, however i have experience with electronics, control systems and programming.
Looks correct. There should be a change of the [tt]VendorStatusCode[/tt] (variable) to 632 at the end of the event as well, since they’re paired.
If that’s working, then you can use Vera’s Advanced Scenes on the Panel-Level object (Device 219), where you should be able to check it for the value “631”. It’s possible this part isn’t working, since I’ve heard issues in the past (I made some tweaks, but mostly for Partition-Level events)
PS: You might want to disconnect your Bell during this type of testing 
@Guessed…Thanks for the feedback. I didn’t notice if a 632 was sent when I restored, I will try and test again. Yeah the Bell doesn’t bother me, but drives my wife bonkers. I am self monitoring, for now, so no worries on the fire department showing up at this point.