Register another URL in Companion App to open itself via https:// URL

[bilogic]

Is your feature request related to a problem? Please describe.

Yes, I cannot form any https://... URL link that will open my CA. https://my.home-assistant.io opens up in browser instead of companion app (CA). This is because the CA expects the URL to start with homeassistant://... which creates another problem because many apps/software do not render homeassistant://... as a clickable link

Describe the solution you'd like

I would like to have a https://... link that will open my companion app.
An easier solution, but not within my control is to have add another registered URL in the CA e.g. direct.home-assistant.io, thus, when I click on https://direct.home-assistant.io/{where-the-user-wanna-go}, it redirects to homeassistant://navigate/{where-the-user-wanna-go}

Describe alternatives you've considered, if any

Update the form on https://my.home-assistant.io to accept homeassistant://navigate/{where-the-user-wanna-go}. Currently when I try to set my URL as homeassistant://navigate/{where-the-user-wanna-go}, it becomes homeassistant://

Additional context

None

WORKING SOLUTION

1. Tested Location: homeassistant://navigate/{where-the-user-wanna-go} on Chrome, did not work
2. This actually works

<META HTTP-EQUIV="Refresh" CONTENT="0;URL=homeassistant://navigate/{where-the-user-wanna-go}">

[dshokouhi]

We already are registering the my home assistant links. Did you turn it off by chance?

[bilogic]

How do I do that? I tried logging out and in again on the companion app and no effect.

[bilogic]

Wait, do you mean it is fixed to https://my.home-assistant.io only? What if I have https://ha.abc.com?

[dshokouhi]

Wait, do you mean it is fixed to https://my.home-assistant.io only? What if I have https://ha.abc.com?

No we don't register for your own URL.

[bilogic]

Ok,

1. I formed the URL https://my.home-assistant.io and have it sent to telegram
2. Clicking on the telegram link leads me to some sort of browser where I enter my custom URL
3. I added my URL and clicked on it, it loads from my domain in that browser, does not jump to companion app

[bilogic]

So, I tested

1. OK - https://api.whatsapp.com/............
2. Not OK - https://my.home-assistant.io
3. Not OK - https://www.home-assistant.io

OK = opens in WhatsApp app
Not OK = does not open in companion app, instead opens in a page powered by Chrome

Taken together it tells me telegram isn't the one blocking these URLs from the respective app, my logical conclusion is to point at the companion app, all permissions already given and I can see URLs 2 and 3 under Supported web addresses in the Set as default.

If this is an existing feature, then this issue will be a bug report

[dshokouhi]

If this is to be a bug report then we need much more information like app version, device info, logs. What URL you are actually using. A my home assistant link is usually configured in a manner like you see on the HA website.

[bilogic]

I tested on another android, same issue: no URL leads to companion app (CA) and I don't think it can happen, here's why:

1. If CA is installed properly, https://my.home-assistant.io should open CA immediately (like WhatsApp) since it appears in Supported web addresses
2. It should never lead to a webpage asking for my custom URL
3. But for some reason, it does not open the CA on both my devices, instead leads to the webpage asking me to input my custom URL
4. Since custom URL is not registered by any app nor CA, it will always open in Chrome

Perhaps can point out where if my understanding and deduction is incorrect?
My 2 devices are both Samsung, 1 tablet, 1 phone.

[bilogic]

@dshokouhi

Alright, I got it figured out. We were talking about 2 very different things.

1. I wanted a https:// that opens the companion app (CA)
2. You were referring to URLs that the CA registered
3. In typical apps that I have seen, registered URLs lead to the app opening itself, but this is currently not the case for CA
4. In order to open the CA, the URL has to be homeassistant://navigate/... and this is not https://...
5. Adding a https://... option is helpful because most apps don't render homeassistant://navigate/... as a URL
6. Thus, this will remain a feature request and I have updated my OP

[jpelgrom]

The app needs to include the URLs it wants to register for to deep link (open app directly) in the manifest file, which is included when the app is built. So overriding your Home Assistant URL won't be possible.

Deeplinks for HA, also for apps, are handled via my.home-assistant.io. If you need this we should add it there instead of making it Android specific. Going to close this as a duplicate of home-assistant/my.home-assistant.io#172.

Not OK - https://my.home-assistant.io

The landing page won't work. A specific page like https://my.home-assistant.io/redirect/energy should open the app.

[bilogic]

@jpelgrom

I found and implemented a working solution on my own domain. HA can implement this for the community too.

[bilogic]

@jpelgrom

How do I go to a specific page of mine? https://my.home-assistant.io/redirect/lovelace results in 404 page not found

[jpelgrom]

The issue I linked to as duplicate is a request to allow arbitrary pages with my. Currently you can only use the predefined destinations.