Security Alarm System integration

[Mihail Panayotov]

There is one thing I would like to see very much in openHAB - a security system integration. The most widespread systems I see are PARADOX and DSC. They both have an "integration module" with RS-232 and/or USB. 

- PARADOX have PRT3, which speaks custom ASCII protocol and C-BUS. I had attached protocol documentation in this issue some time ago - http://code.google.com/p/openhab/issues/detail?id=36.

- DSC have actually two modules - a RS-232 one and an Ethernet one. The Ethernet one uses Microsoft's WSD protocol (Web Services on Devices) and the RS-232 one uses their own ASCII based protocol.

Does anyone have an interest implementing a binding for any of the modules above?

[Victor Belov]

Hi,

I plan to install Paradox in my new house in september-october. They also have an IP/Ethernet module and their own app for iPhone to control the system. So as soon as I get one, will be glad to work on that.

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To view this discussion on the web visit https://groups.google.com/d/msg/openhab/-/wWYciSb9-CkJ.
To post to this group, send email to ope...@googlegroups.com.
To unsubscribe from this group, send email to openhab+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openhab?hl=en.

[Mihail Panayotov]

I'm glad to hear that :) 

As much as I know PARADOX's Ethernet module uses their own application protocol that works only with BabyWare software. There is no protocol documentation available. At least I didn't found one.

BTW, here is a partially written DSC IT100 protocol module for OpenRemote -  http://openremote.svn.sourceforge.net/viewvc/openremote?view=revision&revision=4035

[Thomas Eichstädt-Engelen]

Hi,

please have in mind that Karel already provides a new serial and UDP/TCP binding which will be reviewed by Kai and me and will (hopefully) finds it's way into 1.0.0.

Regards,

Thomas E.-E.

[Mihail Panayotov]

Hi Thomas,

does this new binding provide some sophisticated protocol scheme definition? I think I read somewhere something about that? Could you point me to some additional info?

[EBorges]

 
Hello Mihail

I've not participated a lot in the forum but I read all the discussions with interest.
This is not a direct reply to your question but just would like to note, just in case of you not being aware, that there are some security alarm systems with direct KNX integration.
1. Comfort system by Cytech ( see http://www.cytech.biz )
2. Varuna3 Extra system by Hestia France ( see http://www.hestia-france.com/Centrale_domotique.html )
3. KNX Alarm sold by Jung and Berker ( see for example http://www.jung-catalogue.com/index_fa.htm?uid=2&id=EAM4000GB )

Cytech's Comform is the one I have installed at my home. Very compete and can be used also as a gateway to non KNX systems ( X10, Z-Wave, C-Bus, IR, RS232, ethernet/IP, Binary I/O, GSM, Phone land lines... and so one)

Cheers
Eurico

[Mihail Panayotov]

Thank you, EBorges. I didn't been aware of these. 

Do you know more burglar alarms like these, with KNX integration?

[EBorges]

After posting my message yesterday I became aware , via discussion forum on http://ask.aboutknx.com ( I'm user EB on that forum), of another alarm that integrates directly with KNX made by Satel. Its the Satel Integra model and you can see detais of the central panel and the KNX integration module on http://www.satel.pl/en/cat/2 .

Cheers
Eurico Borges

[Mihail Panayotov]

Thank you for this info.

[Karel Goderis]

For those interested, I will be implementing the binding (based on RS232) for alarm systems from Aritech (previously General Electric). 

From what I know is that there is a legal side to this kind of integration work, e.g. in some countries, like Belgium and also the Netherlands I think, it is legally now allowed  to have a inbound interaction with alarm systems (e.g. you are only allowed to read out data, but you are not allowed to arm or disarm the system from the "outside") because of security reasons. Therefore, some off the shelf systems are quite limited in terms of capabilities. 

KR

K

--
You received this message because you are subscribed to the Google Groups "openhab" group.

To view this discussion on the web visit https://groups.google.com/d/msg/openhab/-/vek-dtvXo0YJ.

[Valdemaras Pipiras]

Hello Karel,

Have you already implemented this binding? 

If yes - it would be nice to see it.

[Karel Goderis]

It is in progress, but is far from finished, and very complicated in terms of building blocks required. 

I have finally installed the ATS Advanced from UTC/Aritech, and I got the "IP" version with an ethernet port, so the controlling happens via TCP/IP

Karel

To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Ηλίας Καρακουλάκης]

For Paradox & Caddx there seems to be a new KNX gateway on the market, I received this on my email a couple of weeks ago:

There's also a new Ksenia alarm system I'd like to get my hands on as it is purely IP-based http://www.kseniasecurity.com/index.php?option=com_content&view=frontpage&Itemid=191&lang=en

I'm currently using Comfort with my projects, I am generally satisfied but I think this system has reached its limits.

Elias

[Toni Lundin]

Web GW for Siemens SPC http://forum.lundix.se/ runs on Linux, license 500sek 75us$

SPC Web Gateway REST and Websocket API description: http://spc-web-gw.lundix.se/forum/download/file.php?id=5

[604...@gmail.com]

SATEL has TCP/IP communication module (ETHM-1) with full documentation: http://www.satel.pl/en/download/instrukcje/ethm1_op_en_1.07.pdf.

[pay...@gmail.com]

I would like to have Satel ETHM-1 binding as well. Unfortunaltey I'm not able to do it by myself, so I hope that someone will do it and share it soon ;)

[jarosla...@gmail.com]

I do plan to work on integration with Satel, but using INT-RS.

[jarosla...@gmail.com]

BTW. It looks like that starting from this year ETHM-1 supports exactly the same protocol, so maybe I will be able to support both INT-RS and ETHM-1.

[604...@gmail.com]

This documentation could be helpful to you: http://www.elektroda.pl/rtvforum/topic2091518.html

[pay...@gmail.com]

This documentation on electroda.pl was made by analizing old protocol without official documentation avaliable (still supported in new firmware, I think).
I suppose that it will be easier to implement ETHM-1 binding with new firmware 1.07 using additional protocol for integration, which is the same as in INT-RS module, and which have full documentation provided by Satel.
I think that both protocols are now supported in new firmware, because I think they didn't change android app KPD-2 after new firmware for ETHM-1 and it still works.

[604...@gmail.com]

Any good news about progress? :-)

W dniu środa, 23 lipca 2014 12:01:18 UTC+2 użytkownik jarosla...@gmail.com napisał:

[krzyszto...@gmail.com]

I was going to implement Satel binding as well, but since somebody else has already started, I would also like to get status update.

[604...@gmail.com]

If you could please begin Satel binding. Maybe more eager people will join to this project when someone begin something.

[druciak]

First I need to purchase a module (likely ethm-1) ;), then find some free time to start the work. Not sure how it will go, but definitely is on my list.
Krzysztof

