Me again 
I’m now trying to use the Zigbee part with Sonoff sensors and a Sonoff bridge as well. No problem installing the USB stick and configuring what’s needed. But then I notice that all services are running but the link is red:
What should I do in this case? The « Allow pairing » button in « Zigbee discovery » is not functional.
Thanks in advance 
As I recall:
Error: Error
at Database.<anonymous> (/src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:179:27)
at /src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:177:50
at new Promise (<anonymous>)
at Query.run (/src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:177:12)
at /src/server/node_modules/sequelize/lib/sequelize.js:314:28
at async SQLiteQueryInterface.bulkDelete (/src/server/node_modules/sequelize/lib/dialects/abstract/query-interface.js:403:12)
at async /src/server/lib/device/device.calculcateAggregateChildProcess.js:142:7 {
name: 'SequelizeTimeoutError',
parent: [Error: SQLITE_BUSY: database is locked] {
errno: 5,
code: 'SQLITE_BUSY',
sql: "DELETE FROM `t_device_feature_state_aggregate` WHERE `type` = 'hourly' AND `device_feature_id` = '4c919947-e87e-49b6-8bbe-48f65f1751f4' AND `created_at` BETWEEN '2023-02-10 14:00:00.000 +00:00' AND '2023-02-10 16:00:00.000 +00:00'"
},
original: [Error: SQLITE_BUSY: database is locked] {
errno: 5,
code: 'SQLITE_BUSY',
sql: "DELETE FROM `t_device_feature_state_aggregate` WHERE `type` = 'hourly' AND `device_feature_id` = '4c919947-e87e-49b6-8bbe-48f65f1751f4' AND `created_at` BETWEEN '2023-02-10 14:00:00.000 +00:00' AND '2023-02-10 16:00:00.000 +00:00'"
},
sql: "DELETE FROM `t_device_feature_state_aggregate` WHERE `type` = 'hourly' AND `device_feature_id` = '4c919947-e87e-49b6-8bbe-48f65f1751f4' AND `created_at` BETWEEN '2023-02-10 14:00:00.000 +00:00' AND '2023-02-10 16:00:00.000 +00:00'",
parameters: {}
}
Is it related?
For Gladys’ logs, I have this:
2023-02-11T10:06:42+0100 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2023-02-11T10:06:42+0100 <info> checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates...
2023-02-11T10:06:42+0100 <info> installMqttContainer.js:98 (Zigbee2mqttManager.installMqttContainer) MQTT broker is starting...
2023-02-11T10:06:47+0100 <info> installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2023-02-11T10:06:47+0100 <info> installZ2mContainer.js:56 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2023-02-11T10:06:47+0100 <info> installZ2mContainer.js:69 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2023-02-11T10:06:53+0100 <info> installZ2mContainer.js:75 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2023-02-11T10:06:53+0100 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2023-02-11T10:06:53+0100 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2023-02-11T10:06:53+0100 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
I don’t see anything abnormal… 
I realize that the problem is somewhat widespread via this thread: Zigbee2mqtt : Error SYS - Ping after 6000ms au démarrage - #161 par guim31
I have the same issue and I don’t see any solution…
I’m using the memory card and a Sonoff. No power issues.
So I don’t know what to do… If you have any ideas?
I tried this: Zigbee2mqtt : Error SYS - Ping after 6000ms au démarrage - #127 par Tlse-vins
But it doesn’t change anything at all
Hello,
I have a Sonoff ZBDongle-E (EFR32MG21) dongle and I
A thousand thanks @qleg! It works for me too! In any case, it no longer restarts endlessly and I have the V instead of the X.
@pierre-gilles: perhaps it would be worth adding this to the documentation? For those who, like me, don’t have power supply issues.
It’s in the zigbee2mqtt documentation
There are several Sonoff dongles ( with different chips)
Silly question, but how can I tell if I have the -E or -P dongle?
It’s noted below: Zigbee Model P
Absolutely, I’d even go so far as to say: could it be automatic? Or if it’s not automatic, could we add a dropdown in the UI so that the user can select their key?
@AlexTrovato What do you think?
I think that if we want it to be simple for users, we absolutely must do it!!!
(Are we indeed talking about doing the special z2m configuration according to the Zigbee USB stick?)
Yes, that’s it! Do you think it’s possible to detect the key, or is it better to add a dropdown and have the user select their key?
Whatever happens, I’ll add a dropdown that the user can use to choose, but I’ll still try to preselect the key if it’s possible to detect its model from the USB inputs.
Can we consider running a test automatically? If that doesn’t work, a ‹ detect key type › button:
Does it change the value, restart the container and verify that it sees Zigbee devices? Some kind of test in the application
Alternatively, a dropdown could also work — you change the value and it triggers a proper restart
I just prefer a dropdown
I’ve had the same issue since Friday with the Sonoff dongle, I just saw this thread. I’ll try it tonight to confirm that it also resolves the problem for me.
EDIT : Adding « adapter: ezsp » works well to restore communication with Z2M for the Sonoff-E dongle
I think we really need to add this information to the documentation to start with 
FYI I started the dev for the specific configuration depending on the dongle… well, it’s not ready yet!
I’ve added this information to the documentation while waiting for it to be available in Gladys
The PR:
The site:
@Kevin I don’t know if you’re a bit of a dev, feel free to make changes directly in the doc if you see possible improvements, everything is open-source and editable by everyone
