Texecom Connect IP/API support?

[ap91]

Hi there,
Do you have any plans to integrate IP support via the Texecom Connect IP module or the API?
Thanks in advance

[kieranmjones]

I plan to do that, I'm sort of thinking that continuing support for the serial interface is sort of pointless as the protocols really aren't good and this isn't the most reliable method of integration. I need to update the firmware on my alarm (Which I don't have the tools for though) and purchase the new Connect module, but short answer yes I'd like to integrate it time and money permitting!

[MichaelVdheeren]

I'm looking for the same thing. Actually pushed the distributor in Belgium to get one installed asap. Running on the new connect hub since about a month. The app is a breeze compared to their previous things. Seems like the hub get's an ip address. But haven't figured out what I can do beyond.

Following the instruction manual of the Hub it seems that it uses SmartCom as the interface to the panel.

[MichaelVdheeren]

I'm in a discussion with the people from Texecom. As I am already using the SmartCom hub it seems you should be using Com 3 for the Connect API. Meaning that it doesn't serve over the IP network. Will follow up if I have more information.

[MichaelVdheeren]

Unfortunately the Smart Com Hub cannot be used with the Connect Protocol, it’s just for the app, at the moment.

However there should have been a small board included with the Smart Com which can be used to connect to the panel’s com port 3, so you can still use the Connect protocol with it.
A Com-IP can be connected to this Com 3 to give IP access or it can be used serially, completely separately to the Smart Com’s app connection.

[ap91]

Good job I never binned the ComIP module then. I think for the API details you have to sign an NDA but from there people seem to be utilising the connectivity for various things so hopefully homebridge is plausible. Would be great to have the alarm integrated and be able to use the sensors for other triggers etc also On 4 Jan 2018, at 13:53, Micha?l Vanderheeren <notifications@github.com<mailto:notifications@github.com>> wrote: Unfortunately the Smart Com Hub cannot be used with the Connect Protocol, it's just for the app, at the moment. However there should have been a small board included with the Smart Com which can be used to connect to the panel's com port 3, so you can still use the Connect protocol with it. A Com-IP can be connected to this Com 3 to give IP access or it can be used serially, completely separately to the Smart Com's app connection. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXroeGuVM-fIM_k-lD9SPI_utcxVU4qCks5tHNf6gaJpZM4REbT0>.

[MichaelVdheeren]

So far a portscan revealed this:

Port Scan has started…

Port Scanning host: 192.168.0.212

	 Open TCP Port: 	10001  		scp-config
Port Scan has completed…

[MichaelVdheeren]

Btw you can fairly easily ask for the API, they will just ask you to sign the NDA - which I did to find out more about it months ago already.

[kieranmjones]

For this plugin I use the Crestron protocol as the other protocols supported by serial interface do not give real time updates of zone events. So if you don't use the Crestron option then you will have to poll for zone status, whereas with the Crestron protocol it updates immediately when a zone event occurs, perfect for home automation. It also allows you to send keypad events to simulate keypad events so you can arm and disarm the Texecom alarm. I don't know what protocols are available on the new Connect Hub.

I didn't sign an NDA to get the protocols as then I would not be able to publish this open source, so instead I simply hooked up a serial cable and watched to see what happened, that coupled with some Googling and I could fairly easily build what I have done so far.

The port that you found on 10001 is the standard port for Wintex and other such things, it's used for ARC communications and other integrations. On the ComIP it's only possible to have one thing connected at once so I hope the new hub is better than that.

I think I'll need to get the new hub and then experiment. I think I need to buy a firmware flasher board as well which is a pain but I believe I need to update my firmwares in order to use the new hub.

Unfortunately I don't see that it is possible for me to develop a Homebridge plugin with the support of Texecom as they would never allow the protocol to be revealed in open source software so we're down to reverse engineering it ourselves if want it to happen.

[jogu]

I've had a smart com installed for a while now.

It does listen on 10001 and as I understand it behaves just like a ComIP there. However it still only accepts one connection.

(It seems to accept multiple connection if you connect via the texecom cloud, but that process is undocumented as far as I know, and also if you have multiple clients connected they interact "oddly" apparently resulting in the app corrupting it's database...)

An ongoing connection to this port causes issues I think - ie. preventing events being sent out to an IP based ARC (unless they're "priority" events like "alarm active" in which case the connection is forcibly dropped).

So, long story short - even with the smart com, if you want to connect a home automation system in you need to use COM3, either via a direct serial connection or via a ComIP.

The new Texecom Connect "API" in the v4 firmware for the panel is just another RS232 protocol; it can be used via a serial port or a ComIP.

[aefo]

"I didn't sign an NDA to get the protocols as then I would not be able to publish this open source"

FYI, based on a related project (https://github.com/jogu/texecom-connect/blob/master/README.md#texecom-nda) it seems they may be OK with open source code even after the NDA if you email to confirm.

[kieranmjones]

This support is being developed in another issue now and hopefully will be available soon, still utilising the Credtron protocol however but from what I hear that is likely the only option for the time being.

#4