Satel binding - support, announcements and feature requests

druciak · November 8, 2018, 8:06pm

Hello all Satel Binding users!

I started this thread to have one place where all of you can help each other to solve Satel Binding issues and also to announce new versions of the binding and discuss about new features.

I hope all of you already migrated to 2.x version. If not, please tell me the reason you still stick with 1.x version - do you encounter troubles during migration or you just prefer the old version because of some features that are missing in the new one. Let’s discuss it here.

I have also the first announcement about a new version of the binding with event log support - as this was one of the features available in 1.x version, but missing in 2.x version. It is still under development, but quite stable and functional.
You can find this version at Eclipse Marketplace and install it directly from PaperUI (using marketplace addon) or download the jar file to addons directory. Updated documentation is here.

Enjoy!

Adam_G · November 10, 2018, 9:23pm

// Dzięki Druciak za fatygę! //

OK. Thanks a lot for the topic and the 2.0 version. I’ve migrated today to the new binding, but… everything collapsed…

OpenHAB found all my partitions, zones and outputs, but nothing what was configured in the old 1.x way works…
I have the /services/satel.cfg file as it was earlier. All the things were configured by /items/satel.items file. There were all my PIRs, partitions, and switches as, e.g.:

Contact SatelPIRLivingRoom "Salon [MAP(pir.map):%s]" { satel="zone:violation:1"}

And now nothing of the settings work. So I’ve changed the .items file to something like:

Contact SatelPIRLivingRoom "Salon [MAP(pir.map):%s]" { channel="satel:zone:22940d22:1:violation"}

Partitions and Switches are now OK, they react and show statuses:

Switch SatelPartitionOutsideArmed "Strefa zewnętrzna [%s]" { channel="satel:partition:22940d22:2:armed" }
Switch  SatelGardenLight 
        "Oświetlenie ogrodu" 
        (gOgrod, gOgrodSwiatlo, gOgrodSwiatloToggles, gSwiatloToggles)
        [swiatlo, ogrod]
        { channel="satel:output:22940d22:43:state" }

but zones (PIR detectors) do not work…

So I made all the clicking to add some of the new things that got into the inbox, e.g. “SatelPirLivingRoom” as Type: Contact, Category: Motion, with label “PIR Salon”. And now one of my rules works:

rule "SatelPirLivingRoom movement"
when
    Item SatelPirLivingRoom changed
then
    postUpdate(SatelPirLivingRoomMotionStamp, new DateTimeType())
end

SatelPirLivingRoomMotionStamp is defined in satel.items as

DateTime SatelPirLivingRoomMotionStamp "Ruch: Salon [%1$td.%1$tm %1$tH:%1$tM]"

How is it possible, that partitions and switches are working, but zones are not until I add them via PaperUI?

And now I have a problem:

How can I do all the configuration:

so I could backup save all the items and settings so I could use it in case of some troubles or new installation
so I had all the funky labels (i couldn’t get those neither in PaperUI nor HABmin):

"Salon [MAP(pir.map):%s]"

What am I doing wrong? I’ve spend all my day fighting with all this…

I made my home system reactive to PIR detectors and partitions states (lights, thermostats etc.), and now nothing work… The lights are turning OFF, because of no movement detected…

And Finally: how to setup Rollershutter item with 2.x channels?
In the 1.x way it was

Rollershutter SatelGarageDoor "Wrota garażowe" { satel="output:39,40" }

but now I don’t know how to use it… I’ve tried:

Rollershutter SatelGarageDoor "Wrota garażowe" { channel="satel:output:22940d22:39,40:state" }

but it just yields errors…

Hope you can help me fast. Thanks in advance.

[EDIT]

Funny thing: I’ve just changed item definition:

Contact SatelPirUpperCorridor "Korytarz Górny [MAP(pir.map):%s]" {channel="satel:zone:22940d22:10:violation"}

to

Switch SatelPirUpperCorridor "Korytarz Górny [MAP(pir.map):%s]" {channel="satel:zone:22940d22:10:violation"}

(item type Contact changed to Switch), and my rule depending on SatelPirUpperCorridor started to work, and the status in sitemap is changing.

druciak · November 12, 2018, 10:14am

Not possible.
You can configure the binding like all other OH2 binding either in *.things and *.items files or just in PaperUI. If decide to go in “files” direction you must define all things (zones, partitions, etc.) in *.things file and then reference them in binding configuration in *.items file.

Look at the examples on the bindign documentation page. You name things in *.things file or via PaperUI, and in *.items file you just reference these things by their ids. You do not specify addresses, input ids etc in *.items file, this is just reference to the thing.

