Provide secondary internal URL

Hi Folks

Would it be possible to add a configuration option for a secondary internal url in the companion app?
My use case: I have my hassio configured with both wifi and wired connection.
For performance reasons, I use the wired connection as primary in the app, but if it becomes unreachable for some reason (e.g. switch down), I currently have to change the internal url manually to the wifi IP. It would be nice if the app could fallback automatically to a predefined URL in that case.

Thanks and keep up the awesome work!

I don’t see a feature there to add because if your instance is linked with Nabu Casa (you don’t indicate it clearly but it looks to be) it’ll automatically update to use the network link avalaible on the PI (so if Ethernet disappears it’ll switch to Wifi if activated and reverse :wink:


Thanks for the quick reply. No my instance is not linked to Nabu Casa, it’s all manually configured. Internal URL is the ip address of my eth0 port and external URL is also linked to this IP (through duckdns & port forwarding). So if the wired port gets unreachable, the app loses all connection (untill I change the internal url to the wlan0 ip).


I use this app to switch between two HA instances.
Link to app description:

If you need some enhancements feel free to ask

I developed this app because i have a HA setup with a public instance accessible from the internet and another one that is hidden to the internet and only accessible from LAN. Both instances are only linked by mqtt. Thus my home HA installation is bullet proof against external hacking.

The public instance can only activate devices that are allowed within the mqtt bridge.

You can only truthfully state that is it has no Internet connection and those using it do not have abn==nd available Internet connection when using HA. Otherwise any software created by fallible humans that can contact the Internet has some, possibly low, risk of being “hacked”

Your are right, i would say i consider it bullet proof, because it’s the local mqtt instance that establishes the connection to the remote mqtt instance. So if the remote server is hacked at best they could try to send an mqtt payload that would be filtred out by the local mqtt instance. :slight_smile:

Assuming no privilege escalation in MQTT or its server…