GE Caddx NX-8E

Making good progress. Was pretty straightforward so far and I have the basics running. Have a GitHub repo for it set up and should be ready for alpha in a few more days of dev time. Probably next week tho, based on available time to spend on this and availability of the test fixture (see below) .

It was made easier by the fact that IanS did almost all the parsing and marshaling as ASCII-encoded hex strings, which are well contained by the current Python 3 unicode native strings. He had a few spots where he seemed to switch back and forth (for reasons I can't quite figure out) between the hex encoding and binary representation. I cleaned up those spots to work only in the hex representation until the very bottom of the plugin, and convert to/from a binary string adjacent to the comm port reads and writes. A nice side effect is that it will be easy to eventually support the ASCII hex encoding of the NS-584 protocol with just a few hours of work. Not convinced of the use case for that yet, but the possibility is there.

One controversial move I made was to do more refactoring that was absolutely necessary. I fixed all the PEP08 warnings, indentation/spacing problems and misspellings. (Of which there were a few thousand, but made easier by PyCharm). Bit of code streamlining also. The downside of this is that it will be harder for reviewers to note the key changes, and for those who extended the plugin to merge their changes to the new version. Sorry about that. OCD, you know... If no one screams, I may just run the whole code base through a formatter before shipping.

WRT testing.... My panel is in a second home and I am doing the development via remote desktop. Also, it is a "production" panel. So I will be unable to do more complete testing until mid-August when I am on site to toggle zones to test device updating and deal with the brokenness that will occur when I remove all my current Caddx Indigo devices and test the "Create Caddx Alarm System Devices"

I guess my goal is to get this in to the plugin store, but there is lots of unimplemented template code there, that needs to be identified and disabled first IMO. The panel does a lot and Ian provided a excellent framework to support just about everything, but I feel plugin needs a bright line documenting what does and does not work at this moment. Have not scoped out that effort yet.

I can help do some testing in a few weeks if you want.

Just an fyi about ASC II. Most of the homebridge and homeassistant integrations I have seen are based upon ASC II not binary from what I have seen.

I can help do some testing in a few weeks if you want.

Just an fyi about ASC II. Most of the homebridge and homeassistant integrations I have seen are based upon ASC II not binary from what I have seen.

Thanks for offer to test. In the next week or so, perhaps you could shoot me a PM with what features you use so I can endeavor to test them.

On ASCII... What you say is true, but the integrations are different code bases with no shared code right now. A panel's serial port can be connected to only one NX-584 at a time, so setting it to the protocol version required for the specific integration and keeping it there would not have any cross integration impact, since there is essentialy no cross integration.

One could image (and there is code out there that I have looked at and considered) where the integrations would interface with a Caddx MQTT adaptor, allowing multiple integrations to use the panel at the same time. Even then the MQTT adaptor would only need to support the ASCII or binary version of the protocol but not both. That would be a totally new Indigo plugin IMO. Could be fun, but I should probably finish this one first. . Squirrel!!!

Sent you a pm

Any updates on status - location to download Beta version?

Done with basic bring up. Back at my second home this week but limited testing time due to good outdoor weather Should be releasing an alpha early next week.


Also:

The original codebase is not something I would want to to support in its current form. My thinking is that I will release a 2.0 version informally off of GitHub and maintain that branch for maybe the next 6 months so folks are not left hanging. With a few exceptions this version will be feature./bug compatible with 1.X version, just on Python 3. (Although I did need to rewrite the bottom of the plugin to fix a nasty bug I was seeing in the old version re data under runs and loss of synchronization state on subsequent messages from panel)

For formal release I have started a highly refactored version 3 and any feature enhancements and long term support will be on that version. Some of the changes might necessitate recreating some of the devices associated with the plugin. If there is sufficient interest, will put in plugin store.

And a BTW for the indigo team… Really love the PyCharm debugging integration. I have always used it for my python web work and being able to use it here helped immensely.

awesome

I have completed a first alpha of the Python3+Refactor version of this plugin, and am currently preparing all the final touches to do a release (e.g., zip download, release tag, instructions). This last part might take a few days, as other chores (and fishing) are calling.

But for folks who know how to work directly off a GitHub repo, you can go here: https://github.com/donhoffman/indigo-caddx-plugin

I have stuck with SemVer vs CalVer, so new version is 2.0.1. The plugin ID and (AFAIK) all the internal state variables are unchanged, so you should be able to install this over the prior plugin without re-creating your devices (and re-install the prior plugin if things are not working... tho back-out was not tested).

As I mentioned earlier, I will be maintaining the 2.X.X version until such time as I have a v3. I will not be adding any new features or implementations of the many partially completed features in this version, but will endeavor to respond to fix any issue where it appears I have broken features in version 1.3.0. However, if you wish to add something I will endeavor to merge any well-formed PRs that are not too disruptive.

Please note: This is currently alpha quality code, so do not install at this point if you are using this plugin for key security functions.

One important bit of behavior I changed... The plugin no longer sets the panel clock on startup. I was not comfortable with having panel configuration side-effects on something as common as a plugin or Indigo restart. You can still invoke this function from the plugin's menu manually or in a periodic Action.

Installed just fine but I am getting an error with my motion detector.

Aug 23, 2022 at 11:19:17 PM
Caddx Security System -- create variable: description :
folderId : 1894940605
globalProps : MetaProps : (dict)
id : 1988356459
name : partitionState
pluginProps : com.ians.caddx : (dict)
readOnly : False
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
value : :
Error device "Caddx_zone 005 - MOTION DETECTOR" state key onOffState not defined (ignoring update request)

Installed just fine but I am getting an error with my motion detector.

Aug 23, 2022 at 11:19:17 PM
Caddx Security System -- create variable: description :
folderId : 1894940605
globalProps : MetaProps : (dict)
id : 1988356459
name : partitionState
pluginProps : com.ians.caddx : (dict)
readOnly : False
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
value : :
Error device "Caddx_zone 005 - MOTION DETECTOR" state key onOffState not defined (ignoring update request)

Can you give me some steps to reproduce? I have several motions in my installation, so may be able to reproduce here.

Motio Error--

Not sure what steps to reproduce. Installed new plugin and get error. My guess is that when the motion detector sensor motion I get the error but now sure otherwise. It never occurred with the prior plug-in..

What can I send you to help determine the issue - logs. If so let me know which specifics.

Motio Error--

Not sure what steps to reproduce. Installed new plugin and get error. My guess is that when the motion detector sensor motion I get the error but now sure otherwise. It never occurred with the prior plug-in..

What can I send you to help determine the issue - logs. If so let me know which specifics.

The text snippet you sent; where did it come from? The log? Formatting does not appear to be anything generated by the plugin.

I would suggest turning on debug for the plugin, then walk in front of the motion detector. Then send all the log entries prefixed with "Caddx Security System".

Do you see any issues with other zones?

Below is what I see in log when I walk in front of motion with debugging on, for example. You see the zone trigger, the go back to normal. Up in the Main window you would see the little dot next to the zone go green briefly.

Code: Select all

   Caddx Security System           processing message:         Zone Status Message,  zone: 14,  length: 8
   Caddx Security System Debug     zoneStatusMessage:        zone status message dictionary: ['08', '84', '0d', '01', '58', '53', 'f0', '01', '00']
   Caddx Security System Debug     zoneStatusMessage:        zone status message bit map dictionary: ['00000001', '01011000', '01010011', '11110000', '00000001', '00000000']
   Caddx Security System Debug     zoneStatusMessage:        zone group type '27',  Perimeter Alarm (activity monitor)  dictionary: '010110000101001111110000'
   Caddx Security System           update zone status:        device configuration ui records successfully updated with zone status message:  zone: 14
   Caddx Security System           update zone status:        device state records successfully updated with zone status message:  zone: 14
   Caddx Security System           zone 014:          'Triggered!' {Offiice PIR }
   Caddx Security System           update zone status:        zoneState device state value successfully updated with zone status message:  zone: 14
   Caddx Security System Debug     sendMsg:           >> sent message: 1d,  ACK,  bytearray(b'\x01\x1d\x1e\x1f')
   Caddx Security System           processing message:         Zones Snapshot Message,  block address: 0,  group: zone 1 - zone 16
   Caddx Security System Debug     zoneSnapshotMessage:        zone snapshot message dictionary: ['0a', '85', '00', '00', '00', '01', '01', '10', '00', '10', '00']
   Caddx Security System Debug     zoneSnapshotMessage:        zone snapshot message bit map dictionary: ['00000000', '00000000', '00000001', '00000001', '00010000', '00000000', '00010000', '00000000']
   Caddx Security System Debug     sendMsg:           >> sent message: 1d,  ACK,  bytearray(b'\x01\x1d\x1e\x1f')
   Caddx Security System           processing message:         Zone Status Message,  zone: 14,  length: 8
   Caddx Security System Debug     zoneStatusMessage:        zone status message dictionary: ['08', '84', '0d', '01', '58', '53', 'f0', '00', '00']
   Caddx Security System Debug     zoneStatusMessage:        zone status message bit map dictionary: ['00000001', '01011000', '01010011', '11110000', '00000000', '00000000']
   Caddx Security System Debug     zoneStatusMessage:        zone group type '27',  Perimeter Alarm (activity monitor)  dictionary: '010110000101001111110000'
   Caddx Security System           update zone status:        device configuration ui records successfully updated with zone status message:  zone: 14
   Caddx Security System           update zone status:        device state records successfully updated with zone status message:  zone: 14
   Caddx Security System           zone 014:          'Normal!' {Offiice PIR }
   Caddx Security System           update zone status:        zoneState device state value successfully updated with zone status message:  zone: 14
   Caddx Security System Debug     sendMsg:           >> sent message: 1d,  ACK,  bytearray(b'\x01\x1d\x1e\x1f')
   Caddx Security System           processing message:         Zones Snapshot Message,  block address: 0,  group: zone 1 - zone 16
   Caddx Security System Debug     zoneSnapshotMessage:        zone snapshot message dictionary: ['0a', '85', '00', '00', '00', '01', '01', '10', '00', '00', '00']
   Caddx Security System Debug     zoneSnapshotMessage:        zone snapshot message bit map dictionary: ['00000000', '00000000', '00000001', '00000001', '00010000', '00000000', '00000000', '00000000']
   Caddx Security System Debug     sendMsg:           >> sent message: 1d,  ACK,  bytearray(b'\x01\x1d\x1e\x1f')



Motio Error--

Not sure what steps to reproduce. Installed new plugin and get error. My guess is that when the motion detector sensor motion I get the error but now sure otherwise. It never occurred with the prior plug-in..

What can I send you to help determine the issue - logs. If so let me know which specifics.

Ah, I have a guess. Do you have any triggers on that zone where you put the state into a variable? If so, can you tell me exactly which Device State you are inserting?

Although I just did some trigger tesst where I wrote the both the zoneState and onOffSate into a variable, and it worked here.

I do not have any triggers set....

Here is the info from debug mode..

Aug 24, 2022 at 12:35:58 PM
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '00', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000000', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '00', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000000', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partitions Snapshot Message, partition 1 - 8, length: 9
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message dictionary: ['09', '87', '01', '02', '02', '02', '02', '02', '02', '02']
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message bit map dictionary: ['00000001', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010']
Caddx Security System update partition snapshot: device state records successfully updated with partition snapshot message: all active partitions:
Caddx Security System Debug updateAlarmDisplay: display message byte: 00000001
Caddx Security System partition 1: 'Not Ready!'
Caddx Security System keypad 1: LCD message line 1: "System Not Ready", LCD message line 2: "For help, press ->"
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zone Status Message, zone: 5, length: 8
Caddx Security System Debug zoneStatusMessage: zone status message dictionary: ['08', '84', '04', '01', '58', '13', 'e0', '01', '00']
Caddx Security System Debug zoneStatusMessage: zone status message bit map dictionary: ['00000001', '01011000', '00010011', '11100000', '00000001', '00000000']
Caddx Security System Debug zoneStatusMessage: zone group type 'no zone group match', no zone group match dictionary: '010110000001001111100000'
Caddx Security System update zone status: device configuration ui records successfully updated with zone status message: zone: 5
Caddx Security System update zone status: device state records successfully updated with zone status message: zone: 5
Error device "Caddx_zone 005 - MOTION DETECTOR" state key onOffState not defined (ignoring update request)
Caddx Security System zone 005: 'Triggered!' {MOTION DETECTOR }
Caddx Security System update zone status: zoneState device state value successfully updated with zone status message: zone: 5
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zones Snapshot Message, block address: 0, group: zone 1 - zone 16
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message dictionary: ['0a', '85', '00', '00', '00', '01', '00', '00', '00', '80', '00']
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message bit map dictionary: ['00000000', '00000000', '00000001', '00000000', '00000000', '00000000', '10000000', '00000000']
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '04', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000100', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '04', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000100', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partitions Snapshot Message, partition 1 - 8, length: 9
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message dictionary: ['09', '87', '03', '02', '02', '02', '02', '02', '02', '02']
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message bit map dictionary: ['00000011', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010']
Caddx Security System update partition snapshot: device state records successfully updated with partition snapshot message: all active partitions:
Caddx Security System Debug updateAlarmDisplay: display message byte: 00000011
Caddx Security System partition 1: 'Disarmed!'
Caddx Security System keypad 1: LCD message line 1: "System Ready", LCD message line 2: "Type code to arm"
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zone Status Message, zone: 5, length: 8
Caddx Security System Debug zoneStatusMessage: zone status message dictionary: ['08', '84', '04', '01', '58', '13', 'e0', '00', '00']
Caddx Security System Debug zoneStatusMessage: zone status message bit map dictionary: ['00000001', '01011000', '00010011', '11100000', '00000000', '00000000']
Caddx Security System Debug zoneStatusMessage: zone group type 'no zone group match', no zone group match dictionary: '010110000001001111100000'
Caddx Security System update zone status: device configuration ui records successfully updated with zone status message: zone: 5
Caddx Security System update zone status: device state records successfully updated with zone status message: zone: 5
Error device "Caddx_zone 005 - MOTION DETECTOR" state key onOffState not defined (ignoring update request)
Caddx Security System zone 005: 'Normal!' {MOTION DETECTOR }
Caddx Security System update zone status: zoneState device state value successfully updated with zone status message: zone: 5
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zones Snapshot Message, block address: 0, group: zone 1 - zone 16
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message dictionary: ['0a', '85', '00', '00', '00', '00', '00', '00', '00', '80', '00']
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message bit map dictionary: ['00000000', '00000000', '00000000', '00000000', '00000000', '00000000', '10000000', '00000000']
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')

Aug 24, 2022 at 12:36:21 PM
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '00', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000000', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partitions Snapshot Message, partition 1 - 8, length: 9
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message dictionary: ['09', '87', '01', '02', '02', '02', '02', '02', '02', '02']
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message bit map dictionary: ['00000001', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010']
Caddx Security System update partition snapshot: device state records successfully updated with partition snapshot message: all active partitions:
Caddx Security System Debug updateAlarmDisplay: display message byte: 00000001
Caddx Security System partition 1: 'Not Ready!'
Caddx Security System keypad 1: LCD message line 1: "System Not Ready", LCD message line 2: "For help, press ->"
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zone Status Message, zone: 5, length: 8
Caddx Security System Debug zoneStatusMessage: zone status message dictionary: ['08', '84', '04', '01', '58', '13', 'e0', '01', '00']
Caddx Security System Debug zoneStatusMessage: zone status message bit map dictionary: ['00000001', '01011000', '00010011', '11100000', '00000001', '00000000']
Caddx Security System Debug zoneStatusMessage: zone group type 'no zone group match', no zone group match dictionary: '010110000001001111100000'
Caddx Security System update zone status: device configuration ui records successfully updated with zone status message: zone: 5
Caddx Security System update zone status: device state records successfully updated with zone status message: zone: 5
Error device "Caddx_zone 005 - MOTION DETECTOR" state key onOffState not defined (ignoring update request)
Caddx Security System zone 005: 'Triggered!' {MOTION DETECTOR }
Caddx Security System update zone status: zoneState device state value successfully updated with zone status message: zone: 5
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zones Snapshot Message, block address: 0, group: zone 1 - zone 16
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message dictionary: ['0a', '85', '00', '00', '00', '01', '00', '00', '00', '80', '00']
Caddx Security System Debug zoneSnapshotMessage: zone snapshot message bit map dictionary: ['00000000', '00000000', '00000001', '00000000', '00000000', '00000000', '10000000', '00000000']
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partition Status Message, partition: 1, length: 9
Caddx Security System Debug partitionStatusMessage: partition status message dictionary: ['09', '86', '00', '20', '00', '00', '40', '01', '04', 'c2']
Caddx Security System Debug partitionStatusMessage: partition status message bit map dictionary: ['00100000', '00000000', '00000000', '01000000', '00000001', '00000100', '11000010']
Caddx Security System update partition status: device state records successfully updated with partition status message: partition: 1
Caddx Security System update keypad status: device state records successfully updated with partition status message: keypad: 1
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Partitions Snapshot Message, partition 1 - 8, length: 9
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message dictionary: ['09', '87', '03', '02', '02', '02', '02', '02', '02', '02']
Caddx Security System Debug partitionSnapshotMessage: snapshot partition message bit map dictionary: ['00000011', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010', '00000010']
Caddx Security System update partition snapshot: device state records successfully updated with partition snapshot message: all active partitions:
Caddx Security System Debug updateAlarmDisplay: display message byte: 00000011
Caddx Security System partition 1: 'Disarmed!'
Caddx Security System keypad 1: LCD message line 1: "System Ready", LCD message line 2: "Type code to arm"
Caddx Security System Debug sendMsg: >> sent message: 1d, ACK, bytearray(b'\x01\x1d\x1e\x1f')
Caddx Security System processing message: Zone Status Message, zone: 5, length: 8
Caddx Security System Debug zoneStatusMessage: zone status message dictionary: ['08', '84', '04', '01', '58', '13', 'e0', '00', '00']
Caddx Security System Debug zoneStatusMessage: zone status message bit map dictionary: ['00000001', '01011000', '00010011', '11100000', '00000000', '00000000']
Caddx Security System Debug zoneStatusMessage: zone group type 'no zone group match', no zone group match dictionary: '010110000001001111100000'
Caddx Security System update zone status: device configuration ui records successfully updated with zone status message: zone: 5

Could it be one of my config settings for #210 or #211 segment

That was helpful. I don’t think it is your panel config, but am not at home to check against mine. One thing that comes to mind is that the Indigo device associated with this zone is missing a state variable (as is implied by the message). Although you did not see an error with the old 1.0 Indigo API, it is possible Indigo is more strict in the 3.0 Indigo API.

Also, it appears that this message comes from the plugin host, not the plugin itself.

Until I get back home later today here are a few things to try:

- Run “Synchronize Database” from the Caddx plugin menu. Run test.
- Recreate the Indigo device for that zone. Run test.

Are all your other zones working OK?