Search results

In the past I had kept the Hass.io add-on Dockerfile the same and just changed the OmniLinkBridge version. The base image I was using was discontinued so I had to switch over to the homeassistant/ARCH-base-debain:buster images. This ensures the base image is up to date for security patches, etc...

This has been resolved. I had a typo in the aarch64 base image docker name. My Hass.io install that I use for testing is amd64 so I hadn't noticed. In Home Assistant you might have to go to the Add-on Store, click the three dots in the upper right, and select Check for updates. If it doesn't...

@pete_c There was an issue with the Home Assistant add-on where the logs / time sync were in UTC. The docker container TZ environment variable was not available to the first process launched in the container. I updated the add-on container to use the S6 overlay as shown in the hassio example...

I had a few moments to build docker images for arm/v7. These were tested on a raspberry pi 4 and everything appears to be working outside of MySQL. When pulling the docker image with portainer use excaliburpartners/omnilink-bridge:latest 

  Yes, mqtt should work without a password. It ignores the fields if the username is blank. However I would recommend using credentials for security reasons.   The official docker package is excaliburpartners/omnilink-bridge. I currently only have amd64 architecture images available. I can look...

  Did the wired sensor fail? The straight forward solution would be using the wired sensor to the Omni zone, which would also show in Home Assistant as a binary sensor.   Going back to your Node RED question, you will need to use MQTT directly. Use the "change" node to set msg.payload to...

  OmniLinkBridge overwrites all Home Assistant discovery information for all homeassistant/*/omnilink/* MQTT topics when started. Home Assistant needs to be restarted to cleanup any old devices it might have discovered from MQTT. Once those devices are gone the ones with the 2 suffix can be...

For those interested below is the config I use for controlling the garage doors with an OmniPro 2. It requires a zone, output, button, and automation rule. By not setting the output name, it won't be discovered by Home Assistant. The button is then used to momentarily turn the output on. In Home...

  Yes the arm away, arm home, and arm night buttons work. You'll probably want to check the OmniLinkBridge logs to see if it shows the MQTT command being received. You could also test by using MQTT Explorer or similar to send the arm command.       Audio support isn't built out in...

  I think that is to be expected. If the thermostat is in heat-cool / auto mode you need to set both. The automation rules you are setting up are solely related to Home Assistant. I did find a post on their community with a workaround.  ...

  Glad to hear! I've been using Home Assistant solely for the last year. Haiku doesn't work on my latest iPhone and Space requires too much navigating around to see the details. So far I only need Space to arm in vacation mode. I wish Leviton/HAI didn't discontinue the product line. I've been...

I just released version 1.1.10, which has the thermostat current status and adds switches to bypass/restore zones from Home Assistant.     You need to set target_temp_hgih and target_temp_low instead of temperature. Please refer...

I actually have this working on the dev branch of OmniLinkBridge. I did introduce a potentially breaking change for those subscribing to the thermostat/current_operation MQTT topic. Currently thermostat/current_operation has idle, cool, and heat as the values. Home Assistant expects them to be...

I've been on the search for a WiFi thermostat that works without a cloud connection.  I've seen the Venstar thermostats, which do have a local API. However I'm not a fan of their styling. I recently found the Honeywell TC500A commercial thermostat. The catch is Home Assistant doesn't have a...

You will also need to change  mqtt_enabled: false  to  mqtt_enabled: true

  You need to configure the MQTT settings in OLB and setup MQTT in Home Assistant. OLB publishes the device discovery info and state to MQTT. Home Assistant will then see these devices through it's MQTT device discovery.

  They should report the same status as PC Access for AC Power and Battery Low. I'll test it later and see if mine is working correctly. There is always a possibility I have a bug in the code.

  Setting mqtt_discovery_ignore_units only removes it from being auto discovered by Home Assistant. You will still be able to read it from MQTT.

  Not exactly. It's a separate module inside OmniLinkBridge. It records events from the OmniPro, not from the MQTT module. 

  If it helps, the unit numbers match what is programmed into the OmniPro PC Access software.