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.
It’s not my guess. I’m currently using it on port 9000 - as explained here.
Ok, so it’s possible although not described 
Right, current official documentation is misleading.
I’d like to suggest to send your improvement ideas to https://homey.app/support
I have similar problems. Even with the normal function Port Forwarding both interface and manual mingle ports 4859 and 4860, leaving it unclear what to use.
I’ve setup a NPM with a Proxy for my Homey Self Hosted Server. The dynamic domain hosted by. Infomaniak works perfectly, SSL certificate is ok. When I check my domain with a curl command, it reaches my NPM server.
When I change the Proxy to http with port 4859, the Homey Local User login is reachable via the domain. https with 4860 doesn’t work.
Whatever I try, I get an error in My Homey Account, when I try to add the domain. I get a timeout every time.
Did you know that Homey SHS is also reachable remotely without opening any ports? Using Homey’s built-in server connection is more secure as well
Can you explain more please?
For Homey SHS, no port forwarding is required. By default, Homey already has a secure remote connection that you can use. If you switch to a different network, you can still use the my.homey.app webapp and Homey mobile app.
That default option is extremely slow and unreliable…
