CHANGE OPENHAB TO ROOT USER FOR EXE BINDING

When changing USER_AND_GROUP on Raspian Jessie Debian distr. to root do the following:

1> /etc/default/openhab - change to root (USER_AND_GROUP=root:root)
2> /usr/lib/systemd/system/openhab.service
- change user and group inside the file
User=root
Group=root
- systemctl daemon-reload
- systemctl start openhab

Pretty simple when you know what to change. Maybe we can document it somewhere?

DS18B20 One wire GPIO with openHab

Step 1: Install and configure openHABianPi

For this tutorial, I used the openHABian image for Raspberry Pi: 
http://docs.openhab.org/installation/openhabian.html4

Also, github page with download link:
https://github.com/openhab/openhabian/releases5

Follow the instructions on the link above to download the .img file, flash to SD card, boot up Pi, wait approximately 45min. It's really that simple.

Connect power and Ethernet to your RasPi, and you should now have a working openHAB with SSH access.

Step 2: Build 1-wire sensor network

Visit the manufacturer's reference document here to help with properly building your network of (wired) 1-wire sensors: https://www.maximintegrated.com/en/app-notes/index.mvp/id/1485

Connect the 1-wire sensors to GPIO pin 4 on the RasPi. 
Below is an example breadboard configuration of the connections on an original Raspberry Pi model B. 
3.3V, GND, and GPIO pin 4 (as labeled) are the only connections on the RasPi side. Once I confirmed this was working I then used CAT-5 cable to run the temp sensors to different rooms of my house.

Fritzing Raspi 1-wire_bb.png1038x1353 176 KB

Note: the 4.7k pull-up resistor on the data pin of the DS18b20. Only one of these is required in total for the 1-wire network. Also note that the RasPi is used to power the 1-wire sensor network so keep that in mind and make sure your RasPi power supply is adequate. This setup is working successfully for me with a 2-amp power supply.

Step 3: Reading Temperature sensors through GPIO on RasPi

The 1-wire Binding for openHAB relies on ow-server, and is therefore limited to serial, USB, or network sockets/tcp for the 1-wire connection. There is no current configuration for GPIO sensors, so instead you will need to use Exec Binding and a script that polls the sensors.
There is a good starter script here: http://www.itbasic.de/openhab-onewire-sensoren-einbinden/13
Below is a modified script for those of us in the USA, which converts the output value to Fahrenheit:

#!/bin/bash
wert=`cat /sys/bus/w1/devices/$1/w1_slave | tail -n1 | cut -d '=' -f2`   
wert2=`echo "scale=3; $wert/1000 * 9.0 / 5.0 + 32.0" | bc`
echo $wert2

Save this script to /etc/openhab2/scripts for use later. Next, configure the RasPi to load the 1-wire devices at boot: **Option 1:SSH into your openHABianPi, and nevigate to /boot. Then use vi or your favorite text editor to open the RasPi config.txt file:

pi@openHABianPi:~$ cd /boot
pi@openHABianPi:/boot$ sudo vi config.txt

**Or, option 2:Power down your RasPi and put the SD card in your PC to access the FAT formatted boot partition. With either method, once you open config.txt, add the following line:

dtoverlay=w1-gpio,gpiopin=4

Note that the config.txt that comes with openHABian contains 3 sections for the various version of RasPi’s: 1, 2, and 3, so the correct section must be modified for the corresponding RasPi version. So, for my Pi model B (aka Pi1), my config.txt looks like this:

[pi1]
kernel=vmlinuz-4.4.0-1-rpi
initramfs initrd.img-4.4.0-1-rpi followkernel
# to disable DeviceTree, uncomment the next line 
device_tree=
dtoverlay=w1-gpio,gpiopin=4

Reboot, and then confirm the RasPi can see the temp sensors by checking here:

pi@openHABianPi:/boot$ cd /sys/bus/w1/devices
pi@openHABianPi:/sys/bus/w1/devices$ ls
28-xxxxxxxxxxxx  28-xxxxxxxxxxxx  28-xxxxxxxxxxxx  w1_bus_master1

