I may be wrong. I think source=1 means “telephone nbr 1” and likely the details about it can be read with EE command. Will dig into this…
Hello @all!
I have a question regarding to the binding and outputs.
Is it principally possible to start my siren (inner-siren - wired) via openhab and the satel binding?
My siren has the output id 8 and I tried to add this information to the .things and .items file.
.things-file entry:
Thing output siren [ id=8]
.items-file entry:
Switch Innensirene "Innensirene" { channel="satel:output:home:siren:state" }
When I try to switch the item “Innensirene” to ON via Sitemap - nothing happens ;-(
Is there something wrong in my configuration or is it basically not possible to activate outputs?
Everything else works like a charm for me…
Many thanks for your support!
Best regards
Christian
Hey @curius
You can control only outputs of type bistable, monostable, etc. The ones you can control using Integra panel.
Additionaly the user configured in openHAB must have privilege #23 (controlling of BI, MONO, TEL outputs).
If both are valid in your case, please look in the log if there are any entries related to this output.
Hi @druciak
Thanks for this information.
I think my output is not from type mono- or bistable…
So i have to check my configuration.
Many thanks and best regards…
Christian
Likely it is connected to one of alarm signals, #2 or so.
If you would like to trigger it from openhab, you either:
- Add BI output type 25 and virtual zone type 8 - alarm will be triggered by this output.
- Add BI output, add additional output of type you currently have your output with id=8, and change output id=8 to type 47 (“OR”) adding both previous outputs to list of triggering outputs.
The first one will trigger alarm, the second one will just turn the siren on.
Hi,
I am trying to migrate to openhab2 version of the satel module though I am encountering connection issues I cannot seem to fix.
Java JCE is installed, though I am not using encryption for now. Here is my thing definition:
Bridge satel:ethm-1:home [ host="example.lan", refresh=5000, userCode="xxxxxx" ] {
Here are the errors in debug mode:
[.satel.internal.protocol.SatelModule] - Send/receive timeout, disconnecting module.
[.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
[satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = Send/receive timeout
[.satel.internal.protocol.SatelModule] - Communication thread stopped
[.satel.internal.protocol.SatelModule] - Communication thread started
[.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at example.lan:7094
[.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
[.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7C, payload =
[.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
Satel1 module works fine with the same settings. Version 2 loops with the ebove messages. I tried not only disabling satel1 but uninstalling it, restarting openhab etc, nothing helped.
Reinstalling satel1 works immediately.
Do you have any idea what else I could try?
Thank you
Hi,
Yes I have a couple of partition, zone and system and event-log configured.
No items assigned yet though.
Try to add at least one item. The binding does not update thing channel if there are no items linked to it.
I tried to add a zone item though the binding loops in
[.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at example.lan:7094
[.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
[.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
I had exactly the same problem - connection restarting more less every minute. The root cause in my case was quite surprising for me - missing addon. I found following entry in logs (also every minute):
[ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-misc-restdocs'
It turns out that the addon loader is restarting all addons every minute trying to load the invalid one… More details:
With such little information it is really hard to guess the reason.
Similar behaviour had other users, have you read this and my answer below?
New version is available at the Marketplace. It contains new rule action for reading the event log.
Check updated docs for syntax and full example.
I created a MR as well, hopefully it will be merged soon.
Enjoy 
Hi, I would like to ask for help with the initial setup. Last month, a new Satel installation was deployed to my parent’s house and I would like to connect it with openHAB. To be able to do that, I forced them to also include the ETHM-1 Plus module. Currently, connection with DLOADX or mobile phone is working. But nevertheless of configuration, I am getting errors with openHAB binding. Could someone help me, what should be configured and where? For reference, I am posting a screenshot of the configuration of ETHM-1 module:
In openHAB, I´ve installed Satel binding and add ETHM-1 thing (bridge). There I´ve configured IP address of the ETHM-1 and that is where I´ve ended with my confidence about configuration.
Firstly, I´ve let the default port (7094) and save. That ended with error and log messages:
2020-04-21 18:51:36.373 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.210.50:7094
2020-04-21 18:51:36.396 [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:83) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:387) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.access$1(SatelModule.java:374) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:523) [bundleFile:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_232]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_232]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_232]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_232]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_232]
at java.net.Socket.connect(Socket.java:607) ~[?:1.8.0_232]
at org.openhab.binding.satel.internal.protocol.Ethm1Module.connect(Ethm1Module.java:72) ~[bundleFile:?]
... 4 more
2020-04-21 18:51:36.403 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket
2020-04-21 18:51:36.453 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
Then I´ve tried port 7091 and as the Encryption key, I´ve configured the GUARDX key from ETHM-1 configuration. But this is also not working. The bridge in Paper UI is still showing OFFLINE - COMMUNICATION_ERROR. The only repeating message in the log is
2020-04-21 19:58:52.158 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.210.50:7091
Lastly, I´ve tried to configure port 7090 and DLOADX key as Encryption key. Also, no success here, the log is showing
2020-04-21 18:56:12.724 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.210.50:7090
2020-04-21 18:56:12.745 [INFO ] [.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
2020-04-21 18:56:12.767 [ERROR] [.satel.internal.protocol.SatelModule] - Unexpected exception occurred during reading a message
java.io.IOException: Too few bytes read. Read: 15, expected: 157
at org.openhab.binding.satel.internal.protocol.Ethm1Module$EncryptedCommunicationChannel.readMessage(Ethm1Module.java:192) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.Ethm1Module$EncryptedCommunicationChannel.access$0(Ethm1Module.java:180) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.Ethm1Module$EncryptedCommunicationChannel$1.read(Ethm1Module.java:146) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.readMessage(SatelModule.java:263) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:416) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.access$1(SatelModule.java:374) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:523) [bundleFile:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2020-04-21 18:56:12.767 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
What I am doing wrong? What is the correct configuration on both sides?
According to the docs:
For ETHM-1 the binding uses integration protocol, so it must be enabled and properly configured
I hope it helps 
I definitely have the integration protocol enabled. I have been using satel1 addon for a long time. When switching to it using debug logging it works immediately:
[DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload =
[DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FE FD E7 FB FF
[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,15,16,17,18,19,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27]
[DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 1A, payload =
[DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 1A, payload = 20 20 05 02 23 14 14 45 22
[DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: IntegraStatusEvent: type = 2, time = Sat May 02 23:14:14 CEST 2020, service mode = false, troubles = true, troubles memory = true, ACU-100 = false, INT-RX = false, grade 2/3 = false
[DEBUG] [.binding.satel.internal.SatelBinding] - Updating item state: item = alarm_clear_troubles_memory, state = ON, event = IntegraStatusEvent: type = 2, time = Sat May 02 23:14:14 CEST 2020, service mode = false, troubles = true, troubles memory = true, ACU-100 = false, INT-RX = false, grade 2/3 = false
Using the new module with the same config just gives (encryption disabled for both modules satel1 and satel…):
[DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread started
[INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at satala.lan:7094
[INFO ] [.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
[DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7C, payload =
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
[ERROR] [.satel.internal.protocol.SatelModule] - Send/receive timeout, disconnecting module.
[INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
→ it continues looping here.
I am using openHAB 2.5.4.
I did check your other posts you mentioned, though that did not help.
I did clear all caches (in /var/lib/openhab2…), any config and jsondb residues, tmp folder.
I also tried removing the addons.cfg file.
Is there anything else I could try or any information I could provide you are missing?
Have you tried this:
Is OH the only client connecting to ETHM-1? The module accepts only one connection, so make sure you don’t have another client (for instance OH 1.x) connected to it.
You could also disconnect ethernet cable for a moment in case your ETHM-1 hung up on an old connection.
?
OH is the only one connecting to it. satel1 is properly removed (double checked in the list of bindings via ssh). I have tried disconnecting the cable and reconnecting it after a couple of minutes.
Unfortunately is still behaves the same (connect successful, disconnect due to send/receive timeout, etc).