OmniLinkBridge to integrate Home Assistant, SmartThings, Node-RED

Looks like OmniLink Bridge has an update available. Is anyone else having trouble getting it to update from within HA? It won't work for me. Any ideas?

"You have 1.1.14.1 installed. Click update to update to version 1.1.15.2"
I'm not getting that message because I can see I've already got 1.1.15.2 running. That might have been the first version I installed though, so I might not have gone through an update process at all.
 
I'm not getting that message because I can see I've already got 1.1.15.2 running. That might have been the first version I installed though, so I might not have gone through an update process at all.
Thank you. it seems like I might need to reinstall from scratch to update...but I hesitate to do this since I have everything set up perfectly now.
 
Noticing an OmniLink Bridge crash with lastest updated version:
Current version: 1.1.16.1

Code:
services-up: info: copying legacy longrun omnilink-bridge (no readiness notification)
s6-rc: info: service legacy-services successfully started
[06:44:24] INFO: Starting OmniLink Bridge...
2024-05-04 06:44:25 [OmniLinkBridge.Settings ERR] Invalid type specified for mqtt_discovery_button_type
[06:44:25] WARNING: OmniLink Bridge crashed, halting add-on
[06:44:25] INFO: OmniLink Bridge stopped, restarting...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

For time being downloaded to previous version from backup.
You have 1.1.15.2 installed. Click update to update to version 1.1.16.1
 
Last edited:
Noticing an OmniLink Bridge crash with lastest updated version:
Current version: 1.1.16.1

Code:
services-up: info: copying legacy longrun omnilink-bridge (no readiness notification)
s6-rc: info: service legacy-services successfully started
[06:44:24] INFO: Starting OmniLink Bridge...
2024-05-04 06:44:25 [OmniLinkBridge.Settings ERR] Invalid type specified for mqtt_discovery_button_type
[06:44:25] WARNING: OmniLink Bridge crashed, halting add-on
[06:44:25] INFO: OmniLink Bridge stopped, restarting...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

For time being downloaded to previous version from backup.
You have 1.1.15.2 installed. Click update to update to version 1.1.16.1
Looks like 1.1.16.2 solved it. Working now.

and now with AUDIO SUPPORT for HAI HiFi!!!
 
Version 1.1.19 has been released with the fix for Home Assistant 2024.6 and the ability to change the arming modes displayed. Problem is, I cant figure out how to do it. (I want to disable arm_vacation and arm_night)

I think I need to type something here, in the configuration tab:

339952177-13e51c82-226a-4d68-9c3c-afd3fbdc4081.png

But I can't get the format correct. Here are the instructions from the documentation tab...any ideas?

339952766-ecac7a9f-664a-4dc0-ae5b-5bbe63113043.png
 
Last edited:
Not totally sure but try adding this to the yaml file using the yaml editor

mqtt_discovery_override_area: id=1;code_disarm=true;arm_vacation=false;arm_night=false

or

mqtt_discovery_override_area: id=1;code_arm=true;code_disarm=true;arm_vacation=false
mqtt_discovery_override_area: id=1;code_arm=true;code_disarm=true;arm_night=false
 
Not totally sure but try adding this to the yaml file using the yaml editor

mqtt_discovery_override_area: id=1;code_disarm=true;arm_vacation=false;arm_night=false

or

mqtt_discovery_override_area: id=1;code_arm=true;code_disarm=true;arm_vacation=false
mqtt_discovery_override_area: id=1;code_arm=true;code_disarm=true;arm_night=false

I'm not sure which yaml file?
 
Configuration of the add on. You see it in GUI form and optionally yaml form.

Omnilink Bridge ==> configuration ==> edit in YAML
 
I have been trying to find a useful upgrade to my HAI system and after much research I decided to go with Home Assistant. My current Leviton touchscreens have been spotty and with my newer camera system, are not compatible with HAI. I would like to use Home Assistant to take over as the primary system with hopes of replacing the touchscreens with tablets running Home Assistant.

I managed to get the Omnilink bridge installed on my Home Assistant. I have been playing around with the Dashboard and have the keypad up, but when I enter in the code to arm I get a message "Arming requires a code but none was given for alarm_control_panel.omnilink_area_1." I downloaded the Omnilink bridge through the add-on store which linked me to Github.

