Satel binding - support, announcements and feature requests

If you are sure your converter works properly, we can move forward to the next step :slight_smile:
Please make sure you have configured your INT-RS to work using integration protocol (Function 2) as described in Integration Protocol doc (available on Satel web site).

Protocol of satel (Funcion 2) specifies as follows:
RS-232 serial port of INT-RS module is configured as 19200/8/1/N. The DB9 connector uses the same lines as in Function 1.

I asume the above is already included in the satel binding?
In my PLC program (which comminicates with INT-RS) I have similar setting:
fbBX_COM_64.ComConfig.eCommPort := COM2; (* Bridge between PIN 7-8 X01, only RS232 *)
fbBX_COM_64.ComConfig.BaudRate := 19200;
fbBX_COM_64.ComConfig.eDataBits := EIGHT_DATABITS;
fbBX_COM_64.ComConfig.eStoppBits := ONE_STOPPBIT;
fbBX_COM_64.ComConfig.eParity := NONE;

And 3 lines of DB9 connector are used for communication:

  • RX (pin 2) - serial input
  • TX (pin 3) - serial output
  • GND (pin 5) - signal ground

You can find relevant code here.

On PLC, did you communicate with INT-RS using integration protocol? I am just making sure all (i.e. dip switches) is configured on the module side properly to work with integration protocol (Function 2).

@druciak thanks for hint. OH and Satel restart/power cycle helped indeed :slight_smile:

I have checked the DIP-switch 8…4 is 0010 (5 is ON) which means Function 2 (integration protocol). I am not the author of the PLC program which communicates with Satel and not easy for me to understand it. In fact I am only reading data of Satel in my PLC but I think the program in every PLC cycle calls some SerialLineControl function to receive the data.

Send me a PM, let’s discuss further steps offline.

I have managed to find the issue :grinning: The firmware in INT-RS was not upgraded to 1.14 while I was trying to do it via Integra 64 central.
In order to upgrade it you need to connect directly to INT-RS module via its DB9 socet!

