Last week, the Network Binding presence detection started having problems. If I restart openHAB, it will work for a while. But if I leave home and come back, it never comes online. I have been using it without trouble until recently for a couple of years.
I am running openHAB 3.3M1 on a Pi4B using openhabian.
I set the logging level for the Network Binding to TRACE. And then a series of messages “host name resolved to other address, (re-)setup presence detection”.
2022-03-20 19:43:19.255 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Found constructor with 0 arguments : public org.openhab.binding.network.internal.discovery.NetworkDiscoveryService()
2022-03-20 19:43:19.257 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : This thread collected dependencies
2022-03-20 19:43:19.259 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : getService (single component manager) dependencies collected.
2022-03-20 19:43:19.262 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Querying state satisfied
2022-03-20 19:43:19.266 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Querying state satisfied
2022-03-20 19:43:19.309 [TRACE] [.network.internal.utils.NetworkUtils] - set minCidrPrefixLength to 24, maximumPerInterface is 255
2022-03-20 19:43:19.327 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : getting activate: activate
2022-03-20 19:43:19.329 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Locating method activate in class org.openhab.binding.network.internal.discovery.NetworkDiscoveryService
2022-03-20 19:43:19.344 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Declared Method org.openhab.binding.network.internal.discovery.NetworkDiscoveryService.activate([interface org.osgi.service.component.ComponentContext]) not found
2022-03-20 19:43:19.347 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Found activate method: public void org.openhab.binding.network.internal.discovery.NetworkDiscoveryService.activate(java.util.Map)
2022-03-20 19:43:19.349 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : invoking activate: activate: parameters [org.apache.felix.scr.impl.helper.ReadOnlyDictionary]
2022-03-20 19:43:19.368 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : invoked activate: activate
2022-03-20 19:43:19.369 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Set implementation object for component
2022-03-20 19:43:19.371 [DEBUG] [al.discovery.NetworkDiscoveryService] - bundle org.openhab.binding.network:3.3.0.M1 (273)[org.openhab.binding.network.internal.discovery.NetworkDiscoveryService(291)] : Changed state from satisfied to active
2022-03-20 19:43:19.652 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.100 ms
2022-03-20 19:43:19.658 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:19.682 [INFO ] [ternal.dhcp.DHCPPacketListenerServer] - DHCP request packet listener online
2022-03-20 19:43:19.685 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: AA:1F:1F:1B:93:C6, hostname: 192.168.1.216, port: null
2022-03-20 19:43:19.803 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.216 on interface: wg0
2022-03-20 19:43:19.818 [TRACE] [g.network.internal.PresenceDetection] - Perform native ping presence detection for 192.168.1.216
2022-03-20 19:43:19.838 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.216 on interface: eth0
2022-03-20 19:43:19.898 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.139 ms
2022-03-20 19:43:19.900 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:19.901 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: , hostname: 192.168.1.189, port: null
2022-03-20 19:43:19.925 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.189 on interface: wg0
2022-03-20 19:43:19.937 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.189 on interface: eth0
2022-03-20 19:43:19.948 [TRACE] [g.network.internal.PresenceDetection] - Perform native ping presence detection for 192.168.1.189
2022-03-20 19:43:19.978 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.098 ms
2022-03-20 19:43:19.980 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:19.981 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: , hostname: 192.168.1.66, port: null
2022-03-20 19:43:20.078 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.133 ms
2022-03-20 19:43:20.080 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:20.082 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: , hostname: 192.168.1.69, port: null
2022-03-20 19:43:20.187 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.124 ms
2022-03-20 19:43:20.189 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:20.191 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: , hostname: 192.168.1.179, port: null
2022-03-20 19:43:20.244 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.116 ms
2022-03-20 19:43:20.246 [TRACE] [g.network.internal.PresenceDetection] - host name resolved to other address, (re-)setup presence detection
2022-03-20 19:43:20.248 [DEBUG] [twork.internal.WakeOnLanPacketSender] - initialized WOL Packet Sender (mac: , hostname: 192.168.1.170, port: null
2022-03-20 19:43:20.861 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.66 on interface: wg0
2022-03-20 19:43:20.873 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.66 on interface: eth0
2022-03-20 19:43:20.888 [TRACE] [g.network.internal.PresenceDetection] - Perform native ping presence detection for 192.168.1.66
2022-03-20 19:43:20.983 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 192.168.1.66: icmp_seq=1 ttl=64 time=61.6 ms
2022-03-20 19:43:20.990 [DEBUG] [g.network.internal.PresenceDetection] - Getting latency from ping result PingResult{success=true, responseTimeInMS=61.6, executionTimeInMS=93.0} using latency mode false
2022-03-20 19:43:21.380 [DEBUG] [g.network.internal.PresenceDetection] - Getting latency from ping result PingResult{success=true, responseTimeInMS=null, executionTimeInMS=451.0} using latency mode false
2022-03-20 19:43:21.435 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.69 on interface: wg0
2022-03-20 19:43:21.444 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.69 on interface: eth0
2022-03-20 19:43:21.494 [TRACE] [g.network.internal.PresenceDetection] - Perform native ping presence detection for 192.168.1.69
2022-03-20 19:43:21.537 [DEBUG] [network.internal.utils.LatencyParser] - Parsing latency from input 64 bytes from 192.168.1.69: icmp_seq=1 ttl=128 time=17.9 ms
2022-03-20 19:43:21.539 [DEBUG] [g.network.internal.PresenceDetection] - Getting latency from ping result PingResult{success=true, responseTimeInMS=17.9, executionTimeInMS=42.0} using latency mode false
2022-03-20 19:43:22.414 [DEBUG] [g.network.internal.PresenceDetection] - Getting latency from ping result PingResult{success=true, responseTimeInMS=null, executionTimeInMS=901.0} using latency mode false
2022-03-20 19:43:22.428 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.179 on interface: wg0
2022-03-20 19:43:22.438 [TRACE] [g.network.internal.PresenceDetection] - Perform ARP ping presence detection for 192.168.1.179 on interface: eth0
2022
I’m going to try deleting all of my Network Things and re-adding them from the UI and see if that helps. I wonder if the IOS Private Wi-Fi feature is creating a situation where over time, as device Private addresses change, which result in the DHCP server assigning a new IP address, eventually led to this situation.