New Binding for Caddx alarm panels [NX584, NX8e, ...]

pfew this issue becomes a real struggle to me! :wink:

When adding a thing in the Paper UI, all channels are added. Can I prevent that every channel is selected by default before adding?

I researched further witch messages are created in the logfile by adding a zone, and, by triggering a zone. This is the outcome (type is juist FYI):

zone zone status message zone status request type
1 0 0 Smoke
2 1 1 Smoke
3 2 2 Smoke
4 3 3 Smoke
5 4 4 Smoke
6 5 5 Smoke
7 6 6 Smoke
8 7 7 Smoke
9 0 8 Smoke
10 1 9 Smoke
11 2 10 Smoke
12 3 11 Contact
13 4 12 Contact
14 5 13 Contact
15 6 14 Contact
16 7 15 Contact
17 0 16 Contact
18 1 17 Contact
19 2 18 Contact
20 3 19 Contact
21 4 20 Contact
22 5 21 Contact
23 6 22 Contact
24 7 23 Contact
25 0 24 Contact
26 1 25 Contact
27 2 26 Contact
28 3 27 Contact
29 4 28 PIR
30 5 29 PIR
31 6 30 PIR
32 7 31 PIR
33 0 32 PIR
34 1 33 PIR
35 2 34 PIR
36 3 35 Smoke
37 4 36 PIR
38 5 37 PIR
39 6 38 Contact
40 7 39 Contact
41 0 40 PIR
42 1 41 Smoke
43 2 42 Contact
44 3 43 Contact

Then, I discovered, when re-enabling the thing, a Zone-update is done. For example, when disabling the bridge, opening the door, and then enable the bridge, Channel ‘Faulted’ changes from CLOSED to OPEN.
(I assume ‘faulted’ is equal to ‘contact’ of the zone…)

My setup consists of a NX-8E with 3 NX-216 16 Zone hardwire expansions and 3 NX-148 keypads

Many thanks for your support, because of the odds, this must become a success! :slight_smile:

Hi,

I don’t know either. I opened a new question if there is something I can specify in the binding.

Can you send me the debug log when you open/close a few Doors and walk through a room with a PIR? I want to see the actual bytes that are being sent from the panel. There is no need to disable/enable the thing. When any zone changes status, the panel sends the Zone Update Message by itself.

Thanks

Yes of course, hereby:

22:52:16.404 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:16.405 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 04 80 7D 5E AE
22:52:16.411 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:16.411 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from OFF to ON
22:52:16.412 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:16.458 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:16.459 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 13 02 02 02 02 02 02 01 B0 ED
22:52:16.461 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:16.462 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:16.509 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
22:52:16.510 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 06 01 01 05 C4 00 00 5E 04
22:52:16.512 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:16.513 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:16.556 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:16.557 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 10 00 00 00 B0 5F
22:52:16.564 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:16.565 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:16.957 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:16.958 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 80 7A A6
22:52:16.966 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from ON to OFF
22:52:16.969 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:16.970 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:17.008 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:17.009 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
22:52:17.014 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:17.015 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:17.060 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 0]
22:52:17.061 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 00 01 01 05 C4 00 00 58 D9
22:52:17.072 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:17.074 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:17.107 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:17.108 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 02 01 00 00 00 00 00 11 11 B4 F2
22:52:17.112 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:17.113 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:18.908 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:18.909 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 04 80 7D 5E AE
22:52:18.914 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from OFF to ON
22:52:18.915 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:18.916 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:18.959 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:18.960 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 13 02 02 02 02 02 02 01 B0 ED
22:52:18.962 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:18.963 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.011 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 0]
22:52:19.012 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 00 01 01 05 C4 00 00 58 D9
22:52:19.018 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.020 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.057 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:19.059 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 02 00 00 00 00 00 00 11 11 B3 EA
22:52:19.066 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.067 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.458 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:19.459 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 80 7A A6
22:52:19.467 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from ON to OFF
22:52:19.470 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.471 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.510 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:19.511 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
22:52:19.516 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.517 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.561 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 5]
22:52:19.562 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
22:52:19.564 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.565 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:19.608 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:19.609 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 10 00 10 00 C0 7F
22:52:19.614 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:19.615 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:24.311 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:24.312 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 04 80 7D 5E AE
22:52:24.318 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:24.319 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from OFF to ON
22:52:24.319 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:24.362 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:24.363 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 13 02 02 02 02 02 02 01 B0 ED
22:52:24.365 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:24.366 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:24.413 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 5]
22:52:24.414 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
22:52:24.416 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:24.417 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:24.460 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:24.461 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 10 00 00 00 B0 5F
22:52:24.468 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:24.469 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:25.758 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:52:25.760 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 80 7A A6
22:52:25.765 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:25.767 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:25.767 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from ON to OFF
22:52:25.812 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:52:25.813 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
22:52:25.815 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:25.816 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:25.864 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 5]
22:52:25.865 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
22:52:25.866 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:25.867 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:52:25.910 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:52:25.911 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 10 00 10 00 C0 7F
22:52:25.918 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:52:25.919 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

