This is the inconsistency I pointed out above. I assure you (and it makes sense) that you can use the external port of your choice via reverse proxy. It works.
I think the Homey app just uses default port 443 and exchanges the url.
If you are using a simple DynDNS and port forward, then you habe to use a separate port for every internal service on the www side of your router.
But for reverse proxy, you only forward one port (443) to the proxy. Then use single subdomains for each dervice like shs.mydomain.com:443. And the proxy maps the (sub)domain to your internal IP/port.
So it’s not neccessary to use another port than 443. Just use 443 with a Letsencrypt certificate and all is fine.
I think the Homey app just uses default port 443 and exchanges the url.
Wrong: you can specify your fqnn+port on homey.app website.
But for reverse proxy, you only forward one port (443) to the proxy.
Wrong too. Your fw this for the challenge, for example.
So it’s not neccessary to use another port than 443. Just use 443 with a Letsencrypt certificate and all is fine.
Need 443 of other services. As proved, homey supports https on different ports, and that’s all I was solving before.
Nice, could also explain how to connect the Homey app on your smartphone when not using the default port?
Once you configured on homey.app (fqdn+port), it’s automatic.
That’s only your assumption. There is only written about adding a domain name to SHS settings. There is no input field for port and no hint about it. It just says it’s using 443 as default.
So if you add a port to your URL, it will be a wrong URI if Homey app is using 443.
It’s not my guess. I’m currently using it on port 9000 - as explained here.
Ok, so it’s possible although not described 
1 Like
Right, current official documentation is misleading.
I’d like to suggest to send your improvement ideas to https://homey.app/support
