GE Caddx NX-8E

Ian,

which version are you using.. the original or my modified version?

Karl

Karl,

I'm using your version since you refined the plugin, removed some errors, etc.

I'm using a network socket connect to a Perle IOLAN

Ian,
1. checking the connection: create a schedule/action request interface Config ... then check variable Caddx_securityState. That should do it

2. on # of zone. I do not see any limits (besides<999) in the plugin for # of zones. BUT I have only 8 zones, and no extension module, so I can not really test that


hope that helps.

Karl

Karl,

I will see what happens after the NX-216E module is installed. If it stays at 8 zones, then I guess there is a limit. If it goes to 24 then we know it is dynamic.

Karl,

So I did a quick and dirty install of the module. I'm awaiting the second cabinet to come in as I'm out of room in the current one. Three additional modules, the wiring, battery and serial to ethernet converter all just won't fit.

The system went into alarm state since no resistors or contact sensors are connected to the additional 16 zones. The system does see the board as the NX-595E using the DLX900 showed 5 modules whereas I had 4 before and the new one says hardwired expansion. I went to create a new devices in Indigo, I selected Caddx as the device and then security zone and it still only showed 8. I looked into the NX-595E via the webpage and it now shows an additional 8 zones. I'll have to see why it only sees 16 and not 24 are listed.

I also realize that this is not your plugin either, you just did some cleanup on it.

So I figured out why I can only see 16 zones.....the panel won't support more than 16. The NX-8V2 can support up to 48 and the NX-8E can support up to 192. So it looks like I'll need to upgrade to an NX-8E to get the zones. Too bad I already have a second cabinet coming as a new panel includes the cabinet. I guess I'll just take the current one down and put the new one up with the second cabinet. Then the fun or programming everything. At least this way if I had to I can put it back as long as I keep track of what cable bundle goes where. I guess in the beginning I just configure the new to work like the current. Once it is working move on to getting it how I want.

Now as to only being able to see 8 zones. Karl, in the menu display box, is it limited to only showing 8 zones? Maybe the plugin supports it but the menu display does not?

Will check tomorrow.


Sent from my iPhone using Tapatalk

Thank you.

Karl,

I took a look at the files in the plugin and it can support more than 8 zones; the default is just to show 8 zones.

https://www.dropbox.com/s/n7znyi3hwnrai6q/Caddx%20Security%20System-v-7.4.3.zip?dl=1

modified: all device dialog boxes go now from 1-32 instead of 1-8. hope that is enough.
not tested As I only have 8 zones /partitions


Karl

we can go to any number you like thats an easy mod

Karl,

Thank you. Hopefully I will be able to fully test it next weekend when the NX-8E has arrived and is in. This way it will get me to the 24 zone mark.

What an ordeal going with an NX-8E has been. The first order I placed, I never got shipping information, I called the company twice, left a message and even emailed. Never heard a thing, so I had to dispute the charge for the panel. I ordered from another company and received that panel a few weeks ago. I bought a spare adapter so I could perform some of the config before replacement. I would say that the NX-586E to connect to the panel makes things easier; it has three alligator clips; Pos, Com and Data. This allows the DLX900 (Windows) software to be used and the panel data can be read, written to, etc. Don't go with the NX-588E as that is the USB version but there are no new drivers to support current versions of Windows. Unless you really like programming through the keypad, I strongly suggest using the DLX900 software with the above mentioned adapter.

New panel was installed, all modules enrolled (NX-216E 16 zone expansion), NX-595E (Ethernet module) and the NX-584E (serial board). Enrollment is quick and easy with the software; you just tell it to enroll the modules. I could have used the onboard serial port, but you need a special cable and I already had the serial board, plus the serial board handles higher baud rates.

I also added a second cabinet which houses the serial port board, the Ethernet board and the serial-to-Ethernet adapter. The first cabinet has the battery, the panel, the wiring and the expansion module.

I still have to split the wiring out, so I'm still at 6 zones. I didn't have heat shrink tubing small enough for the wiring/resistor. Amazon will be delivering some tomorrow. I'll be using 21 of the 24 zones; so a big step up from just six zones. Right now the setup is a little ugly but will tidy it up when I split the wiring up. I'm also going to add a piece of conduit that goes between the cabinets.

Attached is what I have so far. Hopefully by the end of this coming weekend I'll have it all done and be able to test how the plugin works with 21 active zones.

I'm amazed at Caddx protocol in that it really takes very little bandwidth for the updates and the control. The original author of the plugin must have spent a lot of time going through the documentation to create it. In the past 24 hours 18KB of data has been received and 7KB transmitted. That is with a door being opened many times (dog likes to go in and out), a status update about every 15 minutes and the time and date being set.

Good job by Karl updating the plugin as well.

If this isn't an easy fix, then don't worry about it. I have seen this in my logs after I made a change that was not correct. I added an attic fire detector that also handles Rate of Raise (RoR). I thought it would act like a smoke detector but that was not the case, so I had to change the zone type from 8 to 24. The documentation wasn't descriptive as to the difference and 24 had the same verbiage but they added "manual" to it. The end result is the same, the fire LED will illuminate and the temporal siren works the same, the only difference seems to be that type 24 works like a normal door/window sensor instead of a smoke. So the below error started after the system went into alarm and that event was added alarm event log. I'm sure that event entry will be removed in due time. So eventually this will correct itself. If this is an easy fix, it might help others.

Code: Select all

May 6, 2019 at 6:53:47 PM
   Caddx Security System           log event 001:      data dictionary: {0: '0a', 1: '8a', 2: '01', 3: 'b9', 4: 'a5', 5: 'c8', 6: '00', 7: '05', 8: '06', 9: '12', 10: '35'}
   Caddx Security System           log event 001:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:53:47

May 6, 2019 at 6:54:57 PM
   Caddx Security System           log event 002:      data dictionary: {0: '0a', 1: '8a', 2: '02', 3: 'b9', 4: 'a4', 5: 'c8', 6: '00', 7: '05', 8: '06', 9: '12', 10: '36'}
   Caddx Security System           log event 002:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:54:57

May 6, 2019 at 6:56:10 PM
   Caddx Security System           log event 003:      data dictionary: {0: '0a', 1: '8a', 2: '03', 3: 'b9', 4: 'a5', 5: 'c8', 6: '00', 7: '05', 8: '06', 9: '12', 10: '37'}
   Caddx Security System           log event 003:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:56:10

May 6, 2019 at 6:56:52 PM
   Caddx Security System           log event 004:      data dictionary: {0: '0a', 1: '8a', 2: '04', 3: 'b9', 4: 'a4', 5: 'c8', 6: '00', 7: '05', 8: '06', 9: '12', 10: '38'}
   Caddx Security System           log event 004:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:56:52

May 6, 2019 at 7:00:15 PM
   Caddx Security System           log event 005:      data dictionary: {0: '0a', 1: '8a', 2: '05', 3: 'b9', 4: 'a5', 5: 'c8', 6: '00', 7: '05', 8: '06', 9: '12', 10: '3b'}
   Caddx Security System           log event 005:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   19:00:15

Event log history:

Code: Select all

May 6, 2019 at 7:33:43 PM
   Caddx Security System           
   Caddx Security System           Log Event History: (last 25 entries) . . .
   Caddx Security System           . . log event 163:      entering program mode: Security Panel,  address: 0,  partition: 1  ** 6/5/2019   18:33:31
   Caddx Security System           . . log event 165:      registering module: Hardwired Expander NX-216E (start zone 09),  address: 23,  partition: 1  ** 6/5/2019   18:33:47
   Caddx Security System           . . log event 168:      registering module: Keypad (1),  address: 192,  partition: 1  ** 6/5/2019   18:34:14
   Caddx Security System           . . log event 169:      registering module: Keypad (2),  address: 200,  partition: 1  ** 6/5/2019   18:34:15
   Caddx Security System           . . log event 170:      End Download,   ** 6/5/2019   18:34:15
   Caddx Security System           . . log event 171:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:34:31
   Caddx Security System           . . log event 172:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:41:48
   Caddx Security System           . . log event 173:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:42:29
   Caddx Security System           . . log event 174:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:44:07
   Caddx Security System           . . log event 175:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:44:38
   Caddx Security System           . . log event 176:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:46:32
   Caddx Security System           . . log event 177:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:46:48
   Caddx Security System           . . log event 178:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:47:43
   Caddx Security System           . . log event 179:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:48:32
   Caddx Security System           . . log event 180:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:48:40
   Caddx Security System           . . log event 181:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:49:23
   Caddx Security System           . . log event 182:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:50:23
   Caddx Security System           . . log event 183:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:50:42
   Caddx Security System           . . log event 184:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:51:07
   Caddx Security System           . . log event 000:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:51:46
   Caddx Security System           . . log event 001:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:53:47
   Caddx Security System           . . log event 002:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:54:57
   Caddx Security System           . . log event 003:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:56:10
   Caddx Security System           . . log event 004:      alarm event: (164)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   18:56:52
   Caddx Security System           . . log event 005:      alarm event: (165)  is out of range of event dictionary definitions byte 5: (device address 200),  byte 6: (partition 1)  ** 6/5/2019   19:00:15
   Caddx Security System           

