IP Address error ESP32 to MQTT (Virtual host, supervised)

Hello,

I have HA running in supervised mode on a Synology NAS. All seems working fine, got various things running.

Trying to run ESPAltherma which needs an ESP32 with the relevant code configured to talk to a MQTT server on HA.

So i have MQTT running, mosquito which is working, i can test this via the publish and listen feature.

I have applied the relevant code to my ESP32 board, it connects to WiFi and gets an IP and the MQTT IP, user and password. All good.

My home network is 192.168.0.x/24. My HA and MQTT is 192.168.0.45. The ESP32 boards get internal addresses, i can see them in DHPC.

However, the integration with ESPAltherma isn’t working.

Weirdly, on the MQTT server logs i see an IP of 172.30.32.1 and .2 trying to connect to the MQTT server.

The 172.30.32.1 and .2 appears to be related to the “docker” IP network on my virtual host. See picture

Qu. Why is the 192.168.0.60 (ESP32) IP address information being changed to a 172.30.32.1 or .2 IP address by the tie it reaches the MQTT server on my HA at 192.168.0.45?

Here is a log from my MQTT server. You can see a connection from 172.30.32.1 which weirdly is accepted as it contains the correct mqtt user / password. i.e. this must be the ESP which has this info configured on it but it should be IP 192.168.0.60!

The ESPAltherma integration / code just isn’t working as the client name from the ESP32 is just random characters (see log below) it should be a pre set name from the code but it’s not?!

2024-01-24 15:57:10: New client connected from 172.30.32.1:58575 as 3A0ULVD9cMU6a3MNnXoEMX (p2, c1, k60, u’mqtt’).
2024-01-24 15:57:11: Client 3A0ULVD9cMU6a3MNnXoEMX disconnected.
2024-01-24 15:57:21: New connection from 172.30.32.1:43801 on port 1883.
2024-01-24 15:57:21: New client connected from 172.30.32.1:43801 as 0faYOJrRmw9xgBVhLh6PtB (p2, c1, k60, u’mqtt’).
2024-01-24 15:58:06: New connection from 172.30.32.2:40494 on port 1883.
2024-01-24 15:58:06: Client closed its connection.
2024-01-24 15:58:50: Client 4lB0vibsfPu2fRAQpYHgFX has exceeded timeout, disconnecting.
2024-01-24 16:00:06: New connection from 172.30.32.2:55600 on port 1883.
2024-01-24 16:00:06: Client closed its connection.
2024-01-24 16:02:06: New connection from 172.30.32.2:54870 on port 1883.
2024-01-24 16:02:06: Client closed its connection.

024-01-24 16:34:06: New connection from 172.30.32.2:41256 on port 1883.
2024-01-24 16:34:06: Client closed its connection.
2024-01-24 16:34:22: New connection from 172.30.32.1:53319 on port 1883.
2024-01-24 16:34:22: New client connected from 172.30.32.1:53319 as 6qTMLtLU5Zqp3ktLQbed3c (p2, c1, k60, u’mqtt’).
2024-01-24 16:34:22: Client 6qTMLtLU5Zqp3ktLQbed3c disconnected.
2024-01-24 16:36:06: New connection from 172.30.32.2:48638 on port 1883.
2024-01-24 16:36:06: Client closed its connection.
2024-01-24 16:38:06: New connection from 172.30.32.2:55274 on port 1883.
2024-01-24 16:38:06: Client closed its connection.
2024-01-24 16:39:49: Saving in-memory database to /data//mosquitto.db.
2024-01-24 16:40:06: New connection from 172.30.32.2:42952 on port 1883.
2024-01-24 16:40:06: Client closed its connection.

raomin/ESPAltherma: Monitor your Daikin Altherma / ROTEX heat pump with ESP32 (github.com)

Any help greatly appreciated.

Somewhere i guess i need to forward that 172 network to the 192 network. Don’t think on my LAN is where to do it, suspect it’s something on HA Host or config i need to change?

this was related to a programming issue with ProgramIO. Something to do with not using “build” before Upload. Sorted now