Odd Warning after upgrading to 3.4

A couple days ago I upgraded indigo to 2023.1 and noticed the AD2USB 3.2.1 was downrev .....this morning I bumped the blueing up to 3.4 and immediately started getting a warning about wire expansion 107 (see below) .

As with most things in this system , they work so well, for so long, that you forget how they were don in the first place Y'all have any thoughts on what the plugin warning is pointing to?

I reinstalled the v 3.2.1 and get no such warning, so it appears like there's something different in the 3.4 plugin


Dec 7, 2023 at 8:36:05 AM
Stopping plugin AD2USB Alarm Interface (pid 1455)
AD2USB Alarm Interface AlarmDecoder StopThread received
AD2USB Alarm Interface runConcurrentThread completed
AD2USB Alarm Interface called with Name:Alarm Keypad, id:1321680986, TypeId:ad2usbInterface
AD2USB Alarm Interface Device stop completed for Alarm Keypad
AD2USB Alarm Interface called with Name:Alarm Zone 1, id:328661344, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 1
AD2USB Alarm Interface called with Name:Alarm Zone 10, id:225134475, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 10
AD2USB Alarm Interface called with Name:Alarm Zone 10 Virtual, id:1245773239, TypeId:alarmZoneVirtual
AD2USB Alarm Interface Device stop completed for Alarm Zone 10 Virtual
AD2USB Alarm Interface called with Name:Alarm Zone 11, id:1417454933, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 11
AD2USB Alarm Interface called with Name:Alarm Zone 11 Virtual, id:705688944, TypeId:alarmZoneVirtual
AD2USB Alarm Interface Device stop completed for Alarm Zone 11 Virtual
AD2USB Alarm Interface called with Name:Alarm Zone 12, id:1829762316, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 12
AD2USB Alarm Interface called with Name:Alarm Zone 12 Virtual, id:1479497037, TypeId:alarmZoneVirtual
AD2USB Alarm Interface Device stop completed for Alarm Zone 12 Virtual
AD2USB Alarm Interface called with Name:Alarm Zone 2, id:1662176307, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 2
AD2USB Alarm Interface called with Name:Alarm Zone 3, id:1827566762, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 3
AD2USB Alarm Interface called with Name:Alarm Zone 4, id:607939709, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 4
AD2USB Alarm Interface called with Name:Alarm Zone 5, id:411886041, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 5
AD2USB Alarm Interface called with Name:Alarm Zone 6, id:1306355967, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 6
AD2USB Alarm Interface called with Name:Alarm Zone 7, id:427909257, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 7
AD2USB Alarm Interface called with Name:Alarm Zone 8, id:306547627, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 8
AD2USB Alarm Interface called with Name:Alarm Zone 9, id:1004546884, TypeId:alarmZone
AD2USB Alarm Interface Device stop completed for Alarm Zone 9
AD2USB Alarm Interface called with Name:Alarm Zone 9 Virtual, id:206912770, TypeId:alarmZoneVirtual
AD2USB Alarm Interface Device stop completed for Alarm Zone 9 Virtual
AD2USB Alarm Interface serial connection is open... attempting to close...
AD2USB Alarm Interface serial connection is closed...
AD2USB Alarm Interface Plugin shutdown completed
Stopped plugin AD2USB Alarm Interface
Upgrading plugin AD2USB Alarm Interface to newer version 3.4.0 (previous version moved to trash)
Loading plugin "AD2USB Alarm Interface 3.4.0" using API v3.0.0
Starting plugin "AD2USB Alarm Interface 3.4.0" (pid 10000)
AD2USB Alarm Interface Indigo logging level set to:INFO (20)
AD2USB Alarm Interface Plugin logging level set to:INFO (20)
AD2USB Alarm Interface Plugin init completed
Started plugin "AD2USB Alarm Interface 3.4.0"
AD2USB Alarm Interface attempting to connect to:socket://192.168.0.XX:10000
AD2USB Alarm Interface connected to AlarmDecoder:socket://192.168.0.XX:10000
AD2USB Alarm Interface AlarmDecoder communication started...
AD2USB Alarm Interface AlarmDecoder VER (version) command sent
AD2USB Alarm Interface AlarmDecoder C (config) command sent
AD2USB Alarm Interface AlarmDecoder communication startup completed successfully
AD2USB Alarm Interface AlarmDecoder initialized and communication started...
AD2USB Alarm Interface Plugin startup completed. Ready to open link to the ad2usb in Basic mode.
AD2USB Alarm Interface Device startup completed for Alarm Keypad
AD2USB Alarm Interface Device startup completed for Alarm Zone 1
AD2USB Alarm Interface Device startup completed for Alarm Zone 10
AD2USB Alarm Interface Device startup completed for Alarm Zone 10 Virtual
AD2USB Alarm Interface Device startup completed for Alarm Zone 11
AD2USB Alarm Interface Device startup completed for Alarm Zone 11 Virtual
AD2USB Alarm Interface Device startup completed for Alarm Zone 12
AD2USB Alarm Interface Device startup completed for Alarm Zone 12 Virtual
AD2USB Alarm Interface Device startup completed for Alarm Zone 2
AD2USB Alarm Interface Device startup completed for Alarm Zone 3
AD2USB Alarm Interface Device startup completed for Alarm Zone 4
AD2USB Alarm Interface Device startup completed for Alarm Zone 5
AD2USB Alarm Interface Device startup completed for Alarm Zone 6
AD2USB Alarm Interface Device startup completed for Alarm Zone 7
AD2USB Alarm Interface Device startup completed for Alarm Zone 8
AD2USB Alarm Interface Device startup completed for Alarm Zone 9
AD2USB Alarm Interface Device startup completed for Alarm Zone 9 Virtual
AD2USB Alarm Interface Enabling trigger:Burglar Alarm
AD2USB Alarm Interface Enabling trigger:Fire Alarm
AD2USB Alarm Interface AlarmDecoder message processing started
AD2USB Alarm Interface AlarmDecoder Firmware Version is: V2.2a.8.8
AD2USB Alarm Interface AlarmDecoder CONFIG message read: MODE=A&CONFIGBITS=ff05&ADDRESS=18&LRR=N&COM=N&EXP=YNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=Y
AD2USB Alarm Interface AlarmDecoder CONFIG setting are now: ADDRESS=18&LRR=N&EXP=YNNNN&REL=NNNN&DEDUPLICATE=Y

Dec 7, 2023 at 8:36:33 AM
AD2USB Alarm Interface Warning Invalid Numeric Code:107 found in KPM message:"CHECK 107 WIRE EXPANSION

(The warning is triggered every minute)

Take a look at this old post from AlarmDecoder: https://www.alarmdecoder.com/forums/viewtopic.php?t=80

I can see from your log that you have Emulation of zone expander 1 set to "Y" (EXP=YNNNN).

Code: Select all

AD2USB Alarm Interface AlarmDecoder CONFIG setting are now: ADDRESS=18&LRR=N&EXP=YNNNN&REL=NNNN&DEDUPLICATE=Y

You can read about this feature on the AlarmDecoder here: https://www.alarmdecoder.com/wiki/index ... _Emulation

Based on your panel information and home alarm system, is that setting intentional? I have no idea if that is the issue - but it seems similiar.

Take a look at this old post from AlarmDecoder: https://www.alarmdecoder.com/forums/viewtopic.php?t=80

I can see from your log that you have Emulation of zone expander 1 set to "Y" (EXP=YNNNN).

Code: Select all

AD2USB Alarm Interface AlarmDecoder CONFIG setting are now: ADDRESS=18&LRR=N&EXP=YNNNN&REL=NNNN&DEDUPLICATE=Y

You can read about this feature on the AlarmDecoder here: https://www.alarmdecoder.com/wiki/index ... _Emulation

Based on your panel information and home alarm system, is that setting intentional? I have no idea if that is the issue - but it seems similiar.

Yes, I do use a expansion via the AD2USB module, Sensors native to the Indigo system are used in the Vista 20P. I checked the states of them and they were all off. I was refreshing my memory on the systems, when I recalled having to walk my way through all the zoneprogramming in the panel a few years ago, perhaps after a previous plugin upgrade (I'll have to look back in my posts here to verify) ...nevertheless, once I *ed my way through all the programming on the keypad, and 99'd my way out, the warning disappeared.

So the issue has been resolved via your panel actions?

So the issue has been resolved via your panel actions?

Oh, I forgot to mention above that the 2 keypads were scrolling. Messages about expansion zones as well .
I restarted the plug-in, no joy.
I powercycled the AD2usb controller, no joy
I powercycled the alarm box, still no joy
When I got into the alarm zone programming and stepped through all the zones, the problem went away.
So, yes, panel actions resolved the problem, but upgrading the plug-in is what started the problem, maybe some unique identifiers of zones were changed or something ?

I was curious about this and I do fear it may be a longstanding bug. I don't use this feature so I am curious about what you see. The current version of the AlarmDecoder protocol clearly shows three states you can pass to the panel: 0 = CLOSE, 1 = TROUBLE, 2 = OPEN.

"The L command can be used to open, close, or trouble a zones. There are two parameters: the zone and the state. The zone is a zero-padded two-digit number and the state is either 0 = CLOSE, 1 = TROUBLE, 2 = OPEN."

https://www.alarmdecoder.com/wiki/index ... _Emulation

An older version of the protocol (from 2015) shows only two states:

"The L command can be used to open or close zones. There are two parameters: the zone and the state. The zone is a zero-padded two-digit number and the state is either 0 [CLOSE] or 1 [OPEN]."

When I look at the Plugin code, since the very first version I took over, the Actions.xml file has these settings, which seem to have Faulted and Trouble incorrectly numbered as 1 and 2 when they should be 2 and 1. Has the faulting of a VirtualZone ever worked? Or does a faulting action trip a Trouble indicator on your panel?

Code: Select all

<Option value="0">Clear</Option>
<Option value="1">Faulted</Option>
<Option value="2">Trouble</Option>

When I look at the Plugin code, since the very first version I took over, the Actions.xml file has these settings, which seem to have Faulted and Trouble incorrectly numbered as 1 and 2 when they should be 2 and 1. Has the faulting of a VirtualZone ever worked? Or does a faulting action trip a Trouble indicator on your panel?

Code: Select all

<Option value="0">Clear</Option>
<Option value="1">Faulted</Option>
<Option value="2">Trouble</Option>

the faulting of the Zones 9-12 has always worked. These zones are motion and open/close sensors, and will show on the panel when faulted, and trip the siren. I installed it something like 9 years ago, and configured the AD2Pi and original plugin, and other than having some trouble when upgrading the plugin (twice) , it's been bulletproof...evidently something happens when the plugin is upgraded that messes up the virtual zone, and when I walk through the zone config on the panel, it "reprograms" the zones and it's golden again

I just realized that I'm still running v3.2.1 of the plugin after I tried downgrading to fix the warning.
I could try and bump it back up to 3.4 and see what happens. If you're interested in some data , let me know what to do , and I'll give it a try.