I have an annoying problem with several integrations. The problem is that when the hub constructs URLs to itself, it will use https://127.0.0.1/ or even https://HUB_IP_ADDRESS/. The certificate then fails and the clients that are attempting to access the hub don't work. I'm using custom and valid SSL certs. This would be solved if it were possible to specify how the hub should refer to itself instead of using its ip address. This would also allow for more custom setups such as putting the hub behind NAT.
Example integrations where this causes issues are chromecast and sonos.
Here is an example error that I see in the logs:
Error: Certificate for <127.0.0.1> doesn't match any of the subject alternative names: [*.example.com, example.com]
Is this feature already supported somewhere that I'm not looking? Can anyone think of a workaround?