-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too much wake per seconde #7004
Comments
Interesting finding, this might come from nodeserial package. Can you describe your setup? OS / Serial device (uart/usb)? |
Hi,
Debian 10 on raspberry 4 8Gio
All installation was done on the OS (no VM, no docker).
Combee2 mounted on a usb port. Pi connected via wire cable.
A harddisk is mounted on a other usb port
Le ven. 9 avr. 2021 à 05:07, John Doe ***@***.***> a écrit :
… Interesting finding, this might come from nodeserial package.
Can you describe your setup? OS / Serial device (uart/usb)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7004 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQ3GTSA2HZLMOC4AOE3APTTHZVOHANCNFSM42TZVLEA>
.
|
Can you please provide zigbee-herdsman debug logs from the startup of z2mqtt. https://www.zigbee2mqtt.io/information/debug.html |
Hi @ChrisHae , sorry for the delay ...
|
I think the cause is too fast time intervals for checking internal queues. This came with the new "adapter_delay" option in the configuration.yaml in z2mqtt v1.18.0. setting a delay value between 10 and 60 will reduce the cpu load. configuration.yaml:
But I just noticed the value is not passed correctly. So I uploaded a fix to zigbee-herdsman. i think it will be soon in the latest z2mqtt dev-branch version. https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html |
Great, i will happy to test the Dev branch, please notify me when this change will be in the branch. so i will test. Regards |
Will be in the dev branch in 1 hours from now. |
Build and use the dev branch is working as expected. |
Same here |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened
After the service start and in a idle state , zigbee2mqtt wake up too much time per second
It's visible via 2 kind of command :
arround 250 to 300 events/sec
for comparaison, mosquitto : 5 events/sec and home assistant less than 10 events/sec
on the log file, it's content like 3000 clock_gettime per second( like
clock_gettime(CLOCK_MONOTONIC, {tv_sec=125521, tv_nsec=997610561}) = 0
exact number can be found via :
grep -c clock_gettime /tmp/1
then divise by 10 (for 10 second)What did you expect to happen
it's should not wake-up so often or need to change how it's working ?
How to reproduce it (minimal and precise)
Debug info
Zigbee2MQTT version: 1.18.2
Adapter hardware: Conbee II
Adapter firmware version: lasted available : deCONZ_ConBeeII_0x26680700.bin.GCF : release the 30-Nov-2020
The text was updated successfully, but these errors were encountered: