Satel binding - support, announcements and feature requests

antezedens · April 8, 2021, 7:31pm

Hi druciak,
thanks for the fast reply!
I tried with openHAB 3.0.1, same result.
I added a zone manually and I get status updates for the zone, so it works fine, but still no luck with auto discovery.
Maybe I just misunderstood the tutorial.
I expect that when I click on Things (http://localhost:8080/#!/settings/things/), that there should be a link to the inbox if anything was found. Maybe I just look in the wrong spot…

druciak · April 9, 2021, 2:15pm

You add manually bridge thing, then you click “plus” button to start scan, is that correct?
Is bridge thing online ?

druciak · April 9, 2021, 4:14pm

Anyway enable debug and check the log if the is something more that would help to solve the issue.

antezedens · April 9, 2021, 6:49pm

Ok I found it… You need to click Things, then (+) then select satel binding, then click scan.
Works now and saved me from typing 100 names
Thanks for your hint about starting the scan using + button!

Michael_Grymonprez · May 31, 2021, 10:15am

Hi,

I just install the binding for Satel.
The installation was perfect. The module discovered by himself my alarm system configuration…
When I create items, they stay at null value.
Here is my log in debug mode:

2021-05-31 12:05:00.832 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:00.977 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

2021-05-31 12:05:05.832 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:05.976 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

2021-05-31 12:05:10.833 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:10.976 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

2021-05-31 12:05:15.833 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:15.976 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

2021-05-31 12:05:20.834 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:20.976 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

2021-05-31 12:05:25.834 [DEBUG] [.satel.internal.protocol.SatelModule] - Sending message: Message: command = 7F, payload = 

2021-05-31 12:05:25.976 [DEBUG] [.satel.internal.protocol.SatelModule] - Got response: Message: command = 7F, payload = FF FF FF FF FF

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

Thanks for your help.

Regards,

druciak · June 1, 2021, 8:12pm

Hi.
It seems you have properly configured the connection, it gets the list of changes, but after that nothing.
This might happen when there are no things defined for the bridge, but you mentioned that all the things have been discovered. Do you have linked you items to Satel things channels?
Perhaps enabling TRACE level would say something more about the issue.

Michael_Grymonprez · June 1, 2021, 8:34pm

Thanks for your answer.

Yes, I linked some items. I did differents trials yesterday. All binary item stays at null but i receive once the value of the date time by exemple. But only once, no refresh after.

When i will be be back home I will change the level of logging.

gros1k · September 28, 2021, 7:17am

Did anyone try to connect Satel during GSM-X-ETH?
I want to buy satel, but im afraid that it will not work with openhab without ethm

druciak · October 1, 2021, 6:22pm

The binding communicates with alarm system using “integration protocol”. I don’t see on the website that GSM-X-ETH supports this protocol, so I would say, it will not work.

Lukas_Zich · October 3, 2021, 8:28am

Hi druciak, can I get the zone number which caused the partition alarm? Or can I get the zone number which is in the alarm state? I need these number in my rules. Thanks, L.

druciak · October 3, 2021, 9:18am

Hi Lukas.
Well, this question has nothing to do with Satel binding, so I would ask one of scripting masters.
Anyway there is no direct way to read thing’s configuration IMO, so no direct way to extract zone number in a rule. However you could do this using a workaround:

Add zones.map file with content item_name=zone_number and then in a rule

val zoneNumber = transform("MAP", "zones.map", triggeringItem.name)

Add zone number to item name, for example OfficeWindow_Zone12 and then extract zone number from item name using a regular expression:

val zoneNumber = transform("REGEX", ".*_Zone([0-9]+)$", OfficeWindow_Zone12.name)

Maybe there is a better way, these are just ideas that came to my mind.

Patyk · May 24, 2022, 9:18am

Hi druciak.
I have a problem with the zone status.
If the zone is bypassed, the violation status is not presented.
If I have an open window and I want to activate the alarm, I block the zone, so in OH I do not see the status whether the window is open or closed.
In DLOADX, the violation status is displayed irrespective of the bypass.

druciak · May 30, 2022, 1:35pm

Hi Patyk.
Have you checked debug logs, what comes from the system?
It would be easier to understand where the problem is with the logs, I don’t think it will be easy to reproduce this behavior on my system.

Roberto2 · June 12, 2022, 9:15pm

Hi Druciak,
I am using your bidning for more then 2 years. Lastly updated OH to version 3.2.0.
Now while executing your standard rule for sending last 10 logs- I can see following errors

[INFO ] [tel.internal.command.SatelCommandBase] - Other error. Message: command = EE, payload = 03 98

[internal.handler.SatelEventLogHandler] - Unable to read device info: EXPANDER, 24

then logs are send to email -sample here:
: Użycie pilota - expander: N/A, user: ANIA

PLUS → I am receiving popup on Android OH app with info “Partition changed”

But nobody changed Satel status while sending email - tested several times.
Valid event should be: (based on event list from Dload.EXE app)
: Użycie pilota - expander: ACU-120 ABAX, user: ANIA

Could you help me resolve this issue. Looks like on prevision versions there was no such issues.
Thank you for you work on this binding.

druciak · June 14, 2022, 6:03pm

Hi Roberto.
This looks like OH 3.2 issue, but it may be also incompatibility between satel binding and this new OH version.
I would need to install 3.2 on my system and try to reproduce this issue, but for sure it will take some time.
From the log you posted I can’t say anything more.

druciak · August 1, 2022, 2:09pm

Hi @smarthomepch
You have to enable Integration protocol. After that the communication should start working.

smarthomepch · August 1, 2022, 7:13pm

Thanks.
After reading the documentation a bit more carefully I came to the same conclusion:)

Roberto2 · August 11, 2022, 1:49pm

Hi Druciak
Any update here (2 months later) ?

druciak · August 11, 2022, 2:07pm

Hi Robero,
nothing on my side. Any update on your side?

Did you try to investigate a bit more the issue by enabling DEBUG logs?
Does the issue happen frequently or rarely?

I am still on 2.5 and it works great
I don’t have time to migrate to a newer OH version.

Roberto2 · August 11, 2022, 2:23pm

This issue happens every time rule which is sending last 10 logs is executed (your example from doc).
Didn’t have time to analyze logs Two days ago migrated to OH 3.3 (the same issue). Do you want some details? What are best options to enable logs for Satel binding? BTW : do you use Google TTS also? It has also many issues after migration to 3.x (token refresh failure)