[GH-ISSUE #61] [Feature Request] Support local and remote HA instance URLs #60

Open
opened 2026-03-03 16:43:16 +03:00 by kerem · 4 comments
Owner

Originally created by @strabbit on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/nickustinov/itsyhome-macos/issues/61

Originally assigned to: @nickustinov on GitHub.

Many Home Assistant setups have a URL that can be accessed externally, whether through reverse proxy or other means (ex: https://homeassistant.example.com/) and then another URL that can be accessed internally, when you're on the same network as the HA instance (ex: http://192.168.50.123:8123/).

It'd be great to see support added for a local instance URL, such that the local instance URL would be used first, and if unreachable the remote instance URL would be used as a fallback.

Originally created by @strabbit on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/nickustinov/itsyhome-macos/issues/61 Originally assigned to: @nickustinov on GitHub. Many Home Assistant setups have a URL that can be accessed externally, whether through reverse proxy or other means (ex: `https://homeassistant.example.com/`) and then another URL that can be accessed internally, when you're on the same network as the HA instance (ex: `http://192.168.50.123:8123/`). It'd be great to see support added for a local instance URL, such that the local instance URL would be used first, and if unreachable the remote instance URL would be used as a fallback.
Author
Owner

@eschmidt12 commented on GitHub (Feb 20, 2026):

Agree 100% - came here to add this to the feature request list but you beat me to it.

Ideally the local connection would be tested first, and if that connection isn't present, it fails over to the remote connection. This way it defaults to local control, keeping with the spirit of HA, but still allows functionality remotely.

<!-- gh-comment-id:3936564128 --> @eschmidt12 commented on GitHub (Feb 20, 2026): Agree 100% - came here to add this to the feature request list but you beat me to it. Ideally the local connection would be tested first, and if that connection isn't present, it fails over to the remote connection. This way it defaults to local control, keeping with the spirit of HA, but still allows functionality remotely.
Author
Owner

@nickustinov commented on GitHub (Feb 23, 2026):

There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach?

<!-- gh-comment-id:3943816009 --> @nickustinov commented on GitHub (Feb 23, 2026): There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach?
Author
Owner

@eschmidt12 commented on GitHub (Feb 23, 2026):

There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach?

That seems reasonable. Seems like you'd want to have a primary SSID for local URL, then use the remote URL for anything that doesn't match the primary SSID.

<!-- gh-comment-id:3944052607 --> @eschmidt12 commented on GitHub (Feb 23, 2026): > There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach? That seems reasonable. Seems like you'd want to have a primary SSID for local URL, then use the remote URL for anything that doesn't match the primary SSID.
Author
Owner

@strabbit commented on GitHub (Mar 1, 2026):

There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach?

That would work. General fallback might be slightly more robust in my specific use-case, but both approaches would work.

<!-- gh-comment-id:3978956057 --> @strabbit commented on GitHub (Mar 1, 2026): > There have been multiple requests about this, some would prefer different HA connection URL's based on SSID's. Any comments on such approach? That would work. General fallback might be slightly more robust in my specific use-case, but both approaches would work.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/itsyhome-macos#60
No description provided.