If the w1 directory does not exist, the 1-wire driver was not loaded, and you need to check config.txt and make sure it is correct. The 1-wire temp sensors each have a UID (28-xxxxxxxxxxxx) that is displayed in this folder. This UID must be specified when running the sample script. Now that you know your RasPi can see the sensors, head to the scripts folder where you previously saved the 1-wire script. Manually run the script and include the UID of one of your identified sensors. You should get a temperature value output:

pi@openHABianPi:/etc/openhab2/scripts$ sudo bash ./onewiretemp.sh 28-xxxxxxxxxxxx
70.586

If you receive an error, double check the UID, try a different sensor UID, and also check your script for syntax errors. ## Step 4: Creating the openHAB items, things, sitemap, etc The next step is to install Exec Binding, and created the appropriate openHAB files (optionally you may use the wizards to create things and items). In openHAB’s Paper UI (http://192.168.blah.blah:8080/paperui/index.html), the Exec Binding can be installed by navigating to: Add-ons>Bindings>Exec Binding <img src="//community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/9/9edbb2e596cda7cd0d3889f3b00cc46615441dd7.png" width="690" height="210"> **Next, create things and items files, and place them in their respective openHAB folders:** /etc/openhab2/things and /etc/openhab2/items example onewire.things file:

exec:command:onewiretemp1 [command="bash /etc/openhab2/scripts/onewiretemp.sh 28-xxxxxxxxxxxx"]
exec:command:onewiretemp2 [command="bash /etc/openhab2/scripts/onewiretemp.sh 28-xxxxxxxxxxxx"]
exec:command:onewiretemp3 [command="bash /etc/openhab2/scripts/onewiretemp.sh 28-xxxxxxxxxxxx"]

example onewire.items file:

String onewiretemp1Value "Temp 1 is [%s °F]" {channel="exec:command:onewiretemp1:output"}
String onewiretemp2Value "Temp 2 is [%s °F]" {channel="exec:command:onewiretemp2:output"}
String onewiretemp3Value "Temp 3 is [%s °F]" {channel="exec:command:onewiretemp3:output"}

It is important that you specify “output” for the channel that links the item to the thing. Other value options will not work with this ‘script method’ . Sample sitemap entries:

