Moved HA Server, now a new IP - Uh Oh!

1

I had HAOS running on an old PC and wanted to tinker.

So I got a nice mini-PC, installed Proxmox with HAOS in a VM using the great existing scripts and all went (shockingly for me) smoothly. Even for the zigbee, zwave, and UPS USB connectivity working.

But a few dozen Tasmota devices across both local and several remote sites (connected via Wireguard) half-stopped working. Digging deeper I see that the MQTT server they are configured to use is at 192.168.0.103 (the old HAOS server), while the new, current HAOS server is at 192.168.0.162

I am running the Mosquitto Broker add-on and the native MQTT integration.

So, before I start sticking my fingers in things (like changing the new server to the old server’s IP; go to every Tasmota device and change the MQTT server to the new server’s IP; etc.), I thought I would ask here what the best way to fix this would be.

Here are some idea of mine (but I’m cool, even appreciative, if someone has a better solution):

  1. Change the current server to 192.168.0.103
  2. Change a few dozen Tasmota device’s MQTT settings to use 192.168.0.162
  3. Setup an VM running an external MQTT server under proxmox
  4. Add a 2nd IP address to the current HAOS server of 192.168.0.103
  5. Change the Tasmota devices MQTT settings to use the hostname of the local server or 127.0.0.1 or 172.30.32.0 (although this specifically clearly won’t work - .0)

Looking for a solution that is minimal work and least likely to cause problems later (such as this problem now).

Thank you!

2

Hi @josephny

Peronally, I’d change the IP of the new server to match what the old server was. Just make sure the old server isn’t on the network too (using the same address).

I also like to give significant network devices memorable IPs. My HA is at 192.168.0.2. With this in mind, I would change the address of my HA and then point everything that needs to find it at that address. That’s just me though - it’s extra work.