[SOLVED] Presence with Android after using Iphone

grhosso · August 24, 2018, 9:56am

It is the same version that I have, 2.3.0

diyha · August 24, 2018, 10:00am

the number is same, but build is different. temporarily enabled some logs for debugging purpose, at INFO level.
You can drop new file over old file in openhab addons folder.

grhosso · August 24, 2018, 10:34am

ok thank you. I let you know how is going…

grhosso · August 24, 2018, 3:24pm

Here is the log I have added some comments between [ ] in the log to better understaing my test.

Regards.

2018-08-24 17:03:34.476 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:04:34.538 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:04:34.552 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:04:34.555 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:05:34.648 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:05:34.661 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:05:34.664 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:06:34.756 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:06:34.769 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:06:34.772 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:06:39.730 [me.event.ThingUpdatedEvent] - Thing 'network:pingdevice:192_168_2_160' has been updated.         [TURN OFF WIFI FROM MY PHONE]
2018-08-24 17:07:39.782 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:07:39.797 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:07:39.803 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:08:44.791 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:08:44.804 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:08:44.809 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:08:49.758 [vent.ItemStateChangedEvent] - phone_sw changed from ON to OFF							[DETECTED BY BINDING]
2018-08-24 17:09:49.804 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:09:49.818 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:09:49.823 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:10:54.812 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:10:54.827 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:10:54.831 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:11:59.821 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:11:59.835 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:11:59.838 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:11:59.859 [vent.ItemStateChangedEvent] - phone_sw changed from OFF to ON 							[TURN ON WIFI FROM MY PHONE]
2018-08-24 17:11:59.877 [me.event.ThingUpdatedEvent] - Thing 'network:pingdevice:192_168_2_160' has been updated.
2018-08-24 17:12:59.926 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:12:59.939 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:12:59.943 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response.  [I LOCK THE SCREEN IN ORDER TO GET PHONE SLEEP AND SEE WHAT IS HAPPENNING]
2018-08-24 17:14:00.002 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:14:00.016 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:14:00.020 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:15:00.254 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:15:00.269 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:15:00.274 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:16:00.466 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:16:00.480 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:16:00.484 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:17:01.074 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:17:01.089 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:17:01.095 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:18:01.896 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:18:01.909 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:18:01.914 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:18:06.870 [me.event.ThingUpdatedEvent] - Thing 'network:pingdevice:192_168_2_160' has been updated.			[BINDING DOES NOT DETECT PRESENCE]
2018-08-24 17:19:06.922 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:19:06.937 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:19:06.941 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:20:11.931 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:20:11.947 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:20:11.953 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:20:16.898 [vent.ItemStateChangedEvent] - phone_sw changed from ON to OFF								[BINDING CONFIRMS OFF AND SWITCH OFF, BECAUSE ARPING DOES NOT DETECT PHONE] 
2018-08-24 17:21:16.950 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:21:16.969 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:21:16.973 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:22:21.958 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:22:21.972 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:22:21.975 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response
2018-08-24 17:23:26.967 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:23:26.980 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDERR=arping: libnet_init(LIBNET_LINK, eth0): libnet_open_link(): UID/EUID 0 or capability CAP_NET_RAW required
arping: you may need to run as root
2018-08-24 17:23:26.984 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => no response

diyha · August 24, 2018, 3:44pm

Ok. Can you do following?

Login to your OH server, its Linux right?
If yes, do

sudo chmod u+s $(which arping)

grhosso · August 24, 2018, 3:52pm

Yes, linux.

Let mw know…

diyha · August 24, 2018, 3:55pm

Login as pi or openhabian. On your shell prompt (not karaf), run this command

sudo chmod u+s $(which arping)

And then monitor logs. No need to restart Linux or openHAB or binding.

grhosso · August 24, 2018, 4:07pm

After type it

sudo chmod u+s $(which arping)

So far, is arping well, I get time response even with phone locked, so far after 10 minutes, I did not have any “false” OFF. I will post tomorrow after some test.

thanks!

2018-08-24 17:53:04.978 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:53:05.860 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=737.179 msec
2018-08-24 17:53:05.980 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:54:06.055 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:54:06.260 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=77.062 msec
2018-08-24 17:54:06.380 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:55:06.474 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:55:07.090 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=457.160 msec
2018-08-24 17:55:07.230 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:55:11.468 [me.event.ThingUpdatedEvent] - Thing 'network:pingdevice:192_168_2_160' has been updated.
2018-08-24 17:56:11.516 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:56:11.680 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=17.102 msec
2018-08-24 17:56:11.800 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:57:16.527 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:57:17.050 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=377.220 msec
2018-08-24 17:57:17.170 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:58:21.538 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:58:22.380 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=667.275 msec
2018-08-24 17:58:22.500 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 17:59:26.547 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 17:59:27.110 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=377.270 msec
2018-08-24 17:59:27.230 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 18:00:31.559 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 18:00:31.750 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=17.219 msec
2018-08-24 18:00:31.870 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 18:01:36.571 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 18:01:37.150 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=427.066 msec
2018-08-24 18:01:37.270 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 18:02:41.581 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 18:02:41.850 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=117.220 msec
2018-08-24 18:02:41.970 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 18:04:51.604 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 18:04:52.110 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=377.237 msec
2018-08-24 18:04:52.230 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online
2018-08-24 18:05:56.616 [INFO ] [org.openhab.binding.network         ] - Running arping 2.14+ for mac <MAC> ip 192.168.2.160 via eth0
2018-08-24 18:05:57.240 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 STDOUT=ARPING 192.168.2.160
60 bytes from <MAC> (192.168.2.160): index=0 time=477.158 msec
2018-08-24 18:05:57.360 [INFO ] [org.openhab.binding.network         ] - arping 192.168.2.160 via eth0 => online

diyha · August 24, 2018, 4:20pm

Cool.
Watch it for 10 hours please. Yours is Android 8, Samsung?

Also, regarding my doubt about concurrent executions causing libnet native errors, it turns out the binding does arping on all available interfaces on host, I happen to have a 4g modem connected to openhabian host besides local LAN. That 4g modem’s eth1 interface was giving that strange native error. So it wasn’t a concurrency issue at libnet level. I removed randomness+locking fixes from latest code.

Will create a PR once I polish the code such that big brothers don’t reject it.

grhosso · August 24, 2018, 4:24pm

It is Samsung Galaxy s9+. EDIT: Sorry, yes Android 8.0

Sure, tomorrow I will let you know

grhosso · August 25, 2018, 9:21am

This morning I have seen the log and everything worked fine, always got answer from arping. But I am not sure if has been more than 10 hours, so I will have a look today and tomorrow, but it seems that is working good.

diyha · August 25, 2018, 2:00pm

Glad to know its working with Android 8 too.

Here is a summary of important changes that made network binding work for my Android 5 and 7 phones. The PR will contain this summary report:

Adapt to new arping version 2.14 in raspbian stretch. Parameter -w [timeout] now means micro-seconds instead of seconds
New startegy for sending / receiving and terminating arping. Combine -c and -C options. -c6 -C1 -w5000000 means send upto 6 packets, wait for 5 secs in between each send, return with success immediately after receiving 1 packet. This allows for robustness as well as quick result. Current binding sends only 1 packet which is far too optimistic on busy networks.
Introduce -t [MAC] hint to arping. It made my Android phones respond. Only specifying -i [iface] IP doesn’t always work. Not all phones respond to broadcast ARP who-has-ip queries in low power state, but apparently they do respond to queries targeted at their MAC.
Extract latency information from arping output, optionally.
Pipe in STDERR of arping and print it in OH logs, that helps identifying installation issues (especially setuid), illegal argument issues (due to version upgrades), or any other issues.
Try to determine success from arping STDOUT and then fallback to exit code.

rlkoshak · August 25, 2018, 3:13pm

This may be a little outside the scope but I know I and the other Docker users would appreciate it if you too a look to see whether the latest arping is being included in the Docker images and advise what we may need to do if it isn’t re these changes. Obviously it isn’t a big deal until these changes get merged.

diyha · August 25, 2018, 3:33pm

Agreed. I also am inclined to submit a PR to setup arping by default on openhabian with setuid root.

grhosso · August 26, 2018, 9:02am

I confirm that this night presence has been 11 hours ON without any issue, so the arping worked fine. Then I had to go out, so went OFF, but I did not get any false OFF.

Regards.
Thanks for the support.

Matt77 · September 16, 2018, 2:33pm

Hi, I was using the Network binding with an IPhone X, on latest OS and Android (8.1) for quite some time now. But resently it started that I get problems when any of the phones got disconnected from the WiFi.
For my Android phone for example it takes sometimes up to 30 minutes after disconnecting
from wifi to change the status.
The settings im using are:
Retries 10
Refresh interval 60000
Timeout 5000.
Any idea what could cause this huge delay?

andre · February 10, 2019, 5:29am

@diyha did your binding updates get PR’d and merged? I don’t see them in the official repo that I can tell?

diyha · April 3, 2019, 2:29pm

Not yet. I didn’t get chance to collaborate with maintainer, I was busy. I have posted links to code and explanation is here on thread. We should get this mac address based arping in. It did help my phone.

Olymp · September 8, 2019, 7:54am

Is this present in openHAB 2.5.0 Build # 1684?

Martin_Maat · June 1, 2020, 7:34pm

I followed all the leads in this topic (as far as they seemed to apply to my current OH version on a Synology Disk Station) but they did not seem to make much difference. My Android phone, the wife’s iPhone and her Apple Watch, they all dropped out at irregular intervals before being spotted again while all devices were home. I experimented with the network thing settings for a day or two and now it looks stable: both my Android phone and the wife’s iPhone have been ON for over 24 hours without once dropping out. This is encouraging. My settings are:

Refresh interval: 5000
Retry: 180
Timeout: 5000

This may seem overly aggressive to some but I do not think this is a problem. Pings are cheap. It pings the phone every 5 seconds and if it does not get an answer it will do this for 15 minutes before concluding the phone is not there.
Apparently within a 15 minutes time frame the phone’s network stack will always wake up shortly to do something. I guess this may depend on the kind of apps that are installed on the phone, this appears to work for me but your milage may vary. My phone is running Android 7.1.2 by the way.

Getting back home should typically be noted pretty quickly, although it could take a while if the phone is in a dozing period at the time I get home.

I think the 15 minute delay is actually quite nice. If I have my phone in my pocket and walk up to the snail-mailbox or take the garbage container to the street, I may lose wifi for a couple of minutes but I would not consider myself not home.

Maybe this will help someone.

As much as I like the idea of using one’s Ubiquity Wifi network and the Ubiquity binding (I read this somewhere), I do not have a convenient way to keep a UniFi controller running permanently in my network. I do have Ubiquity access points and a Windows server that is always on but the UniFi controller is a desktop application and there is not always someone logged on to the server, let alone always the same user. So this does not seem to work for me.