Yes, this is something that has changed in OH2 - the system is now more strict about types. In OH1.x you could define as Switch or Contact or even Number and it worked. In OH2 you must define an item in correct type.

Adam_G · November 12, 2018, 3:52pm

OK. I’m retyping the complete configuration of things and items. First I thought the documentation is for OH1.x, now I get it - everything looks clear and consistent. Will see if I can build it up again.

BUT! Now I cannot connect to ETHM-1

It was working fine on the same settings earlier (IP, port etc.). Now, when I built the Bridge config, I’m getting these:

2018-11-12 16:42:05.680 [TRACE] [.satel.internal.protocol.SatelModule] - Checking communication thread: true, true

2018-11-12 16:42:05.989 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.1.112:7090

2018-11-12 16:42:05.999 [DEBUG] [.satel.internal.protocol.SatelModule] - Connection failed

org.openhab.binding.satel.internal.protocol.SatelModule$ConnectionFailureException: IO error occurred while connecting socket

	at org.openhab.binding.satel.internal.protocol.Ethm1Module.connect(Ethm1Module.java:81) [234:org.openhab.binding.satel:2.3.0]

	at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:358) [234:org.openhab.binding.satel:2.3.0]

	at org.openhab.binding.satel.internal.protocol.SatelModule.access$1(SatelModule.java:345) [234:org.openhab.binding.satel:2.3.0]

	at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:480) [234:org.openhab.binding.satel:2.3.0]

	at java.lang.Thread.run(Thread.java:748) [?:?]

Caused by: java.net.ConnectException: Connection refused (Connection refused)

	at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]

	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:?]

	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:?]

	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:?]

	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:?]

	at java.net.Socket.connect(Socket.java:589) ~[?:?]

	at org.openhab.binding.satel.internal.protocol.Ethm1Module.connect(Ethm1Module.java:70) ~[?:?]

	... 4 more

2018-11-12 16:42:06.022 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket

2018-11-12 16:42:06.027 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.internal.protocol.Ethm1Module@1d52d25

2018-11-12 16:42:06.031 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.handler.Ethm1BridgeHandler@a53a0b

2018-11-12 16:42:06.037 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.handler.SatelSystemHandler@1c9807a

2018-11-12 16:42:06.041 [TRACE] [ding.satel.handler.SatelThingHandler] - Handling incoming event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket

2018-11-12 16:42:06.046 [TRACE] [satel.internal.event.EventDispatcher] - Distributing to org.openhab.binding.satel.handler.SatelZoneHandler@106b047

2018-11-12 16:42:06.050 [TRACE] [ding.satel.handler.SatelThingHandler] - Handling incoming event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket
[...]

I can see there:

Connection refused.

OKAY. So I tried to connect via DLOADX app - with success:

Tried to ping the ETHM-1 - success. But when trying to telnet 192.168.1.112 7090 it says the connection is refused… Even after restarting both Satel and OH@RasPi… Even tried to connect when Service Mode on Satel was on… Nothing…

On DLOADX Events List there is the entry that my RasPi’s IP (192.168.1.3) was connecting, but it failed (my comp’s IP: 192.168.1.254):

Why is that? The port is OK, the IP is okay as well. It was working for months, and now it stopped… :\

druciak · November 13, 2018, 8:59am

There are 3 cases:

You bridge configuration is wrong.
You have something already connected to ethm-1 on the same port - other version of the binding, other oh installation, etc.
Your ethm-1 hanged on some other connection that is already terminated, but the module doesn’t know about it. This is the worst case and the only thing you can do unlock communication is to powercycle the module. You could also try to unplug it from your network.

fpracek · November 13, 2018, 9:53pm

I wrote this rule:

rule "Aggiorna Log Satel"
when
   Time cron "0/15 * * * * ?" or
   Member of SATEL_ZONES_GROUP changed to ON
then
    logDebug("SATEL_LOG", "INIT")
    SATEL_LOG_PREVIOUS_INDEX.postUpdate(NULL)
    SATEL_LOG_CURRENT_INDEX.sendCommand(-1)
end


rule "Send event log next"
when
    Item SATEL_LOG_PREVIOUS_INDEX changed
then

  var String eventLogMsgBody = ""

  var i = 0
  while ((i=i+1) < 11) {
    logDebug("SATEL_LOG", i.toString())
        if(eventLogMsgBody!=""){
           eventLogMsgBody += "\n" 
        }
        eventLogMsgBody += (SATEL_LOG_DATETIME.state as DateTimeType).format("%1$tF %1$tR") + "|" + SATEL_LOG_DESCRIPTION.state
        SATEL_LOG_CURRENT_INDEX.sendCommand(SATEL_LOG_PREVIOUS_INDEX.state)
  }
  logDebug("SATEL_LOG_MSG", eventLogMsgBody.toString())
  SATEL_LOG_MESSAGES.sendCommand(eventLogMsgBody)
end

but I receive this log error:

22:49:59.129 [DEBUG] [ipse.smarthome.model.script.SATEL_LOG] - INIT
22:49:59.185 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'SATEL_LOG_CURRENT_INDEX' received command -1
22:49:59.196 [INFO ] [smarthome.event.ItemStateChangedEvent] - SATEL_LOG_PREVIOUS_INDEX changed from 260337 to NULL
22:49:59.221 [DEBUG] [ipse.smarthome.model.script.SATEL_LOG] - 1
22:49:59.249 [ERROR] [untime.internal.engine.RuleEngineImpl] - Rule 'Send event log next': An error occurred during the script execution: Could not invoke method: org.eclipse.smarthome.model.script.actions.BusEvent.sendCommand(org.eclipse.smarthome.core.items.Item,java.lang.String) on instance: null
22:49:59.662 [INFO ] [smarthome.event.ItemStateChangedEvent] - SATEL_LOG_PREVIOUS_INDEX changed from NULL to 260337
22:49:59.666 [DEBUG] [ipse.smarthome.model.script.SATEL_LOG] - 1
22:49:59.706 [ERROR] [untime.internal.engine.RuleEngineImpl] - Rule 'Send event log next': An error occurred during the script execution: Could not invoke method: org.eclipse.smarthome.model.script.actions.BusEvent.sendCommand(org.eclipse.smarthome.core.items.Item,java.lang.String) on instance: null

It seems a problem with previous index…

Adam_G · November 14, 2018, 4:22am

Well… I think that was the case… Unplugged network cable od the module, waited a minute, re-plugged in. And it didn’t actually help.
So I halted the openHAB service, cleared cache, waited 20 minutes, restarted service and… here it is:

2018-11-14 05:16:34.577 [hingStatusInfoChangedEvent] - 'satel:system:home:Satel' changed from UNINITIALIZED to INITIALIZING
2018-11-14 05:16:34.601 [hingStatusInfoChangedEvent] - 'satel:system:home:Satel' changed from INITIALIZING to ONLINE

Now I have to configure the rest of the system (and I still have weird problems with z-wave after the upgrade…).

Thanks for your help @druciak, at least for now!

druciak · November 14, 2018, 7:32am

Hey @fpracek
You cannot iterate over the event log using while loop or any other synchronous way. This must be done asynchronously - you send command to the item and exit your rule. When items are populated by the binding, the rule get fired again and you repeat all steps there just for one event log record. You finish iterating once you reach requested number of records (or on any other condition).
Look at the example on the documentation page, this is how it should be done.

fpracek · November 14, 2018, 5:20pm

Thanks for your help, now the problem is solved.
For your information I wrote

var Number id = SATEL_LOG_PREVIOUS_INDEX.state
    SATEL_LOG_CURRENT_INDEX.sendCommand(id)

because using SATEL_LOG_CURRENT_INDEX.sendCommand(SATEL_LOG_PREVIOUS_INDEX.state) was an error cause in my log

18:11:08.940 [ERROR] [untime.internal.engine.RuleEngineImpl] - Rule 'Send event log next': An error occurred during the script execution: Could not invoke method: org.apache.commons.lang.StringUtils.split(java.lang.String,java.lang.String,int) on instance: null

I’d have a question for you: Is it possible to have a switch item for a new log item notification? In this case we can update our log only when it is necessary…

Thanks

druciak · November 14, 2018, 6:02pm

It works for me as it is in the example, but I am on OH 2.4 - this may be the difference.

Not sure what you mean by this, could you explain, please?

fpracek · November 14, 2018, 6:43pm

I asked if it is possible to manage an item that indicates when a new log entry is present in the control unit. In this way it will be possible to intercept the moment in which to read the logs again for a fresh list to display

thanks

druciak · November 14, 2018, 6:48pm

There is no such notification in integration protocol, unfortunately. The only way is to poll for new items on some interval. You should be able to achieve that using OH rules.

fpracek · November 14, 2018, 9:04pm

I’m doing it.
Thanks for your help and for your binding.

Adam_G · November 17, 2018, 1:04pm

OK. Next one.

After I reinstalled OH completely, I managed to connect and receive info from items/things. But when I try to send anything to Satel, I get no effect, eg. cannot arm/disarm, can’t reset troubles memory, cannot switch lights, or control gates… Tried with Integra Control App for Android and I can see in DLOADX (and in real world), that switching options in Integra Control affects outputs on Satel board. But when doing the same with OH I have no effect, except entries in log:

