How to check if my Zigbee2Mqtt works properly?

SilentImp · January 21, 2024, 1:01pm

Problems I see:

I can’t read data manually from sensors
It seems like data didn’t actually being updated
I can’t change any device settings

Hardware configuration

Setup looks like this

There are Phillips Hue hub and wifi router near it.

Zigbee map

Devices

Trying to read temperature from one of the sensors

I put heater into the boiler room, no change was detected, now the sensor in my pocket in my room, still nothing. I did resterted the sensor. No changes.

I feel that my zigbee setup do not work properly.
What I can do to confirm this assumption and fix this?

Stiltjack · January 21, 2024, 1:33pm

The screenshots all seem to come from the Z2M add-on. Are you detting any device info in the MQTT integration?

SilentImp · January 21, 2024, 1:39pm

Can you, please, explain how I can check this?
In the Zigbee2Mqtt devices I have plenty:

If you mean the mqtt broker, I don’t think there are any devices listed:

In the logs:

Summary

2024-01-21 13:07:22: New connection from 172.30.32.2:43286 on port 1883.
2024-01-21 13:07:22: Client closed its connection.
2024-01-21 13:09:22: New connection from 172.30.32.2:51742 on port 1883.
2024-01-21 13:09:22: Client closed its connection.
2024-01-21 13:11:22: New connection from 172.30.32.2:36026 on port 1883.
2024-01-21 13:11:22: Client closed its connection.
2024-01-21 13:13:22: New connection from 172.30.32.2:48918 on port 1883.
2024-01-21 13:13:22: Client closed its connection.
2024-01-21 13:15:22: New connection from 172.30.32.2:40890 on port 1883.
2024-01-21 13:15:22: Client closed its connection.
2024-01-21 13:17:22: New connection from 172.30.32.2:59676 on port 1883.
2024-01-21 13:17:22: Client closed its connection.
2024-01-21 13:19:22: New connection from 172.30.32.2:34370 on port 1883.
2024-01-21 13:19:22: Client closed its connection.
2024-01-21 13:21:22: New connection from 172.30.32.2:58068 on port 1883.
2024-01-21 13:21:22: Client closed its connection.
2024-01-21 13:22:25: Saving in-memory database to /data//mosquitto.db.
2024-01-21 13:23:22: New connection from 172.30.32.2:60294 on port 1883.
2024-01-21 13:23:22: Client closed its connection.
2024-01-21 13:25:22: New connection from 172.30.32.2:50252 on port 1883.
2024-01-21 13:25:22: Client closed its connection.
2024-01-21 13:27:22: New connection from 172.30.32.2:53632 on port 1883.
2024-01-21 13:27:22: Client closed its connection.
2024-01-21 13:29:22: New connection from 172.30.32.2:34372 on port 1883.
2024-01-21 13:29:22: Client closed its connection.
2024-01-21 13:31:22: New connection from 172.30.32.2:50536 on port 1883.
2024-01-21 13:31:22: Client closed its connection.
2024-01-21 13:33:22: New connection from 172.30.32.2:59184 on port 1883.
2024-01-21 13:33:22: Client closed its connection.
2024-01-21 13:35:22: New connection from 172.30.32.2:57056 on port 1883.
2024-01-21 13:35:22: Client closed its connection.
2024-01-21 13:36:23: Client mqttjs_871ae575 disconnected.
2024-01-21 13:36:26: New connection from 172.30.33.0:46088 on port 1883.
2024-01-21 13:36:26: New client connected from 172.30.33.0:46088 as mqttjs_40bd65fd (p2, c1, k60, u’mqtt’).
2024-01-21 13:37:22: New connection from 172.30.32.2:55650 on port 1883.
2024-01-21 13:37:22: Client closed its connection.
2024-01-21 13:39:22: New connection from 172.30.32.2:33812 on port 1883.
2024-01-21 13:39:22: Client closed its connection.
2024-01-21 13:41:22: New connection from 172.30.32.2:35586 on port 1883.
2024-01-21 13:41:22: Client closed its connection.
2024-01-21 13:43:22: New connection from 172.30.32.2:55716 on port 1883.
2024-01-21 13:43:22: Client closed its connection.
2024-01-21 13:45:22: New connection from 172.30.32.2:51132 on port 1883.
2024-01-21 13:45:22: Client closed its connection.
2024-01-21 13:47:22: New connection from 172.30.32.2:41150 on port 1883.
2024-01-21 13:47:22: Client closed its connection.
2024-01-21 13:49:22: New connection from 172.30.32.2:40722 on port 1883.
2024-01-21 13:49:22: Client closed its connection.
2024-01-21 13:51:22: New connection from 172.30.32.2:34196 on port 1883.
2024-01-21 13:51:22: Client closed its connection.
2024-01-21 13:52:26: Saving in-memory database to /data//mosquitto.db.
2024-01-21 13:53:22: New connection from 172.30.32.2:44742 on port 1883.
2024-01-21 13:53:22: Client closed its connection.
2024-01-21 13:55:22: New connection from 172.30.32.2:47868 on port 1883.
2024-01-21 13:55:22: Client closed its connection.
2024-01-21 13:57:22: New connection from 172.30.32.2:35100 on port 1883.
2024-01-21 13:57:22: Client closed its connection.
2024-01-21 13:59:22: New connection from 172.30.32.2:55592 on port 1883.
2024-01-21 13:59:22: Client closed its connection.
2024-01-21 14:01:22: New connection from 172.30.32.2:34330 on port 1883.
2024-01-21 14:01:22: Client closed its connection.
2024-01-21 14:03:22: New connection from 172.30.32.2:42390 on port 1883.
2024-01-21 14:03:22: Client closed its connection.
2024-01-21 14:05:22: New connection from 172.30.32.2:33824 on port 1883.
2024-01-21 14:05:22: Client closed its connection.
2024-01-21 14:07:22: New connection from 172.30.32.2:58934 on port 1883.
2024-01-21 14:07:22: Client closed its connection.
2024-01-21 14:09:22: New connection from 172.30.32.2:49688 on port 1883.
2024-01-21 14:09:22: Client closed its connection.
2024-01-21 14:11:22: New connection from 172.30.32.2:57416 on port 1883.
2024-01-21 14:11:22: Client closed its connection.
2024-01-21 14:13:22: New connection from 172.30.32.2:54786 on port 1883.
2024-01-21 14:13:22: Client closed its connection.
2024-01-21 14:15:22: New connection from 172.30.32.2:46942 on port 1883.
2024-01-21 14:15:22: Client closed its connection.
2024-01-21 14:17:22: New connection from 172.30.32.2:55298 on port 1883.
2024-01-21 14:17:22: Client closed its connection.
2024-01-21 14:19:22: New connection from 172.30.32.2:43918 on port 1883.
2024-01-21 14:19:22: Client closed its connection.
2024-01-21 14:21:22: New connection from 172.30.32.2:36146 on port 1883.
2024-01-21 14:21:22: Client closed its connection.
2024-01-21 14:22:27: Saving in-memory database to /data//mosquitto.db.
2024-01-21 14:23:22: New connection from 172.30.32.2:44586 on port 1883.
2024-01-21 14:23:22: Client closed its connection.
2024-01-21 14:25:22: New connection from 172.30.32.2:34138 on port 1883.
2024-01-21 14:25:22: Client closed its connection.
2024-01-21 14:27:22: New connection from 172.30.32.2:39494 on port 1883.
2024-01-21 14:27:22: Client closed its connection.
2024-01-21 14:29:22: New connection from 172.30.32.2:60322 on port 1883.
2024-01-21 14:29:22: Client closed its connection.
2024-01-21 14:31:22: New connection from 172.30.32.2:46770 on port 1883.
2024-01-21 14:31:22: Client closed its connection.
2024-01-21 14:33:22: New connection from 172.30.32.2:54646 on port 1883.
2024-01-21 14:33:22: Client closed its connection.
2024-01-21 14:35:22: New connection from 172.30.32.2:59642 on port 1883.
2024-01-21 14:35:22: Client closed its connection.
2024-01-21 14:37:22: New connection from 172.30.32.2:58750 on port 1883.
2024-01-21 14:37:22: Client closed its connection.
2024-01-21 14:39:22: New connection from 172.30.32.2:47006 on port 1883.
2024-01-21 14:39:22: Client closed its connection.

Stiltjack · January 21, 2024, 1:54pm

In the MQTT integration.

Shouldn’t there be a device info page for each one?

SilentImp · January 21, 2024, 2:01pm

Yes, thank you very much, I did find it:

devices:

entries:

Inside boiler humidity/temperature sensor

dproffer · January 21, 2024, 5:13pm

A couple thoughts from your post:

In Zigbee2MQTT, I would enable the ‘Availability (advance)’ display. Picture below. This is really the best view of when the coordinator last communicated with each of your devices. Picture below.
From my understanding, especially for battery powered end devices, you really can not expect to reliably ask the device it’s current state. In Zigbee, end devices ‘push’ information to the coordinator or other devices, pulling information from an end device is really not part of Zigbee design, it can be done, but not reliably. Battery powered end devices and may even some ‘powered’ end devices go to sleep and wake up on a schedule they select. There is no way to override this. So if the device is asleep and you ask the coordinator to send a message to the device or query it state, there is a timeout to the message, if the end device does not wake within the timeout of the message, the message is lost. I do not thing there is a automatic resend of the message by it coordinator, if you as the ‘operator’ on top of the coordinator want to try again, it is up to you to manually asked the coordinator to send a new message.
Your Zigbee2MQTT console is the most ‘up to date’ snapshot of your network and devices. And unfortunately, without more complex tools, your view of your zigbee network is just a snapshot in time.

Good hunting!

SilentImp · January 21, 2024, 6:36pm

I did turn on an advanced mode. Now the picture is:

Some are offline, what I should do to get them back online?

From my understanding, especially for battery powered end devices, you really can not expect to reliably ask the device it’s current state.

But what about changing configurations of the devide? Is it any more relyable? Example, I am trying to add device to a group. But this fails as well:

Do I understand correctly and any change can fail randomly in case device is in sleep mode?

dproffer · January 21, 2024, 9:08pm

I’m brain farting (missing) on something I told you, as you should see a ‘Last seen’ column as well.

See if this explainer is better than I am:

I’ve not done much with direct configuration of battery powered end devices, but from what I understand and read, you have to ‘poke the button once’ or similar just prior to sending your commands to the device, such that it is awake to receive the message. You will see an error from the coordinator after the timeout period if you are not success with waking up the device. Some, however I am not sure all, devices will show in their configuration on status or configuration tab on Zigbee2MQTT. I’m not sure group membership stuff shows there.