its easy to add event type 164,, but what should it show?
here the If event type... with a dded 164. copied 168

Code: Select all

           if deventType == 138:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      Loss of Supervision (wireless): %s,  zone: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
            if deventType == 139:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      Loss of Supervision RESTORED (wireless): %s,  zone: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
            if deventType == 164:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      system DISARMED: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
                if self.plugin.enableSpeakPrompts:
                    indigo.server.speak(sayDisarmed)
            elif deventType == 168:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      system DISARMED: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
                if self.plugin.enableSpeakPrompts:
                    indigo.server.speak(sayDisarmed)
            elif deventType == 169:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      system ARMED: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
                if self.plugin.enableSpeakPrompts:
                    indigo.server.speak(sayArmed)
            elif deventType == 173:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      entering program mode: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
                # update enter keypad program mode states in plugin perferences
                self.plugin.pluginPrefs[u"isKeypadProgramming"] = True
                self.plugin.pluginPrefs[u"panelStatus"] = "Program Mode (enter)  ** %s " % self.timestamp()
                variableID = "Caddx_panelStatus"
                panelStatusVariable = (u"Program Mode (enter)  ** %s " % self.timestamp())
                self.updateVariable(variableID, panelStatusVariable)
            elif deventType == 174:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:        exiting program mode: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1),  dpartitionNumber , timeLogEvent)
                # update exit keypad program mode states in plugin perferences
                self.plugin.pluginPrefs[u"isKeypadProgramming"] = False
                self.plugin.pluginPrefs[u"panelStatus"] = "Program Mode (exit)  ** %s " % self.timestamp()
                variableID = "Caddx_panelStatus"
                panelStatusVariable = (u"Program Mode (exit)  ** %s " % self.timestamp())
                self.updateVariable(variableID, panelStatusVariable)
            elif deventType == 245:
                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      registering module: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1),  dpartitionNumber , timeLogEvent)
            elif deventType == 247:
                logEventMessagePrint = u"log event %s:      confirm alarm system time and date set: %s  ** %s" % (deventNumber, timeStamp, timeLogEvent)
            else:
                logEventMessagePrint = u"log event %s:      alarm event: (%s)  is out of range of event dictionary definitions byte 5: (device address %s),  byte 6: (partition %s)  ** %s" % (deventNumber, deventType, (dzoneUserDevice -1), dpartitionNumber, timeLogEvent)
                if self.plugin.alarmEventInfo or self.plugin.debug:
                    indigo.server.log(u"log event %s:      data dictionary: %s " % (deventNumber, dataDict))


need to change This:

Code: Select all

                eventDeviceDescription = self.messageLogDeviceAddressDict(dzoneUserDevice -1)
                logEventMessagePrint = u"log event %s:      system DISARMED: %s,  address: %s,  partition: %s  ** %s" % (deventNumber, eventDeviceDescription, (dzoneUserDevice -1), dpartitionNumber , timeLogEvent)
                if self.plugin.enableSpeakPrompts:
                    indigo.server.speak(sayDisarmed)


what would you like to have? see the other conditions. eg
logEventMessagePrint = u"log event %s: confirm alarm system time and date set: %s ** %s" % (deventNumber, timeStamp, timeLogEvent)
??


Karl

I think it had an issue with what was in the log. I just downloaded the log...it took awhile and it goes back to when I installed the panel back in December.

Code: Select all

Date   Time   Partition   Event   Description   
5/6/2019   4:42:01 PM   1   Alarm Zone 8   Attic - ROR   
5/6/2019   4:46:01 PM   1   *  Alarm restore Zone 8   Attic - ROR   

That appears to be what 164 and 165 are. They aren't numbered in the logs but what is around it is listed elsewhere and; this is the first time those two messages are in the logs which also goes with when that error from the plugin started.

Any ideas?