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

Add-ons Bindings
, ,
83

Hi @jossuar

Thanks you. I have PM’d you the logs etc. Hope its what you need.

Mark

84

Thanks,
i will have a look during the next days.

85

Hi @Mark_VG,

I’m curious about your panel model and firmware version.
The Log event message is according to the manual 10 bytes long, but your panel sends 17 bytes. Fortunately the 10 first bytes are the same as far as i can tell.
Also are you located in the US, Europe or elsewhere?

Please check with the following binding and the log messages should be displayed.
https://github.com/jossuar/openhab2-addons/releases/download/v1.3.0/org.openhab.binding.caddx-2.5.9-SNAPSHOT.jar
Delete the old file from the addons folder and add Add the above version. Openhab should automatically in the next few seconds notice the change and restart the binding.

Thanks for the info and the testing.

86

Hi @jossuar

Thanks so much for getting back to me so quickly. I will download the new version and give it a try and feedback.

I am is South Africa and the Panel Details are: NZ-8-ZA-TK and from the binding the Firmware Version is 5.38

I have a copy of the Installation Manual and could send you a scan of any info that might help?. Just not sure where to look.
Cheers
Mark

EDIT: The logs now seems to display correctly - only weird this is there is now a special character after the Firmware Version? - 5.38�

EDIT 2: The special character resolved after restarting the OpenHab services on Windows… Also battled with the new version till then. Seems to hold the older bindings etc till the service is restarted. Was getting all sorts of errors with sending commands etc. Will have to remember to restart after any upgrades etc.

87

Hi @Mark_VG,

Yes you need to restart due to the binding missing the actions workaround: https://github.com/openhab/openhab-addons/issues/8116.

I did not implement it because all new contributions will be first against version 3.0, for which the workaround will not be needed. (i think)

88

Hi @jossuar

Just wanted to thank you again for the great work. I have been very happy with what I have been able to achieve with your assistance and the community in a short while. Had been really frustrated with my previous solution - especially since the plugin was no longer supported.

With your latest build I am now able to see the log entries. I have also upgraded openHAB to 2.5.9 with no issues.

My current challenges (for which any feedback/advise would be appreciated are:

  1. To be able to see the “Triggered Alarm” information such as:
    a) Triggered Partition
    b) Triggering Zones
    c) Time of event (though not sure this is available as I do not see on *3 on Keypad

    I have looked at the status messages etc, but these all seem to be switches and not messages back - so not sure where to get the information

  2. Display an alarm event similar to above and also send notification. I presume the notification would involve the openHAB cloud connector which I have not looked as as yet.

  3. Find a reliable and usable User Interface for use on PC as well as Mobile Device. Both my sitemap and HABpanel attempts have shortcomings. The SiteMap/Basic UI seems most functional - though limited to 2 columns and on mobile have to set the browser to use “Desktop” mode each time. My HABpanel attempt looks great on PC and then terrible on mobile - so no happy medium so far.

  4. Integrate with Google Assistant - though concerned about security etc.

I have managed to implement two different keypad solutions (BasicUI and HABpanel) using the following:

HABpanel:

BasicUI:

So these look like this:
BasicUI:

BasicUI Keypad
BasicUI Keypad1070×457 12.6 KB

HABPanel:

HABpanel Keypad
HABpanel Keypad1275×572 52.3 KB

As I mentioned - any and all suggestion will be greatly appreciated.

Mark

89

Have a look at the following design pattern:

I suppose you could put all the zones in a group and iterate the members to find which zones have the Alarm Memory flag set. From this info you could build a string for display.

90

Hi @jossuar

Appreciate the suggestion. Have had a read through and looked feasible. However I still am not getting any results.

For testing I have Partition 3, which has a single Zone connected (Zone 18). This Partition has recent alarm activity (*3 on Keypad gives Zone 18).

I have created items for Partition 3 Alarm Memory as well as Zone 18 Alarm Memory (PIRCEILING) and displayed them. Both are switches which are OFF. Did the same test with Partition 2, which also has recent alarm when checked with *3, however both the Partition and Zone Alarm Memories are OFF.

IS there not a possibility that maybe some of these switch items should be STRING maybe? (See that under a Zone there is a Name item - would expect this to be a STRING possibly?)

EDIT: This is a STRING and is now displaying the correct name

My sitemap looks like this:

    Frame label="Testing" {
    Default item=BXSIDEBEDROOM_AlarmMemory label="BXSIDEBEDROOM_AlarmMemory"
    Default item=Partition2_AlarmMemory label="Partition2_AlarmMemory"
    Default item=VXCOTTAGE_AlarmMemory label="VXCOTTAGE_AlarmMemory"
    Default item=Partition3_AlarmMemory label="Partition3_AlarmMemory"
    Default item=PIRCEILING_AlarmMemory label="PIRCEILING_AlarmMemory"
    Default item=PIRCEILING_Name label="PIRCEILING_Name [%s]"
    }

All of these are displayed as SWITCHES which are OFF.

Any other suggestions?

Thanks
Mark

91

Hi @Mark_VG,

add also the zone_faulted channel. If i remember correctly, without it, the thing does not get online and the rest of the channels do not get updated.

92

Hi @jossuar

Thanks. I am already using the Zone Faulted channel and can see any activity on a Zone etc. So doing a walktest around the house and monitoring on OpenHab with e Caddx Binding works well.

Mark

93

Hi@jossuar

Also just wanted to check that I am still using the correct Binding version:

openhab> bundle:list -s|grep caddx
238 x Active x  80 x 2.5.9.202010052003      x org.openhab.binding.caddx
openhab>

I am trying to silence an alarm using the following:

import org.eclipse.smarthome.model.script.ScriptServiceUtil

rule "Silence Alarm"
when
    Item Silence_Alarm  received command ON
then
if (Pin_Number.state.toString == "" ) {
    logWarn("actions", "Please enter PIN")
            Alarm_Feedback.postUpdate("Please enter PIN")
            createTimer(now.plusSeconds(5), [
            Alarm_Feedback.postUpdate("")
        ])
}
else
{
    val actions = getActions("caddx","caddx:panel:e59e4935:panel")
    if (null === actions) {
        logWarn("actions", "Actions not found, check thing ID for bridge")
        return
    }
    var EnteredPin = ScriptServiceUtil.getItemRegistry.getItem("Pin_Number")
            logInfo("", "EnteredPin " + EnteredPin.state.toString)
       
    actions.turnOffAnySounderOrAlarm(EnteredPin.state.toString)
    Pin_Number.postUpdate("")
}
end

But get the following error when using the panel level:

14:35:33.837 [ERROR] [untime.internal.engine.RuleEngineImpl] - Rule 'Silence Alarm': Instance is not a CaddxPartitionActions class.

I managed to get the function to work on the Partition Level though.

Thanks
mark

94

Hi @jossuar

I remembered I’ve got this issue before, in my previous HA controller (Vera/Micasaverde). The author of that plugin, futzle, helped me with (what I see now :wink: ) the same problem. Please see this thread.

I can’t judge if this issue (in Luup) is the same as in your code, but a small change to solve the bug was made (see github)

Can you maybe have a look at this?

95

Hi @jossuar

So just an update on my post #89 above.

This morning I noticed that the Zone level Alarm Memory entries have updated (they are no longer just off). So I went through the process of creating Partition Groups with all the Zone Alarm Memory in each partition group. So I can see which Zones in each Partition last triggered the alarm.

I also tested this by forcing an alarm action and the Zone level Alarm Memory switches do update to match the *3 response on the Keypad…

The Partition Level Alarm Memory however does not change. So need to find a way to see which Partition Last triggered the alarm (and when?) - work in progress.

While adding the Zone Level entries I discovered that each Zone Thing has to be restarted to force a channel update - though did try this with my previous attempts. Suspect that the Alarm Memory entries updated during my many restarts over the last few days.

Will keep on digging.

Mark

96

Hi @Mark_VG,

I have currently many last versions. :slight_smile: I’m in the process to change my build environment to 3.0 so that i can submit pull requests, to have the latest changes incorporated in the official distribution. The version you have is correct.

This I have to check.

The partition you can get also from the zone. There are channels on the zone that indicate to which partitions it belongs. About the time I suppose you could add a rule when the alarm_memory flag changes to capture the current time when an alarm is triggered.

97

Hi @Jo0p,

Yes I had a look. The bug was regarding the Zones Snapshot message. I’m using the Zone Status Message which conveys a lot more info about the zone. I will have again a look at the logs from your previous posts and I will come back to you.
Did you try to have only one expansion card connected to the panel?
Did your panel work correctly with Vera/MiCasaVerde?
Also what firmware version is your panel?

98

Hi @jossuar
Thanks again for your response and confirming that I am still on the correct version. Will look forward to any feedback on the error with silencing the alarm.

I have managed to get the zones etc. and they are sorted by Partition into logical areas etc. I have even got so far as to be able to see the only the last triggering zones in each partition. What I cannot see how to retrieve is when an alarm triggers and what triggered it. Have looked through the documentation as well as all the channels etc. - But there does not seem to be an option for this. So cant find a way to trigger an action when an alarm is activated. I have even gone so far as to look at the
“Networx NX-584 RS-232 Gateway Interface Protocol” document which is what I guess your work is based on.

Reading this document made me wonder if some of the information is maybe hidden inside other information or has to be reconstructed from information that is not readily available via the binding?

Have you been able to access any information about when an alarm is triggered and the causes etc?

Once again thank you SO much for the work. I have become a bit addicted to adding to what I have on the Caddx setup.

Mark

99

Could this not maybe have something to do with Caddx Zone Doubling? Just a thought as I had issues with zone doubling many years ago and eventually forked out for an expansion card to get around them.

100

Thanks for your thought Mark! I will try this by changing the config (less complicated than unwire the expanders).

101

Hi

So it turns out that the Alarm Memory at Partition level is not so much a “memory” as an active switch.
The channel is ON while the alarm is triggered and goes back to OFF as soon as the alarm is cancelled. Different to the Zone level which is always ON after an alarm event - till the next event clears and updates to last event.

I am using the following rule to keep track of the activations:

rule "Partition 1 Alarm Timestamp"
when
    Item Partition1_AlarmMemory changed to ON 
then
        postUpdate(Partition1_Last_Alarm, new DateTimeType())
        logInfo("", "Partition 1 Alarm Timestamp " + Partition1_Last_Alarm.state )
end

And display in the Sitemap as:

 Default item=Partition1_Last_Alarm              label="Partition1_Last_Alarm [%1$td %1$tb %1$tl:%1$tM %1$tp]"

I guess I could display alarms in the last X hours etc and use Groups as well as “visibility” to only show partitions with alarms in that time period? Any suggestions on how to do this more elegantly? (limit coding knowledge).

Mark

102

ad. 1
Yes; I tested serveral things: First of all, zone 1-8 on the main board are working well.
My setup has 3 keypads and 2 wired expander cards

Then I triggered zone 16 (7th of the first expander card) with several conditions:

  • 1 expander, 3 keypads connected

    15:10:17.558 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
    15:10:17.559 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 80 7A A6
    15:10:17.565 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_f8f0aaaf_partition1_partition_ready_to_arm changed from ON to OFF
    15:10:17.566 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
    15:10:17.567 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
    15:10:17.619 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
    15:10:17.620 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
    15:10:17.622 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
    15:10:17.623 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
    15:10:17.659 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 7]
    15:10:17.661 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 07 01 01 05 C4 00 00 5F 0B
    15:10:17.663 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
    15:10:17.663 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
    15:10:17.700 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
    15:10:17.701 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 00 00 00 00 00 08 00 00 10 A7 D5
    15:10:17.712 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
    15:10:17.713 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

1 expander, 1 keypad (192)

15:27:38.394 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
15:27:38.524 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 80 7A A6
15:27:38.672 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_f8f0aaaf_partition1_partition_ready_to_arm changed from ON to OFF
15:27:38.678 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:27:38.684 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:27:38.729 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
15:27:38.776 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
15:27:38.792 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:27:38.794 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:27:38.828 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 7]
15:27:38.830 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 07 01 01 05 C4 00 00 5F 0B
15:27:38.834 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:27:38.836 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:27:38.889 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
15:27:38.891 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 00 00 00 00 00 08 00 00 10 A7 D5
15:27:39.032 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:27:39.033 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

with zone doubling enabled (this was not…) (same results with the option 'Disable on board zones)

15:39:42.010 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
15:39:42.012 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 86 00 20 00 08 41 01 00 A0 9A C6
15:39:42.017 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_partition_f8f0aaaf_partition1_partition_ready_to_arm changed from ON to OFF
15:39:42.020 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:39:42.021 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:39:42.071 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
15:39:42.072 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 87 11 02 02 02 02 02 02 01 AE DD
15:39:42.074 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:39:42.075 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:39:42.112 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 7]
15:39:42.113 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 84 07 01 01 05 C4 00 00 5F 0B
15:39:42.115 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:39:42.116 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F
15:39:42.153 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
15:39:42.154 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 85 00 00 00 00 00 08 00 00 10 A7 D5
15:39:42.162 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Positive Acknowledge
15:39:42.163 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 1D 1E 1F

As mentioned earlier; When re-enable the caddx bridge, the zone is updated correctly (only once):

20:51:12.201 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.202 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 00 27 50
20:51:12.246 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.247 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 00 00 00 00 00 08 00 00 00 17 C0
20:51:12.261 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'caddx:panel:f8f0aaaf:panel' changed from OFFLINE to ONLINE
20:51:12.266 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'caddx:bridge:f8f0aaaf' changed from OFFLINE to ONLINE
20:51:12.274 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.276 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 01 28 51
20:51:12.346 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.347 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 01 00 10 00 00 10 00 00 00 30 5A
20:51:12.349 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.350 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 02 29 52
20:51:12.407 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.408 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 02 00 00 00 00 00 03 11 11 36 EE
20:51:12.410 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.411 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 03 2A 53
20:51:12.448 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.449 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 03 00 00 00 00 00 00 00 00 12 BB
20:51:12.451 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.452 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 04 2B 54
20:51:12.509 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.510 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 04 00 00 00 00 00 00 00 00 13 C4
20:51:12.512 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.513 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 05 2C 55
20:51:12.549 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.550 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 05 00 00 00 00 00 00 00 00 14 CD
20:51:12.552 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.553 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 06 2D 56
20:51:12.590 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.591 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 06 00 00 00 00 00 00 00 00 15 D6
20:51:12.593 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.594 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 07 2E 57
20:51:12.651 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.652 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 07 00 00 00 00 00 00 00 00 16 DF
20:51:12.654 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.655 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 08 2F 58
20:51:12.692 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.693 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 08 00 00 00 00 00 00 00 00 17 E8
20:51:12.695 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.696 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 09 30 59
20:51:12.753 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.754 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 09 00 00 00 00 00 00 00 00 18 F1
20:51:12.756 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.757 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 0A 31 5A
20:51:12.794 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.795 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 0A 00 00 00 00 00 00 00 00 19 FA
20:51:12.796 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zones Snapshot Request
20:51:12.798 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 25 0B 32 5B
20:51:12.854 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zones Snapshot Message
20:51:12.855 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 0A 05 0B 00 00 00 00 00 00 00 00 1A 04
20:51:12.857 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Partition Status Request [Partition: 0]
20:51:12.858 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 26 00 28 52
20:51:12.895 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
20:51:12.896 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 06 00 20 00 00 41 62 04 A0 77 46
20:51:12.903 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Partitions Snapshot Request
20:51:12.904 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 01 27 28 29
20:51:12.904 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'caddx:partition:f8f0aaaf:partition1' changed from OFFLINE to ONLINE
20:51:12.956 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partitions Snapshot Message
20:51:12.957 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 07 03 02 02 02 02 02 02 01 20 E8
20:51:12.959 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Status Request [Zone: 15]
20:51:12.960 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 24 0F 35 5D
20:51:12.997 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 15]
20:51:12.998 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 04 0F 01 00 13 F0 00 00 20 F6
20:51:13.008 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Name Request
20:51:13.009 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 23 0F 34 5B
20:51:13.032 [INFO ] [smarthome.event.ItemStateChangedEvent] - caddx_zone_f8f0aaaf_zone16_zone_faulted changed from OPEN to CLOSED
20:51:13.034 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'caddx:zone:f8f0aaaf:zone16' changed from OFFLINE to ONLINE
20:51:13.315 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Name Message
20:51:13.317 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 12 03 0F 4D 43 20 69 6E 62 20 6B 61 73 74 20 20 20 20 20 84 AE
20:51:13.319 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Partition Status Request [Partition: 0]
20:51:13.320 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 26 00 28 52
20:51:13.396 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Partition Status Message [Partition: 0]
20:51:13.397 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 09 06 00 20 00 00 41 62 04 A0 77 46
20:51:13.404 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Status Request [Zone: 6]
20:51:13.406 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 24 06 2C 54
20:51:13.457 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Status Message [Zone: 6]
20:51:13.458 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 08 04 06 01 01 05 C4 00 00 DD 00
20:51:13.465 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: Zone Name Request
20:51:13.466 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - ->: 7E 02 23 06 2B 52
20:51:13.466 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'caddx:zone:f8f0aaaf:zone7' changed from OFFLINE to ONLINE
20:51:13.748 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: Zone Name Message
20:51:13.749 [DEBUG] [ding.caddx.internal.CaddxCommunicator] - <-: 7E 12 03 06 52 4D 20 6F 75 64 65 72 73 6B 20 20 20 20 20 20 9B 07

ad. 2. The panel worked after I got a ‘custom’ lua file from Futzle (this post, this file)

ad. 3 . This is an interesting question; as in your plugin and in DL900 as well, none is given! How do you manage the firmware of the panel? It seems nog possible with DL900.

Thanks again for you’re great work, I hope I can enjoy also soon :slight_smile:
Have a nice weekend!