First walkthrough:
Zone 6 = PIR zone 31
Zone 0 = PIR zone 33
Zone 5 = PIR zone 30

22:59:12.803 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 4]
22:59:12.804 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 04 01 01 05 C4 00 00 5C F5
22:59:12.806 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:12.807 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:12.857 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:59:12.858 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 02 00 00 01 00 00 00 11 11 B4 F0
22:59:12.863 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:12.864 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:13.604 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:59:13.605 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 40 01 00 80 79 A2
22:59:13.611 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:13.612 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:13.612 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from ON to OFF
22:59:13.656 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:59:13.657 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
22:59:13.662 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:13.663 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:13.709 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 7]
22:59:13.710 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 07 01 01 05 C4 00 00 5F 0B
22:59:13.711 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:13.712 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:13.751 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:59:13.752 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 00 80 00 00 00 00 00 00 10 20 B9
22:59:13.795 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:13.796 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:15.660 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 4]
22:59:15.661 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 04 01 01 05 C4 00 00 5C F5
22:59:15.663 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:15.664 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:15.703 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:59:15.704 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 02 00 00 00 00 00 00 11 11 B3 EA
22:59:15.708 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:15.709 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:17.056 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:59:17.057 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 40 01 04 80 7D 5D AA
22:59:17.062 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:17.064 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:17.064 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from OFF to ON
22:59:17.108 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
22:59:17.109 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 13 02 02 02 02 02 02 01 B0 ED
22:59:17.111 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:17.112 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:17.161 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 7]
22:59:17.162 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 07 01 01 05 C4 00 00 5F 0B
22:59:17.164 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:17.165 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:17.204 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:59:17.205 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 00 80 00 00 00 00 00 00 00 10 A9
22:59:17.212 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:59:17.213 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:59:20.305 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
22:59:20.306 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 40 01 00 80 79 A2
22:59:20.313 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_04e51230_partition1_partition_ready_to_arm changed from ON to OFF

Another test:
Zone 4 = PIR Zone 37
Zone 7 = Contact Zone 16

Regards,

Johan.

The panel sends an incorrect zone number.
For example

22:52:16.510 <-: 7E 08 84 ***06*** 01 01 05 C4 00 00 5E 04

Thε 06 should have been 1E if it is PIR zone 31.

I had a look through the manual of the NX-216E.
On the board there are some dip-switches which designate the starting zone number of the expander card. Can you check that the dip switches are set correctly? [Be careful not to change anything in the panel, it needs to be powered off first] (If you don’t understand what i’m talking about, you need the help of an installer)

From what i gathered of your installation you should have for DIP1-DIP6:

1st card: ON OFF OFF OFF OFF OFF
2nd card: OFF ON OFF OFF OFF OFF
3rd card: OFF OFF ON OFF OFF OFF

If the NX-216 cards have all the DIP switches on OFF that would explain why the numbering is not correct. Unfortunately i do not have a NX-216 and cannot verify/test my hypothesis.

Hi @jossuar,

Thanks for investigating! I installed the whole system by myself. I’ve checked the dip-switch settings, but the’re conform the manual you’re reffering.

