All the devices are in the same subnet.
How I stop and start the binding? where is the console?
I’m now upgrading from OH 2.4 snapshot 1443 to 2.4 stable and my network binding problem comes back. The binding is not relyable. It detects powered off devices as ON and some powered on devices as OFF. I checked with windows ping command in parallel and this gives me the right values.
I’m on windows and my config is:
binding.network:allowSystemPings=false
binding.network:allowDHCPlisten=false
binding.network:arpPingToolPath=
binding.network:cacheDeviceStateTimeInMS=2000
network:pingdevice:ekeyLAN [ hostname="10.4.1.3", retry=2, timeout=5000, refreshInterval=60000 ]
This device is allways on and pingable via windows ping command “ping 10.4.1.3 -t”. But network binding sometimes (once in 10min.) gives me OFF as status.
If I change “binding.network:allowSystemPings=true” which in my understanding just changes from java ping to windows ping and has nothing to do with arping command all my devices are at every time ON even if they are powered off. This means systemping does not work on windows? or I missed something.
On OH 2.4 snapshot all went correct.
Use network:allowSystemPings=true if you want to use the windows ping utility. Java pings don’t work on windows. It is strange that system pings don’t work reliable for you though. Honestly I have never testes this as I do not have a windows around anymore, but this option was introduced because of Windows users.
If it worked before and doesn’t now, then a recent commit that I haven’t performed myself broke something, I don’t know. But also have no time to investigate right now.
I checked it again. It looks that it take a while for the binding to work well.
I use
binding.network:allowSystemPings=false
an this is the only way it works. But I have to wait 1h with no config change on the binding to get relyable values. Now it looks like it works perfect again.
binding.network:allowSystemPings=true
never works for me. At all time it gives me all devices ON even if the do not exist or are off. Does a debug log helps you?
Could you please create a bug report and link this topic? I know why it happens but without a windows PC I’m not able to fix it. What you can do is ping your device with the windows tool and paste the output and also ping a non existing device and report the output.
Hey. I’m a little new to this. Thanks for showing me active this community is! I am struggling a little bit to get this up and running on Windows. Would I be better off on a Pi or a linux box? Both are options for me.
Right at this moment Linux works more reliable for network pings until those windows related problems are fixed.
can you lead me where to open a bug report?
Hi, all!
Just tried to install OH on my RPI3 and ran into the same issue as the topic starter.
I followed the tutorial from here:
All steps up until using network binding to find devices. I installed the network binding, all was successful. After that I go in the inbox and start a search using the network binding. It starts searching, but nothing is found.
If I add a device manually from the same interface it is added and I can see it in control panel ok. I am using a cell phone connected via WIFI to test this. Ping from the CLI also works fine. Only searching from inbox is not working.
I tried unplugging the power from RPI - didn’t help.
Then I tried stopping and restarting the binding as suggested above. Also no luck.
I checked the folders for binding config related information:
/conf/services
/conf/things
/conf/items
They are all empty, except services folder, but there is nothing about networking binding.
This is a clean install of openHABian. All I did after initial install is installed the network binding and tried to do a search for network devices as the tutorial suggests. But that failed.
Here is some information about my system:
And this is the log:
2019-01-02 12:45:22.971 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 12:45:23.048 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 12:45:23.614 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-01-02 12:45:24.157 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2019-01-02 12:45:24.245 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 12:45:24.247 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 13:14:14.658 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2019-01-02 13:15:11.579 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-01-02 13:15:13.812 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 13:15:13.822 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 13:16:19.643 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2019-01-02 13:16:19.807 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2019-01-02 13:16:19.902 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
==> /var/log/openhab2/events.log <==
2019-01-02 13:16:07.396 [thome.event.ExtensionEvent] - Extension ‘package-standard’ has been installed.
2019-01-02 13:16:20.517 [thome.event.ExtensionEvent] - Extension ‘ui-homebuilder’ has been installed.
2019-01-02 13:16:20.528 [thome.event.ExtensionEvent] - Extension ‘ui-basic’ has been installed.
2019-01-02 13:16:20.534 [thome.event.ExtensionEvent] - Extension ‘ui-habpanel’ has been installed.
2019-01-02 13:16:20.538 [thome.event.ExtensionEvent] - Extension ‘ui-paper’ has been installed.
2019-01-02 13:17:09.127 [thome.event.ExtensionEvent] - Extension ‘binding-network’ has been installed.
==> /var/log/openhab2/openhab.log <==
2019-01-02 13:31:57.408 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2019-01-02 13:31:57.709 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2019-01-02 13:48:06.723 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-01-02 13:48:09.156 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 13:48:09.160 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at xxx
2019-01-02 13:48:09.685 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
Any thoughts on what else I can try?
Same issue here…
I use a NanoPI Neo2 and I installed everything by myself…
so i was thinking that i made a mistake…
arping is in the path…
But if in network config i change arping to arppong or to any inexistent command and i launch discovery…
i dont get any error message in log. (i serarch log here tail -f /var/log/openhab2/openhab.log -f /var/log/openhab2/events.log -f /var/log/openhab2/audit.log)
So, where i can find log of network binding discovery?
Network binding discovery is not working in OH 2.4. will probably come back in 2.5 snapshots at some point.
I have the same issue…
OH 2.4 on a raspberry pi 3b+