Network Binding - problem with discovering windows 10

[borand (Jorn Borup-Andersen)]

Hi OpenHab team

I need some help – got stuck

Using: Openhab2, Raspberry pi 3, Raspbian, Oracle java version “1.8.0_121”

Implemented “Network Binding” and it seems to be working fine. I have rules reacting when devices get online.

But noticed that I have trouble with discovering 3 devices, which all run windows 10.

I have no problem with doing a ping from the rasp to the win10 boxes.

Found this link:

NetworkHealth : Unable to detect some devices?

It’s usually not a good idea to run applications as root, so instead of starting openhab as root you can also grant java the permission to use raw and packet sockets. Install setcap (sudo apt-get install libcap2-bin) and figure out where the java binary is located on the filesystem: pi@rpi-openhab ~ $ which java /usr/bin/java pi@rpi-openhab ~ $ ls -l /usr/bin/java lrwxrwxrwx 1 root root 22 jan 31 2015 /usr/bin/java -> /etc/alternatives/java pi@rpi-openhab ~ $ ls -l /etc/alternatives/java …

So, I have executed this command:

pi@raspbox3:~ $ sudo setcap cap_net_raw=ep /opt/jdk1.8.0_121/bin/java

but afterwards, OH2 will not start:

pi@raspbox3:~ $ sudo service openhab2 status

● openhab2.service - openHAB 2 - empowering the
smart home

Loaded: loaded
(/usr/lib/systemd/system/openhab2.service; enabled)

Active: failed (Result: start-limit)
since Wed 2017-02-15 22:14:21 CET; 22s ago

 Docs:

http://docs.openhab.org

       https://community.openhab.org

Process: 9434
ExecStop=/usr/share/openhab2/runtime/bin/stop (code=exited, status=127)

Process: 9335
ExecStart=/usr/share/openhab2/start.sh server (code=exited, status=127)

Main PID: 9335 (code=exited, status=127)

Feb 15 22:14:21 raspbox3 systemd[1]: Unit openhab2.service entered failed state.

Feb 15 22:14:21 raspbox3 systemd[1]: openhab2.service holdoff time over, scheduling restart.

Feb 15 22:14:21 raspbox3 systemd[1]: Stopping openHAB 2 - empowering the smart home…

Feb 15 22:14:21 raspbox3 systemd[1]: Starting openHAB 2 - empowering the smart home…

Feb 15 22:14:21 raspbox3 systemd[1]: openhab2.service start request repeated too quickly, refusing to start.

Feb 15 22:14:21 raspbox3 systemd[1]: Failed to start openHAB 2 - empowering the smart home.

Feb 15 22:14:21 raspbox3 systemd[1]: Unit openhab2.service entered failed state.

Also noticed that I can not run java:

pi@raspbox3:~ $ java -version

java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory

removing the ‘setcap’ fix’es the OH2, so it can run but still issues with win10.

sudo setcap -r /opt/jdk1.8.0_121/bin/java

pi@raspbox3:~ $ java -version

java version “1.8.0_121”

Java™ SE Runtime Environment (build 1.8.0_121-b13)

Java HotSpot™ Client VM (build 25.121-b13, mixed mode)

Tried a variant on setcap but with same result.

sudo setcap cap_net_raw,cap_net_admin=eip realpath /usr/bin/java

pi@raspbox3:~ $ java -version

java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory

So, what should I do ?

[borand (Jorn Borup-Andersen)]

No comments ? Has this been answered in some other topic that I have missed ?

/Jorn

[borand (Jorn Borup-Andersen)]

Bit more searching… and it is now solved…

Amazon Dash, cannot use due permission issue - #2 by marcolino7

My command:
sudo ln -s /opt/jdk1.8.0_121/lib/arm/jli/libjli.so /usr/lib/

;-))

[borand (Jorn Borup-Andersen)]

And just to finish it…

if there still a Windows 10 box that doesn’t show, follow this guide to enable ‘reception’ of ping on windows box.

https://technet.microsoft.com/en-us/library/cc749323(v=ws.10).aspx

Now Paper UI can discover my win10 systems.

/Joern