danmpark

Thanks for the suggestion, I'll start that way and consider different SSID's later.

Just installed my Eisy in one of my homes and used UD Mobile to connect to it. It replaced my old isy device that I've been using for over ten years. Both remote and local connections work well. Then I went to my other home where I'll be installing a second Eisy device and hit a problem. I use the same SSID in both homes with different IP networks. Unfortunately, the the UD device simply uses the SSID name to identify the local network. Therefore in my second home, it could not connect locally and there is no failover to a remote connection. My options were to either turn off Wi-Fi or connect to my guest network SSID. Really wish there was a better way to identify local networks, like (10.1.0.0/24), then via SSID. I like using the same SSID in both homes as it simplifies moving wireless devices like printers back and forth. However, the UD Mobile applications use of SSID to identify local networks would force me to use unique SSID's in my homes. I'm moving from MobiLinc Pro which had no issues with this as it understood IP networks at the IP address level. Is there a work around for customers with multiple homes using your UD Mobile application when the Wi-Fi network in each home has the same SSID value. You could add additional important information like the actual network ID (10.1.0.0/24) in addition to SSID so UD Mobile would then know to use a remote connection instead of trying to use a local connection which fails. Hate to have a critical home automation application limit my network design across multiple homes. Hope you can help me resolve this. Thanks Dan