Hello everyone,
I’m having a problem with the Zigbee2mqtt dashboard: it no longer communicates with the Zigbee devices nor with the Gladys dashboard. However, in the other direction it
Hello @Psoy, that doesn’t ring a bell.
Have you tried just restarting?
Maybe it’s an issue with Zigbee2mqtt due to a recent update on their end..
[quote="pierre-gilles, post
Hello,
Could someone test whether they can properly control their Zigbee devices from the Zigbee2mqtt dashboard?
thanks for your feedback 
have a good day
Hi @Psoy 
I just tested it just now at my place, I’m controlling a light in Zigbee2mqtt, it turns on in real life + in Gladys the state is properly updated live.
Do you have any error logs (on the Zigbee2mqtt side / or Glad
hello @pierre-gilles
No, I don’t have anything abnormal in Gladys logs, however I just noticed that the timestamps of the Zigbee2MQTT logs are shifted by 2 hours, so I can’t see my actions on the dashboard, I’ll wait. Why are the logs shifted?
Gladys logs :
2024-04-19T10:28:44+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:28:56+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:29:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:25 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 19 Apr 2024 08:29:00 GMT
2024-04-19T10:29:06+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:29:16+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:29:23+0200 \u003cinfo\u003e netatmo.loadDevices.js:146 (NetatmoHandler.loadDevices) Netatmo devices not supported : 0
2024-04-19T10:29:26+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:29:36+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
2024-04-19T10:29:46+0200 \u003cwarn\u003e poll.js:14 (RtspCameraHandler.poll) Unable to poll camera
And the Zigbee2MQTT logs :
Zigbee2MQTT:info 2024-04-19 08:32:31: MQTT publish: topic 'zigbee2mqtt/lampe loupe', payload '{"child_lock":"UNLOCK","current":0.2,"energy":4.02,"indicator_mode":"off/on","linkquality":69,"power":42,"power_outage_memory":"off","state":"ON","voltage":235}'
Zigbee2MQTT:info 2024-04-19 08:32:44: MQTT publish: topic 'zigbee2mqtt/plafonnier meca', payload '{"child_lock":"UNLOCK","current":0.08,"energy":1.29,"indicator_mode":"off/on","linkquality":57,"power":15,"power_outage_memory":"off","state":"ON","voltage":229}'
Zigbee2MQTT:info 2024-04-19 08:32:56: MQTT publish: topic 'zigbee2mqtt/chauffage Sam', payload '{"linkquality":48,"power_on_behavior":"previous","state":"OFF"}'
Zigbee2MQTT:info 2024-04-19 08:33:19: MQTT publish: topic 'zigbee2mqtt/lampe loupe', payload '{"child_lock":"UNLOCK","current":0.2,"energy":4.02,"indicator_mode":"off/on","linkquality":66,"power":42,"power_outage_memory":"off","state":"ON","voltage":235}'
Zigbee2MQTT:info 2024-04-19 08:33:19: MQTT publish: topic 'zigbee2mqtt/lampe loupe', payload '{"child_lock":"UNLOCK","current":0.2,"energy":4.02,"indicator_mode":"off/on","linkquality":66,"power":42,"power_outage_memory":"off","state":"ON","voltage":235}'
Zigbee2MQTT:info 2024-04-19 08:33:31: MQTT publish: topic 'zigbee2mqtt/lampe loupe', payload '{"child_lock":"UNLOCK","current":0.2,"energy":4.02,"indicator_mode":"off/on","linkquality":69,"power":42,"power_outage_memory":"off","state":"ON","voltage":235}'
pi@gladys:~ $Nothing serious, it’s just displayed in UTC in my opinion (two hours behind French time at the moment)
So they are live logs
And on your
here are the broker logs, I don’t understand this.
1713448504: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713450305: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713452106: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713453907: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713454378: Client nodered_6c3d5b6181803498 disconnected.
1713454382: New connection from 192.168.1.134:34676 on port 1884.
1713454382: New client connected from 192.168.1.134:34676 as nodered_5e88f3a31a6389c4 (p2, c1, k60, u'gladys').
1713454522: Client nodered_5e88f3a31a6389c4 disconnected.
1713454525: New connection from 192.168.1.134:35000 on port 1884.
1713454525: New client connected from 192.168.1.134:35000 as nodered_1463b0086ee0befb (p2, c1, k60, u'gladys').
1713454662: Client nodered_1463b0086ee0befb disconnected.
1713454663: New connection from 192.168.1.134:35312 on port 1884.
1713454663: New client connected from 192.168.1.134:35312 as nodered_481b6ea9866969b3 (p2, c1, k60, u'gladys').
1713454916: Client nodered_481b6ea9866969b3 disconnected.
1713454917: New connection from 192.168.1.134:35912 on port 1884.
1713454917: New client connected from 192.168.1.134:35912 as nodered_8553fb2c8316af4a (p2, c1, k60, u'gladys').
1713455043: Client nodered_8553fb2c8316af4a disconnected.
1713455045: New connection from 192.168.1.134:36244 on port 1884.
1713455045: New client connected from 192.168.1.134:36244 as nodered_e4796d9ff5658e4a (p2, c1, k60, u'gladys').
1713455081: Client nodered_e4796d9ff5658e4a disconnected.
1713455083: New connection from 192.168.1.134:36368 on port 1884.
1713455083: New client connected from 192.168.1.134:36368 as nodered_acb5988a89844f2c (p2, c1, k60, u'gladys').
1713455708: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713457509: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713459310: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713461111: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713462912: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713464713: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713466514: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713468315: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713470116: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713471917: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713473718: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713475519: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713477320: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713479121: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713480922: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713482723: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713484524: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713486325: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713488126: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713489927: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713491728: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713492047: Client gladys-main-instance-87345 has exceeded timeout, disconnecting.
1713492083: New connection from ::1:43988 on port 1884.
1713492083: New client connected from ::1:43988 as gladys-main-instance-87345 (p2, c1, k60, u'gladys').
1713493529: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713495330: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713497131: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713498932: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713500733: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713502534: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713504335: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713506136: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713507937: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713509738: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713511539: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713513340: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713515141: Saving in-memory database to /mosquitto/config//mosquitto.db.
1713516942: Saving in-memory database to /mosquitto/config//mosquitto.db.
You still have this, it’s not reassuring (7 hours ago)
what can cause that,?
and how do you interpret the numbers
1713516942: Saving in-memory database to
It’s a timestamp (a date), you can paste it into this site to find out the date:
Network issue, problem with the host, Gladys being overwhelmed, and plenty of others 
Could you see what that might be? Can you tell me more about your setup?
Rpi3b+, with a 128GB SSD
I use Gladys’ broker for MQTT
same for Zigbee, everything is on the same Pi
I have 37 Zigbee devices
12 Tasmota devices
74 MQTT devices (virtual and real)
2 Hue devices
I have OwnTracks, LAN Manager for presence
about a hundred active scenes
I have an RFLink connected to the Pi via a powered USB Port
Node-RED on the same Pi but not the Gladys one
the Pi is connected directly to the router, and for the network with a speed test I have a download speed of 280 Mbps and the same upload (I don’t know if that’s relevant for Gladys’ local network)
that’s my environment
Is the RPi3 at its limit? 
Maybe not the RPi, though its power supply certainly is! 
Looks like a switch to a mini-PC! 
1 Like
Have you already run a quick htop to check CPU / RAM usage?
Does Gladys seem fast to use or not?
Thanks for your help
I’m having issues with camera snapshots in messages — they don’t keep up, one image every 5 seconds on Telegram after my gate opens, and I’ve noticed that from time to time the same image is sent; otherwise the device commands respond quickly.
here’s the htop :
login as: pi
pi@192.168.1.134's password:
Linux gladys 5.10.103-v7+ #1530 SMP Tue Mar 8 13:02:44 GMT 2022 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Apr 19 10:15:25 2024 from 192.168.1.128
Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.
pi@gladys:~ $ htop
0[||||||||||||||||||||||||||||||||||||||||||| 38.8%] Tasks: 45, 144 thr; 1 running
1[||||||||||||||||||||||||| 22.6%] Load average: 0.26 0.44 0.53
2[||||||||||| 9.7%] Uptime: 2 days, 04:36:07
3[||||||||||||||||| 15.1%]
Mem[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||353M/923M]
Swp[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||96.2M/100.0M]
PID USER PRI NI VIRT RES SHR S CPU%▽MEM% TIME+ Command
1414 pi 20 0 210M 75420 15844 S 0.0 8.0 0:20.01 node-red
1419 root 20 0 188M 60816 10532 S 0.0 6.4 0:00.00 node index.js
1420 root 20 0 188M 60816 10532 S 0.0 6.4 1:26.77 node index.js
1421 root 20 0 188M 60816 10532 S 0.0 6.4 1:25.00 node index.js
1422 root 20 0 188M 60816 10532 S 0.0 6.4 1:23.35 node index.js
1423 root 20 0 188M 60816 10532 S 0.0 6.4 1:25.03 node index.js
1441 pi 20 0 210M 75420 15844 S 0.0 8.0 0:00.00 node-red
1442 root 20 0 788M 10524 7244 S 0.0 1.1 0:00.00 /watchtower --cleanup --include-restarting
1443 root 20 0 788M 10524 7244 S 0.0 1.1 0:02.11 /watchtower --cleanup --include-restarting
1444 root 20 0 788M 10524 7244 S 0.0 1.1 0:02.18 /watchtower --cleanup --include-restarting
1446 root 20 0 188M 60816 10532 S 0.0 6.4 0:00.00 node index.js
1490 pi 20 0 210M 75420 15844 S 0.0 8.0 0:00.51 node-red
1491 pi 20 0 210M 75420 15844 S 0.0 8.0 0:00.50 node-red
1492 pi 20 0 210M 75420 15844 S 0.0 8.0 0:00.53 node-red
1493 pi 20 0 210M 75420 15844 S 0.0 8.0 0:00.52 node-red
1525 root 20 0 188M 60816 10532 S 0.0 6.4 0:05.30 node index.js
1526 root 20 0 188M 60816 10532 S 0.0 6.4 0:05.31 node index.js
1527 root 20 0 188M 60816 10532 S 0.0 6.4 0:05.30 node index.js
1528 root 20 0 188M 60816 10532 S 0.0 6.4 0:05.31 node index.js
1535 root 20 0 784M 5004 2844 S 0.0 0.5 0:12.17 /usr/bin/containerd-shim-runc-v2 -namespace moby -id ad98edfcb887b6fac64038d3b4871b3d65e628973ee666159e6c0c9c67ccbdad -address /run/containerd/containerd.sock
1536 root 20 0 783M 1848 692 S 0.0 0.2 0:05.75 /usr/bin/containerd-shim-runc-v2 -namespace moby -id f9486fbed00d9874326503b0dd43479eb69216cae3c4aea7642d523e95e8d1bc -address /run/containerd/containerd.sock
7686 root 20 0 783M 1708 760 S 0.6 0.2 0:49.08 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7688 root 20 0 783M 1708 760 S 0.0 0.2 0:08.09 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7689 root 20 0 783M 1708 760 S 0.0 0.2 0:00.00 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7690 root 20 0 783M 1708 760 S 0.0 0.2 0:07.45 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7691 root 20 0 783M 1708 760 S 0.0 0.2 0:00.00 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7692 root 20 0 783M 1708 760 S 0.0 0.2 0:05.71 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7693 root 20 0 783M 1708 760 S 0.0 0.2 0:00.00 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7694 root 20 0 783M 1708 760 S 0.0 0.2 0:06.77 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7695 root 20 0 783M 1708 760 S 0.0 0.2 0:07.13 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7714 root 20 0 783M 1708 760 S 0.0 0.2 0:07.12 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
7727 root 20 0 601M 162M 15704 S 0.0 17.6 0:00.01 node index.js
7728 root 20 0 601M 162M 15704 S 0.0 17.6 14:42.23 node index.js
7729 root 20 0 601M 162M 15704 S 0.0 17.6 14:43.54 node index.js
7730 root 20 0 601M 162M 15704 S 0.0 17.6 14:39.82 node index.js
7731 root 20 0 601M 162M 15704 S 0.0 17.6 14:35.49 node index.js
7732 root 20 0 601M 162M 15704 S 0.0 17.6 0:00.00 node index.js
7960 root 20 0 784M 4936 2960 S 0.0 0.5 0:02.95 /usr/bin/containerd-shim-runc-v2 -namespace moby -id a2aa4c1a4eac9a739b4f405cac1eda69cd899557a4cec7e2cfd5f53921ba64a8 -address /run/containerd/containerd.sock
8421 root 20 0 14520 6900 5960 S 0.0 0.7 0:00.16 sshd: pi [priv]
8539 pi 20 0 14412 7460 6500 S 0.0 0.8 0:01.07 /lib/systemd/systemd --user
8540 pi 20 0 37344 3392 1656 S 0.0 0.4 0:00.00 (sd-pam)
8564 pi 20 0 14520 4412 3468 S 1.8 0.5 0:01.08 sshd: pi@pts/0
8565 pi 20 0 8596 3796 2832 S 0.0 0.4 0:00.16 -bash
9499 root 20 0 784M 4936 2960 S 0.0 0.5 0:21.33 /usr/bin/containerd-shim-runc-v2 -namespace moby -id a2aa4c1a4eac9a739b4f405cac1eda69cd899557a4cec7e2cfd5f53921ba64a8 -address /run/containerd/containerd.sock
11122 root 20 0 788M 10524 7244 S 0.0 1.1 0:01.69 /watchtower --cleanup --include-restarting
11697 root 20 0 783M 1708 760 S 0.0 0.2 0:06.75 /usr/bin/containerd-shim-runc-v2 -namespace moby -id b60c1589b881cd75b345e836a05d475ce5e307c7fb0af8155e9c4c7e19fdb497 -address /run/containerd/containerd.sock
11872 root 20 0 784M 5004 2844 S 0.0 0.5 0:20.52 /usr/bin/containerd-shim-runc-v2 -namespace moby -id ad98edfcb887b6fac64038d3b4871b3d65e628973ee666159e6c0c9c67ccbdad -address /run/containerd/containerd.sock
13840 root 20 0 783M 1240 356 S 0.0 0.1 0:05.18 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 60820bfc3bcd2f9c55e576218660e33022149618e82048e91971edb88bd53633 -address /run/containerd/containerd.sock
21785 root 20 0 783M 1816 748 S 0.0 0.2 0:05.16 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 5a686ae1ebf2401669afd0eb84cd49773ea1f1a6311c050f67e739c6cdfbb223 -address /run/containerd/containerd.sock
23604 systemd-t 20 0 22280 4820 4308 S 0.0 0.5 0:00.33 /lib/systemd/systemd-timesyncd
23605 systemd-t 20 0 22280 4820 4308 S 0.0 0.5 0:00.00 /lib/systemd/systemd-timesyncd
28894 root 20 0 788M 10524 7244 S 0.0 1.1 0:01.58 /watchtower --cleanup --include-restarting
31979 root 20 0 784M 5004 2844 S 0.0 0.5 0:22.02 /usr/bin/containerd-shim-runc-v2 -namespace moby -id ad98edfcb887b6fac64038d3b4871b3d65e628973ee666159e6c0c9c67ccbdad -address /run/containerd/containerd.sock
13678 root 20 0 87832 16256 10028 S 14.0 1.7 0:00.23 /usr/bin/ffmpeg -i http://192.168.1.136:8084 -f image2 -vframes 1 -qscale:v 15 -vf scale=640:-1 pipe:1
F1Help F2Setup F3SearchF4FilterF5Tree F6SortByF7Nice -F8Nice +F9Kill F10Quit
Ok, the Pi doesn’t seem « underwater » though.
On the Gladys side, however, what you’re telling me could be a symptom that Gladys is struggling.
How many cameras do you have? You didn’t say in your previous post What’s the refresh rate?
Cameras are the most resource-intensive thing
I forgot them, I have 5 that refresh every 10 seconds
That might be a bit aggressive every 10 seconds, especially on a Pi 3 — could you switch to a lower frequency? At least for testing
Given that the live exists now, it makes less sense to refresh so often
Ok I’ll do that to test,
I’m waiting for a Raspberry Pi 4 4GB, we’ll see if it will be better. I’ll get back to you
Thanks again for your help
Have a good day
1 Like
good evening @pierre-gilles
that’s it — I switched to an RPI4. Well, apparently no big changes; my Rpi3 must have been working fine with the SSD. However, when running Htop you can clearly see the difference — the Rpi4 handles it much better.
pi@gladys:~ $ htop
0[||||| 3.9%] Tasks: 44, 140 thr; 1 running
1[||||| 3.9%] Load average: 0.26 0.67 0.58
2[||||| 3.9%] Uptime: 00:42:16
3[|||| 3.3%]
Mem[|||||||||||||||||||||||||||||||||||| 428M/3.75G]
Swp[ 0K/100.0M]
However, for Zigbee2mqtt there’s no change — the TB doesn’t work; it doesn’t control any device. But when you go into the device’s expose, the commands work there. The problem comes from zigbee2mqtt, but what?