Reading the add-on configuration documentation, there is no place mentioned to add a code to validate. It appears it doesn't seem to pull the codes through the bridge. When I elect to not to require a code, the OmniLink bridge will work, arming and disarming the system. I looked through the UI and the Yaml and there doesn't seem to be a place to add this. I'm too new to Yaml to know if I add a section that it will work or break.

Any help is greatly appreciated.
 
I have been trying to find a useful upgrade to my HAI system and after much research I decided to go with Home Assistant. My current Leviton touchscreens have been spotty and with my newer camera system, are not compatible with HAI. I would like to use Home Assistant to take over as the primary system with hopes of replacing the touchscreens with tablets running Home Assistant.

I managed to get the Omnilink bridge installed on my Home Assistant. I have been playing around with the Dashboard and have the keypad up, but when I enter in the code to arm I get a message "Arming requires a code but none was given for alarm_control_panel.omnilink_area_1." I downloaded the Omnilink bridge through the add-on store which linked me to Github.

Reading the add-on configuration documentation, there is no place mentioned to add a code to validate. It appears it doesn't seem to pull the codes through the bridge. When I elect to not to require a code, the OmniLink bridge will work, arming and disarming the system. I looked through the UI and the Yaml and there doesn't seem to be a place to add this. I'm too new to Yaml to know if I add a section that it will work or break.

Any help is greatly appreciated.

If you set the add-on
Code:
mqtt_discovery_override_area
to
Code:
id=1;code_disarm=true;
it will require a code to disarm.
 
I have been trying to find a useful upgrade to my HAI system and after much research I decided to go with Home Assistant. My current Leviton touchscreens have been spotty and with my newer camera system, are not compatible with HAI. I would like to use Home Assistant to take over as the primary system with hopes of replacing the touchscreens with tablets running Home Assistant.

I managed to get the Omnilink bridge installed on my Home Assistant. I have been playing around with the Dashboard and have the keypad up, but when I enter in the code to arm I get a message "Arming requires a code but none was given for alarm_control_panel.omnilink_area_1." I downloaded the Omnilink bridge through the add-on store which linked me to Github.

Reading the add-on configuration documentation, there is no place mentioned to add a code to validate. It appears it doesn't seem to pull the codes through the bridge. When I elect to not to require a code, the OmniLink bridge will work, arming and disarming the system. I looked through the UI and the Yaml and there doesn't seem to be a place to add this. I'm too new to Yaml to know if I add a section that it will work or break.

Any help is greatly appreciated.
I keep my settings so it will always require a code. When I want to automate a "disarm" I created a code for an automated user in my omni and send that code through an automation rule when triggered.

Example for disarming when a valid code is entered in my back door lock. Check the "Code" box and enter the code you want to use to disarm.
1733413474833.png
 
If you set the add-on
Code:
mqtt_discovery_override_area
to
Code:
id=1;code_disarm=true;
it will require a code to disarm.

y settings so it will always require a code. When I want to automate a "disarm" I created a code for an automated user in my omni and send that code through an automation rule when triggered.

Thanks for your guys response and help with my issue.

rsw686, I have that command already which gives me the keypad. This is what I have under the configuration area.

1733603186280.png

This allows my dashboard keypad to look like this.

1733603370006.png

When I enter a code to arm or disarm, I get this message.

1733603285172.png

I don't see anywhere in the configuration area where I can enter a code for validation. I switch the view from UI to YAML and I don't even know if I can add a section anywhere that might possible resolve this.

In the interim, I tried playing around with the HACS, Alarmo, and it recognizes all the doors, windows, and motions detectors. The configuration file also has a section to add a code. However, when I arm the system, my HAI Omni II alarm panel doesn't arm.


Swamiller, you mentioned you still have the code disarm feature enabled but have automated a digital lock to send a disarm code. I don't have any automated locks to trigger this. Do yo have keypad setup like above?

I have read a few threads in these forums and a handful of people say the Omnilink add-on is successful for them. I'm really curious what they did to resolve this issue.

I just wanted to reiterate that when I installed this add-on, I followed the instructions and I directed the add-on to github's code link https://github.com/excaliburpartners/OmniLinkBridge.git

I did notice when I went back to see I was missing something, there was a fix for the keypad (see screenshot below). I'm not too familiar with Github and unsure if it this fix was included when I linked the code or if I have to overwrite something in the configuration file.

1733604462084.png
 
Back
Top