Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

SensiNact/Bridge-openhab

< SensiNact
Revision as of 12:29, 19 March 2018 by Jbotnascimento.gmail.com (Talk | contribs) (Created page with "=== Description === This bridge is capable of finding the openhab instances running on the local network and instantiate its switch devices into sensinact without further con...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

This bridge is capable of finding the openhab instances running on the local network and instantiate its switch devices into sensinact without further configuration.

The switch type devices on OpenHab are devices that respond to ON/OFF command.

Configure

No configuration is necessary, as long as the UDP packages between openhab and the sensinact machines are not been blocked, sensinact will be able to find the openhab instance without issues. Be aware that some routers are configured to block this kind of package in multi-hop, and VPN tunneling as well. In this situation you can manually specify the openhab address using the method described below.

Installing

Via OBR

If the openhab bridge bundle isnt installed in your platform, you can install it using OBR.

On sensinact console, execute:

obr:deploy sensinact-openhab

And start the openhab bundle installed.

Declaring openhab manually

This method can be used to bypass the discovery method.

In order to do so, create a file called openhab-0.cfg in the fileinstall folder ( e.g. $SENSINACT_HOME/load/openhab/), with the following content:

#this should be replace by the IP of your openhab server
ip=192.168.1.68
#this is optional, but if its omitted 8080 is assumed.
port=8082
version=2.0

If the version is not specified, the version 1.8 is assumed.

If you used this type of instantiation, probably you want to disable the discovery entirely by adding the line below in conf/config.properties.

fr.cea.sna.gateway.device.openhab.OpenHabDiscoveryv1.disabled=true
fr.cea.sna.gateway.device.openhab.OpenHabDiscoveryv2.disabled=true

This will create a pointer to an instance of OpenHab, that should be reacheable. This procedure bypasses the discovery and should be used when the discovery was not able to find your openhab instance; This happens when you are over an ssh tunnel for instance.

Back to the top