I’ve specially imported this panel from the USA (I live in the Netherlands) for the compatibility with the Vera controller. That was working several years till I was fed up with the Vera ecosystem.

I wonder where the problem is, can I change something else in the communication settings, or is there some other misunderstanding between the bridge and panel? :-S

1
2
https images app

Hi @Jo0p,

About not linking all channels by default in PaperUI, you have to turn off PaperUI simple mode and then link the desired channels one by one.

For the problem with the zone number I can only hypothesize.
The binding does interpret the data from the panel. If the panel does not send the correct info, then there is nothing i can do on the binding side.

I had also a look on the programming of the NX-8E.
The DIP switch settings for the NX-216E I posted above were wrong.

According also to the NX-8E manual, they should be:

1st card: ON  OFF OFF OFF OFF OFF
2nd card: ON  ON  OFF OFF OFF OFF
3rd card: ON  OFF ON  OFF OFF OFF

Can you confirm?

Also check if on the panel zone doubling is enabled and there is an overlap on the zones from the panel and the expander cards.

If the DIP switches are correctly set, I would try with “divide and conquer” on the panel side. E.g. disconnect the two expander cards, leave only the one connected and check what the panel sends. etc.

Another idea is to ask in an alarm forum. (I don’t know of any).

Hi Jossuar,

Yes, the dipswitches are all right, according to the manual (I didn’t mention the incorrect overview in your post :slight_smile: ). When it was not, also the alarm panel itself doesn’t work properly either


The 3rd card has only 8 zone’s as max (dip4) but I changed it.

Now it’s time for rigourus countermeasures. Wil disable soms expander card what you suggest. Must find some time to do that.

Thanks for your support so far. I’ll let you know.

Johan.

Just a note. dip4 is not for disabling the upper 8 zones, it is dip6 which is unpopulated.

Just out of curiosity, what module numbers are enrolled on the below drop down on your installation?

Hi
I have installed the latest version of th eBinding. Configured for the correct serial port etc (Windows 10).
Caddx Bridge shows “Online” if I use ASCII.

However when I try autodiscover nothing is found.

If I manually add things (Zone/Partition) they show Offline for ages and sometimes come ONLINE.

New to OpenHab etc, so not sure if I am missing something.

Fairly sure panel is configured correctly as I previously used HomeSeer with Rien du Preez addon.

Thanks
Mark

Hi
Hoping @jossuar ossuar will be able to help as I have now made progress and have my system working for informational purpoases but would liek to be able to send commands to the panel - which I am having no success with.

I have set a rule as follows:

rule "Chime when STAY Pressed"
when
    Item Partition1_Stay  received command ON
then
if (Partition1_ReadyToArm.state == ON) {
    logWarn("actions", "Ready to ARM is ON")
}
else {
    val actions = getActions("caddx","caddx:zone:thebridge:partition1")
    if (null === actions) {
        logWarn("actions", "Actions not found, check thing ID for bridge")
        return
    }
    logWarn("actions", "Ready to ARM is ON")
    actions.chime()
}
end

Using

caddx.things as folows:

