UD Mobile Remote Access Problem when on Home WiFi

[Aceland, LLC]

I have two Eisys-one at my main home, and one at my cabin. When trying to access my cabin from my primary home, UD Mobile fails to connect when on my local WIFI. If I turn WIFI off, I can access it just fine using my cellular connection. The reverse scenario, however, works fine when accessing my main home from my cabin's WiFi. Is there possibly a blocked port I need to open? Any other possible scenarios?

[Javi]

The local connection settings for the cabin are incorrect, accessing a local ip (i.e. eisy.local), or you have defined a WiFi access Point which is incorrect.

Go the the Cabin's Controller Settings and check the Local Connection Settings.

[Aceland, LLC]

Thanks for your reply. 

Keep in mind that I can remotely access the Eisy if using a cellular connection, but not a wifi connection on my home network from 200 miles away. Also, if I use wifi from another remote connection, I also don't have an issue. 

At any rate, where do I find the controller settings you're referring to? I don't see anything on the Admin Console that would seem to pertain. 

[Javi]

Understood, the issue is likely UD Mobile is trying to connect to a local connection (IP Address) when on your WiFi network. The controller settings are in UD Mobile has nothing to do with the Admin Console.

[dbwarner5]

19 hours ago, Aceland, LLC said:

Thanks for your reply. 

Keep in mind that I can remotely access the Eisy if using a cellular connection, but not a wifi connection on my home network from 200 miles away. Also, if I use wifi from another remote connection, I also don't have an issue. 

At any rate, where do I find the controller settings you're referring to? I don't see anything on the Admin Console that would seem to pertain. 

In UDM.. go to Settings, scroll down to controller, click on your controller you want to manage, then scroll down you will see two sections;  Remote Connections Settings and Local Connection Settings.

You local settings are picking up your local network at home and therefore can't connect to the remote cabin.

So for your remote setting you should have the long https://my.isy.io/isy/<long string> that you copy and pasted from the Portal. That is working as expected and why when on cellar you can connect to your cabin. 

For you local settings you will have http://eisy.local.  The problem is that the cabin is NOT on your local network. UDM is picking up your house network and thinks you are local  and tries to make the connection as http://eisy.local, but with all the wrong controller information, so its trying to actually connect to your house eisy but with the wrong credentials. 

This probably because under the next section System Network Relations:  you have your house network as the local network under the cabins controller. Delete that and the next time you are at you cabin, add the cabins's local network to this section.

I think it should work after that. 

[Aceland, LLC]

Thanks for the detailed instructions. I found and fixed the culprit which turned out to be slightly different. The local connection was already pointing to the eisy's IP address, not http://eisy.local. BUT in local connection settings, under System Network Relations were listed the local WiFi networks for both houses. Once I deleted the main home network, voila, UD mobile then pointed to the remote connection.  Now both eisys can be selected seamlessly. 

Thanks again!

[dbwarner5]

So tha means that when you are home, you are actually using hte remote connection vs the local connection since it doesn't recognize you home network since you deleted it?

Am not sure what the proper fix / set up is since I dont have two homes with Eisy to test, but ideally, you would want both local networks in UDM and it should know depending on which Controller you select, which network is to be considered the Local network that corresponds to the selected controller, thereby connecting you locally if possible, or remotely otherwise. 

@Javi seems like once you load a Local connection into UDM, you should be then asked to "link" it to a controller and then have UDM do the logic to use the Local connection or remote connection depending on which local network I am connected to and which controller I chose, this house or the second house. 

[Javi]

10 hours ago, dbwarner5 said:

 

@Javi seems like once you load a Local connection into UDM, you should be then asked to "link" it to a controller and then have UDM do the logic to use the Local connection or remote connection depending on which local network I am connected to and which controller I chose, this house or the second house. 

This is how it works now, Each controller can have "links" to WiFi Networks (multiples links in case the 5GHz and 2.4GHz have different names/ssid).  UDM will only attempt a local connection when on the "linked" network.  Each controller's WiFi links are unique to the controller, but can be shared with other controllers, so you only have to define the network one time if you have multiple controllers on the same network.

Issue can arise if both the homes/locations have the same WiFi Network Name (which I have encountered once), but this is rare and, in my opinion, not good practice on the user's end.  Android allowed us to read the BSSID(UUID) of the network but iOS does not (gives a faux BSSID) so if this issue arises the user will need to name the WiFi networks differently or use UDM's the automatic detection with a hard coded numerical IP Address for the local connection and the numerical IPs must be different.

[Aceland, LLC]

My cabin Eisy config had both home networks in it, (Settings > Controllers > Cabin Eisy > System Network Relations > Local Networks) so when I was at my main home, it was trying to use the local WiFi rather than looking remotely. Once I took out the main home's network, the problem went away.

Keep in mind that in this case, this config is within the settings for the cabin's controller settings--it's not global--so deleting the main home wifi had no effect on the main home's Eisy connection. 

[dbwarner5]

4 hours ago, Aceland, LLC said:

My cabin Eisy config had both home networks in it, (Settings > Controllers > Cabin Eisy > System Network Relations > Local Networks) so when I was at my main home, it was trying to use the local WiFi rather than looking remotely. Once I took out the main home's network, the problem went away.

Keep in mind that in this case, this config is within the settings for the cabin's controller settings--it's not global--so deleting the main home wifi had no effect on the main home's Eisy connection. 

so you still have the home wifi in the home controller settings for local connections, and then the cabin wifi in the cabin controller so you will still have local connections there.

yes. that was what I was trying to get you to.

thanks for the update

 

Edited Monday at 06:59 PM by dbwarner5