Ok, best I can tell OH has arping disabled. (The arp_state in the properties is Disabled. And uses_ios_wakeup is Yes. But, the device in question is an Android phone…guessing it knows nothing about ios wakeups. )
I adjusted the wait, etc. in paperui but, see no change in the presence of the phone when sleeping.
The network binding does not apply binding configurations without a service reload. The easiest way is an OH restart.
The next version will handle that differently.
The binding tries it’s best to use the installed arping. On windows there is one arping version that apparently does not work yet. But in general if you can call it from the command line, it should work from within openHAB as well (if you have given OH/java the correct permissions).
To check the address of MAC-A, use knowledge of MAC-B and IP-B.
$ arping -S <IP-B> -s <MAC-B> -p <MAC-A>
Time to wait between pings, in microseconds.
-W sec Same as -w, but in floating point seconds.
Ubuntu man pages on the other hand don’t list a -W. Nor do the Linux man pages on the web.
So, -w is the standard and -W is maybe something added to the rasbian/debian/openhabian.
As @David_Graeff said, it should be in the documentation. So just make sure to read the docs next time to find out how to set things up for a binding
The problem here (I guess) is that there are different versions of arping around with different capabilities. They come from different packages and thus it depends what your arping is capable of and that also changes the behaviour of the wait time parameter which can either just be a small w or case sensitive w and W. If I am not mistaken the meaning of the small w parameter also changes unfortunately. But that should not be important since the binding takes care of that normally.
As I noted, the elevated permissions seems to have fixed my issue. Maybe I’m referring to the documentation as the readme?
I certainly agree about the RTFM comment. Even after a 45 year career as a software/hardware engineer, who’s made the same comment many times, I need to be reminded occasionally.
In this particular case trhough, I had read the documentation, but, I was focused on the bad behavior being the same as before the upgrade to version 2 of the binding and expected that some setting in the binding had not taken effect when the upgrade happened (and arping did work from the command line)…I brushed over the elevated privilege note.
Yes, this is apparently the case. especially between utilities that are available on windows and linux. Different or lacking arguments between OS’s are more prevalent with linux utilities implemented on windows (sometimes, windows just can’t do the same thing, or in some cases vice-versa). Not sure why this is the case between two debian derived distros…but, c’est la vie.