>All routers have some way of finding out the IP leases. Sure, with 1001 ways of accessing a router's IP leases table varying depending on the manufaturer, use

>All routers have some way of finding out the IP leases. Sure, with 1001 ways of accessing a router's IP leases table varying depending on the manufaturer, user names and passwords, whether anyone has changed the password, where to click, interfaces, apps, avahi daemon, nmap, ipv6, temperature outside, God's mood, and another 1001 ways of screwing it up even you know how it's supposed to work. Try to explain to a non-tech friend (even a relatively IT savvy one) how to find the IP of the Raspberry Pi on the local network and you'll understand why it is a bad idea. If you have client isolation, which some routers and setups have, you're screwed, too. It's so bad that Google has to have a dedicated app just to find the IP of the Raspberry Pi on the network - I'm not kidding [1]. And that's supposed for the people who are courageous enough to try programming a Pi. Yeah technically you can do it, but if it's so stupid and flaky that you can't rely on it, then can't be counted as a method to do something. 1: https://play.google.com/store/apps/details?id=com.google.android.apps.aiy&hl=en_US https://play.google.com/store/apps/details?id=com.google.and...