|
|
| Line 1: |
Line 1: |
| − | == Description ==
| |
| | | | |
| − | This bridge finds the [http://openhab.org/ OpenHab] instances running on the local network and instantiates its switch devices into sensiNact without further configurations.
| |
| − |
| |
| − | The switch type devices on OpenHab are devices that respond to ON/OFF command.
| |
| − |
| |
| − | == Configure ==
| |
| − |
| |
| − | No configuration is needed 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 packets in multi-hop networks, and VPN tunneling as well. In this situation, you can manually specify the OpenHab address using the method described below.
| |
| − |
| |
| − | == Installing ==
| |
| − |
| |
| − | 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. <code>$SENSINACT_HOME/load/openhab/</code>), with the following content:
| |
| − |
| |
| − | <source lang="html4strict" highlight="1-4">
| |
| − | # This should be replaced by the IP of your OpenHab server
| |
| − | ip=192.168.1.68
| |
| − | # This is optional, but if its omitted 8080 is assumed.
| |
| − | port=8082
| |
| − | </source>
| |
| − |
| |
| − | If you used this type of instantiation, probably you want to disable the discovery entirely by adding the line below in <code>conf/config.properties</code>.
| |
| − |
| |
| − | <code>
| |
| − | fr.cea.sna.gateway.device.openhab.OpenHabDiscovery.disabled=true
| |
| − | </code>
| |
| − |
| |
| − | This will create a pointer to a reachable instance of OpenHab. 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.
| |
