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: Request failed with status code 429 #29

Open
TomKrysz opened this issue Jan 26, 2022 · 1 comment
Open

Error: Request failed with status code 429 #29

TomKrysz opened this issue Jan 26, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@TomKrysz
Copy link

After update to version 1.4.16 I noticed that plugin performs TAPO flloding at port 80 and all L510E stopped working (visible but not reachable). After downgrade to 1.4.15 all back to normal.

To Reproduce: This occurs every time I restarted HomeBridge.

Expected behavior:

Logs:
[25/01/2022, 05:35:13] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[25/01/2022, 05:35:13] [Tapo Smart Platform] 371 Error: Request failed with status code 429
[25/01/2022, 05:35:13] [Tapo Smart Platform] 371 Error: read ECONNRESET
[25/01/2022, 05:35:13] [Tapo Smart Platform] 371 Error: read ECONNRESET

Plugin Config:

"platforms": [
    {
        "name": "Tapo Smart Platform",
        "username": ,
        "password": ,
        "platform": "TapoP100",
        "devices": [
            {
                "name": "Bulb 1",
                "host": "10.1.2.X",
                "type": "Bulb",
                "updateInterval": 30,
                "timeout": 5
            },
            {
                "name": "Bulb 2",
                "host": "10.1.2.X",
                "type": "Bulb",
                "updateInterval": 30,
                "timeout": 5
            },
            {
                "name": "Bulb 3",
                "host": "10.1.2.X",
                "type": "Bulb",
                "updateInterval": 30,
                "timeout": 5
            },
            {
                "name": "Bulb 4",
                "host": "10.1.2.X",
                "type": "Bulb",
                "updateInterval": 30,
                "timeout": 5
            },
            {
                "name": "Smart Plug 1",
                "host": "10.1.2.X",
                "type": "Plug",
                "updateInterval": 30
                "timeout": 5            },
            {
                "name": "Smart Plug 2",
                "host": "10.1.2.X",
                "type": "Plug",
                "updateInterval": 30
                 "timeout": 5
           },
            {
                "name": "Smart Plug 3",
                "host": "10.1.2.X",
                "type": "Plug",
                "updateInterval": 30
                "timeout": 5
            },
        ]
    }    
]

Screenshots:

Environment:

  • Plugin Version: 1.4.16
  • Homebridge Version: 1.4.0
  • Node.js Version: 16.13.2
  • NPM Version: 8.3.0
  • Operating System: Debian 11 (bullseye)
@TomKrysz TomKrysz added the bug Something isn't working label Jan 26, 2022
@TomKrysz
Copy link
Author

TomKrysz commented Apr 5, 2022

Versions 16 and 17 beta, still with bug 449. Status requests seem to overlap with timeouted reconnections, resulting in tcp L510 flooding and connection dropping. Several hours after restarting HB, four L510s are plagued by several dozen connections per second, which generates error 449 (checked in router logs). Please do something about it, as plugins from version 16 on are useless as they are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant