It is the best step-by-step guide I’ve seen to getting OpenHab working on Pi. Even includes specifics on configuring a Hue setup.
Details on the Hue binding are here:
Get the Hue running first BEFORE you attempt the Plex or Sonos. It is more straightforward device and the examples in the MakeUseOf article and Hue binding doc are more complete.
You’ll also need to install the Plex and Sonos bindings and configure them.
Things which you are controlling that have a ranges of values (dimmers or volume for example)
are usually Dimmers in your ITEMS file but Slider in the sitemap. Again from Hue,
(EVENTUALLY - you will also need to eventually stop using the Pi’s SD card except for booting and use a USB stick or USB-attached disk. See this thread re that topic.
The link @watou posted at the end of the thread is good. I wish I’d had that rather than having to hand-roll via the links I posted in same thread).
Thank you for this information, I have reinstalled the pi2 and started the
instructions from the beginning.
However I keep hitting this problem, do you have any advice?
HTTP ERROR 500
Problem accessing /openhab.app. Reason:
Sitemap ‘demo’ could not be found
Caused by:
org.openhab.ui.webapp.render.RenderException: Sitemap ‘demo’ could not be
found
at
org.openhab.ui.webapp.internal.servlet.WebAppServlet.service(WebAppServlet.j
ava:114)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(Servle
tRegistration.java:61)
If you have already created your sitemap for your implementation and placed in the sitemaps directory, this is probably because you are not passing the sitemap parameter on the url, e.g.,
[Substitute ip-address of your Pi and name of your sitemap ]
AFAIR if you do not pass the sitemap argument, OH defaults to looking for “demo” ie file demo.sitemap. If you did not install the demo files, it will not be there and this message will appear.
Look in your sitemaps directory (ie openhab/configurations/sitemaps. If demo.sitemap is not there, you probably did not install the demo files. If you want the demo setup, download distribution-1.7.1-demo.zip from www.openhab.org and install. No real need to do this if you’ve already started your particular configuration-you might end up over-writing your work.
You are running Tomcat on the Pi also ? If so, apache server installed and probably autostarts also when you boot.
If so, most likely a port conflict between Tomcat and the Openhab jetty server both trying to use :8080 by default.
Not in a position to test this theory at the moment, but I think if you go into /openhab/server there is an eclipse.ini file. (It is plain text.) One line in that file looks like this:
-Dorg.osgi.service.http.port=8080
I’d change that 8080 to something else, like 8090 or 9080 etc. and retry.
I have disabled tomcat, what’s strange is that I didn’t install it. I noticed when trying to install on my qnap that the openhab runs on 8082 which makes more sense.
I don’t suppose you know anyone who would install standard openhab capabilities for plex, Sonos & hue remotely for me as part of my freelancer project?
Your big problem with any sort of remote installation is going to be TESTING. You can probably find someone to do the items and sitemaps for you (except for the Echo – no existing binding AFAIK). But since you are mainly controlling (as far as I can see) lighting and entertainment items, it will be pretty difficult to remotely test the adequacy of the implementation. So someone else might do the base config stuff via the items and sitemaps, but YOU are going to have to do the testing.
This is all just assuming you’re trying to get some sort of unified UI and remote control for your lighting/entertainment. If you want to start doing some actual automation with it, rules and scripts will be the tools and, again, very difficult to actually test remotely when you’re doing lighting/coloring/playlists/volume/etc etc.