Ok, I'll merge in the changes and release it soon, maybe even today.
I don't experience this in my network, but I only have 3 APs for the IoT WiFi, and each AP has a transmit power setting appropriate for the location, among other things.
Not in the firmware, no, I would always recommend to use a static DHCP lease for these devices. It actually does switch to using the MAC as network ID once it knows it. Once it has done that, it can follow IP changes as long as HE is on the same subnet.
As far as auto-discovery goes, there's still issues with broadcast message flooding I'm looking at nailing down. I'm also considering a network-scan approach, it could be done fairly quickly, but this is not something I've decided on as of yet. This of course only works if HE is on the same subnet as the devices, or you have equipment forwarding broadcasts beyond the one hop these broadcasts send. I try to write these drivers so that they work in the broadest possible set of network topologies, while still being "easy" to use for the average HE user.
It all requires time, I have the background for this, but even so it is a complicated platform to write for.
This has been talked about at length in this forum, and I guess we will never see it, we can still hope, but don't count on it. The only "metric" we could possible have would be based on analyzing the logs and the time between entries and how that time changes.
