-
Notifications
You must be signed in to change notification settings - Fork 22
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 many events in Zigbee2MQTT log file for LiXee #194
Comments
Seems known in Zigbee2MQTT: |
This happens after a Zlinky_TIC firmware update or not ? |
Can't tell you, installed Z2M and upgraded directly :( |
could you try to just reboot Z2M or unpair ZLinky then reboot Z2M then re pair |
I have similar problem in zigbee2mqt logs (error logs only): |
Note: Rebooting Z2M does not fix the issue. |
Reboot ing Z2M - re-appairing Lixee does not fix the problem i have on Z2M logs |
Just had a look to my db, it's 16GB 🤯, mostly filled by zlinky. This is what I get:
Any way to debug this? |
Sorry but I don't know why there is a flood. It cannot be provided by ZLinky. |
You're talking about |
I had the same problem, I am at the origin of the 2 posts quoted above (and one new post, maybe not necessary i'll delete him) I was able to work around the problem with these values in Z2M: With these values, I get a poll every 60 seconds (??? why exactly 60 ? Don't know. Sometimes ~50 sec), rarely more but it can happen... I've created another post on this problem to push towards the 0xff66 cluster which is supposed to indicate the poll frequency Hope it can help :) |
Ok sorry it's not exactly the same problem since it's only the indexes that are brought up here, not the values of those indexes as was the case with me. On the other hand, I've just tested a solution given here: #174 (comment) |
Same problem for me in zigbee2mqtt logs ` ` |
New installation, new hardware, same issue.
|
Could someone provide the debug log of this? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
Hi @Koenkk, thanks for jumping in! |
Can you try to increase the polling time? The default is 60 seconds, in the z2m configuration.yaml: devices:
'0x00158d000638db70':
measurement_poll_interval: 600 # <-- add this line, increases polling rate from 60 to 600 seconds |
Hi @Koenkk, my config was set to 61 (already tried to go above default setting) which did not change anything. |
The new configuration with a poll set at 600 is really better. That said I can see that the issue still occurs:
We can see these lines are individual items because link quality changes in the records. |
For me, the only thing working is to set the Poll Interval to 120 / Measurement Poll Chunk to 120 AND Debounce to 30 (the most important for me). With theses data, i have a return each 60 sec, sometimes 30 sec but rarely. |
There are no bug with this module. This module is used with a lot of other plugin and there aren't this issue. |
So, there is a problem with z2mqtt because we have 60 reports every seconds when the parameters are set by default :/ |
As I can see, It's seem to be not the case for all users and I don't know why... But no link with ZLinky firmware. The best is to post this issue in the right place. |
Sorry, but it's the same for me, spam of logs: ` ` Just I want to stop this.. |
Pushed a fix to reduce the spamming, please check with the latest dev. If the issue is still present:
Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Yeah ! Thanks a lot :) |
Hi @Koenkk, just updated my docker image to latest-dev. Will report the result soon. |
I can see occurrences using
|
@tomav can you provide the debug log of 10 minutes? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
Here it is. Look at 09:34:23 |
Next to the |
I don't see flood anymore with value 5 or 10. Sometimes 2 events in the same second, but never more.
I can see multiple occurrences of this error. |
could you try a lower chunk value? e.g. 3 or 4 |
No more error with a value of 4 during the past 8 hours.
|
Great, set the default to 4 now. |
Thanks @Koenkk! |
Hi there, thanks for the LiXee which I found reliable so far and easy to integrate.
I post this message in english in case @Koenkk wants to jump in the conversation.
I have several zigbee devices configured in my Z2M but LiXee is spreading a lot of similar info at the same time as you can see in the following extract:
This happens at every poll, currently configured at 15s.
I don't understand why there are some many lines in a short period of time.
I don't know neither if the problem comes from the LiXee firmware (
4000-0013
) or from Zigbee2MQTT (1.30.4 commit: b2dd21e
).Log level is
info
, changing towarn
removes all lines with payload.Any clue?
Thanks.
The text was updated successfully, but these errors were encountered: