'Allow association' for zigbee2mqtt no longer activates

Configuration
1

Greetings to all !

I think it’s all in the title.

I just received some new Zigbee gear so I can’t wait to test it! And bam… the pairing doesn’t stay active. I click the dongle and a few seconds later, after refreshing, it is disabled without any action on my part.

Does anyone else observe the same behavior?

For info I hadn’t tried adding a device for at least 3 versions… so I can’t say whether the problem is recent!

2

Have you tried checking on the Zigbee2mqtt side?

3

Trying again just now without having changed anything in particular, normal behavior returned…

I therefore think it’s a hardware issue. Having had quite a few problems with the Raspberry Pi in the past, I have, in chronological order:

  • moved Gladys to an SSD, making sure to add an appropriate power supply
  • decided to invest in a mini PC…
  • in the meantime used a VM on my Freebox Delta
  • since it was working rather well I postponed buying the mini PC
  • then again there were latencies in actions and access problems with the interface that was churning… anyway!
  • I found a refurbished Fujitsu i5 / 8GB mini PC not too expensive and it’s arriving tonight!

So I hope this will make Gladys run smoothly and efficiently!

To be continued

2 Likes
4

Ok, keep us posted — normally Gladys is pretty smooth; it’s not normal to have slowdowns!

5

By the way, what Linux distro do you recommend?

Not too much of a pain to install (especially when it comes to Wi‑Fi and Bluetooth support…).

I’m only planning to run Gladys, no need for a screen…

Thanks in advance…

6

Ubuntu server :slight_smile:

2 Likes
7

thank you @pierre-gilles

8

I’m on a Fedora server administered via Cockpit (also available on Ubuntu) with regular backups using Timeshift. It works perfectly.

Note: it’s Fedora, so there are many updates. Cockpit can be configured to install only security fixes during the distribution’s lifecycle (a Fedora release is supported for 1 year, which may be restrictive for our use).

9

hello just to help you a bit in case
I had problems too, Alex Trovato helped me

try the commands below if it’s not already done

force a full configuration: docker rm gladys-z2m-zigbee2mqtt

docker restart: docker restart gladys-z2m-zigbee2mqtt
USB test: sudo dmesg
docker restart gladys
docker stop gladys-z2m-mqtt

logs gladys-z2m-zigbee2mqtt

10

I got motivated this weekend to install this mini-PC with Ubuntu Server 22.04!

First problem encountered, the small Wi‑Fi dongle provided with the PC was not supported!

  • searching for Realtek drivers
  • modifying the config file …

Ok I have a connection!

  • I install Gladys following the Docker tutorial
  • everything goes well
  • access from the browser OK
  • Gladys connection + backup restoration OK

About an hour later everything crashed! no access to Gladys anymore, SSH doesn’t respond
Shutting down with a short press of the machine’s button doesn’t work

  • I try a long press, and it restarts

Still no access…

11

Ah!

Do you have any logs to see what’s going wrong?

12

Unfortunately not

I can’t access anything anymore

I feel like nothing is restarting anymore

13

Are you installing anything else on the machine besides Gladys? Because I can accept that Gladys might be down, but for it to completely wreck the OS seems weird to me!

14

No, no other installs/services… I really wanted to have only Gladys on the machine
To keep it tidy.

15

The Dashboard has just reappeared after a hard restart.

16

and logically PuTTY manages to connect

17

Try to get Gladys’ logs

18

Not being

19 
docker logs gladys --tail=1000

(You replace « 1000 » with the number of lines you want to retrieve)

1 Like
20 
2023-07-24T12:12:51+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature indicator_mode not configured in Gladys.
2023-07-24T12:12:51+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature power_outage_memory not configured in Gladys.
2023-07-24T12:13:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.che                                                                                     ckCalendarTriggers) Checking calendar triggers at Mon, 24 Jul 2023 10:13:00 GMT
2023-07-24T12:13:50+0200 <info> lan-manager.scan.js:19 (LANManager.scan) LANManager                                                                                      starts scanning devices...
2023-07-24T12:14:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.che                                                                                     ckCalendarTriggers) Checking calendar triggers at Mon, 24 Jul 2023 10:14:00 GMT
2023-07-24T12:14:10+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c13823dbf93057, feature indicator_mode not configured in Gladys.
2023-07-24T12:14:10+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c13823dbf93057, feature power_outage_memory not configured in Gladys.
2023-07-24T12:14:10+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c13823dbf93057, feature indicator_mode not configured in Gladys.
2023-07-24T12:14:10+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c13823dbf93057, feature power_outage_memory not configured in Gladys.
2023-07-24T12:14:21+0200 <error> lan-manager.scan.js:49 (NmapScan.onError) LANManag                                                                                     er fails to discover devices over network - Illegal netmask in "192.168.0.0/254". A                                                                                     ssuming /32 (one host)

2023-07-24T12:14:21+0200 <info> lan-manager.stop.js:12 (LANManager.stop) LANManager                                                                                      stops scanning devices
2023-07-24T12:14:30+0200 <info> index.js:28 (Object.stop) Stopping LAN Manager serv                                                                                     ice
2023-07-24T12:14:55+0200 <info> index.js:28 (Object.stop) Stopping Tuya service
2023-07-24T12:15:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.che                                                                                     ckCalendarTriggers) Checking calendar triggers at Mon, 24 Jul 2023 10:15:00 GMT
2023-07-24T12:15:08+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<ano                                                                                     nymous>) device.calculateAggregate: Finishing processing for interval monthly
2023-07-24T12:15:14+0200 <info> index.js:28 (Object.stop) Stopping eWeLink service
2023-07-24T12:15:32+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update not configured in Gladys.
2023-07-24T12:15:32+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update_available not configured in Gladys.
2023-07-24T12:15:32+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update not configured in Gladys.
2023-07-24T12:15:32+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update_available not configured in Gladys.
2023-07-24T12:15:34+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update not configured in Gladys.
2023-07-24T12:15:34+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update_available not configured in Gladys.
2023-07-24T12:15:34+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update not configured in Gladys.
2023-07-24T12:15:34+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0026b75683, feature update_available not configured in Gladys.
2023-07-24T12:15:37+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0023527ca4, feature color_mode not configured in Gladys.
2023-07-24T12:15:38+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0x00                                                                                     124b0023527ca4, feature color_mode not configured in Gladys.
2023-07-24T12:15:50+0200 <info> lan-manager.scan.js:19 (LANManager.scan) LANManager                                                                                      starts scanning devices...
2023-07-24T12:15:55+0200 <error> lan-manager.scan.js:49 (NmapScan.onError) LANManag                                                                                     er fails to discover devices over network - Illegal netmask in "192.168.0.0/254". A                                                                                     ssuming /32 (one host)

2023-07-24T12:15:55+0200 <info> lan-manager.stop.js:12 (LANManager.stop) LANManager                                                                                      stops scanning devices
2023-07-24T12:16:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.che                                                                                     ckCalendarTriggers) Checking calendar triggers at Mon, 24 Jul 2023 10:16:00 GMT
2023-07-24T12:16:08+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature indicator_mode not configured in Gladys.
2023-07-24T12:16:08+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature power_outage_memory not configured in Gladys.
2023-07-24T12:16:08+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature indicator_mode not configured in Gladys.
2023-07-24T12:16:08+0200 <warn> handleMqttMessage.js:106 () Zigbee2mqtt device 0xa4                                                                                     c138720bd5bffb, feature power_outage_memory not configured in Gladys.
2023-07-24T12:16:24+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<ano                                                                                     nymous>) device.calculateAggregate: Finishing processing for interval monthly