HAI omnilink binding for Openhab 2.0

Add-ons Bindings
, ,
101

I just updated my system to the 2.4 release and the recent version of the binding in the market place. all well so far. thank you!

102

Is the new Binding available in the marketplace?
I can only find what looks like a binding.

" Omnilink Binding
market:binding-3388559 - 1.0"

103

@Abnormal I believe the marketplace version is the latest. You can also get the latest version here, and manually add to your addons folder:

https://s3-us-west-2.amazonaws.com/craigham-pub/org.openhab.binding.omnilink-2.4.0-SNAPSHOT.jar

104

Hi, Iā€™ve used OpenHab1 for a while until a power outage fried my Raspberry PI. I installed OH2 with the latest Omnilink binding, it all seems to be working fine. I do have 2 questions that Iā€™m hoping someone can help with.

  1. The OH2 binding doesnt seem to support Z-Wave devices or Units through Omnilink ā€“ is this true? if so, are there plans to get that working?
  2. Can I run the v1.8 or 1.9 binding at the same time and leverage its Z-Wave/Unit capability? It seems like locks are supported in 2.4 but not in 1.9 so would running both be a problem?

Thanks for any help and support of this binding!

Jerry

105

Jerry, you could consider using this MQTT bridge to get zwave working.

106

I have had to forego my KwikSet lock functionality with the OH Z-Wave binding but it had always worked well using OmniLink. If Iā€™m understanding this post correctly, Iā€™d like to think I could use this bridge to go back to using my OmniLink Z-Wave connections instead.

If so, using this bridge could I get rid of the OH Z-Wave binding and use the Z-Wave connections I have used successfully in the past inside OmniLink?

Also, Iā€™m behind on MQTT. Is this just a bridge install and no other programming in OH needed?

Thanks.

107

My early testing with the bridge is that you could replace the binding with it. It uses HA MQTT standards and the devices populated correctly on my test setup. I have not done much work beyond that.

108

Thanks for the info. It would be nice to get my locks back in the fold.

Iā€™ll give it a try and let you know how it works out.

1 Like
109

Thanks, Iā€™ll give it a try and see if I can get it working

110

The binding supports units (I use UPB). I would need to double check if we have to code specifically for unit type.

What issue are you seeing?

111

Hi I am running openhab 2.4 and have installed the binding from the marketplace and got it to work.

On my omni console temperature is reported in 0.5 degree C increments. But when I add the temperature sensor to openhab as a thing I only see 1 degree C increments eg 26.5 on the console will be displayed as 26.0 in openhab.

using the following in the in the items file.
Number Inside_Temperature ā€œInside Temperature [%.1f Ā°C]ā€ <temperature> {channel=ā€œomnilink:temp_sensor:b5e56fa9:2:temperatureā€}

am I doing something wrong?

*edit I see someone else had the same issue

113

Iā€™m out of town until Saturday so I may get the terms wrong, but I have relays connected to the voltage output units 385-392. These donā€™t seem to be detected by the binding. I tried adding a manual thing but that didnt seem to work either. You probably know that Z-Wave units donā€™t seem to work either. This weekend I will either try to install the 1.9 binding or use @mjcummingā€™s suggestion to use MQTT. Weā€™ll see how adventurous I get. Thanks for any help you may offer. Iā€™m pretty eager to get this up and running.

Thanks,
Jerry

115

Quick question. What are you doing with the outputs and what sort of functionality are you driving? I usually drive my outputs with Buttons.

116

I have the outputs connected to relays which turn on/off landscape lights. It really isnā€™t anything more than an on off switch. I have one output driven through a button. Thatā€™s for my garage door and it just requires a simple contact and release to activate the remote. The only reason I used a button there was to prevent me from tapping on the SnapLink UI for outputs too many times and leaving my garage door in a bad state. The button is more deliberate and has an extra UI confirmation. But using buttons for the other outputs (other than for OpenHab) seems unnecessary. I want to be able to see state (On/Off). The outputs show state in SnapLink and stay on when the lights are on and off when the lights are off, buttons donā€™t show state. And for a simple switch the button has an extra click that is necessary for the garage door but really annoying when you just want to turn a light on or off. The button doesnā€™t seem to add anything to the solution if OH were not in the picture. But this is another good idea that I will consider to get everything working in OH. Thank you.

Jerry

117

Thanks everyone ā€“ I wound up creating flags in my Lumina for all the Z-Wave and Output Units. Its a ton of extra programming but it keeps the configuration in OH straight forward and easy to troubleshoot. If the Omnilink binding ever supports ZWave or Output Units its easy to revert. Thanks for all the suggestions.

Jerry

118

I am going to work on generic units (zwave)/outputs and also the ability to turn on a unit/output for a specific duration.

1 Like
119

Thanks @broconne! That would be fantastic.

120

Hi

Any feedback to my post above regarding the Temperature displayed?

121

The binding reports the correct values - so something must be happening when convert F to C. A work around would be to create a virtual temperature item and use a rule to set that value when the actual temperature item changes.

122

It shouldnā€™t be converting F to C. The binding returns the temp in whatever format the panel is set to (C or F).