You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At https://companion.home-assistant.io/en/getting_started/migration it seems to say that one can enter a URL if one is not on "home wifi". Later, in the Nabu Casa troubleshooting section, it says one cannot set up Nabu Casu directly, and one needs to be on the home LAN first. It is really not clear if a connection to the HA instance uses any methods other than via the https:://hass.example.com:8123 URL, or if this is merely about finding internal (presumably working only on one SSID) vs external (presumably working everywhere) URLs.
The notion of a trailing slash, presumably "https://hass.example.com:8123" vs "https://hass.example.com:8123/" is also confusing. Technically one has no path and the other a path with no components, but it does not make sense that any software would treat these separately, especially for URLs entered by humans, almost none of whom understand the syntax subtleties.
The migration guide says only "or you can manually enter the URL", and doesn't address trailing slashes.
(I am running into this helping someone not physically with me configure the iOS app to access a server that neither of us are physically at -- but it does have a straightforward, entirely accessible, domain name.)
The text was updated successfully, but these errors were encountered:
At https://companion.home-assistant.io/en/getting_started/migration it seems to say that one can enter a URL if one is not on "home wifi". Later, in the Nabu Casa troubleshooting section, it says one cannot set up Nabu Casu directly, and one needs to be on the home LAN first. It is really not clear if a connection to the HA instance uses any methods other than via the https:://hass.example.com:8123 URL, or if this is merely about finding internal (presumably working only on one SSID) vs external (presumably working everywhere) URLs.
The notion of a trailing slash, presumably "https://hass.example.com:8123" vs "https://hass.example.com:8123/" is also confusing. Technically one has no path and the other a path with no components, but it does not make sense that any software would treat these separately, especially for URLs entered by humans, almost none of whom understand the syntax subtleties.
The migration guide says only "or you can manually enter the URL", and doesn't address trailing slashes.
(I am running into this helping someone not physically with me configure the iOS app to access a server that neither of us are physically at -- but it does have a straightforward, entirely accessible, domain name.)
The text was updated successfully, but these errors were encountered: