Zigbee2MQTT: Not connected to MQTT Server (but in fact, it looks like it is)

Configuration Zigbee
,
1

Hello,

I’m totally lost. Everything was running great, until at 2PM today, it didn’t worked anymore.
I’m using a Zigbee2MQTT addon, running on HomeAssistant OS, and using the last version of Mosquitto Broker, Zigbee2MQTT, and HomeAssistant.
Everything is up to date with the last upgrades.

When I start Zigbee2MQTT, everything looks fine, it populates MQTT correctly:
MQTTInfo

But then, I get a:
“Not connected to MQTT”
And I get this error message in a loop.

image_2023-09-17_214027747
image_2023-09-17_2140277471551×841 69.2 KB

Unfortunately, I have no more clues about what happens.
The fact is that … it’s able to update MQTT topic …

image_2023-09-17_214125158
image_2023-09-17_2141251582272×349 43.2 KB

I don’t know what to do to make it working.
Can someone help me please ? :pray:

Thanks !

2

What do your mqtt logs say?

And please stop posting pictures of logs. Copy, paste, been around for decades.

3

Sorry, should have done it for the Zigbee2MQTT logs, but the values of MQTT topics where too big to be posted, I just wanted to show that it’s still filled, so not a connection issue by itself.

On the Mosquitto broker, I get a tons of:

2023-09-18 09:17:15: New client connected from 172.30.32.1:43488 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:15: Client mqttjs_ab0544b2 disconnected due to malformed packet.
2023-09-18 09:17:16: New connection from 172.30.32.1:43494 on port 1883.
2023-09-18 09:17:16: New client connected from 172.30.32.1:43494 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:16: Client mqttjs_ab0544b2 disconnected due to malformed packet.
2023-09-18 09:17:17: New connection from 172.30.32.1:43508 on port 1883.
2023-09-18 09:17:17: New client connected from 172.30.32.1:43508 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:17: Client mqttjs_ab0544b2 disconnected due to malformed packet.
2023-09-18 09:17:18: New connection from 172.30.32.1:43518 on port 1883.
2023-09-18 09:17:18: New client connected from 172.30.32.1:43518 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:18: Client mqttjs_ab0544b2 disconnected due to malformed packet.
2023-09-18 09:17:19: New connection from 172.30.32.1:43532 on port 1883.
2023-09-18 09:17:19: New client connected from 172.30.32.1:43532 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:19: Client mqttjs_ab0544b2 disconnected due to malformed packet.
2023-09-18 09:17:21: New connection from 172.30.32.1:43540 on port 1883.
2023-09-18 09:17:21: New client connected from 172.30.32.1:43540 as mqttjs_ab0544b2 (p2, c1, k60, u'mqttuser').
2023-09-18 09:17:21: Client mqttjs_ab0544b2 disconnected due to malformed packet.

Also, I rollbacked to Zigbee2MQTT 1.32-1 and it works. I just can’t upgrade anymore :frowning:

4

Then use a code share site to make it easier to help you :wink:

That’s caused by the Supervisor and isn’t related to Z2M, what does your Z2M MQTT config look like?

5

I had a very similar problem lately, it was fixed by a host reboot (ie not just restarting HA Core)

6

Already restarted (electrical reboot) multiple times :frowning:

Socat

enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false

MQTT

base_topic: zigbee2mqttHA
user: mqttuser
password: 10b9jabm
server: mqtt://192.168.31.23:1883

Serial

port: /dev/ttyUSB0
adapter: ezsp

Worth to mention that it’s currently working with 1.32-1 but if I upgrade, then it breaks

7

I am having the same issue after my Linky passed to mode “Standard”. Reverting to 1.32.2-1 “fixed” the issue.

8

What on earth does that mean?

9

There are two modes for Linky, “Historique” and “Standard”. The mode “Historique” does not give production data with TIC interface which Lixee uses, so I called Enedis to change my Linky mode to “Standard”. Then, the Zigbee2MQTT started to show error message “Not connected to MQTT”. I read this topic and reverted to 1.32.2-1, no more this error message.

10

What is linky?

11