Frame label="Environment" {
Text label=”Temperatures” icon=”temperature_hot” {
Text item=onewiretemp1Value
Text item=onewiretemp2Value
Text item=onewiretemp3Value
}

Step 5: Testing the UI display

Assign your custom sitemap to the Basic UI. 
You can do this through Paper UI>Configuration>Services>BasicUI>Configure.

You should now have a fully functioning 1-wire temperature sensor network, displaying live temps:

LOCATION FILE FOR OPENHAB INSTALL BY APT-GET INSTALL METHOD

/usr/share/openhab

Set the autostart of openHAB
The Linux system on the Raspberry PI can be set up so that openHAB is started automatically when it is restarted. A precondition for the correct operation of the following instructions is an installation of openHAB following the steps of the previous instructions. If openHAB was not installed according to this guide, the paths must be adapted accordingly. Depending on the used init system using the installed Linux, one of the two solutions must be used. The command cat /proc/1/commcan be used to determine which init system is using the installed Linux version.
Autostart with systemd
(For current Linux versions, for example, Raspbian Jessy)
In order for openHAB to start automatically at boot time, the two script files openhab and openhab.service are required. 
The files to download, unpack, and then copy my WINSCP or USB stick on the Paspberry PI.
If you are using modbus serial binding please add -Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0:/dev/ttyS0 to Java 
The script file openhab:
#! /bin/sh
# Author: Pierre Metzner

# set path to openhab
OPENHAB_PATH=/opt/openhab

# set ports for HTTP(S) server
HTTP_PORT=8080
HTTPS_PORT=8443

# change directory to openHAB runtime
cd $OPENHAB_PATH

# get path to equinox jar inside $OPENHAB_PATH folder
cp=$(find ./server -name "org.eclipse.equinox.launcher_*.jar" | sort | tail -1);

# starting openHAB
echo "Launching the openHAB runtime.."
java -Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0:/dev/ttyS0 -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true -Djetty.port=$HTTP_PORT -Djetty.port.ssl=$HTTPS_PORT -Djetty.home=. -Dlogback.configurationFile=configurations/logback.xml -Dfelix.fileinstall.dir=addons -Djava.library.path=lib -Djava.security.auth.login.config=./etc/login.conf -Dorg.quartz.properties=./etc/quartz.properties -Dequinox.ds.block_timeout=240000 -Dequinox.scr.waitTimeOnBlock=60000 -Djava.awt.headless=true -jar $cp -console &> /dev/null
exit 0
The autostart script openhab.service:
[Unit]
Description=A vendor and technology agnostic open source automation software for your smart home.
After=network.target

[Service]
Type=forking
ExecStart=/usr/bin/openhab

[Install]
WantedBy=multi-user.target
After the files have been downloaded and unpacked, copy them to the Raspberry PI in the following directories.
Copy the script file openhab to the directory / usr / bin
Copy the autostart script openhab.service to / etc / systemd / system
To set the autostart, the following steps must be carried out on the Raspberry:
Change to the directory where the script open / is copied
cd /usr/bin
Change the file properties so that it can be executed
sudo chmod a+x openhab
Change the group and owner of the file
sudo chgrp root openhab
sudo chown root openhab
Checking the changes 
ls -l
The output should look as follows:
-rwxr-xr-x 1 root root 1757 Apr 16 23:27 openhab
If steps 1-4 have been carried out, openHAB can be started and terminated with the following commands: 
sudo service openhab startstarted 
sudo service openhab stopstopped and queried with 
sudo service openhab statusthe status
Finally, the system must be instructed to start openhab at booting
sudo systemctl enable openhab.service
Additional links: - https://wiki.ubuntuusers.de/Dienste/ - https://wiki.ubuntuusers.de/systemd/
Autostart with SysVinit
(For older Linux versions, such as Raspbian Wheezy or Debia Wheety)
For openHAB to start automatically when booting, the two script files openhab and openhab.cfg are needed. 
Simply download the files , unzip them and then copy them to the Paspberry PI using WINSCP or USB stick.
The script file openhab:
#! /bin/sh
### BEGIN INIT INFO
# Provides:          starts openhab from home
# Required-Start:    $local_fs $network $named $portmap $remote_fs $syslog $time
# Required-Stop:     $local_fs $network $named $portmap $remote_fs $syslog $time
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Kurze Beschreibung
# Description:       Längere Bechreibung
### END INIT INFO
# Author:

# set ports for HTTP(S) server
HTTP_PORT=8080
HTTPS_PORT=8443

if test -f /etc/default/openhab.conf; then
    . /etc/default/openhab.conf
else
    echo "Please set OPENHABPATH in /etc/default/openhab.conf"
    exit 1
fi

# Aktionen
case "$1" in
    start)
        if [ -f /var/run/openhab.pid ]; then
                echo "openhab seems to run allready. If not, please delete /var/run/openhab.pid"
        else

                cd $OPENHABPATH
                # get path to equinox jar inside $OPENHABPATH folder
                cp=$(find ./server -name "org.eclipse.equinox.launcher_*.jar" | sort | tail -1);

                echo Launching the openHAB runtime..
                java -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true -Djetty.port=$HTTP_PORT -Djetty.port.ssl=$HTTP$

                echo $! > /var/run/openhab.pid
        fi
        ;;
    stop)
        echo "stopping openhab"
        kill `cat /var/run/openhab.pid`
        rm /var/run/openhab.pid
        ;;
    restart)
        echo "does not work"
        ;;
esac

exit 0
The configuration file openhab.cfg
# PATH TO OPENHAB
OPENHABPATH=/opt/openhab

# set ports for HTTP(S) server
HTTP_PORT=8080
HTTPS_PORT=8443
After the files have been downloaded and unpacked, copy them to the Raspberry PI in the following directories.
Copy the script file openhab to the /etc/init.d/ directory
Copy the configuration file openhab.cfg to / etc / default
In order to set the autostart, the following steps must now be carried out on the Raspberry:
Change to the directory where the script open / is copied
cd /etc/init.d
Change the file properties so that it can be executed
sudo chmod a+x openhab
Change the group and owner of the file
sudo chgrp root openhab
sudo chown root openhab
Checking the changes 
ls -l
The output should look as follows:
-rwxr-xr-x 1 root root 1757 Apr 13 23:27 /etc/init.d/openhab
Change to the directory where the configuration file openhab.cfg is copied
ch /etc/default
After the script is executable, it must be entered into the runnnlevel. 
Execute the following command:
sudo update-rc.d openhab defaults
Now openhab can use the command 
sudo /etc/init.d/openhab startstarts with bez sudo /etc/init.d/openhab stopbe stopped.
Install Oracle Java 8 on Debian Jessie and Raspbian Jessie Via PPA
Update Java 8 for raspberry Pi to run cloud connector Openhab

https://www.linuxbabe.com/desktop-linux/install-oracle-java-8-debian-jessie-raspbian-jessie-via-ppa
In a previous tutorial, I showed you how to install Oracle Java 8 on Ubuntu, Linux Mint and Elementary OS via PPA. You can also use the same PPA to install Oracle Java 8 on Debian Jessie and Raspbian Jessie. But the process of adding PPA to Debian and Raspbian is a little different. So I dedicated a whole article to guide you through the process.
Install Oracle Java 8 on Debian Jessie and Raspbian Jessie
Step1: Add the PPA and install Oracle Java 8
First remove OpenJDK
sudo apt-get remove openjdk*
Next, fetch the GPG signing key for this PPA with this command:
sudo apt-key adv --recv-key --keyserver keyserver.ubuntu.com EEA14886
Then, edit /etc/apt/sources.list file.
sudo nano /etc/apt/sources.list
Append the following two lines at the end of the file.
deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main 
deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
Save and close the file. Now update local package index and install Oracle Java 8.

sudo apt-get update

sudo apt-get install oracle-java8-installer
oracle-java8-installer is not the Java binary. Instead it’s a installer that can fetch Java binary from Oracle website and then install it on your Debian or Raspbian machine.
Step2: Check Version.
Once the installation is complete, we can check Oracle Java version with this command:
java -version
Check Java compiler version.
javac -version
Step3: Set Java Environment Variables

n order to let Debian or Raspbian to know where Java JDK and JRE is located, we need to set environment variables. Run the following command to set Java environment variables.
sudo apt-get install oracle-java8-set-default
Once installed, there will be two new files under /etc/profile.d/ directory: jdk.csh and jdk.sh. These two files are shell scripts that contains commands to set 5 enviroment variables. We can use cat command to check out its content.
cat /etc/profile.d/jdk.sh
Output:
export J2SDKDIR=/usr/lib/jvm/java-8-oracle
export J2REDIR=/usr/lib/jvm/java-8-oracle/jre
export PATH=$PATH:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
export JAVA_HOME=/usr/lib/jvm/java-8-oracle
export DERBY_HOME=/usr/lib/jvm/java-8-oracle/db
What we need to do is to use the source command to execute the /etc/profile bash shell script to let these environment variables to take effect.
source /etc/profile
source is used specifically to execute commands in a shell script. If you are using the bash shell, then source can be abbreviated to a dot like this:
. /etc/profile
This has the same effect. Now you can check these 5 environment variables like below:
echo $JAVA_HOME
As you can see, the process of installing Oracle Java 8 on Debian Jessie and Raspbian Jessie via PPA is roughly the same, except that the method of adding PPA is little bit different.