I assume this expander was in the system when you were on OH 3.1.x? And the binding properly read name of this expander?
Hi @druciak
unfortunately I didnât manage to connect my Satel to OH3.3.0.
Seems that connection is established for very short time, but still something is wrong
Now I see below debug information:
2022-08-22 16:18:58.505 [DEBUG] [.internal.handler.Ethm1BridgeHandler] - Initializing handler
2022-08-22 16:18:58.505 [DEBUG] [.internal.handler.SatelBridgeHandler] - Initializing bridge handler
2022-08-22 16:18:58.506 [DEBUG] [.internal.handler.SatelBridgeHandler] - Satel module opened
2022-08-22 16:18:58.506 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
2022-08-22 16:18:58.506 [DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread started
2022-08-22 16:18:58.508 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.100.100:7094
2022-08-22 16:18:58.509 [INFO ] [.satel.internal.protocol.Ethm1Module] - ETHM-1 module connected successfully
2022-08-22 16:18:58.509 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7E, payload =
2022-08-22 16:18:58.510 [DEBUG] [.satel.internal.protocol.Ethm1Module] - Encrypting data: A38C00003A00FEFE7ED860FE0D000000
2022-08-22 16:18:58.688 [ERROR] [.satel.internal.protocol.SatelModule] - Unexpected exception occurred during reading a message
java.io.IOException: End of input stream reached
at org.openhab.binding.satel.internal.protocol.Ethm1Module$EncryptedCommunicationChannel.readMessage(Ethm1Module.java:187) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.Ethm1Module$EncryptedCommunicationChannel$1.read(Ethm1Module.java:147) ~[bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.readMessage(SatelModule.java:260) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:413) [bundleFile:?]
at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:520) [bundleFile:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
2022-08-22 16:18:58.689 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
2022-08-22 16:18:58.689 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
2022-08-22 16:18:58.689 [DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread stopped
Any idea?
Thanks in advance
Hey @smarthomepch
Show your alarm system configuration please (dloadx screen). I would double check your encryption configurationm, it is a common mistake. Does the communication work properly when encryption is disabled? Did you try this?
Hmm, unfortunately I am simply alarm user, so I donât have access to this, unless I can see it somehow in Satel app, through web browser or in Satel manipulator?
Did you set the same encryption key on both sides (satel and OH)?
Did you try to connect to the system without encryption?
Yes. Just checked on the manipulator and added new encryption key on both sides.
No, I didnât. As I said I canât access it through DloadX. I can change setting only using the manipulator. Is it enough to clear the âKlucz kodowania integracjiâ?
Did you enable encryption in Integration protocol settings?
If you donât have enabled it on alarm system side, just remove encryptionKey setting on OH side.
Yes, expander was in the system and bindig was working. Do you have plans to check/upgrade code which is reading expander? What details you need ?
Turn on DEBUG logging level and execute the rule. Then send me the logs and I will look into this issue.
Continuing the discussion from Satel binding - support, announcements and feature requests:
Witam,
Mam zainstalowane na Raspi Openhab4 i niestety nie dziala tutaj Binding Satel.
na innym RASPI Openhab3 te same ustawienia wszystko dziala.
W czym jest tutaj problem?
Dzieki Pozdr
2023-11-06 14:42:37.525 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket
2023-11-06 14:42:37.565 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
2023-11-06 14:42:42.567 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
2023-11-06 14:42:47.508 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.99.50:7093
2023-11-06 14:42:47.516 [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:84) ~[?:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:384) ~[?:?]
at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:520) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:549) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
at java.net.Socket.connect(Socket.java:633) ~[?:?]
at org.openhab.binding.satel.internal.protocol.Ethm1Module.connect(Ethm1Module.java:73) ~[?:?]
... 3 more
Hey.
It looks that you have both OH running, but only one connection to ETHM-1 is possible. Turn off all instances of OH and then run OH4 instance.
I hope it will help.
ok now
du you speak polish?
2023-11-06 18:36:39.081 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket
2023-11-06 18:36:44.069 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
2023-11-06 18:36:49.062 [INFO ] [.satel.internal.protocol.Ethm1Module] - Connecting to ETHM-1 module at 192.168.99.50:7093
2023-11-06 18:36:49.073 [DEBUG] [.internal.handler.SatelBridgeHandler] - Module not initialized yet, skipping refresh
2023-11-06 18:36:49.069 [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:84) ~[?:?]
at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:384) ~[?:?]
at org.openhab.binding.satel.internal.protocol.SatelModule$CommunicationWatchdog$2.run(SatelModule.java:520) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:549) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
at java.net.Socket.connect(Socket.java:633) ~[?:?]
at org.openhab.binding.satel.internal.protocol.Ethm1Module.connect(Ethm1Module.java:73) ~[?:?]
... 3 more
2023-11-06 18:36:49.077 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = IO error occurred while connecting socket
Raspbarry 3 and Openhab 4 is this Problem or NO? Maybe JAVA Version?
Raspbarypi 3 and Openhab 3 and Satel working.
ETHM-1 is connecting and after 25 Seconds ERROR!!!??
Help
Thank You
2023-11-06 20:34:36.866 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 00
2023-11-06 20:34:36.870 [INFO ] [.satel.internal.protocol.Ethm1Module] - Closing connection to ETHM-1 module
2023-11-06 20:34:36.872 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: org.openhab.binding.satel.internal.event.ConnectionStatusEvent: connected = false, reason = null
2023-11-06 20:34:36.878 [DEBUG] [.satel.internal.protocol.SatelModule] - Communication thread stopped
Yes, I do, but this is an international community and we should speak English.
It might be Java version problem, but you did not mention that you have different versions on each installation. Try to use the same version of Java. Try to eliminate any difference that you have between OH3 and OH4.
I donât use OH on Raspberry Pi, so I cannot confirm that it works well on this platform. Maybe someone else will.
What differences do you mean? The settings or Java version? The strange thing is that it briefly turns green when starting and after about 30 seconds there is a communication problem. All zones and motion detectors were also found and imported by the system. Letâs see what else can be done.
Thank you
I have no idea, any difference may be important.
I donât have a RasPi, so I cannot test it nor give you furter help.
Do you have open openHABian or raspian installed on your pi?
I have OPENHABIAN
Hi !
Recently I updated from OH2.5 to 4.1 and I have extended Satel option with new (for me) things.
One of them is reading troubles and possibility to clean them.
I used function with auto discovery and got thing for troubles and assign switch item for it:
UID: satel:system:alarm:System
label: Alarm System
thingTypeUID: satel:system
configuration: {}
bridgeUID: satel:ethm-1:alarm
channels:
- id: troubles
channelTypeUID: satel:troubles
label: Troubles
description: Active when the system has troubles (trouble led is blinking on a panel)
configuration: {}
It looks like it doesnât work. Ie I had smoke alarm in kitchen and then red led is blinking on panels.
My item switch doesnât get update, it is still âoffâ.
I have checked binding debug:
`2024-01-13 18:54:45.906 [DEBUG] [satel.internal.event.EventDispatcher] - Distributing event: IntegraStatusEvent: type = 4, time = 2024-01-13T19:06:41, service mode = false, troubles = false, troubles memory = true, ACU-100 = false, INT-RX = false, grade 2/3 = false`
Also when I click to off this switch (clean) it has no reaction:
2024-01-13 19:06:12.191 [DEBUG] [ernal.handler.SatelStateThingHandler] - New command for satel:system:alarm:System:troubles: OFF
2024-01-13 19:06:12.193 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 8B, payload = 03 03 FF FF FF FF FF FF
2024-01-13 19:06:12.854 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = EF, payload = FF
I am not sure why Satel reported that troubles=false if LED is blinking.
Hi.
Smoke alarm is not a trouble, this is an alarm. Troubles are signaled by yellow led, not the red one.
Trouble is for example when your battery is dead. Check the documentation for full list of possible troubles.