Jump to content

Local connection local network identification issue using SSID with multiple homes


Recommended Posts

Posted

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

Local Connection Settings with Comment.png

Posted
1 hour ago, danmpark said:

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

 

The local network option in UD Mobile may not work well in this situation, the original implementation used the WiFi network's BSSID but it only worked on Android, iOS does not expose the BSSID to apps so we are limited to the SSID.  We understood that there was a possibility for conflict, but it would be rare.  

My suggestion, is to remove the SSID in UD Mobile for the location where you spend less time.  The Local Connection are not required and override default settings. 

  • 3 weeks later...
Posted
On 5/4/2024 at 3:14 PM, Javi said:

The local network option in UD Mobile may not work well in this situation, the original implementation used the WiFi network's BSSID but it only worked on Android, iOS does not expose the BSSID to apps so we are limited to the SSID.  We understood that there was a possibility for conflict, but it would be rare.  

My suggestion, is to remove the SSID in UD Mobile for the location where you spend less time.  The Local Connection are not required and override default settings. 

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

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.5k
×
×
  • Create New...