I have 3 different hubs, all on the same subnet. Two in location A and 1 in location B. So I'm having to routinely switch between 3 different hubs and 2 different locations.
Feedback is that in that the user exerience of trying to do this at all in the iPad App is extremely poor.
Doesn't try and connect remotely if local connection is unavailable
Connects to the wrong hub other than what you've selected if it finds a similar IP
No way to force a remote connection other than to find it via registered hubs page (totally different spot in the UI) and connect there
Slow and unintuitive methods to switch
I accept that someone that runs 3 hubs in 2 different locations with the same subnet may not be typical, but it would be good to see some improvements in the switching experience. This has been a long term issue (see this closed thread) and I like the user that started this closed thread normally give up and just end up having a number of remote pages in a browser.
What version of the mobile app are you using? The topic you linked to is nearly 4 years old and refers to the 1.x version of the app. In the current 2.x version, you can switch hubs by tapping your hub name on the Home tab and selecting Switch to another hub.
I'm using the latest version. All of this feedback is based on the latest version of the app. I was using this other post to highlight a simialr thread, but acknowledge that some work has been done to improve the experience since this time. However issues remain which is the reason for the feedback. Other issue I'm having setting up a web based portal to manage all of my instances is that when you launch from this page https://remoteaccess.aws.hubitat.com/ I'm not seeing a way to keep multiple connections to multiple hubs open at the same time.
When you say "connect" are you referring to tapping the hub name and then Connect to Hub? Or the app itself connecting to the hub? The "Connect to Hub" option is really just a convenience, I would recommend just using a browser directly (on a PC ideally).
Have never had an issue with this.
Similar? Or exact same? I suspect the latter only.
It is 3 taps in the app?
Hub Name > Switch to Another Hub > New Hub Name
Yes that would work, but I can't save those as a group because of the fact that it's incognito. It's only persistent for as long as Chrome/Edge remains open. I'm referring to the connection of the app itself to a given hubitat node. I think many of my issues are to do with the fact that all nodes are on the same network subnet. So...
Location A: Hubitat 1 (192.168.0.x)
Location B: Hubitat 2 (192.168.0.y)
Location B: Hubitat 3 (192.168.0.z)
So if I'm at location A, trying to switch to another hub using the iPad app to Hubitat 2 or 3, it tries to make a local connection no matter what, probably because the app things it should be there given the subnet and there is no ability to flick it to a remote mode. I will just hang and say that the node is unreachable.
If hypothetically hubitat's 1 and 3 had the same IP address despite being in different locations, if I was in location A and tried to connect to Hubitat 3, Hubitat 1 would be displayed (if using the connect to hub function). There is no validation of the name. Just seems to be using IP address.
You could say that I need to have different subnets for each location, however they are sizeable networks and no simple task just to get Hubitat working properly. Issue goes away if I make remote connections for everything.
I think a few suggestions/feedback would
If it can't be found locally and the device is online remotely, then a failed local connection should fail over to a remote connection
If you are after device A, then it should validate the name of that and not just go off IP address if using the connect to hub function.
Be able to have multiple connections open to multiple HUBs in a way that it can be saved as a group in a browser
Its supposed to, without knowing the exact logic of how the app works its hard to know what the failure point is in your case.
The "Connect to Hub" button in the app, if you are local, literally just takes the IP it thinks the hub is on and opens a browser within the app. AFAIK there is no handshake to validate a hub name, If you are remote then it uses the remote admin, there is some sort of token going on so I would suspect it always gets on the correct hub when remote.
Thanks so much for the feedback. Again, acknowledge that there has been some improvement but I think there is room for additional robustness features which is the nature of the feedback. If you are saying that at least for point 1 of the suggestions, it should work that way, then it is likely to do with the fact that my subnets are the same across sites. However, only a developer can confirm this. Perhaps the development team can consider item 1 a bug and items 2 and 3 as feedback for consideration in the future.
