Omnilink 1.8.1 Binding Openhab2?

Hi Steve, you might be the first :wink: Is there anything in the log file?

On Mon, Feb 15, 2016 at 9:09 AM Steve Miller bot@community.openhab.org wrote:

swamiller https://community.openhab.org/users/swamiller Steve Miller
https://community.openhab.org/users/swamiller
February 15

Has anyone successfully implemented the 1.8.1 omnilink binding in OpenHAB2?

I installed the compatibility program, the omnilink JAR file, openhab.cfg,
my .item and .sitemap from my openhab1 install into the appropriate
OpenHAB2 config folders.

Everything shows up on the web page and seems to function but apparently
there is no connection to my OP2 controller because none of the items react
to inputs.

Any guidance would be greatly appreciated!

Visit Topic
https://community.openhab.org/t/omnilink-1-8-1-binding-openhab2/7586/1
or reply to this email to respond.

To stop receiving notifications for this particular topic, click here
https://community.openhab.org/t/omnilink-1-8-1-binding-openhab2/7586/unsubscribe.
To unsubscribe from these emails, change your user preferences
https://community.openhab.org/my/preferences


Sent from my mobile.

thanks for the reply, Dan

I don’t see anything that means anything to me…it log file shows that it received the commands. I tried using a specific UPB lamp module that worked in OpenHAB 1 for my testing. I have a VERY rough and basic set up at this point until I figure out how to make my OP2 panel work. Here is an excerpt from my log file:

