970 BUG: old-connected Mac still showing on network

So I have another instance of a phantom device - it's a real device, that does not get purged. I know how it works - on Thursday last, I grabbed my daughter's MacBook Pro and brought it to my house, as she was having some trouble with getting an update finished, backup wasn't configured right, etc. - some simple housekeeping of her laptop. It was on my network, the 970 Orbi.  I got the work done, and took the laptop back later in the day.

 

So this weekend, I noticed it was showing up on my network - connected at 2.4GHz. I know it was the laptop, I verified the MAC address. It comes and goes. I tried blocking it, waiting for it to be removed from the connected list in Access Control, and then I could delete it. I checked yesterday, it showed as unconnected in the Orbi app, so I deleted it there too. But it's back.

 

Some table is not being cleared out. This is not the first time it's happened, it's happened with a visitor's iPhone too.

 

I suspect we have had no FW updates on the 970 since forever as they are trying to get the disconnects/flips to cellular working. But there are a growing number of other problems that could be fixed and improve the user experience - why not release with them? Isn't there some sort of workaround on the disconnects that could be done until the final solution?

 

Issues that could be fixed:

• IPv6 does not reliably stay connected on Apple 6E/7 devices when 6E setting set to Auto, devices will show connected to the wrong Orbi, devices will show as wired when they are not
• Turning on logging causes memory creep and eventual crashes of router and satellites
• DHCP messages flooded from devices - sometimes 80-100 DHCP requests in an hour, some times it's from devices that don't move around (like an Apple HomePod or printer)
• Old devices still show as connected to 2.4GHz