Bridge caddx:bridge:thebridge  "Bridge"                   [ protocol="Ascii", serialPort="COM1", baudrate=9600 ] {
    Thing partition partition1 "Main House Alarm"         [ partitionNumber=1 ]
    Thing zone      zone1      "MAG Front Door 01"        [ zoneNumber=1 ]
    Thing zone      zone2      "MAG Kitchen Door 02"      [ zoneNumber=2 ]
    Thing zone      zone3      "PIR Kitchen 03"           [ zoneNumber=3 ]
    Thing zone      zone4      "PIR Lounge 04"            [ zoneNumber=4 ]
    Thing zone      zone5      "PIR Garage 05"            [ zoneNumber=5 ]
    Thing zone      zone6      "PIR Main Bedroom 06"      [ zoneNumber=6 ]
    Thing zone      zone17     "PIR Dining Room 17"       [ zoneNumber=17 ]
    Thing zone      zone23     "PIR Passage 23"           [ zoneNumber=23 ]

caddx.items as follows:

Group:Contact:OR(OPEN,CLOSED)  MotionSensors1   "Motion Sensors [%s]"   <motion>
Group:Contact:OR(OPEN,CLOSED)  Windows1         "Doors [%s]"            <door>

Group:Contact:OR(OPEN,CLOSED)  MotionSensors2   "Motion Sensors [%s]"   <motion>
Group:Contact:OR(OPEN,CLOSED)  Windows2         "Doors [%s]"            <door>

Group:Contact:OR(OPEN,CLOSED)  MotionSensors3   "Motion Sensors [%s]"   <motion>
Group:Contact:OR(OPEN,CLOSED)  Windows3         "Doors [%s]"            <door>

Group:Contact:OR(OPEN,CLOSED)  MotionSensors4   "Motion Sensors [%s]"   <motion>
Group:Contact:OR(OPEN,CLOSED)  Windows4         "Doors [%s]"            <door>

Contact   MAG_Front_Door_01     "MAG Front Door 01 [%s]"	<door>       (Windows1)  	{ channel="caddx:zone:thebridge:zone1:zone_faulted" }
Contact   MAG_Kitchen_Door_02   "MAG Kitchen Door 02 [%s]"      <door>       (Windows1)          { channel="caddx:zone:thebridge:zone2:zone_faulted" }
Contact   PIR_Kitchen_03        "PIR Kitchen 03 [%s]"           <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone3:zone_faulted" }
Contact   PIR_Lounge_04         "PIR Lounge 04 [%s]"            <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone4:zone_faulted" }
Contact   PIR_Garage_05         "PIR Garage 05 [%s]"            <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone5:zone_faulted" }
Contact   PIR_Main_Bedroom_06   "PIR Main Bedroom 06 [%s]"      <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone6:zone_faulted" }
Contact   PIR_Diningroom_17     "PIR Diningroom 17 [%s]"        <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone17:zone_faulted" }
Contact   PIR_Passage_23        "PIR Passage 23 [%s]"           <motion>       (MotionSensors1)  { channel="caddx:zone:thebridge:zone23:zone_faulted" }

Switch    Partition1_Armed      "Armed [%s]"            <house>   { channel="caddx:partition:thebridge:partition1:partition_armed" }
Switch    Partition1_EntryGuard "Entry Guard [%s]"      <house>   { channel="caddx:partition:thebridge:partition1:partition_entryguard" }
Switch    Partition1_ReadyToArm "Ready to Arm [%s]"     <house>   { channel="caddx:partition:thebridge:partition1:partition_ready_to_arm" }
Switch    Partition1_PreviousAlarm "Previous Alarm [%s]"     <house>   { channel="caddx:partition:thebridge:partition1:partition_partition_previous_alarm" }
Switch    Partition1_Stay       "Arm is STAY [%s]"      <house>   { autoupdate="false" }

and .sitemap:

sitemap alarm label="Alarm at 59" {
    Frame label="Main House" {
    Text item=Partition1_Armed
    Text item=Partition1_EntryGuard
    Text item=Partition1_ReadyToArm
//    Text item=Partition1_PreviousAlarm
//    Switch item=Partition1_Armed
//    Switch item=Partition1_EntryGuard
     Switch item=Partition1_Stay mappings=[ON="STAY"]

    Text item=MotionSensors1
        Text label="Motion Sensors (detailed)" {
            Text item=PIR_Kitchen_03
            Text item=PIR_Lounge_04
            Text item=PIR_Garage_05
	    Text item=PIR_Main_Bedroom_06
	    Text item=PIR_Diningroom_17
	    Text item=PIR_Passage_23
        }

    Text item=Windows1
        Text label="Windows (detailed)" {
            Text item=MAG_Front_Door_01
            Text item=MAG_Kitchen_Door_02
        }
    }

I am however now able to get the rule to send any command to the panel as the getActions() returns NULL

2020-09-16 17:21:22.621 [WARN ] [lipse.smarthome.model.script.actions] - Actions not found, check thing ID for bridge

I assume this is because I am using the incorrect thing?

Tried to follow the examples at https://github.com/jossuar/openhab2-addons/tree/caddx_actions/bundles/org.openhab.binding.caddx#rule-actions however the rule examaple does not tie in with the .things and .items in the article.

Would appreciate any guidance as to what I am doing wrong and hwo I go about sending commands such as stay(), exit(), disarm(String pin) to a specific partition.

Many Thanks
Mark

Mark, I think your issue lies with this statement. If you wish to call an action on a partition thing, try this instead:

val actions = getActions("caddx","caddx:partition:thebridge:partition1")

@manjestic Thank you. Tried that but still get the same error:

 2020-09-17 06:03:54.646 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'caddx.rules'
2020-09-17 06:03:56.646 [WARN ] [lipse.smarthome.model.script.actions] - Actions not found, check thing ID for bridge

@jossuar, @manjestic So I have no redone my entire config using the discovered things and linked items etc. Have my interface back up and running fully - updating Zone faults, Ready to Arm, Armed, Entry Guard etc.

Have tried the rule again however edited to use the eaxt same syntax as the exapmple provided other than using my Bridge ID:

rule "Arm in STAY"
when
    Item Partition1_Stay  received command ON
then
if (Partition1_ReadyToArm.state == OFF) {
    logWarn("actions", "Ready to ARM is OFF")
}
else {
    val actions = getActions("caddx","caddx:zone:e59e4935:zone5")
    if (null === actions) {
        logWarn("actions", "Actions not found, check thing ID for bridge")
        return
    }
    logWarn("actions", "Ready to ARM is ON" + actions)
    actions.chime()
}
end

However still no result from getActions()

2020-09-17 11:47:42.458 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'caddx.rules'
2020-09-17 11:48:10.474 [WARN ] [lipse.smarthome.model.script.actions] - Actions not found, check thing ID for bridge

ANY ides would be greatly appreciated.

Mark

Hi @Mark_VG,

did you manually install the binding from the link in the 1st post above or do you use the binding which is bundled with the openhab distribution?

@jossuar Hi. I added the file from the link above to the addons folder - but seemed to be the same version as I had.

New to this - can you tell me how to make sure I am running the downloaded one?

On what OS you running openhab?
What openhab version? [openahb-cli info]
Did you install the binding from the PaperUI?

Running on Windows 10
INFO:

Karaf
Karaf version 4.2.7
Karaf home C:\openHAB2\runtime
Karaf base C:\openHAB2\userdata
OSGi Framework org.eclipse.osgi-3.12.100.v20180210-1608

JVM
Java Virtual Machine OpenJDK 64-Bit Server VM version 25.265-b11
Version 1.8.0_265
Vendor Azul Systems, Inc.
Pid 6956
Uptime 1 hour 49 minutes
Process CPU time 2 minutes
Process CPU load 0.25
System CPU load 0.50
Open file descriptors -1
Max file descriptors -1
Total compile time 1 minute
Threads
Live threads 138
Daemon threads 74
Peak 181
Total started 2223
Memory
Current heap size 54,092 kbytes
Maximum heap size 466,432 kbytes
Committed heap size 179,712 kbytes
Pending objects 0
Garbage collector Name = ‘PS Scavenge’, Collections = 72, Time = 1.650 seconds
Garbage collector Name = ‘PS MarkSweep’, Collections = 4, Time = 1.162 seconds
Classes
Current classes loaded 16,085
Total classes loaded 16,218
Total classes unloaded 133
Operating system
Name Windows 10 version 10.0
Architecture amd64
Processors 2

I did initially install the Binding from Paper UI, but then saw there was a version on your post and added that to the addons folder.

Not sure how to activate it though - was concerned about losing all my setting if I uninstalled from PaperUI?

Got this a well:

openhab> bundle:list -s |grep caddx
213 x Active x 80 x 2.5.8 x org.openhab.binding.caddx
228 x Active x 80 x 2.5.8.202009061514 x org.openhab.binding.caddx
openhab>

@jossuar THANK YOU…
It turns out I was running TWO versions at the same time. I uninstalled the Paper UI version using:

bundle:uninstall 213

So now:
openhab> bundle:list -s |grep caddx
228 x Active x 80 x 2.5.8.202009061514 x org.openhab.binding.caddx

And my keypad just chimed… So now on to the next step - ARMING and DISARMING :slight_smile: