Zigbee2mqtt: Error SYS - Ping after 6000ms on startup

Thank you Leader,

I will follow your advice and the link you provided. Do I also need to restart the entire procedure, from the SD card to flashing the SSD?

I noted that this is a separate issue from Gladys. As I mentioned at the beginning, I only have Zigbee devices, so my dashboard is empty; I cannot test the system’s features.

What I still see from your 3 responses is that you all have an SSD connected directly to the Pi in addition to the Zigbee USB key.

The Zigbee2mqtt documentation clearly states about the « Ping after 6000ms » error:

If using a Raspberry Pi; this problem can occur if you are using a bad power supply or when other USB devices are connected directly to the Pi (especially occurs with external SSD), try connecting other USB devices through a powered USB hub.

If you want to be sure, several options:

  • Try reinstalling without an SSD (with a micro-SD) just to test and verify that your Zigbee USB key is working properly.
  • Try an SSD installation, but connect the Zigbee dongle to a powered external USB hub.

PS: No need to call me « leader », Pierre-Gilles is fine :stuck_out_tongue:

I will opt for connecting the dongle to a powered hub and will test it on Wednesday.

For Domadoo’s response, you were right, pierre-gilles:
"If the issue comes from the MQTT library and not the product, we cannot guarantee its proper functioning as only the developers of this library will be able to implement a fix.

Therefore, if you wish to cancel, please go to retour.domadoo.com."

The MQTT library is not at fault, as @pierre-gilles I suspect a power supply issue (as indicated in the zigbee2mqtt FAQ)

I have an SSD connected to the Pi and a hub with the Zigbee key. And when I plug it in like this, Gladys becomes inaccessible.

docker logs gladys

:wink:

Impossible, I can’t see the Pi on my network anymore, it’s inaccessible.

What kind of USB hub are you using?
Mine is this one but it’s buggy.

Primewire - 4-Port Active USB 3.0 Hub, USB 3.2 Gen.1 Powered USB Hub Multiport USB Dock – 4 in 1 Hub for PC Laptop Notebook Ultrabook MacBook, SuperSpeed up to 5 Gbps - Aluminum - Plug & Play Primewire - Hub 4 Ports USB 3.0 Actif, USB 3.2 Gen.1, alimenté multiprise Dock – Hub 4 en 1 pour PC Laptop Notbook Ultrabook MacBook, SuperSpeed jusqu'à 5 Gbps - Aluminium - Plug & Play : Amazon.fr: Informatique

Another attempt.
New install on SD just by connecting the Zigbee key.

Here are the logs


And still an under voltage detected

I thought I had it,
I connected the Sonoff key to the powered hub and swapped the other USB connections (keyboard-mouse, SSD) on the pi but to no avail.
Here’s what I get when I run docker logs gladys … :

Good night

Sorry, but there is little information besides the logs of the same error, so we cannot do anything.

Which hub, which power supply? I have the impression that you have a keyboard/mouse/screen on your Pi? Unplug everything except the Zigbee key.

dmesg | grep -iC 3 "under-voltage detected"

This will tell us if it’s still a power supply issue.

Here is the result of the command

Good evening,
Regarding the hardware, I use:
Atolla Hub USB 3.0 powered, 4-Port USB Hub power strip with individual on/off switches - Power adapter included

SanDisk SSD Plus 240GB SATA III Internal 2.5" SSD up to 530MB/s

WAVLINK External Hard Drive Enclosure 2.5" for 2.5" SATA SSD hard drive 9.5 or 7 mm, tool-free mounting, UASP acceleration

A raspberry 3 with power supply model DSM-0530 5V 3A

I notice the same error as TIse-vins for the voltage:

When I run the command docker logs gladys, the scrolling stops on a date/time that does not match the current time.

Thank you

Would this solve our problems?

@pierre-gilles could this help?

You can try just the conf part

User rights are not affected in docker environment

For the news.
I changed the power supply and I no longer have under-voltage detected
That’s done.

On the other hand, I added

And here is the result:

So in fact you need to use GENERATE and not GENERATED
But it still doesn’t work.

However, I just noticed that there is a 2-hour difference between the SSH logs and the current time.
Could that be the issue?

I’ll try without the option, you have a proper power supply, it’s worth trying and checking the logs

Same as @Psoy, I don’t know what to do anymore.
I put everything back to its original state in the configuration file, and the logs are identical.

I just added a USB extension, it’s the same.
I changed the USB port on the Pi, it’s the same.
I changed the USB port in the configuration file, it’s the same.

I read all the Zigbee documentation and checked everything (well, I think so)

Will changing the Zigbee key make a difference? I don’t think so because it’s the same with Sonoff devices.

edit: the container restarts every 30 seconds.

Good evening @Tlse-vins
I no longer have the Zigbee2Mqtt problem, but I completely reinstalled Gladys, with the new 64-bit version,