Texecom integration updated

yulasinio · July 24, 2020, 10:36am

Welcome Jon.

You are not wrong, there are no idiot proof guides out there. There a few ways to integrate Texecom in HA and a few people that did it but there are no fool proof write ups anywhere.
2 days ago I started to look into it again and I’m currently deciding which path to go i.e. use COM port for connection or MQTT and NodeMCU.
If I’m able to figure it all out I’m planning to write a step by step document.

dchesterton · August 17, 2020, 9:21pm

I’ve released a Docker image which fully supports Texecom and MQTT including remote arming/part arming/disarming as well as full zone updates: https://hub.docker.com/r/dchesterton/texecom2mqtt. It has Home Assistant auto-discovery built-in too.

Texecom won’t allow me to publish the source code unfortunately as I’ve signed the NDA but I hope it’s useful to someone.

yulasinio · August 17, 2020, 9:30pm

Thank you for doing this Daniel. I’m running HA in docked on my NAS so I can easily install this and test.

dchesterton · August 17, 2020, 9:41pm

Great! Let me know how you get on I’ve only tested it with my Elite 24 panel and a ComIP but it should work with other panels and the SmartCom

anthonyangel · August 17, 2020, 10:17pm

I’ve pulled your image and am testing it with a SmartCom and an Elite 64. Looks good so far - it connects to the alarm, the autodiscovery works nicely and it pulls all of my sensors in correctly (I haven’t tried arming the alarm as I’m not brave enough to risk waking kids up!).

As there’s no GitHub repo for it it would probably be useful to have 1 forum post for feedback, questions & suggestions.

dchesterton · August 17, 2020, 11:28pm

Glad to hear it’s working I’m really keen to get feedback from people such as yourself using the bigger panels as there are some API differences between the panel types.

Good idea, I’ve created a thread here:

Feel free to post any feedback or issues there.

fredkruger · September 13, 2020, 12:26pm

Hi Daniel,

Thanks for all your hard work. I’ve just managed to get this working with my Elite 168 panel.
Sensors working great! Not tried arming yet.

Some small problems I did notice:

My 2 areas show up as “9” & “10” in the log. I guess this is because of some differences in the simple protocol for the 168.
I haven’t managed overide the zone name & class types in the config yet. Mayve I’m doing something wrong? I get messaged in the HA log like this:

20-09-13 11:36:40 WARNING (MainThread) [supervisor.addons.validate] Unknown options zones
20-09-13 11:36:40 WARNING (MainThread) [supervisor.addons.validate] Unknown options areas

This is what I have in my config:

zones:
‘1’:
device_class: motion
name: test
‘2’:
device_class: motion
name: test2
areas:
house:
mapping:
full_arm: armed_away
detatched_garage:
mapping:
part_arm_1: armed_night2

dchesterton · September 13, 2020, 4:52pm

Thanks, I’ll take a look at that.

The zones and areas config should be under homeassistant, so you should have something like:

texecom:
  host: ...

mqtt:
  host: ...

homeassistant:
  discovery: true
  zones:
    '1':
      device_class: motion
      name: test
    '2':
      device_class: motion
      name: test2
  areas:
    house:
      mapping:
        full_arm: armed_away
    detached_garage:
      mapping:
        part_arm_1: armed_night

There was a small issue with parsing the config so I’ve just pushed an update to the add-on. Can you try updating the add-on and see if it works?

fredkruger · September 13, 2020, 5:20pm

dchesterton:

  discovery: true
  zones:
    '1':
      device_class: motion
      name: test
    '2':
      device_class: motion
      name: test2
  areas:
    house:
      mapping:
        full_arm: armed_away
    detached_garage:
      mapping:
        part_arm_1: armed_night

Thanks, still no luck.
This is my config now:

texecom:
  host: 192.168.0.101
  udl_password: 'xxxxxx'
  port: 10001
mqtt:
  host: 'mqtt://core-mosquitto:1883'
  username: mosquitto
  password: #######
homeassistant:
  discovery: true
  prefix: homeassistant
  zones:
    '1':
      device_class: motion
      name: test
    '2':
      device_class: motion
      name: test2
  areas:
    house:
      mapping:
        full_arm: armed_away
        part_arm_1: armed_night
    detached_garage:
      mapping:
        full_arm: armed_away
        part_arm_1: armed_night

heres your texecom2mqtt log:

2020-09-13 18:06:02 - INFO: Connected to alarm, sleeping for 0.5 seconds...
2020-09-13 18:06:03 - INFO: Connection ready
2020-09-13 18:06:03 - INFO: Fetched serial number: 100####
2020-09-13 18:06:03 - INFO: Logging in
2020-09-13 18:06:03 - INFO: Successfully logged in
2020-09-13 18:06:03 - INFO: Connected to MQTT
2020-09-13 18:06:04 - INFO: Fetched panel info: Premier Elite 168 (V5.00.02LS1)
2020-09-13 18:06:05 - INFO: Fetched zone 1: Doorbell Push Switch (type: Latch Key) (areas: [9,10])
2020-09-13 18:06:05 - INFO: Fetched zone 2: Hall PIR (type: Guard Access) (areas: [9])
2020-09-13 18:06:05 - INFO: Fetched zone 3: Kitchen/BreakfasPIR (type: Guard) (areas: [9])
2020-09-13 18:06:06 - INFO: Fetched zone 4: Lounge PIR (type: Guard) (areas: [9])
2020-09-13 18:06:06 - INFO: Fetched zone 5: Sun/Dining PIR (type: Guard) (areas: [9])
2020-09-13 18:06:06 - INFO: Fetched zone 6: Landing PIR (type: Guard) (areas: [9])
2020-09-13 18:06:07 - INFO: Fetched zone 7: Garage PIR (type: Guard Access) (areas: [9])
2020-09-13 18:06:07 - INFO: Fetched zone 8: Smoke Detetector (type: Fire) (areas: [9])
2020-09-13 18:06:08 - INFO: Fetched zone 10: Detached Garage PIR 1 (type: Guard Access) (areas: [10])
2020-09-13 18:06:08 - INFO: Fetched zone 12: Detached Garage Side Door (type: Entry/Exit 1) (areas: [10])
2020-09-13 18:06:08 - INFO: Fetched zone 13: Detached Garage Main Door (type: Guard) (areas: [10])
2020-09-13 18:06:11 - INFO: Fetched zone 20: Front Door Contact (type: Entry/Exit 1) (areas: [9])
2020-09-13 18:06:11 - INFO: Fetched zone 21: Back Door Contact (type: Guard) (areas: [9])
2020-09-13 18:06:11 - INFO: Fetched zone 22: Kitchen French DContact (type: Guard) (areas: [9])
2020-09-13 18:06:11 - INFO: Fetched zone 23: Sunroom French DContact (type: Guard) (areas: [9])
2020-09-13 18:06:12 - INFO: Fetched zone 24: Util/Garage DoorContact (type: Guard) (areas: [9])
2020-09-13 18:06:12 - INFO: Fetched zone 25: Roller Garage DrContact (type: Entry/Exit 2) (areas: [9])
2020-09-13 18:06:12 - INFO: Fetched zone 26: Roller Access Access Keypad (type: Latch Key) (areas: [9])
2020-09-13 18:06:13 - INFO: Fetched zone 27: Zone 27 (type: Custom) (areas: [9])
2020-09-13 18:06:14 - INFO: Fetched zone 30: Manual Bell Trig (type: Custom) (areas: [12])
2020-09-13 18:06:27 - INFO: Fetched zone 73: Drive Beam (type: Latch Key) (areas: [9])
2020-09-13 18:06:58 - INFO: Fetched area 9: Area I
2020-09-13 18:06:58 - INFO: Updating all zone states
2020-09-13 18:06:58 - INFO: Updating all area states
2020-09-13 18:13:06 - INFO: Kitchen/BreakfasPIR status changed to Active
2020-09-13 18:13:18 - INFO: Kitchen/BreakfasPIR status changed to Secure

And heres part of the system log:

20-09-13 17:06:01 WARNING (MainThread) [supervisor.addons.validate] Unknown options prefix
20-09-13 17:06:01 WARNING (MainThread) [supervisor.addons.validate] Unknown options zones
20-09-13 17:06:01 WARNING (MainThread) [supervisor.addons.validate] Unknown options areas
20-09-13 17:06:02 INFO (SyncWorker_5) [supervisor.docker.addon] Start Docker add-on dchesterton/texecom2mqtt with version None

it doesnt seem to like any of my config from " prefix: homeassistant".

any ideas?

dchesterton · September 13, 2020, 5:26pm

I think there’s 2 issues:

It’s not picking up your areas correctly (will take a look at this)
You need to pull the latest version of the add-on which should fix the ‘Unknown options’ error

dchesterton · September 13, 2020, 6:33pm

I’ve pushed an update to the container which should fix the areas issue. Can you try deleting the add-on completely and re-adding? Hopefully it should all work

fredkruger · September 13, 2020, 6:56pm

Thanks a million, all sorted now. Let me know if you need anything else testing.

fredkruger · September 13, 2020, 9:49pm

there might be a slight problem with the areas, some of them are duplicated. see log below:

2020-09-13 22:43:18 - INFO: Fetched area 1: House
2020-09-13 22:43:18 - INFO: Fetched area 2: Detached Garage
2020-09-13 22:43:18 - INFO: Fetched area 4: Area D
2020-09-13 22:43:18 - INFO: Fetched area 2: Area B
2020-09-13 22:43:18 - INFO: Fetched area 4: Area D
2020-09-13 22:43:18 - INFO: Updating all zone states
2020-09-13 22:43:18 - INFO: Updating all area states

dchesterton · September 13, 2020, 11:46pm

Ah, sorry about that. I’ve pushed another fix which should fix the issue for you. I think you’re the first person to run the app on one of the larger panels so you’re unearthing a few bugs

fredkruger · September 14, 2020, 5:35pm

Thanks Daniel,don’t you sleep:-). Anyway just tried tonight as been at work, that’s sorted it.

Something else I noticed.for the areas. in the config i have:

  areas:
    '1':
      mapping:
        full_arm: armed_away
        part_arm_1: armed_night
    '2':
      mapping:
        full_arm: armed_away
        part_arm_1: armed_night

But in the front end it shows buttons for “Arm Away” & “Arm Home”, I think it should come up with .“Arm Away” & “Arm Night”, for that config. Unless I’ve missed something.

dchesterton · September 14, 2020, 5:58pm

Nice one let me know if you see any other bugs.

Unfortunately the frontend is configured separately and the app can’t control it. You’ll just need to change the ‘states’ config within the Lovelace card: https://www.home-assistant.io/lovelace/alarm-panel/.

fredkruger · September 14, 2020, 8:03pm

ah didn’t know about the Alarm Panel card until now, thanks for pointing it out.
I’ll let you know if I find anything else…

I don’t know what anyone else thinks, but i think it would be nice if there was a config option for Entity IDs so that they use just zone numbers and area numbers.
That way any changes in automaions and lovelace configs etc are not affected if the panel names are updated or changed.

biggaz · September 15, 2020, 7:51pm

Any thoughts about allowing outputs to be controlled with this? It looked like it was possible from the docs, and not just the “pc control” outputs either … unless I read them wrong.

biggaz · September 15, 2020, 8:06pm

Also, if it helps, this seems to run on “Podman”, which is some kind of open source Docker implementation.

I installed Podman, and had to allow a user multiple guid/uuid on Fedora, then able to run the container not as root, which seems a good thing - podman/docs/tutorials/rootless_tutorial.md at bec96ab03479c5a799be8581bd32c2777ff23ea7 · containers/podman · GitHub

So I did …

dnf install podman
podman pull dchesterton/texecom2mqtt
mkdir texecom2mqtt
vim texecom2mqtt/config.yaml

Pasted and edited the config with VIM. Then …

podman run -v $PWD/texecom2mqtt/config.yaml dchesterton/texecom2mqtt

Edit, found a guide to installing an MQTT server here - How to install an MQTT Broker - Mosquitto Install/Config on Debian/Ubuntu/Mint/Fedora/Raspbian
And how to point home assistant at it here - MQTT - Home Assistant

dchesterton · September 15, 2020, 11:30pm

It’s not supported yet but it’s a feature I’m interested in adding. I can’t promise a timeline but it’s something I’m looking to add fairly soon.