[druciak]

FYI: I started working on this binding, but I cannot say when it will be finished. Hopefully by the end of next month there will be initial release with just some functions implemented.
Krzysztof

[604...@gmail.com]

Great news! Thanks! Now I have to buy ethm-1 :-).

[604...@gmail.com]

I've bought ETHM-1 PLUS. Now, I'm patiently waiting for first release.

W dniu środa, 29 października 2014 19:48:58 UTC+1 użytkownik druciak napisał:

[druciak]

I've bought ETHM-1 PLUS. Now, I'm patiently waiting for first release.

Wow, you did this before me. I am hoping to get my module by the end of this week. Then I will new few free hours to install it.
The good news is that early version is almost done, but I haven't had a chance to test it with an ETHM-1, so likely it will not work. But if you are very unpatient, you could test it on your module, if it is already installed. What kind Integra do you have?
Krzysztof

[Stefaan Bolle]

Would it be possible to have the caddx NX-8(E) series integrated with Openhab?

[604...@gmail.com]

I have Integra 32 (v1.12). My ETHM-1 is already installed :-). One tip before you try connect via WWW. Don't use Java version higher than 7.71.Satel firmware dosen't work with Java 8.25.

Of course, I can with pleasure test this early version.

[druciak]

Attached binding file.
First of all, you need to enable ethm-1 integration feature in the module properties in DloadX program. Do not enable encryption (it is not implemented yet) and leave default port 7094.

Then configure the module in openhab.cfg:

satel:host=<ip of your ethm-1>

These are all the settings with defaults, but you don't need to put them:

satel:port=7094
satel:timeout=5000
satel:refresh=10000
satel:user_code=
satel:encryption_key=

Then configure satel binding logging to use its own file. Put following lines to logback.xml:

<appender name="SATELFILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
   <file>logs/satel.log</file>
   <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
      <!-- weekly rollover and archiving -->
      <fileNamePattern>logs/satel-%d{yyyy-ww}.log.zip</fileNamePattern>
      <!-- keep 30 days' worth of history -->
      <maxHistory>30</maxHistory>
   </rollingPolicy>
   <encoder>
     <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{30}[:%line]- %msg%n%ex{5}</pattern>
   </encoder>
</appender>

<!-- Change DEBUG->TRACE for even more detailed logging -->
<logger name="org.openhab.binding.satel" level="TRACE" additivity="false">
   <appender-ref ref="SATELFILE" />
</logger>

Then you can add some items to your items file. General item binding config syntax is:

<object_type>[:<state_type>][:<object_number>]

where
- object_type is one of zone, input, output, doors,
- state_type depends on object_type, see below,
- object_number is an integer specyfying either zone number, input number etc.

For zones state_type can be for example: armed, entry_time, alarm, alarm_memory, and others
For intput: violation, tamper, alarm, alarm_memory, etc
For output you omit this parameter.
For doors: opened, opened_long.

Example items:

Group    All
Group    Satel    "Satel"        (All)
Contact    Satel_Input1        "Input 1"        (Satel)        { satel="input:violation:1" }
Switch    Satel_Output1        "Output 1"        (Satel)        { satel="output:1" }
Contact    Satel_Zone1_Alarm    "Alarm in zone 1"    (Satel)        { satel="zone:alarm:1" }

Let me know if you have any questions.
Krzysztof

[604...@gmail.com]

Thanks!, I'll chceck this tomorrow.

[druciak]

Would it be possible to have the caddx NX-8(E) series integrated with Openhab?

I know nothing about this system, but if there is add-on module or it exposes some data through RS or ETH, I guess it would.
Krzysztof

[604...@gmail.com]

My log file. Something goes wrong :-)

In satel integration ON, port: 7094, encryption OFF.

2014-11-18 17:13:34.995 DEBUG o.o.b.s.i.SatelActivator[:30]- Satel binding has been started.

2014-11-18 17:13:35.050 TRACE o.o.b.s.internal.SatelBinding[:91]- Binding configuration updated: org.eclipse.equinox.internal.cm.ConfigurationDictionary@2d61d305

2014-11-18 17:13:35.068 INFO  o.o.b.s.i.protocol.Ethm1Module[:46]- Connecting to ETHM-1 module at 192.168.0.250:7094

2014-11-18 17:13:35.074 INFO  o.o.b.s.i.protocol.SatelModule[:131]- Communication thread started

2014-11-18 17:13:35.075 DEBUG o.o.b.s.i.protocol.SatelModule[:296]- Sending message: Message: command = 0x7E, payload = 

2014-11-18 17:13:35.075 DEBUG o.o.b.s.i.protocol.SatelModule[:164]- Command enqueued: Message: command = 0x7E, payload = 

2014-11-18 17:13:35.078 TRACE o.o.b.s.i.p.SatelMessage[:104]- Calculated checksum = 0x04

2014-11-18 17:13:35.079 TRACE o.o.b.s.i.protocol.SatelModule[:300]- Waiting for response

2014-11-18 17:13:35.080 TRACE o.o.b.s.internal.SatelBinding[:111]- Binding properly configured

2014-11-18 17:13:35.080 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 17:13:39.062 TRACE o.o.b.s.i.SatelGenericBindingProvider[:62]- Processing binding configuration for item Satel_Input1

2014-11-18 17:13:39.065 TRACE o.o.b.s.i.SatelGenericBindingProvider[:62]- Processing binding configuration for item Satel_Zone1_Alarm

2014-11-18 17:13:40.295 ERROR o.o.b.s.i.protocol.SatelModule[:258]- Unexpected exception occurred during reading a message

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at java.net.SocketInputStream.read(SocketInputStream.java:210)

at org.openhab.binding.satel.internal.protocol.SatelModule.readMessage(SatelModule.java:208)

at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:301)

2014-11-18 17:13:45.081 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 17:13:55.081 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

W dniu poniedziałek, 17 listopada 2014 21:34:53 UTC+1 użytkownik druciak napisał:

[druciak]

Try this one, if you have time. I just changed logging, don't expect this one is going to work... ;)
Krzysztof

[604...@gmail.com]

My log file:

2014-11-18 18:25:30.390 DEBUG o.o.b.s.i.SatelActivator[:30]- Satel binding has been started.

2014-11-18 18:25:30.414 TRACE o.o.b.s.i.SatelGenericBindingProvider[:62]- Processing binding configuration for item Satel_Input1

2014-11-18 18:25:30.477 TRACE o.o.b.s.internal.SatelBinding[:91]- Binding configuration updated: org.eclipse.equinox.internal.cm.ConfigurationDictionary@54129ed9

2014-11-18 18:25:30.500 INFO  o.o.b.s.i.protocol.Ethm1Module[:46]- Connecting to ETHM-1 module at 192.168.0.250:7094

2014-11-18 18:25:30.505 DEBUG o.o.b.s.i.protocol.SatelModule[:164]- Command enqueued: Message: command = 7E, payload = 

2014-11-18 18:25:30.506 INFO  o.o.b.s.i.protocol.SatelModule[:131]- Communication thread started

2014-11-18 18:25:30.507 DEBUG o.o.b.s.i.protocol.SatelModule[:309]- Sending message: Message: command = 7E, payload = 

2014-11-18 18:25:30.508 TRACE o.o.b.s.internal.SatelBinding[:111]- Binding properly configured

2014-11-18 18:25:30.509 TRACE o.o.b.s.i.p.SatelMessage[:104]- Calculated checksum = D860

2014-11-18 18:25:30.510 TRACE o.o.b.s.i.protocol.SatelModule[:269]- Writing message bytes: 7E D8 60

2014-11-18 18:25:30.510 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 18:25:30.516 TRACE o.o.b.s.i.protocol.SatelModule[:313]- Waiting for response

2014-11-18 18:25:35.732 ERROR o.o.b.s.i.protocol.SatelModule[:258]- Unexpected exception occurred during reading a message

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at java.net.SocketInputStream.read(SocketInputStream.java:210)

at org.openhab.binding.satel.internal.protocol.SatelModule.readMessage(SatelModule.java:208)

at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:314)

2014-11-18 18:25:40.511 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 18:25:50.511 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh 

[druciak]

Last one today, if you don't mind testing it.
I guess I'll need to wait for my own module to get it working...
Krzysztof

[604...@gmail.com]

Now log file looks better...

2014-11-18 20:35:20.922 DEBUG o.o.b.s.i.SatelActivator[:30]- Satel binding has been started.

2014-11-18 20:35:20.944 TRACE o.o.b.s.i.SatelGenericBindingProvider[:62]- Processing binding configuration for item Satel_Input1

2014-11-18 20:35:21.111 TRACE o.o.b.s.internal.SatelBinding[:91]- Binding configuration updated: org.eclipse.equinox.internal.cm.ConfigurationDictionary@4f2c3657

2014-11-18 20:35:21.121 INFO  o.o.b.s.i.protocol.Ethm1Module[:46]- Connecting to ETHM-1 module at 192.168.0.250:7094

2014-11-18 20:35:21.124 INFO  o.o.b.s.i.protocol.SatelModule[:131]- Communication thread started

2014-11-18 20:35:21.126 DEBUG o.o.b.s.i.protocol.SatelModule[:312]- Sending message: Message: command = 7E, payload = 

2014-11-18 20:35:21.126 TRACE o.o.b.s.i.protocol.SatelModule[:164]- Command enqueued: Message: command = 7E, payload = 

2014-11-18 20:35:21.127 TRACE o.o.b.s.i.p.SatelMessage[:104]- Calculated checksum = D860

2014-11-18 20:35:21.127 TRACE o.o.b.s.internal.SatelBinding[:111]- Binding properly configured

2014-11-18 20:35:21.128 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 20:35:21.128 TRACE o.o.b.s.i.protocol.SatelModule[:280]- Writing message bytes: FE FE 7E D8 60 FE 0D

2014-11-18 20:35:21.129 TRACE o.o.b.s.i.protocol.SatelModule[:316]- Waiting for response

2014-11-18 20:35:21.131 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: FE

2014-11-18 20:35:21.132 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: FE

2014-11-18 20:35:21.132 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 7E

2014-11-18 20:35:21.133 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 01

2014-11-18 20:35:21.133 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 31

2014-11-18 20:35:21.134 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 31

2014-11-18 20:35:21.134 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 32

2014-11-18 20:35:21.135 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 32

2014-11-18 20:35:21.135 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 30

2014-11-18 20:35:21.135 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 31

2014-11-18 20:35:21.136 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 33

2014-11-18 20:35:21.136 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 31

2014-11-18 20:35:21.137 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 31

2014-11-18 20:35:21.137 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 32

2014-11-18 20:35:21.138 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 39

2014-11-18 20:35:21.138 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 00

2014-11-18 20:35:21.138 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: FF

2014-11-18 20:35:21.139 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 33

2014-11-18 20:35:21.139 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: FF

2014-11-18 20:35:21.140 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: FE

2014-11-18 20:35:21.140 TRACE o.o.b.s.i.protocol.SatelModule[:210]- Read byte: 0D

2014-11-18 20:35:26.151 ERROR o.o.b.s.i.protocol.SatelModule[:259]- Unexpected exception occurred during reading a message

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at java.net.SocketInputStream.read(SocketInputStream.java:210)

at org.openhab.binding.satel.internal.protocol.SatelModule.readMessage(SatelModule.java:208)

at org.openhab.binding.satel.internal.protocol.SatelModule.communicationLoop(SatelModule.java:317) 

2014-11-18 20:35:31.128 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 20:35:41.129 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 20:35:51.130 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

2014-11-18 20:36:01.131 DEBUG o.o.b.s.internal.SatelBinding[:75]- Module not initialized yet, skipping refresh

[druciak]

Created new PR for Satel binding: https://github.com/openhab/openhab/pull/1723 and started new thread: https://groups.google.com/forum/?hl=pl#!topic/openhab/xGsY8oJwhDE
Krzysztof