[113:org.eclipse.smarthome.model.script:0.8.0.201601301304]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:900)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:863)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:222)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:445)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:226)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:188)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.smarthome.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:77)[114:org.eclipse.smarthome.model.script.runtime:0.8.0.201601301304]
at org.eclipse.smarthome.model.rule.runtime.internal.engine.ExecuteRuleJob.execute(ExecuteRuleJob.java:60)[112:org.eclipse.smarthome.model.rule.runtime:0.8.0.201601301304]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
2016-02-14 16:00:02.975 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 27
2016-02-14 16:00:03.118 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 5
2016-02-14 16:00:03.123 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 27 to 5
2016-02-14 16:00:04.764 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0
2016-02-14 16:00:04.770 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 5 to 0
2016-02-14 16:00:04.897 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0
2016-02-14 16:01:13.623 [INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been terminated.
2016-02-14 16:01:24.575 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI
2016-02-14 16:01:24.686 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI

where did you store the openhab.cfg? I am not quite sure but could you please create a config file omnilink.cfg under <openhabhome>/conf/services and add the according configuration elements without the omnilink: prefix.

################################# Omnilink ############################################
#
# Enter the port (4369) host ip or name and the two crypto keys for your omni panel.
# The two keys may be found in the installer menu on a HAI keypad or touchscreen. Each
# key is 16 hex characters in pairs separated by colons (aa:bb:cc)
#
# Ff generateItems is set to true then the binding will print all known items and a
# sample sitemap to the log file (INFO).  Useful when setting up for the first time.
#
#port=4369
#host=panel.yourdomain.com
#key1=00:AA:BB:CC:DD:EE:FF:11
#key2=00:AA:BB:CC:DD:EE:FF:11
#generateItems=true

Teichsta,

I do have an exact copy of the openhab.cfg file from my original openhab1 install located in the conf/services folder.

Do I need to remove all of the other default non-omnilink related references in the openhab.cfg? Again, mine is very basic for testing. Other than what is not commented out by default the omnilink settings are all that is active in that file.

Also, I’m not sure I understand what you mean by “without the omnilink: prefix”? Is there something else I should edit in the setup?

From: Thomas Eichstädt-Engelen bot@community.openhab.org
Reply-To: openHAB Community replies+c2bdc197553099b97d1ce38766fa3f81@community.openhab.org
Date: Tuesday, February 16, 2016 at 3:25 AM
To: Steve’s MacBook swamiller@gmail.com
Subject: [openHAB] [Add-ons/Bindings] Omnilink 1.8.1 Binding Openhab2?

 teichsta Thomas Eichstädt-Engelen maintainer

February 16

swamiller:
openhab.cfg
where did you store the openhab.cfg? I am not quite sure but could you please create a config file omnilink.cfg under /conf/services and add the according configuration elements without the omnilink: prefix.
################################# Omnilink ############################################

Enter the port (4369) host ip or name and the two crypto keys for your omni panel.

The two keys may be found in the installer menu on a HAI keypad or touchscreen. Each

key is 16 hex characters in pairs separated by colons (aa:bb:cc)

Ff generateItems is set to true then the binding will print all known items and a

sample sitemap to the log file (INFO). Useful when setting up for the first time.

#port=4369
#host=panel.yourdomain.com
#key1=00:AA:BB:CC:DD:EE:FF:11
#key2=00:AA:BB:CC:DD:EE:FF:11
#generateItems=true

Visit Topic or reply to this email to respond.

Previous Replies

 swamiller Steve Miller

February 16
thanks for the reply, DanI don’t see anything that means anything to me…it log file shows that it received the commands. I tried using a specific UPB lamp module that worked in OpenHAB 1 for my testing. I have a VERY rough and basic set up at this point until I figure out how to make my OP2 panel work. Here is an excerpt from my log file:[113:org.eclipse.smarthome.model.script:0.8.0.201601301304]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:900)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:863)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:222)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:445)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:226)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:188)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.smarthome.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:77)[114:org.eclipse.smarthome.model.script.runtime:0.8.0.201601301304]
at org.eclipse.smarthome.model.rule.runtime.internal.engine.ExecuteRuleJob.execute(ExecuteRuleJob.java:60)[112:org.eclipse.smarthome.model.rule.runtime:0.8.0.201601301304]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
2016-02-14 16:00:02.975 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 27
2016-02-14 16:00:03.118 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 5
2016-02-14 16:00:03.123 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 27 to 5
2016-02-14 16:00:04.764 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0
2016-02-14 16:00:04.770 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 5 to 0
2016-02-14 16:00:04.897 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0
2016-02-14 16:01:13.623 [INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been terminated.
2016-02-14 16:01:24.575 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI
2016-02-14 16:01:24.686 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
Visit Topic or reply to this email to respond.

To stop receiving notifications for this particular topic, click here. To unsubscribe from these emails, change your user preferences

try creating the file conf/services/omnilink.cfg , the contents should be in the following format
port=4369 host=omni.yourdomain.com key1=00:00:00:00:00:00:00:00 key2=00:00:00:00:00:00:00:00

I was able to get it to connect under OH2 on a test system I still have access to, so I think it should work ok. If you start OH2 up with the start_debug.sh/bat script, enter log:set DEBUG org.openhab.binding.omnilink at the prompt to get more detailed logging

Dan,

That worked! Although I named the new file “openhab.cfg" and over wrote the existing openhab.cfg I imported from Openhab1.

Thank you for your help!

Does this mean this binding is a contender to be automatically added to the list of compatible OH2 bindings?

From: Dan bot@community.openhab.org
Reply-To: openHAB Community replies+772e5fbf9b901f864d82e93bad4643e4@community.openhab.org
Date: Tuesday, February 16, 2016 at 6:03 PM
To: Steve’s MacBook swamiller@gmail.com
Subject: [openHAB] [Add-ons/Bindings] Omnilink 1.8.1 Binding Openhab2?

 digitaldan Dan

February 16
try creating the file conf/services/omnilink.cfg , the contents should be in the following format
port=4369
host=omni.yourdomain.com
key1=00:00:00:00:00:00:00:00
key2=00:00:00:00:00:00:00:00I was able to get it to connect under OH2 on a test system I still have access to, so I think it should work ok. If you start OH2 up with the start_debug.sh/bat script, enter log:set DEBUG org.openhab.binding.omnilink at the prompt to get more detailed logging
Visit Topic or reply to this email to respond.

Previous Replies

 swamiller Steve Miller

February 16
Teichsta,I do have an exact copy of the openhab.cfg file from my original openhab1 install located in the conf/services folder.Do I need to remove all of the other default non-omnilink related references in the openhab.cfg? Again, mine is very basic for testing. Other than what is not commented out by default the omnilink settings are all that is active in that file.Also, I’m not sure I understand what you mean by “without the omnilink: prefix”? Is there something else I should edit in the setup?From: Thomas Eichstädt-Engelen bot@community.openhab.org Reply-To: openHAB Community replies+c2bdc197553099b97d1ce38766fa3f81@community.openhab.org Date: Tuesday, February 16, 2016 at 3:25 AM To: Steve’s MacBook swamiller@gmail.com Subject: [openHAB] [Add-ons/Bindings] Omnilink 1.8.1 Binding Openhab2?
teichsta Thomas Eichstädt-Engelen maintainer
February 16swamiller: openhab.cfg where did you store the openhab.cfg? I am not quite sure but could you please create a config file omnilink.cfg under /conf/services and add the according configuration elements without the omnilink: prefix.
########################### Omnilink
Enter the port (4369) host ip or name and the two crypto keys for your omni panel.
The two keys may be found in the installer menu on a HAI keypad or touchscreen. Each
key is 16 hex characters in pairs separated by colons (aa:bb:cc)
Ff generateItems is set to true then the binding will print all known items and a
sample sitemap to the log file (INFO). Useful when setting up for the first time.
port=4369
host=panel.yourdomain.com
key1=00:AA:BB:CC:DD:EE:FF:11
key2=00:AA:BB:CC:DD:EE:FF:11
generateItems=true
Visit Topic or reply to this email to respond.Previous Replies
swamiller Steve Miller
February 16 thanks for the reply, DanI don’t see anything that means anything to me…it log file shows that it received the commands. I tried using a specific UPB lamp module that worked in OpenHAB 1 for my testing. I have a VERY rough and basic set up at this point until I figure out how to make my OP2 panel work. Here is an excerpt from my log file:[113:org.eclipse.smarthome.model.script:0.8.0.201601301304] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:900)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:863)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:222)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:445)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:226)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:188)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533] at org.eclipse.smarthome.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:77)[114:org.eclipse.smarthome.model.script.runtime:0.8.0.201601301304] at org.eclipse.smarthome.model.rule.runtime.internal.engine.ExecuteRuleJob.execute(ExecuteRuleJob.java:60)[112:org.eclipse.smarthome.model.rule.runtime:0.8.0.201601301304] at org.quartz.core.JobRunShell.run(JobRunShell.java:202)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304] 2016-02-14 16:00:02.975 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 27 2016-02-14 16:00:03.118 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 5 2016-02-14 16:00:03.123 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 27 to 5 2016-02-14 16:00:04.764 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0 2016-02-14 16:00:04.770 [INFO ] [marthome.event.ItemStateChangedEvent] - Lights_FamilyRoom_Lamp_Switch changed from 5 to 0 2016-02-14 16:00:04.897 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘Lights_FamilyRoom_Lamp_Switch’ received command 0 2016-02-14 16:01:13.623 [INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been terminated. 2016-02-14 16:01:24.575 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI 2016-02-14 16:01:24.686 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI Visit Topic or reply to this email to respond.To stop receiving notifications for this particular topic, click here. To unsubscribe from these emails, change your user preferences
Visit Topic or reply to this email to respond.

To stop receiving notifications for this particular topic, click here. To unsubscribe from these emails, change your user preferences

It would be great if you could report back after a day or two of use any
new problems with the binding under OH2, if none then I would say yes.

On Wed, Feb 17, 2016 at 12:03 PM Steve Miller bot@community.openhab.org wrote:

swamiller https://community.openhab.org/users/swamiller Steve Miller
https://community.openhab.org/users/swamiller
February 17

Dan,

That worked! Although I named the new file “openhab.cfg" and over wrote
the existing openhab.cfg I imported from Openhab1.

Thank you for your help!

Does this mean this binding is a contender to be automatically added to
the list of compatible OH2 bindings?

From: Dan bot@community.openhab.org
https://community.openhab.orgmailto:bot@community.openhab.org Reply-To:
openHAB Community
replies+772e5fbf9b901f864d82e93bad4643e4@community.openhab.org
https://community.openhab.orgmailto:replies+772e5fbf9b901f864d82e93bad4643e4@community.openhab.org
Date: Tuesday, February 16, 2016 at 6:03 PM To: Steve’s MacBook
swamiller@gmail.com
https://community.openhab.orgmailto:swamiller@gmail.com Subject:
[openHAB] [Add-ons/Bindings] Omnilink 1.8.1 Binding Openhab2?

digitaldan Dan

February 16 try creating the file conf/services/omnilink.cfg , the
contents should be in the following format port=4369 host=
omni.yourdomain.com key1=00:00:00:00:00:00:00:00
key2=00:00:00:00:00:00:00:00I was able to get it to connect under OH2 on a
test system I still have access to, so I think it should work ok. If you
start OH2 up with the start_debug.sh/bat script, enter log:set DEBUG
org.openhab.binding.omnilink at the prompt to get more detailed logging
Visit Topic or reply to this email to respond.

Previous Replies

swamiller Steve Miller

February 16 Teichsta,I do have an exact copy of the openhab.cfg file from
my original openhab1 install located in the conf/services folder.Do I need
to remove all of the other default non-omnilink related references in the
openhab.cfg? Again, mine is very basic for testing. Other than what is not
commented out by default the omnilink settings are all that is active in
that file.Also, I’m not sure I understand what you mean by “without the
omnilink: prefix”? Is there something else I should edit in the setup?From:
Thomas Eichstädt-Engelen bot@community.openhab.org Reply-To: openHAB
Community replies+c2bdc197553099b97d1ce38766fa3f81@community.openhab.org
Date: Tuesday, February 16, 2016 at 3:25 AM To: Steve’s MacBook
swamiller@gmail.com Subject: [openHAB] [Add-ons/Bindings] Omnilink 1.8.1
Binding Openhab2? teichsta Thomas Eichstädt-Engelen maintainer February
16swamiller: openhab.cfg where did you store the openhab.cfg? I am not
quite sure but could you please create a config file omnilink.cfg under
/conf/services and add the according configuration elements without the
omnilink: prefix.
##################### Omnilink

Enter the port (4369) host ip or name and the two crypto keys for your
omni panel. The two keys may be found in the installer menu on a HAI keypad
or touchscreen. Each key is 16 hex characters in pairs separated by colons
(aa:bb:cc) Ff generateItems is set to true then the binding will print all
known items and a sample sitemap to the log file (INFO). Useful when
setting up for the first time. port=4369 host=panel.yourdomain.com
key1=00:AA:BB:CC:DD:EE:FF:11 key2=00:AA:BB:CC:DD:EE:FF:11
generateItems=true Visit Topic or reply to this email to respond.Previous
Replies swamiller Steve Miller February 16 thanks for the reply, DanI don’t
see anything that means anything to me…it log file shows that it received
the commands. I tried using a specific UPB lamp module that worked in
OpenHAB 1 for my testing. I have a VERY rough and basic set up at this
point until I figure out how to make my OP2 panel work. Here is an excerpt
from my log
file:[113:org.eclipse.smarthome.model.script:0.8.0.201601301304] at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.*doEvaluate(XbaseInterpreter.java:900)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.*doEvaluate(XbaseInterpreter.java:863)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:222)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.*doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.*doEvaluate(XbaseInterpreter.java:758)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:218)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:445)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:226)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:202)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:188)[127:org.eclipse.xtext.xbase:2.6.2.v201407030533]
at
org.eclipse.smarthome.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:77)[114:org.eclipse.smarthome.model.script.runtime:0.8.0.201601301304]
at
org.eclipse.smarthome.model.rule.runtime.internal.engine.ExecuteRuleJob.execute(ExecuteRuleJob.java:60)[112:org.eclipse.smarthome.model.rule.runtime:0.8.0.201601301304]
at
org.quartz.core.JobRunShell.run(JobRunShell.java:202)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)[93:org.eclipse.smarthome.core.scheduler:0.8.0.201601301304]
2016-02-14 16:00:02.975 [INFO ] [smarthome.event.ItemCommandEvent ] - Item
’Lights
FamilyRoom_Lamp_Switch’ received command 27 2016-02-14
16:00:03.118 [INFO ] [smarthome.event.ItemCommandEvent ] - Item
’Lights_FamilyRoom_Lamp_Switch’ received command 5 2016-02-14 16:00:03.123
[INFO ] [marthome.event.ItemStateChangedEvent] -
Lights_FamilyRoom_Lamp_Switch changed from 27 to 5 2016-02-14 16:00:04.764
[INFO ] [smarthome.event.ItemCommandEvent ] - Item
’Lights_FamilyRoom_Lamp_Switch’ received command 0 2016-02-14 16:00:04.770
[INFO ] [marthome.event.ItemStateChangedEvent] -
Lights_FamilyRoom_Lamp_Switch changed from 5 to 0 2016-02-14 16:00:04.897
[INFO ] [smarthome.event.ItemCommandEvent ] - Item
’Lights_FamilyRoom_Lamp_Switch’ received command 0 2016-02-14 16:01:13.623
[INFO ] [.openhab.core.internal.CoreActivator] - openHAB runtime has been
terminated. 2016-02-14 16:01:24.575 [INFO ]
[assic.internal.servlet.WebAppServlet] - Stopped Classic UI 2016-02-14
16:01:24.686 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic
UI Visit Topic or reply to this email to respond.To stop receiving
notifications for this particular topic, click here. To unsubscribe from
these emails, change your user preferences Visit Topic or reply to this
email to respond.

To stop receiving notifications for this particular topic, click here. To
unsubscribe from these emails, change your user preferences

Visit Topic
https://community.openhab.org/t/omnilink-1-8-1-binding-openhab2/7586/7
or reply to this email to respond.

To stop receiving notifications for this particular topic, click here
https://community.openhab.org/t/omnilink-1-8-1-binding-openhab2/7586/unsubscribe.
To unsubscribe from these emails, change your user preferences
https://community.openhab.org/my/preferences


Sent from my mobile.

@digitaldan

Ok, so I’ve had a few days to test and I don’t think the 1.8.1 omnilink binding is ready for OpenHab2 just yet. I was able to connect but controlling lights was hit or miss. Sending commands to units (UPB) would usually show as not connected true in the debug log. But the log also shows the controller connected by showing the time, sunrise, sunset, and battery status. On occasion it will connect but controlling one unit would sometimes make several units (lights) turn on.

Any interest in configuring the omnilink binding for Openhab2?

Does this also apply to the 1.9.0-SNAPSHOT binding?

@Watou

I found 1.9.0-SNAPSHOT and it connects quite well, so far.

Thanks! I’ll keep testing and give an update later.

From: watou bot@community.openhab.org
Reply-To: openHAB Community replies+b2d416852c474029387fc22ff2dca51a@community.openhab.org
Date: Sunday, February 21, 2016 at 2:52 AM
To: Steve’s MacBook swamiller@gmail.com
Subject: [openHAB] [Add-ons/Bindings] Omnilink 1.8.1 Binding Openhab2?

1.9.0-SNAPSHOT

1 Like

Hi,

I have taken a first cut at implementing the omnilink binding for Openhab 2. I tried to use as much of Dan’s earlier binding code as possible.

As of right now it supports discovery of units and zones.

Here is the location to my addon:

(look in openhab2-addons/addons/binding/omnilink)

To get it to build in my eclipse i had to rename the prior generation binding (i.e., append -1 to it’s project name)

This is really alpha, but I was able to control a light and have the motion sensor of a zone turn a switch on and off.

This was my first exposure to openhab 2 as well, so I am learning it as I go, and don’t feel I quite get it all.

For me, I had to add an entry into an item file, and sitemap to see it on the classic ui.

eg.
in the demo.items i added:

Switch LivingRoomMotion { channel=“omnilink:zone:3:status” }
Dimmer FoyerLights {channel=“omnilink:unit:2:light level”}

then in the demo.sitemap just refer to those items as you did in 1.x

I haven’t implemented discovery of the omnilink controller yet. For that go to inbox, search for things, then pick omnilnik. Then pick add manual. The access point shows as a thing you can add. Choose that and then enter the ip and keys.

Then discovery for omnilink should pick up your units and zones. You may have to reboot openhab after first adding the controller…not sure.

Would really appreciate if someone would be able to test this out and offer some feedback so I can keep the progress going.

cheers,
craig

Ok,

I have hopefully made a jar which can be dropped in as a bundle, instead of needing to be a build, etc.

Just let me know if you have any problems.

https://github.com/QuailAutomation/openhab2-addons/blob/c41f060eee8d90f7ecac040e0ec6cd75363ecb75/org.openhab.binding.omnilink-2.0.0-SNAPSHOT.jar

@craigh
I downloaded the jar from your site that I plan on installing on a test instance of OH2. My current set up using 1.9.0 is very stable but I’d still like to eventually have a binding for OH2 specifically (non-compatibility mode).

Are you still working on the Omnilink binding for OH2? If so, any chance of extending the current functionality of the 1.9.0 binding to include locks controlled by the omnipro board as well as flag status, and current temperature control unit status (Cooling, Heating, Idle)?

@swamiller
Basic question. Where do you download the 1.9.0?

@jacksteraz

Try this link: https://openhab.ci.cloudbees.com/job/openHAB1-Addons/ws/bundles/binding/org.openhab.binding.omnilink/target/

Thanks for the 1.9.0 SNAPSHOT tip. I was getting this error running omnilink-1.8.3 under openhab2. Swapping out the jar file for the 1.9.0 version made the errors go away.

21:55:11.578 [ERROR] [org.openhab.binding.omnilink        ] - [org.openhab.binding.omnilink.binding(0)] The deactivate method has thrown an exception
java.lang.IllegalMonitorStateException
        at java.lang.Object.notifyAll(Native Method)[:1.8.0_101]
        at org.openhab.binding.omnilink.internal.OmniLinkBinding$OmniConnectionThread.setRunning(OmniLinkBinding.java:324)
        at org.openhab.binding.omnilink.internal.OmniLinkBinding.deactivate(OmniLinkBinding.java:123)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_101]
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)[:1.8.0_101]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)[:1.8.0_101]
        at java.lang.reflect.Method.invoke(Unknown Source)[:1.8.0_101]
        at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:222)
        at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:37)
        at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:615)
        at org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:499)
        at org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:295)
        at org.apache.felix.scr.impl.manager.SingleComponentManager.disposeImplementationObject(SingleComponentManager.java:342)[34:org.apache.felix.scr:2.0.2]
        at org.apache.felix.scr.impl.manager.SingleComponentManager.deleteComponent(SingleComponentManager.java:157)[34:org.apache.felix.scr:2.0.2]
        at org.apache.felix.scr.impl.manager.SingleComponentManager.ungetService(SingleComponentManager.java:913)[34:org.apache.felix.scr:2.0.2]
        at org.apache.felix.scr.impl.manager.SingleComponentManager.ungetService(SingleComponentManager.java:902)[34:org.apache.felix.scr:2.0.2]
        at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$2.run(ServiceFactoryUse.java:260)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$2.run(ServiceFactoryUse.java:1)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_101]
        at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryUngetService(ServiceFactoryUse.java:258)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.ungetService(ServiceFactoryUse.java:160)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.ungetService(ServiceConsumer.java:50)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.ungetService(ServiceRegistrationImpl.java:581)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.ungetService(ServiceRegistry.java:540)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.eclipse.osgi.internal.framework.BundleContextImpl.ungetService(BundleContextImpl.java:661)[org.eclipse.osgi-3.10.2.v20150203-1939.jar:]
        at org.apache.felix.cm.impl.helper.BaseTracker.ungetRealService(BaseTracker.java:207)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:161)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1444)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1400)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:143)[7:org.apache.felix.configadmin:1.8.8]
        at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:110)[7:org.apache.felix.configadmin:1.8.8]
        at java.lang.Thread.run(Unknown Source)[:1.8.0_101]

Hi Steve,

Unfortunately I have not been working lately on the 2.0 build. I really like using jython for my rules and that isn’t ready in 2.0. I have reverted back to 1.8 for now.

As for locks, flags, and temperature control unit. I do not have locks for thermostats hooked up to my omnipro, so not sure I would be able to do much work. As for the flags, I will take a look to see if I am using flags, and if i can put something together.

regards,
craig

Thanks @craigh.

Flags alone would be a big help. To your point about your rules engine preferences, I have found that I can build some functions easier from within the omnipro programming environment vs. openhab. Having flags would give me the ability to have openhab monitor flag changes programmed in the omni and have openhab react via a rule.

As for locks, I currently use Haiku as a control app and I can see there are other complications around locks and security, such as the ability to use user codes to lock or unlock doors and arm/disarm the security system. The current OH binding is primarily geared toward controlling units and some very basic security integrations but nothing around knowing who disarmed the alarm or unlocked a door via user code integrations.

Currently (as a test), I can control my zigbee door locks (via the omnipro) with openhab but I had to write a program on my omni that basically turned the lock controls into a switch (unit). The switch shows up as a light switch that I can control the lock/unlock from openhab but it definitely isn’t an ideal solution.

Another use for flags is measuring duration of my climate control system “on time”. I have my Rainforest EAGLE smart meter energy monitor working in OH2 but I’d like to measure my electricity usage against the big ticket items that are running, such as my A/C units and pool pumps. The current binding won’t tell me if my A/C (or heat) is current active, but a flag could be programmed in the omni to provide that on/off information.

Thanks for the response, Craig. Any assistance you can offer is greatly appreciated!

@smk,

I had the same luck with the 1.8.x binding with OH2 and 1.9.0 has been pretty flawless for me.

I’m using most of the current functionality the binding has to offer (units, thermo control, buttons, and basic security) and all seems to work well. As with most of the home automation solutions I’ve experimented with, however, there are still a few more functions that would be helpful in the binding, such as the ability to enter user codes to arm/disarm the alarm, integration of door locks controlled via the omnipro, and the ability to read flag settings triggered within the omnipro.

Overall, though, I’ve been very happy (with much learning) with the abilities built in to OH2. It has definitely expanded my ability to integrate more “stuff” and use a single interface to control all.

I’m just getting started with OH + Omni but I’m battling an annoying problem present under OH and OH2: My outside temp won’t update posted here. Do you have an outside temp sensor, and if so, is it updating? @digitaldan said his worked just fine. I’m going back trying to run Dan’s jOmnilinkII example code to see if I can figure out where the source of the problem is.