2018-11-17 13:40:30.904 [ome.event.ItemCommandEvent] - Item 'SatelPartitionInsideArmed' received command ON
2018-11-17 13:40:30.919 [vent.ItemStateChangedEvent] - SatelPartitionInsideArmed changed from OFF to ON
2018-11-17 13:40:32.610 [ome.event.ItemCommandEvent] - Item 'SatelPartitionOutsideArmed' received command ON
2018-11-17 13:40:32.629 [vent.ItemStateChangedEvent] - SatelPartitionOutsideArmed changed from OFF to ON

2018-11-17 14:02:18.064 [ome.event.ItemCommandEvent] - Item 'SatelStaircaseLightSwitch' received command ON
2018-11-17 14:02:18.077 [vent.ItemStateChangedEvent] - SatelStaircaseLightSwitch changed from OFF to ON

2018-11-17 14:02:36.981 [ome.event.ItemCommandEvent] - Item 'SatelTroublesMemory' received command OFF
2018-11-17 14:02:36.986 [vent.ItemStateChangedEvent] - SatelTroublesMemory changed from ON to OFF
2018-11-17 14:02:39.467 [ome.event.ItemCommandEvent] - Item 'SatelTroubles' received command OFF

Below is my configuration (basic non-working things, that may be as an example). What is wrong with that?

satel.things:

Bridge satel:ethm-1:home "Satel" [ host="192.168.1.112", referesh=2000, usercode="XXXX"] {

    Thing system Satel [  ]
    Thing partition SatelPartitionInside [ id=1, forceArming=true ]
    Thing partition SatelPartitionOutside [ id=2 ]

    Thing shutter SatelGarageDoor [ upId=39, downId=40 ] 
    Thing output SatelStaircaseLight [ id=49 ]

}

satel.items:

Switch SatelPartitionInsideArmed "Strefa Wew. [%s]" 
   (gSatel)
   { channel="satel:partition:home:SatelPartitionInside:armed" }
Switch SatelPartitionOutsideArmed "Strefa Zew. [%s]" 
   (gSatel) 
   { channel="satel:partition:home:SatelPartitionOutside:armed" }

Switch SatelTroubles "Awarie [%s]" 
   (gSatel) 
   { channel="satel:system:home:Satel:troubles" }
Switch SatelTroublesMemory "Awarie - pamięć [%s]" 
   { channel="satel:system:home:Satel:troubles_memory" }

Rollershutter SatelGarageDoorDrive "Wrota garażowe" 
   (gSatel,Gates) 
   { channel="satel:shutter:home:SatelGarageDoor:state" }

Switch SatelStaircaseLightSwitch "Schody [%s]" 
   (gSatel,gLights) 
   { channel="satel:output:home:SatelStaircaseLight:state" }

basic.sitemap:

sitemap basic label="Major Domus" {
   Frame label="SATEL" {
        Switch item=SatelTroublesMemory icon=error
        Switch item=SatelTroubles mappings=[OFF="Kasuj"] icon=error

        Switch item=SatelPartitionInsideArmed mappings=[ON="Czuwa"] icon=siren
        Switch item=SatelPartitionOutsideArmed mappings=[ON="Czuwa", OFF="Wyłącz"] icon=siren

        Switch item=SatelStaircaseLightSwitch icon=light
        Switch item=SatelDarknessStatusSwitch icon=light
    }    
}

druciak · November 17, 2018, 1:41pm

Does the user have rights to control outputs, arm/disarm partitions, etc?

Adam_G · November 17, 2018, 7:12pm

Of course. This is the same user that was before I updated OH and Satel Binding to 2.3…

Adam_G · November 17, 2018, 7:32pm

Here is some excerpt from debug logs:

2018-11-17 20:29:36.639 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2018-11-17 20:29:36.867 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD 77 FB DF

2018-11-17 20:29:36.874 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [01,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,26,27]

2018-11-17 20:29:41.639 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2018-11-17 20:29:41.673 [ome.event.ItemCommandEvent] - Item 'SatelPartitionInsideArmed' received command ON

2018-11-17 20:29:41.678 [DEBUG] [ding.satel.handler.SatelThingHandler] - New command for satel:partition:home:SatelPartitionInside:armed: ON

2018-11-17 20:29:41.865 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD 77 FB DF

2018-11-17 20:29:41.872 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [01,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,26,27]

2018-11-17 20:29:43.606 [ome.event.ItemCommandEvent] - Item 'SatelPartitionOutsideArmed' received command OFF

2018-11-17 20:29:43.611 [DEBUG] [ding.satel.handler.SatelThingHandler] - New command for satel:partition:home:SatelPartitionOutside:armed: OFF

2018-11-17 20:29:43.627 [vent.ItemStateChangedEvent] - SatelPartitionOutsideArmed changed from ON to OFF

2018-11-17 20:29:46.640 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2018-11-17 20:29:46.865 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD 77 FB DF

2018-11-17 20:29:46.872 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [01,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,26,27]

2018-11-17 20:29:51.628 [ome.event.ItemCommandEvent] - Item 'SatelPartitionOutsideArmed' received command ON

2018-11-17 20:29:51.633 [DEBUG] [ding.satel.handler.SatelThingHandler] - New command for satel:partition:home:SatelPartitionOutside:armed: ON

2018-11-17 20:29:51.636 [vent.ItemStateChangedEvent] - SatelPartitionOutsideArmed changed from OFF to ON

2018-11-17 20:29:51.640 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2018-11-17 20:29:51.864 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD 77 FB DF

2018-11-17 20:29:51.867 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [01,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,26,27]

2018-11-17 20:29:56.641 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2018-11-17 20:29:56.865 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD 77 FB DF

2018-11-17 20:29:56.873 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: NewStatesEvent: changed = [01,02,03,04,05,06,07,08,0A,0B,0C,0D,0E,0F,10,11,12,14,15,16,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,26,27]

druciak · November 17, 2018, 7:58pm

Not sure if this the reason, but try changing “usercode” to “userCode”. I think thing properties are case sensitive, but I might be wrong. Also you have a typo for “refresh” property, please double check all the configuration you have.

Adam_G · November 17, 2018, 9:25pm

Man! You’re genius! I was looking for typos for a whole day in 3 files! But didn’t look at the Bridge line… Woooow! Now it is running OK!

BUT!
Please correct the Satel docs at Satel Integra Alarm System - Bindings | openHAB for shutter channel. It’s not “state” but “shutter_state” (you’re welcome… ).
Shutters (gate drives) was the last thing not working. But I looked at API results and found the “shutter_state”:

[...]
"UID": "satel:shutter:home:SatelGate",
    "thingTypeUID": "satel:shutter",
    "channels": [
      {
        "linkedItems": [],
        "uid": "satel:shutter:home:SatelGate:shutter_state",
        "id": "shutter_state",
        "channelTypeUID": "satel:shutter_state",
        "itemType": "Rollershutter",
        "kind": "STATE",
        "label": "Shutter state",
        "description": "Represents state of the roller shutter",
        "defaultTags": [],
        "properties": {},
        "configuration": {}
      }
[...]

Adam_G · November 17, 2018, 10:39pm

DAMN!
I’ts not working…

I can arm/disarm partitions, I can control outputs, but I have no response from zones now…

When I use API, I get strange results for the same config:

Partitions are ONLINE:

{
  "statusInfo": {
    "status": "ONLINE",
    "statusDetail": "NONE"
  },
  "editable": false,
  "label": "Partition",
  "bridgeUID": "satel:ethm-1:home",
  "configuration": {
    "forceArming": true,
    "id": 1
  },
  "properties": {},
  "UID": "satel:partition:home:SatelPartitionInside",
  "thingTypeUID": "satel:partition",
  "channels":
[...]

but zones are OFFLINE:

{
  "statusInfo": {
    "status": "OFFLINE",
    "statusDetail": "BRIDGE_OFFLINE"
  },
  "editable": false,
  "label": "Zone",
  "bridgeUID": "satel:ethm-1:home",
  "configuration": {
    "id": 10
  },
  "properties": {},
  "UID": "satel:zone:home:SatelPirUpperCorridor",
  "thingTypeUID": "satel:zone",
  "channels": 
[...]

also outputs are OFFLINE, even though they are responding…:

{
  "statusInfo": {
    "status": "OFFLINE",
    "statusDetail": "BRIDGE_OFFLINE"
  },
  "editable": false,
  "label": "Output",
  "bridgeUID": "satel:ethm-1:home",
  "configuration": {
    "id": 49
  },
  "properties": {},
  "UID": "satel:output:home:SatelStaircaseLight",
  "thingTypeUID": "satel:output",
  "channels": [
[...]

What is wrong? Logs say that bridge is connected, outputs and partitions are OK. Why zones not? Few hours ago zones were OK, and I didn’t touch them…

When I was on OH 2.1 with Satel Binding 2.1 everything was working OK… I made all configuration in one weekend… This time, after update I made last weekend, I’m still fighting… 9 days…