After resolving the firmware issue, the discovery of satel binding works fine and all may Satel`s zones, partitions and others were identified😊. I am progressing with items and things definition…

But I have noticed a difference to my current set-up in OH2 integrated with satel via PLC/modbus: Why zones in satel binding are presented as switch items and not as contact items?

If I understand correctly we shall read state of zones from satel and not set them up in the OH2?

Also there are quite nice dynamic icons in OH2 for contact items including: <motion> for PIR sensor attached to satel and <door> / <windows> for reed switch (attached to satel)

Is it possible to change zone items from Switch type to Contact type? For example channel violation of the Zone thing to be a contact type?

Main reason is: because it was easier for me to implement the binding that way. Zone things have many channels and I wasn’t sure which of them should be contact, and for which of them a switch would be better. For some of them you can send commands (BYBASS), some of them obviously should be contact (VIOLATION), but the rest isn’t so obvious, so I decided to use switch type for all of them. That maybe wasn’t a good decision, but now it is not easy to change it.
Besides OH is very flexible and you can achieve whatever you want in many ways. You can for example rename icons (or copy to new files) door-open.png to door-on.png and voilà, you have dynamic icon for doors. :wink:

Thank you for your hint regarding dynamic icons. In addition I have changed Switch item type into String type on site map so there are no switches for violation items😊
New questions and observations:

  1. What is the difference between Armed channel and Really Armed channel in Partition thing?

  2. When I am setting Armed in OH2 (using Armed channel) and I have a blocked or violated zone ( ex open window) the satel is arming despite that Force Arming option in Partition thing is off.

  3. When I am setting Armed in OH2 for partition with a given time to leave option in Satel(ex 30 sec) the thing changes back into Disarmed then after ~30esc it changes into Armed, as follows:

2020-10-05 21:10:43.692 [ome.event.ItemCommandEvent] - Item 'Satel_PARTITION_1_ARMED' received command ON
2020-10-05 21:10:43.710 [nt.ItemStatePredictedEvent] - Satel_PARTITION_1_ARMED predicted to become ON
2020-10-05 21:10:43.758 [vent.ItemStateChangedEvent] - Satel_PARTITION_1_ARMED changed from OFF to ON
2020-10-05 21:10:45.420 [vent.ItemStateChangedEvent] - Satel_PARTITION_1_ARMED changed from ON to OFF
2020-10-05 21:11:14.171 [vent.ItemStateChangedEvent] - Satel_PARTITION_1_ARMED changed from OFF to ON

I have already put this statement before, but once again:
I am not professional security installer, just a developer of this binding. I have some knowledge of Satel alarms, but I don’t know all the configuration options and the way they work. So please don’t ask me what is this feature for, what is that option for, etc. I have just implemented the integration protocol basing on the documentation, but I don’t know the meaning and purpose of all those things :slight_smile:

As far as I know, “armed” is when the system is going to arm, when you pressed “arm” button but exit time have not passed. “Really armed” is when the system is indeed armed and all the violations trigger an alarm.

My observation is the alarm is not armed, however the binding shows it is. Which is weird, but I don’t think this is a bug in the binding.

I don’t have “Armed” item, I use “Really armed” channel.

Ok, clear enough :slight_smile: and thank you for binding!

This also directed me to look first at the int-rs protocol description for explenation. And I have found a direct answer to my question:

There is a note:
for INTEGRA v1.12 and newer, both 0x09 and 0x0A commands indicate really armed partitions, regardless of suppression arm status time.

As I have Integra v1.19 there should not be any difference between both

I assume that most users of the satel binding are not the satel professional installers so I think this forum might serve for exchange of experience regarding satel binding setting and knowledge as well :slight_smile:

1 Like

Somehow I missed this info, thanks. Good to know. :slight_smile:

Hi druciak

I have defined all items and things (~40) which are feeded by Satel binding and I am observing them now while not changing/adding any thing new. Unfortunattely my binding is not reliable yet :frowning:

First I have observed that quite often my INT-RS bridge is disconnected and in the next second it is connected back.I have used and modify your program I found here https://community.openhab.org/t/satel-lack-of-module-connected-and-module-connected-since/50639/3 to calculate number of disconnect/connect and there are about 20 from last day like the following:

2020-10-09 15:30:14.638 [hingStatusInfoChangedEvent] - 'satel:int-rs:46d26acd' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)
....
2020-10-09 15:30:15.269 [hingStatusInfoChangedEvent] - 'satel:int-rs:46d26acd' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE

The above would not be an issue since 1 second of disconnection is not a problem.
But I have experienced also that after ~1 day of working there is a disconnection without connection back :frowning: and the message in the log refers to time out.

Sometimes when I click on my INT-RS bridge in paper UI connection goes back but sometime I must stop and restart openhab to have satel binding working back.

I have set up the INT-RS bridge with time out is set to 5000ms and refresh to 1000ms.
Majority of satel binding enthusiasts have ETHM-1 and not sure if they signal any similar issue in their environments?
Any hints what to investigate further?

Does it disconnect after specific command sent or there is no pattern and diconnections happen at random?
To check this please enable debug logging level and observe for some time if it always disconnects after the same command or different ones.

It is random.
I have set up DEBUG level for a separate log fille. Then I restarted openhab at 18:04. The first disconnection/reconnection event took place at 20:25 but I can not find an evidence of it in the separate logfile(?)
But I can see that starting at 19.40 there are some strange (?) lines in the log as follows:

11-Oct-2020 19:40:48.010 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 19:40:48.037 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF
11-Oct-2020 19:40:48.039 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
11-Oct-2020 19:40:50.010 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 19:40:50.030 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FD FD 7F FF FF
11-Oct-2020 19:40:50.033 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [00,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
11-Oct-2020 19:40:50.036 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.038 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.040 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.041 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.043 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.044 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.046 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.048 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.050 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.052 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.053 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.055 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.056 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.058 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.060 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.061 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.063 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.065 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.066 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.068 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.070 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.072 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.073 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 19:40:50.074 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 00, payload = 
11-Oct-2020 19:40:50.106 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 00, payload = 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
11-Oct-2020 19:40:50.107 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: IntegraStateEvent: command = 00, extended = false, active = {18}
11-Oct-2020 19:40:52.011 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 19:40:52.033 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF
11-Oct-2020 19:40:52.037 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
11-Oct-2020 19:40:54.011 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 19:40:54.038 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF

The above lines repate then from time to time. Not sure if this might lead somehow to disconnection?

I don’t see any disconnection on this log excerpt. What makes you think this log is suspicious? I don’t see anything that could cause troubles.
Please try to catch a disconnection while having DEBUG level turned on. What is interesting happens just before it. It would be good to have 2-3 occurrences logged.

Please find below, 3 occurences as follows (click on arrows):

yesterday at 22:25
11-Oct-2020 20:25:47.175 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 00, payload = 
11-Oct-2020 20:25:47.176 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 00, payload = 
11-Oct-2020 20:25:47.208 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 00, payload = 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00
11-Oct-2020 20:25:47.209 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: IntegraStateEvent: command = 00, extended = false, active = {19}
11-Oct-2020 20:25:49.122 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 20:25:53.123 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
11-Oct-2020 20:25:54.145 [DEBUG] [penhab.binding.satel.internal.protocol.IntRSModule] - Closing connection to INT-RS module
11-Oct-2020 20:25:57.130 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
11-Oct-2020 20:25:57.150 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connection to INT-RS module has been closed
11-Oct-2020 20:25:57.151 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
11-Oct-2020 20:25:57.187 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread stopped
11-Oct-2020 20:25:57.991 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread started
11-Oct-2020 20:25:57.996 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connecting to INT-RS module at /dev/USB-satel
11-Oct-2020 20:25:58.006 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - INT-RS module connected successfuly
11-Oct-2020 20:25:58.008 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
11-Oct-2020 20:25:58.035 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FD FD 7F FF FF
11-Oct-2020 20:25:58.037 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = true, reason = null
11-Oct-2020 20:25:58.136 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [00,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
11-Oct-2020 20:25:58.137 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 17, payload = 
today at 22:04
12-Oct-2020 22:04:22.889 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF
12-Oct-2020 22:04:22.894 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
12-Oct-2020 22:04:24.865 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
12-Oct-2020 22:04:28.866 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
12-Oct-2020 22:04:29.898 [DEBUG] [penhab.binding.satel.internal.protocol.IntRSModule] - Closing connection to INT-RS module
12-Oct-2020 22:04:32.875 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
12-Oct-2020 22:04:32.904 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connection to INT-RS module has been closed
12-Oct-2020 22:04:32.907 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
12-Oct-2020 22:04:32.939 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread stopped
12-Oct-2020 22:04:33.393 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread started
12-Oct-2020 22:04:33.394 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connecting to INT-RS module at /dev/USB-satel
12-Oct-2020 22:04:33.404 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - INT-RS module connected successfuly
12-Oct-2020 22:04:33.406 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
12-Oct-2020 22:04:33.427 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF
12-Oct-2020 22:04:33.428 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = true, reason = null
12-Oct-2020 22:04:33.482 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
12-Oct-2020 22:04:33.485 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 17, payload = 
12-Oct-2020 22:04:33.486 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 17, payload = 
today at 22:39
12-Oct-2020 22:39:07.764 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FC FD 7F FF FF
12-Oct-2020 22:39:07.768 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
12-Oct-2020 22:39:09.742 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
12-Oct-2020 22:39:13.743 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
12-Oct-2020 22:39:14.774 [DEBUG] [penhab.binding.satel.internal.protocol.IntRSModule] - Closing connection to INT-RS module
12-Oct-2020 22:39:17.745 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 7F, payload = 
12-Oct-2020 22:39:17.778 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connection to INT-RS module has been closed
12-Oct-2020 22:39:17.780 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
12-Oct-2020 22:39:17.811 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread stopped
12-Oct-2020 22:39:18.794 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Communication thread started
12-Oct-2020 22:39:18.795 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - Connecting to INT-RS module at /dev/USB-satel
12-Oct-2020 22:39:18.812 [INFO ] [penhab.binding.satel.internal.protocol.IntRSModule] - INT-RS module connected successfuly
12-Oct-2020 22:39:18.814 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 
12-Oct-2020 22:39:18.830 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FD FD 7F FF FF
12-Oct-2020 22:39:18.831 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = true, reason = null
12-Oct-2020 22:39:18.851 [DEBUG] [enhab.binding.satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [00,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
12-Oct-2020 22:39:18.854 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 17, payload = 
12-Oct-2020 22:39:18.856 [DEBUG] [penhab.binding.satel.internal.protocol.SatelModule] - Command already in the queue: Message: command = 17, payload = 

I do not see any suspect apart from disconnection/connection info :frowning:

@druciak I have no issues with the module, just wanted to thank you for your great work on this. It must have taken tons of your time, it works great. Thank you.

1 Like

After upgrading to 3.0 my Satel binding stoped working.
When I open thing ’ ETHM-1’ I seen an error:
Status:

OFFLINE

**COMMUNICATION_ERROR**

IO error occurred while connecting socket

Everything worked perfectly fine on 2.4.
I run openhab in docker and upgraded by installing a newer image