-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
BUFFER FULL, does anyone know what's the cause? #26736
Comments
Could you try the fw from Koenkk/Z-Stack-firmware#518 (comment) ? |
Thank you @Koenkk . I downgraded the firmware before your reply to 20221226, I did that about 24 hours ago. I have had no "BUFFER FULL" so far. @Koenkk , There is one thing I found out yesterday. I run this server for a client of mine, and he received this device a few days ago from his energy supplier. I confirmed that it communicates via Zigbee with the energy meter. Could that be related? Is it possible that it might disrupt the network and cause error like that? |
Maybe it could cause interference, but it is hard to judge that. Could you also give |
@Koenkk ,a few updates: |
What happened?
I have the latest HA, latest z2m, latest emqx, Dongle-P with latest FW, updated Debian.
3 days ago I got
failed with status '(0x11: BUFFER_FULL)' (expected '(0x00: SUCCESS)
on all my powered devices (a.k.a. routers) it happened every day since then, yesterday twice.
@Koenkk , do we know what's behind that error. I'm on the latest Z-stack FW for at least 3 months and never had this issue. I did not make any significant changes to my setup recently. Just added one IKEA TRETAKT plug, but there were already 3 before this one, never had issue with TRETAKT's.
I have currently 32 devices connected to coordinator. Is it too much? Is there any way to limit that amount? I can see via map that the most recent TRETAKT is not even directly connected to the dongle, it's just routed.
I'm gonna try tomorrow that 2022 firmware that was suggested in another post, although, it has a mixed feedback... I'd rather find out what the culprit is...
Funny thing is that somehow this affects only powered devices, end-devices remain online, even tho their routers reports to be offline. First time it happened I noticed it after 15 hours, all my 41 powered devices were offline, and all 47 of my end-devices were reporting still online
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.1.3
Adapter firmware version
20240710
Adapter
Sonoff Dongle-P
Setup
Docker installation, Pi
Debug log
No response
The text was updated successfully, but these errors were encountered: