Skip to content
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

Error: client quota exceeded #84

Closed
quartist opened this issue Oct 20, 2020 · 2 comments
Closed

Error: client quota exceeded #84

quartist opened this issue Oct 20, 2020 · 2 comments
Labels

Comments

@quartist
Copy link

Hello,

I have tree yeelight lamps: 2x ceiling lamp, 1x meteorite. Today my ceiling lamp stop working with this error in console:

[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 2 after 400ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: '[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 2 after 400ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 5 after 3200ms.
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed to send cmd 212 after 5 retries.' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 5 after 3200ms.
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed to send cmd 212 after 5 retries.

could you help me to resolve? From Yeelight App all lamps working grate. Meteorite lamp works from HomeBridge and Yeelight app. Only ceiling lamps stops working from HomeBridge.

@vieira
Copy link
Owner

vieira commented Aug 20, 2023

This might happen if you send a lot of commands per minute. It should resolve itself within a minute or so.

From Yeelight WiFi Light Inter-Operation Specification:

Yeelight WiFi smart device support up to 4 simultaneous TCP connections, any further connect attempt will be rejected. For each connection, there is a command message quota, that is 60 commands per minute. There is also a total quota for all the LAN commands: 144 commands per minute (4 × 60 × 60%).

@vieira vieira closed this as completed Aug 20, 2023
vieira added a commit that referenced this issue Aug 22, 2023
When setting brightness or color the bulb must already be on, so we call
setPower before sending the brightness or color command, however
setPower itself should only send the command if the device is not
already on.

Due to a mismatch of types (1 !== true) the command was being sent even
when the bulb was already on.

Can fix #84.
@github-actions
Copy link

🎉 This issue has been resolved in version 2.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants