Difference between revisions of "OpenHAB2"

Revision as of 04:26, 2 December 2017

Things, Iitems etc .. http://docs.openhab.org/configuration/things.html

Openhab hacks

• log files are at ohab: log files
• karaf console login: By default disabled from anywhere but localhost. Thus ssh into ohab, then ssh from there to

  ssh -p 8101 openhab@localhost

  default pwd is habopen.
• timeout exception prevents any further updates. This is evidently a eclipse smarthome framework bug

  2017-11-21 16:59:30.517 [WARN ] [org.apache.karaf.services.eventadmin] - EventAdmin: Blacklisting ServiceReference [{org.osgi.service.event.EventHandler, org.eclipse.smarthome.core.events.EventPublisher}={event.topics=smarthome, component.name=org.eclipse.smarthome.core.internal.events.OSGiEventManager, component.id=38, service.id=139, service.bundleid=109, service.scope=bundle} | Bundle(org.eclipse.smarthome.core_0.9.0.201711202142 [109])] due to timeout!

  • It appears the same bug is described here as well: https://community.openhab.org/t/openhab-stopped-working-after-update-2-2-0-build-1088/36441/2
  • there is a fix in that thread, basically add

    org.apache.felix.eventadmin.Timeout=0

    to

    /var/lib/openhab2/etc/org.apache.felix.eventadmin.impl.EventAdmin.cfg

    . This should probably be removed at some point since it basically hides long running (or never returning) event handlers

Homekit setup

• there is a issue with the homekit addon overwriting the generated mac address on exit (I think). See https://github.com/openhab/openhab2-addons/issues/1822
  • for now, after successful pairing, set /var/lib/openhab2/jsondb/homekit.json read only after successful pairing. May have to undo to re-create a new pairing
• after a reset of the openhab server, it may take quite some time for homekit to attempt a reconnect to the server. You can force a reconnect by putting the iPhone etc temporarily into and out of airplane mode. This forces homekit to reconnect

Alexa setup

• Install the openhab cloud connector in add-ons -> misc. This will create a UUID and secret that we need for hitching up to the openhab cloud. In the background, it already attempted to log on with the created credentials, but fails (since there is no account on myopenhab yet), and will not attempt to go any further. As we'll see, this creates a bit of a problem later.
• get the UUID and secret from

  /var/lib/openhab2/uuid

  and

  /var/lib/openhab2/openhabcloud/secret

  and create/sign on at http://myopenhab.org
• myopenhab needs to verify email address, do so...
• Tricky: myopenhab will still say that your openhab instance is not connected. This is b/c a earlier attempt by the openhab server failed, and now it has given up. Go back to paper ui, configuration -> services -> openHAB cloud and hit configure. Just hitting "Save" will retrigger the log-on process, which should now be ok.The log files will tell you.
• Once we have the myopenhab cloud setup working, go to amazon.com, and search for the openhab skill. Install that skill to your amazon alexa skill set. This will ask you to permit the myopenhab cloud to get credentials and permissions from the alexa cloud. Use the defaults, eventually there is a web page that says "close this window" (you'll need pop-ups enabled in your browser, otherwise you'll miss that window).
• Once the connection between Alexa and Myopenhab is made via the openhab skill. ask alexa to "discover devices". It should announce all devices that have HomeKit tags (both the homekit plugin and the alexa skill use the same tagging system)

MQTT

• needed to use node-red as flow editor....
• topics and stuff