Texecom Alarm Integration

The -d flag means the container runs in the background. If you type docker logs c8b3e2632f7664d67346f9a5aa4bd2d86a0471bcf9a4fcad5013294f55c3eed6 you should see the log output.

Thanks for your help. Now my Docker is running with texecom image and Log is showing everything running smoothly

2020-09-01 07:16:40 - DEBUG: Publishing to texecom-1010987/power: {“battery_charging_current”:18,“battery_voltage”:13.56,“panel_current”:585,“panel_voltage”:13.7}

In Hass.io I have installed Mosquitto Broker and have setup the integration also but still there are no devices or entities showing in integration. Below is the Mosquitto Broker Log:

[17:52:58] INFO: Setup mosquitto configuration
[17:52:58] INFO: Found local users inside config
[17:53:00] INFO: Initialize Hass.io Add-on services
[17:53:00] INFO: Initialize Home Assistant discovery
[17:53:00] INFO: Start Mosquitto daemon
1598876581: mosquitto version 1.6.3 starting
1598876581: Config loaded from /etc/mosquitto.conf.
1598876581: Loading plugin: /usr/share/mosquitto/auth-plug.so
1598876581: |-- *** auth-plug: startup
1598876581: ├── Username/password checking enabled.
1598876581: ├── TLS-PSK checking enabled.
1598876581: └── Extended authentication not enabled.
1598876581: Opening ipv4 listen socket on port 1883.
1598876581: Opening ipv6 listen socket on port 1883.
1598876581: Opening websockets listen socket on port 1884.
1598876581: Opening ipv4 listen socket on port 8883.
1598876581: Opening ipv6 listen socket on port 8883.
1598876581: Opening websockets listen socket on port 8884.
1598876581: Warning: Mosquitto should not be run as root/administrator.
1598876596: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1598876599: New client connected from 172.30.32.1 as auto-15E28A24-B5D9-3ADD-849A-B5F0EA82C56A (p2, c1, k60, u’homeassistant’).
1598876684: Socket error on client auto-15E28A24-B5D9-3ADD-849A-B5F0EA82C56A, disconnecting.
1598878382: Saving in-memory database to /data/mosquitto.db.
1598878962: New connection from xxx.xxx.2.198 on port 1883.
[INFO] found my_user on local database
1598878972: New client connected from xxx.xxx.2.198 as texecom2mqtt (p2, c1, k30, u’my_user’).
1598879008: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1598879012: New client connected from 172.30.32.1 as auto-8D3A7AA9-2804-A880-349A-E8ECE6875BCE (p2, c1, k60, u’homeassistant’).
1598879012: Client auto-8D3A7AA9-2804-A880-349A-E8ECE6875BCE disconnected.
1598879012: New connection from 172.30.32.1 on port 1883.
1598879012: New client connected from 172.30.32.1 as auto-A2F71370-2D95-FCBA-3390-D996DA093D6D (p2, c1, k60, u’homeassistant’).
1598879050: Socket error on client auto-A2F71370-2D95-FCBA-3390-D996DA093D6D, disconnecting.
1598879050: New connection from 172.30.32.1 on port 1883.
1598879050: New client connected from 172.30.32.1 as auto-09C144E1-92F6-EF75-64F1-AE3753E78641 (p2, c1, k60, u’homeassistant’).
1598880183: Saving in-memory database to /data/mosquitto.db.
1598881530: Client texecom2mqtt has exceeded timeout, disconnecting.
1598881984: Saving in-memory database to /data/mosquitto.db.
1598883785: Saving in-memory database to /data/mosquitto.db.
1598885586: Saving in-memory database to /data/mosquitto.db.
1598886242: Client auto-09C144E1-92F6-EF75-64F1-AE3753E78641 has exceeded timeout, disconnecting.
1598886245: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1598886249: New client connected from 172.30.32.1 as auto-C47AE5E3-DF16-0476-DE59-581FF84A7F5F (p2, c1, k60, u’homeassistant’).
1598887387: Saving in-memory database to /data/mosquitto.db.
1598888716: New connection from xxx.xxx.2.198 on port 1883.
[INFO] found my_user on local database
1598888719: New client connected from xxx.xxx.2.198 as texecom2mqtt (p2, c1, k30, u’my_user’).
1598888719: Socket error on client texecom2mqtt, disconnecting.
1598889188: Saving in-memory database to /data/mosquitto.db.
1598941420: Saving in-memory database to /data/mosquitto.db.
1598941630: New connection from xxx.xxx.2.198 on port 1883.
[INFO] found my_user on local database
1598941633: New client connected from xxx.xxx.2.198 as texecom2mqtt (p2, c1, k30, u’my_user’).
1598943221: Saving in-memory database to /data/mosquitto.db.

My Raspberry pi is on xxx.xxx.2.31 and my Laptop is on xxx.xxx.2.198

Hi,

This looks interesting @dchesterton - i have a risco panel at the moment which has HA support but runs via the cloud so PIR responses can be a little slow and when used for light trigger it obviously has issues.

I’m moving house and looking for a new panel - if i went texecom premier elite does this integration get local updates from the panel or are they via cloud and may suffer the same lag ?

Thanks a lot

Question, if I use this docker component to add HA integration can I still have my alarm monitored by an external company?

Well, I use this integration and have an external monitoring company. You need a spare ComIp or SmartCom if you still want to use the app in my experience thought.

This integration is probably the best bit of my (quite) large HA setup :slight_smile:

Andrew

Hi AGW,

Thanks for this. I literally have just configured the panel (texecom premier elite) and I opted for the 4g+WIFI smartcom. I thought, if your gonna do it , do it proper.

I assume if I want to use the integration, and still have access to texecom cloud (wifi+4g) will will need the comIp, right?

Angelo

@dchesterton I have created the docker-compose.yml file and the config.yml file, I’m unable to find how to mount this file as a volume in Docker on windows. Any guidance please? Thanks.

@dchesterton I feel I have made progress but cannot seem to get this config file bound. Anyone have any help please with the command line? Thanks.

‘’’
PS C:\Users\user> docker run -d -v $PWD/SystemWidgets/config.yml:/app/config.yml --name texecom2mqtt dchesterton/texecom2mqtt:latest

a70df8405d98acbb674cb48eb74ca90af22799309478d86464fb57ec3ab3f5c9

PS C:\Users\user> docker logs a70df8405d98acbb674cb48eb74ca90af22799309478d86464fb57ec3ab3f5c9 /snapshot/app/dist/config.js:51
throw new Error(Error loading config file: ${e});
^

Error: Error loading config file: Error: EISDIR: illegal operation on a directory, read
at loadYamlConfig (/snapshot/app/dist/config.js:51:15)
at loadConfig (/snapshot/app/dist/config.js:62:24)
at /snapshot/app/dist/index.js:11:44
at Object. (/snapshot/app/dist/index.js:81:3)
at Module._compile (pkg/prelude/bootstrap.js:1794:22)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.runMain (pkg/prelude/bootstrap.js:1847:12)
at node:internal/main/run_main_module:17:47
‘’’