Replies: 1 comment 1 reply
-
|
Devices rarely update link quality on its own. They send a message and link quality comes as a parameter with that message. Debounce is only for mqtt-level, it's not helpful. So did the rssi reporting help? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have six Perenio smart plugs. They're routers, and I use them as both smart plugs and as a router to extend my network. One problem is that they send a lot of mqtt messages. Each one can update its link quality up to five times per minute. I have six of them, which results in 30 messages that my smart home system registers. How can I reduce the link quality status flow to once per minute (per device)? Ideally, I should set a value (like in reports) to compare against, and whether to notify.
I tried using debounce, but it didn't work (as expected). Setting it to 60 and entering the debounce_ignore state (on/off switch), as well as other required values, resulted in strange behavior when manually toggling the switch (publish prevoius state when current, or prevoius only).
P.S. Used the current dev branch with fixes from perenio reports.
I set threshold values to calm the sockets down.
P.S. 10 minutes later with RSSI config. When I change rssi report to 60 when link quality changed, started coming once a minute.
P.S.S But for some devices, I would like to be able to control frequent link quality updates.
Beta Was this translation helpful? Give feedback.
All reactions