core icon indicating copy to clipboard operation
core copied to clipboard

Tasmota broken on different networks

Open ChuckHL opened this issue 4 months ago • 0 comments

The problem

I am using home assistant OS with Tasmota and MQTT (mosquito) as the broker.

My HAOS internal ip is 10.10.1.15 and every device used to be able to connect fine. Devices in my homenetwork 10.10.1.0/24 and devices in my work network 10.10.5.0/24 (connected through openvpn and well routed).

With the latest updates, devices relying in TASMOTA with MQTT mosquito from a different network are not working (but i know its not MQTT fault as other services that are not using TASMOTA but use MQTT from my other network works fine.

Here is a sample of the MQTT log (also not sure why not the devices from the other network are appearing as the docker ip of the HAOS):

2024-10-13 23:02:29: Client 5T8mpYOAkstNVgfvALRS89 disconnected. 2024-10-13 23:02:37: Client 5gjTJ8rnUugn3ItrjAY85c disconnected. 2024-10-13 23:02:37: New connection from 10.10.1.15:40495 on port 1883. 2024-10-13 23:02:37: New client connected from 10.10.1.15:40495 as 5Aif7CbBJZYmAZjQPgWQs8 (p2, c1, k60, u'tasmota'). 2024-10-13 23:03:48: New connection from 172.30.32.2:46070 on port 1883. 2024-10-13 23:03:48: Client closed its connection. 2024-10-13 23:05:48: New connection from 172.30.32.2:45432 on port 1883. 2024-10-13 23:05:48: Client closed its connection. 2024-10-13 23:07:48: New connection from 172.30.32.2:44290 on port 1883. 2024-10-13 23:07:48: Client closed its connection. 2024-10-13 23:08:13: Client DVES_8FFA68 closed its connection. 2024-10-13 23:08:24: New connection from 10.10.1.52:51089 on port 1883. 2024-10-13 23:08:24: New client connected from 10.10.1.52:51089 as DVES_8FFA68 (p2, c1, k30, u'tasmota'). 2024-10-13 23:08:27: Client DVES_8FFA68 closed its connection. 2024-10-13 23:08:44: New connection from 10.10.1.52:57808 on port 1883. 2024-10-13 23:08:44: New client connected from 10.10.1.52:57808 as DVES_8FFA68 (p2, c1, k30, u'tasmota'). 2024-10-13 23:08:46: Client DVES_8FFA68 closed its connection. 2024-10-13 23:09:07: New connection from 10.10.1.52:59779 on port 1883. 2024-10-13 23:09:07: New client connected from 10.10.1.52:59779 as DVES_8FFA68 (p2, c1, k30, u'tasmota'). 2024-10-13 23:09:10: Client DVES_8FFA68 closed its connection. 2024-10-13 23:09:37: New connection from 10.10.1.52:65335 on port 1883. 2024-10-13 23:09:37: New client connected from 10.10.1.52:65335 as DVES_8FFA68 (p2, c1, k30, u'tasmota'). 2024-10-13 23:09:48: New connection from 172.30.32.2:41258 on port 1883. 2024-10-13 23:09:48: Client closed its connection. 2024-10-13 23:11:48: New connection from 172.30.32.2:33358 on port 1883. 2024-10-13 23:11:48: Client closed its connection.

Hope this is the right place to ask.

Regards

What version of Home Assistant Core has the issue?

core-2024.10.2

What was the last working version of Home Assistant Core?

core-2024.10.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tasmota

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_tasmota_2024-10-14T05-17-32.484Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

ChuckHL avatar Oct 14 '24 05:10 ChuckHL