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

jossuar · April 3, 2021, 9:31am

here is the new binding: binding

An oversight from my part. I had the value 15 hard coded.
Now it should take the value defined for the keypad thing, you just need to put in the rule:

actions.enterTerminalMode ()

without a parameter.

I had put a restriction that the display location should be only one-digit long. (Removed now)
We have to try out some combinations i suppose. Like:

actions.sendKeypadTextMessage("0","My test ") 
actions.sendKeypadTextMessage("17","My test ")

The value of the display location can be between 0 - 255.
Also, when you do a test, paste also the log lines with the byte sequences, like:

17:50:20.008 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Keypad Terminal Mode Request
17:50:20.008 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 03 2C C0 0F FE 21
17:50:20.211 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:50:20.211 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F

Thanks for helping out with the debugging.

Mark_VG · April 3, 2021, 1:43pm

I have installed the new version:

246 | Active |  80 | 3.1.0.202104030926      | openHAB Add-ons :: Bundles :: Caddx Binding

It looks like the Terminal Mode timeout is now 0. I have it set to 120 on my Thing. Also tried sending a value via teh rule - same result:

15:31:28.626 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'Testing_Switch' received command ON
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Sending Messages
15:31:28.641 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:0, 0:77, 1:121, 2:32, 3:116, 4:101, 5:115, 6:116, 7:32
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Message1 Sent
15:31:28.641 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:8, 0:109, 1:101, 2:115, 3:115, 4:97, 5:103, 6:101, 7:32
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Message2 Sent
15:31:28.641 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:9, 0:49, 1:50, 2:51, 3:52, 4:53, 5:54, 6:55, 7:56
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Message3 Sent
15:31:28.641 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:17, 0:49, 1:50, 2:51, 3:52, 4:53, 5:54, 6:55, 7:56
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Message4 Sent
15:31:28.641 [WARN ] [org.openhab.core.model.script.actions] - Entering Terminal Mode
15:31:28.657 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - Address: 192, Seconds: 0
15:31:28.657 [WARN ] [org.openhab.core.model.script.actions] - Entered Terminal Mode
15:31:28.657 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Testing_Switch' changed from OFF to ON
15:31:30.653 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
15:31:30.653 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 00 4D 79 20 74 65 73 74 20 C0 A7
15:31:30.918 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
15:31:30.918 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
15:31:30.934 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
15:31:30.950 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 08 6D 65 73 73 61 67 65 20 08 01
15:31:31.106 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
15:31:31.106 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
15:31:31.137 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
15:31:31.137 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 09 31 32 33 34 35 36 37 38 A6 7B
15:31:31.309 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
15:31:31.309 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
15:31:31.330 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
15:31:31.330 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 11 31 32 33 34 35 36 37 38 AE C3
15:31:31.533 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
15:31:31.533 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
15:31:31.533 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Keypad Terminal Mode Request
15:31:31.533 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 03 2C C0 00 EF 12
15:31:31.658 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
15:31:31.658 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F

Would it not be more flexible to allow the timeout to be sent via the Rule and either failover to the value on the Thing, or remove the value from the thing entirely?

No problem at all.

Bit worried about getting the response back from the Keypad to the keypad_key_pressed (string) Item. While in terminal Mode (before this version) - the system seems to go in to “Expansion Trouble” if you try press a key. It then takes some fiddling to clear the error and back to normal operation., Have not tested much though, Just tried to press some numbers to see if the Item got updated.

Also BTW, when chnaging setting on the Keypad Thing - the binding has to be restarted to bring the Thing online. As soon as you edit it it goes OFFLINE.

jossuar · April 3, 2021, 2:58pm

Hi @Mark_VG,

here is a new binding binding

The configuration value was not read correctly. This should be fixed now.

Yes.
When i designed the binding, i did not even know what half of the settings meant. Now that I have a better understanding, this part can be redefined.

Don’t get that far.
Let’s first get the display working. Did you get anything in the 2nd line of the display?

If not try with: 0, 8 for the first line (working) and 16, 24 for the 2nd line. If the message is displayed, the keypad actions can be changed to sendFirstLine and sendSecondLine and the splitting to eight characters will be done from the binding. That way it would be easier to write the rules.

Because the terminalModeSeconds were send as 0? Let’s try again. [Sorry for the trouble]

Noted. Will look into it together with the rest of the online/offline handling.

Mark_VG · April 3, 2021, 3:38pm

Looks better:

17:34:59.199 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'Testing_Switch' received command ON
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Sending Messages
17:34:59.261 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:0, 0:77, 1:121, 2:32, 3:116, 4:101, 5:115, 6:116, 7:32
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Message1 Sent
17:34:59.261 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:8, 0:109, 1:101, 2:115, 3:115, 4:97, 5:103, 6:101, 7:32
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Message2 Sent
17:34:59.261 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:16, 0:49, 1:50, 2:51, 3:52, 4:53, 5:54, 6:55, 7:56
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Message3 Sent
17:34:59.261 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - keypad Address: 192, display location:24, 0:56, 1:55, 2:54, 3:53, 4:52, 5:51, 6:50, 7:49
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Message4 Sent
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Entering Terminal Mode
17:34:59.261 [DEBUG] [x.internal.handler.ThingHandlerKeypad] - Address: 192, Seconds: 90
17:34:59.261 [WARN ] [org.openhab.core.model.script.actions] - Entered Terminal Mode
17:34:59.292 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Testing_Switch' changed from OFF to ON
17:34:59.873 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
17:34:59.873 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 00 4D 79 20 74 65 73 74 20 C0 A7
17:35:00.082 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:35:00.082 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
17:35:00.098 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
17:35:00.114 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 08 6D 65 73 73 61 67 65 20 08 01
17:35:00.286 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:35:00.286 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
17:35:00.301 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
17:35:00.317 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 10 31 32 33 34 35 36 37 38 AD BA
17:35:00.489 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:35:00.489 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
17:35:00.519 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Send Keypad Text Message
17:35:00.519 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 0C 2B C0 00 18 38 37 36 35 34 33 32 31 B5 57
17:35:00.686 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:35:00.686 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F
17:35:00.686 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Keypad Terminal Mode Request
17:35:00.686 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 03 2C C0 5A 4A 6C
17:35:00.832 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Positive Acknowledge
17:35:00.832 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 01 1D 1E 1F

My Keypad Thing is set with a 90 second timeout.

Current Rule (had the starting positions all wrong (might be better to let the binding break it up?:

rule "Keypad Message Test"
when
    Item Testing_Switch received command ON
then
    val actions = getActions("caddx","caddx:keypad:e59e4935:Caddx_Alarm_Keypad")
    if (null === actions) {
        logWarn("actions", "Actions not found, check thing ID for bridge")
        return
    }
 
    logWarn("actions", "Sending Messages")  
    actions.sendKeypadTextMessage("0","My test ") 
    logWarn("actions", "Message1 Sent")
    actions.sendKeypadTextMessage("8","message ")
    logWarn("actions", "Message2 Sent") 
    actions.sendKeypadTextMessage("16","12345678") 
    logWarn("actions", "Message3 Sent")
    actions.sendKeypadTextMessage("24","87654321")
    logWarn("actions", "Message4 Sent")     
    logWarn("actions", "Entering Terminal Mode")
    actions.enterTerminalMode ()
    logWarn("actions", "Entered Terminal Mode")      
end

Should we continue this offline (Maybe PM?)

Will test some longer and later positions as per your request above and get back to you shortly.

Mark_VG · April 3, 2021, 3:45pm

Yes, this seems to be working now that I have the positions correct - had to write it out to get them right (thanks for the hint)

Are you going to restrict to two lines?

Don’t think so - but happy to test. I tried it when the Terminal Mode was still set top 15 seconds.

Mark_VG · April 26, 2021, 6:44pm

Hi @jossuar

Hope you well.

I have been working on a Graphical Widget, which will allow partition selection inside the widget and then arming, disarming, bypassing, etc. Still a work in progress but getting quite near to being able to share… Just quite time consuming as I am really not a programmer/coder by any stretch of the imagination. I have however got most of what I planned working, just cleaning up and adding some details. Will also then have to work on the layout (won’t be a responsive widget), so fixed size etc.

On another note…

How difficult would it be to implement some of the System Status channels related to Power of the system?

These do not appear to be in your implementation. Not sure if you had planned to add them at a later stage?

I would like to include these in my system for monitoring issues with the alarm system. In South Africa we have “load shedding”, so power can get switched off for various time slots when there is a shortage of power in the country.

Thanks
Mark

EDIT:

I just posted this:

jossuar · May 2, 2021, 9:56am

Hi @Mark_VG,

should be easy to add these channels. I’m currently on vacation and cannot access my installation. Will be back next week.

Jo0p · May 20, 2021, 7:25pm

Hi @jossuar,

I had some delay in upgrading my ‘production’ instance to OH3 due several other important things

Now, I upgraded to OH3.0.2 and have Caddx Binding 3.1.0.202104031452 running.

Unfortunately, I think the problem with the zones interpretation on the expander cards (>zone8) is not yet solved in this version.

These are the results when adding zone 30:

21:15:07.216 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Status Request [Zone: 30]
21:15:07.218 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 24 1D 43 6B
21:15:07.256 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 30]
21:15:07.257 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 04 1D 01 58 13 F0 00 00 86 13
21:15:07.261 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Name Request
21:15:07.263 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 23 1D 42 69
21:15:07.537 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Name Message
21:15:07.538 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 12 03 1D 50 49 52 20 6B 61 6E 74 6F 6F 72 20 20 20 20 20 DF A7

This is the result when hitting the zone:

21:09:16.741 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
21:09:16.743 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
21:09:16.748 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:16.750 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
21:09:16.782 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
21:09:16.784 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 00 00 10 00 B0 3F
21:09:16.799 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:16.801 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
21:09:19.092 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
21:09:19.094 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
21:09:19.097 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:19.099 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
21:09:19.133 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
21:09:19.135 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 00 00 00 00 A0 1F
21:09:19.152 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:19.154 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
21:09:20.541 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
21:09:20.542 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
21:09:20.545 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:20.546 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
21:09:20.602 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
21:09:20.603 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 00 00 00 00 10 00 B0 3F
21:09:20.620 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
21:09:20.621 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

Can you (or someone else ofcourse ) maybe track back what is going wrong?

Thank you very much for a reply!

Johan.

jossuar · May 25, 2021, 3:34pm

Hi @Jo0p,

the problem is clear from the log.

When the binding sends a “Zone Status Request” for Zone 30 your panel responds with “Zone Status Message” for Zone 30. Correct.
When the Zone 30 is triggered your panel sends a “Zone Status Message” for Zone 6. Incorrect.
When the Zone 30 is triggered your panel sends a “Zone Snapshot Message” with correct information for Zone 30. Correct.

With the current binding you should see Zone 6 changing when Zone 30 is triggered.

The solution is to ignore via a configuration the 2nd type of messages and handle only the 3rd type. I’m already half way through with the porting of the changes i had done in the past for the 2.5 binding.
Will inform when ready for testing.

Jo0p · May 25, 2021, 4:02pm

Hi @jossuar,

Thank you for the update, I can’t hardly wait
Good luck with your work!

jossuar · May 25, 2021, 4:40pm

Lol.

@Jo0p Here you are: binding [Totally untested, I will test later today]

There is a new configuration on the bridge: “Ignore Zone Status Transitions”. This should be set to true/enabled on your case.

Jo0p · May 25, 2021, 7:49pm

Wow, thanks for this on demand solution

De new switch is available. I think this version has some testing to do:
(also after restarting)

22:08:02.335 [DEBUG] [ddx.internal.handler.ThingHandlerZone] - handleCommand(): Command Received - caddx:zone:afdba8a490:zone30:zone_faulted REFRESH.
22:08:02.555 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Status Request [Zone: 30]
22:08:02.557 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 24 1D 43 6B
22:08:02.608 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 30]
22:08:02.609 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 04 1D 01 58 13 F0 00 02 88 15
22:08:02.615 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Name Request
22:08:02.617 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 23 1D 42 69
22:08:02.619 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'caddx:zone:afdba8a490:zone30' changed from OFFLINE to ONLINE
22:08:02.899 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Name Message
22:08:02.901 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 12 03 1D 50 49 52 20 6B 61 6E 74 6F 6F 72 20 20 20 20 20 DF A7
22:08:13.113 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
22:08:13.114 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
22:08:13.116 [DEBUG] [x.internal.handler.CaddxBridgeHandler] - Zone 6 Transition ignored.
22:08:13.118 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:08:13.119 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:08:13.154 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:08:13.155 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 08 00 00 00 10 00 B8 6F
22:08:13.171 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:08:13.173 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:08:16.912 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
22:08:16.913 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
22:08:16.915 [DEBUG] [x.internal.handler.CaddxBridgeHandler] - Zone 6 Transition ignored.
22:08:16.916 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:08:16.918 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
22:08:16.953 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
22:08:16.955 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 08 00 00 00 00 00 A8 4F
22:08:16.973 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
22:08:16.975 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

jossuar · June 6, 2021, 11:37am

Hi @Jo0p, @Mark_VG,

i did add to the binding a few changes that Mark has asked for. (New channels on the panel thing regarding AC status, corrected thing status initialization).

Johan, had you any chance to test the binding?

Latest Binding (for now)
Latest Documentation (for now)

Mark_VG · June 6, 2021, 12:11pm

Thanks Georgios.

Would I have to delete the Panel Thing and rediscover?

I have still not managed to get any more information from Caddx about the Messages etc. What state did you leave that in the binding? (Regarding the syntax to use to send messages to panel?)

Could you confirm what you added?

Jo0p · June 6, 2021, 12:32pm

Hi Georgios,

Some misunderstandig here!

I posted the results of your version directly. I’m sorry, but can’t debug this logfile any further. Do you have any idea what ik can check anymore?

(Just for your information, I tested again with the .jar you provided)

14:27:49.034 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Status Request [Zone: 30]
14:27:49.036 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 24 1D 43 6B
14:27:49.077 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 30]
14:27:49.079 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 04 1D 01 58 13 F0 00 02 88 15
14:27:49.198 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'caddx:zone:afdba8a490:zone30' changed from OFFLINE to ONLINE
14:27:54.376 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
14:27:54.377 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
14:27:54.379 [DEBUG] [x.internal.handler.CaddxBridgeHandler] - Zone 6 Transition ignored.
14:27:54.380 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
14:27:54.382 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
14:27:54.417 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
14:27:54.418 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 08 00 00 00 10 00 B8 6F
14:27:54.436 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
14:27:54.438 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
14:27:56.527 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
14:27:56.528 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 05 01 01 05 C4 00 00 5D FC
14:27:56.530 [DEBUG] [x.internal.handler.CaddxBridgeHandler] - Zone 6 Transition ignored.
14:27:56.531 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
14:27:56.533 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
14:27:56.568 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
14:27:56.569 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 01 00 10 08 00 00 00 00 00 A8 4F
14:27:56.588 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
14:27:56.590 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

jossuar · June 6, 2021, 12:33pm

Hi Mark,

Yes

I did not incorporate the changes for displaying information on the keypad.
This part is like on the official binding.

Changes (On top of the official binding):

Support for ignoring Zone Status Transitions
Things should go ONLINE when they should.
Addition of the following three channels.

	<channel id="panel_ac_fail" typeId="panel_flag">
		<label>AC fail</label>
		<description>AC fail</description>
	</channel>
	<channel id="panel_ac_power_on" typeId="panel_flag">
		<label>AC Power On</label>
		<description>AC Power On</description>
	</channel>
	<channel id="panel_low_battery_memory" typeId="panel_flag">
		<label>Low Battery Memory</label>
		<description>Low Battery Memory</description>
	</channel>

jossuar · June 6, 2021, 12:48pm

Hi @Jo0p,

from the log, everything looks ok.
Did you make any addition on any of the openhab pages to display information from configured binding items?
If say, you added items for your motion sensors, you should see them switch on and off when you walk through the rooms.

Jo0p · June 6, 2021, 1:05pm

mmm… This issue really drives me crazy, but it’s all about the odds

Yes! Now it’s working! In the new version, with the fresh install, I did not created the ‘panel’ item. That was a indispensable part
Thanks for your support!!

Johan.

Mark_VG · June 6, 2021, 1:52pm

Hi Georgios

Thanks so much.

Tested the AC Fail and AC Power ON. Both work perfectly. The is obviously a delay before AC Fail triggers, which coincides with when the panel sends a message to Alarm Company.

I also restarted OH on my Windows Machine and all the Caddx things came online without having to restart the Caddx Thing - which is GREAT!

I will try and schedule a test of the Low Battery Memory - though that is a lot more difficult as it could take a LONG time for my alarm batteries to deplete enough to trigger - will see what I can do though.

Thanks so much

alexkarageorgis · June 24, 2021, 12:17pm

Hi guys, has anyone setup the Caddx binding on openhab 3? could you kindle share a couple of the rules setup so I can mirror if you did?