These Homely alarm services uses the Homely API to check on status of the alarm system, components and zigbee network - reporting statuses into home automations that use Home Asstant style MQTT with automatic device discovery.
The Homely API is available for subscribers from Homely support upon request. It is probably not not the final API. The API is currently read-only, i.e. you cannot use these tools to change the state of the Homely alarm system. All API usage included here is based on periodic polls from the API servers provided. They are separate from the endpoints used by the alarm central and the Homely app.
It is recommended that you run these services provided here, the MQTT servers and the home automation services on the same host.Distributing the services is absolutely possible, but some further security measures should be taken.
For now, these services are implemented as Linux systemctl services only. Being small and simple, they should be pretty easy to set up if you have some basic Linux skills at hand.
By default, the services will automatically start on system startup as well as restart upon failure. You can easily follow the status from journalctl -fu homely2mqtt or journalctl -fu homely2domoticz
This part was the initial exploration of the Homely API. This service will simply updates the Domoticz alarm state, and a virtual multiselect switch based on the polled Homely alarm state
This service will provide:
- Alarm status updates
- In Domoticz, the built-in alarm state is directly updated using the JSON API
- A switch to monitor that all components reports being online from your alarm central
- A switch to monitor that all components have an OK battery status
- A switch to monitor that no components have been tampered with
- A measurement device for the lowest link quality (in %) reported for all alarm components
- Reporting all the temperature values for all alarm components that have a temp sensor
- At service startup, a topology listing of the Homely zigbee components is also provided (you can find it later from
journalctl -u homely2mqtt)
This service uses the MQTT Auto Discovery features in Home Assistant and recent releases of Domoticz (and probably more systems) for fully automatic device creation
The service will listen for web socket events as well as poll the home / device statuses. The web socket will deliver updates in near real time. The polled status is a fallback for the websocket not being updated as well as populating MQTT auto discovery devices that do not appear until a payload message is received.
Please download locally to a user with sudo root privileges, and install from there:
git clone https://github.com/hansrune/homely-tools.git
cd homely-toolsYou will have to create a configuration file as described below to contain your Homely account details as a minimum
You may want to review ./mqtt/install-mqtt.sh and ./mqtt/homely2mqtt.service if you want to change installation paths, the user that the service runs under, or other
If you are happy with running the service from /opt/homely2mqtt as the current user ($USER) , you can install or update as follows:
./mqtt/install-mqtt.shYou can easily follow the status from systemctl status homely2mqtt or journalctl -fu homely2mqtt
Updates can be done by:
git pull
./mqtt/install-mqtt.shYou can do some inital tests for communication with the API services as follows:
export HOMELY_USER=<your Homely login name (email)
export HOMELY_PASSWORD=<your password>
export PYTHONPATH="$PWD/API"
./ws/ws-test-threaded.py -dThis should list some home details, device details, a device table, then start the websocket communication, ending something like this:
INFO:engineio.client:WebSocket upgrade was successful
INFO:engineio.client:Sending packet PING data None
INFO:engineio.client:Received packet PONG data None
INFO:engineio.client:Received packet MESSAGE data 2["event",{"type":"device-state-changed","data":{"deviceId":"e143ddc5-33e9-492c-b1be-...","gatewayId":"5e2eed4f-f018-4c8f-ba37-...","locationId":"fb324b11-8301-4749-8a8f-...","modelId":"87fa1ae0-824f-4d42-be7a-...","rootLocationId":"5b11a8b9-e90c-40b5-b2d0-...","changes":[{"feature":"temperature","stateName":"temperature","value":19.2,"lastUpdated":"2022-HH-MMT06:36:04.875Z"}]}}]
INFO:socketio.client:Received event "event" [/]
websocket callback: {'type': 'device-state-changed', 'data': {'deviceId': 'e143ddc5-33e9-492c-b1be-...', 'gatewayId': '5e2eed4f-f018-4c8f-ba37-...', 'locationId': 'fb324b11-8301-4749-8a8f-...', 'modelId': '87fa1ae0-824f-4d42-be7a-...', 'rootLocationId': '5b11a8b9-e90c-40b5-b2d0-...', 'changes': [{'feature': 'temperature', 'stateName': 'temperature', 'value': 19.2, 'lastUpdated': '2022-XX-09T06:36:04.875Z'}]}}
INFO:engineio.client:Sending packet PING data None
INFO:engineio.client:Received packet PONG data None
.
.
INFO:engineio.client:Sending packet PING data None
INFO:engineio.client:Received packet PONG data None
websocket callback: {'type': 'alarm-state-changed', 'data': {'locationId': '5b11a8b9-e90c-40b5-b2d0-...', 'state': 'ARM_NIGHT_PENDING', 'timestamp': '2022-HH-MMT06:52:23.656Z'}}
INFO:engineio.client:Received packet MESSAGE data 2["event",{"type":"alarm-state-changed","data":{"locationId":"5b11a8b9-e90c-40b5-b2d0-...","state":"ARMED_NIGHT","userId":"1985b1af-62de-4cc2-8fe7-...","userName":"Your full name","timestamp":"2022-HH-MMT06:52:23.605Z","eventId":1249}}]
INFO:socketio.client:Received event "event" [/]
websocket callback: {'type': 'alarm-state-changed', 'data': {'locationId': '5b11a8b9-e90c-40b5-b2d0-...', 'state': 'ARMED_NIGHT', 'userId': '1985b1af-62de-4cc2-8fe7-...', 'userName': 'Your full name', 'timestamp': '2022-HH-MMT06:52:23.605Z', 'eventId': 1249}}
INFO:engineio.client:Sending packet PING data None
INFO:engineio.client:Received packet PONG data NoneAvailable command line options can be found from /opt/homely2mqtt/homely2mqtt.py -h
Normally, command line options will be added to FLAGS settings in the systemctl service definition file (homely2mqtt.service)
Settings like username and password should be added to the service environment file (/etc/default/homely2mqtt) with strict permissions (chmod 600 /etc/default/homely2mqtt).
You should also run the service as a dedicated user to avoid exposing the environment to non-root users. The user defaults to the user that runs the install script ($USER). If you want to change this username, modify homely2mqtt.service. The install script will only change the user and group if domo
Available environment settings:
HOMELY_USER- Your Homely username (normally your email address)HOMELY_PASSWORD- Your Homely passwordHOMELY_HOME- Your Homely instance name to use if you have more than one alarm set upMQTT_DISCOVERY- The MQTT discovery topic prefix, normally homeassistantMQTT_STATE- The MQTT state topic prefix. By default this is now homelyMQTT_SERVER- Defaults to 127.0.0.1MQTT_PORT- Defaults to 1883