Double entries on DHCP reservation list

[busman1598]

Google Home lists duplicate entries for each device on my DHCP Reservation list.  All other Home features are working correctly. The  Home app has been uninstalled and reinstalled with no change to the reservation list.  I installed the app on my wife's iphone and the issue does not appear there.  I have the app installed on my Moto G Power 2023 which I have rebooted several times with no change to the issue.  After 1.5 hours on the phone last night with Google support, they basically gave up.  Any suggestions??

[busman1598]

All my reservations remain as entered.  No issues with that.  Possibly WIMPLER forgot to save.

[Lidelse]

That or maybe an issue with the newest beta if he is running that? honestly Android 15 QPR2 beta 3 broke some stuff in other areas. 80 percent charge limit just doesn't work on pixel tablet or pixel 6 pro for me anymore for instance. toggle still there. worked in previous two qpr2 betas. now just broken. But like I said I haven't noticed reservations borked. But I don't run a pixel 9.

[busman1598]

I am running Android 14 on a Moto G Power 2023.  When 14 was installed I lost WiFi calling, but that's another subject. 😁

[juggalolefty]

It seems that although the thread is not dead and the issue is not resolved, nobody from Google is weighing in anymore. Maybe one day they will address it. I don't believe the issue is related to CGNAT. I tested and I am not behind CGNAT. The issue that @wimpler is having is due to the way the router retains device information. I've found that when I assign a DHCP reservation, I have to wait up to 24 hours for the previous device that held the IP to drop out of the devices list. There are ways to work around this but it still takes time for the router to renew the lease to the newly assigned IP. I believe these routers are more geared toward plug and play users than those of us that have different use cases, i.e. DHCP reservations, port forwarding, etc.

[Lidelse]

Yeah it's definitely entry level. Part of why I went with this vs the 2 grand for a top end mesh system to test a mesh system out first. I'll be honest I need to run at least one more wire and in my house that'd hard given its age. So yeah. But as a heads up even on android 16 beta 1 on the new version of Google home that triggers the issue is still there. It's definitely not a big problem so I doubt it is high on priority given it really seems to just be cosmetic. 

[hauklandsverk2]

I have the same issue. I first noticed it a couple of months back. This is an issue regardless of what Device you access Google home on. there seems to have been a few other issues occurring at the same time:

1. Some devices connect and disconnect tens of times per day 
2. Once in a while the guest network disappears, and the devices on this IP range are listed in the normal network device list, but all of them listed as wired
3. Logs have become hopelessly unreliable, sometimes showing device histories and sometimes not. The same with device lists for seven and 30 days.
4. Known devices reconnecting often register as unknown devices, are logged as such, but seconds later the known device is listed and the unknown device will never again connect
5. Functionality available to the iOS app is gradually disappeared. One response from Google was that this was due to increased security features. Nevertheless, the functionality is still available in the android version, meaning that this answer cannot be trusted.

Anyone else experiencing these simultaneous problems?

[busman1598]

My Google Home devices randomly appear as off-line but in fact, they are still on-line.  Google continues to ignore and look the other way. ☹️

[Lidelse]

Do either of you use a VPN or private dns? Those definitely can mess with Google home functionality. Also aparrently android 16 beta 1 is broke on Google home for a lot of people though I have had zero issues personally.

[asterger]

No VPN and Android 15 for me.

[busman1598]

I don't use a VPN.  I use Pi-hole as my DNS.  My android version is 14.  I haven't checked lately but the double DHCP list was not an issue on my wife's iPhone. 

[Lidelse]

So just checked on android 16 beta it still shows double DHCP with latest Google home app on the public preview. I'll check the android 14 Lenovo tablet thoufh but it wouldn't surprise me if pi hole makes Google home have hiccups depending how it's configed.  Shouldn't. But. Sometimes nextdns does for me. 

[Lidelse]

on lenovo android 14 tablet also still double dhcp.

[busman1598]

Switching to my ISP's DNS vs Pi-hole makes no difference here.  My wife uses the same DNS as I do with no issues on here iPhone.  Go figure.

EDIT:  All DNS inquiries are directed to Pi-hole.  At that point, Pi-hole filters out the unwanted requests and the forwards the rest to Google (8.8.8.8) for processing.  Pi-hole only filters and forwards.

[asterger]

Just checked IP Reservations and its back to single entries.  Only recent change was to DNS changed from Automatic (default) to Custom (experimented with a No Ad provider for a day) then to ISPs DNS which is the current setting where I now have single DHCP reservations.

[asterger]

Also ISPs DNS seems to be "snappier".

[asterger]

That didn't last long; double IP Reservation entries are back.

[chucktomasi]

Just to add my note that I am having the same issue. Annoying, but not impacting the functionality insofar as I can tell.