Plugin slows down Homebridge

[ellisvalentiner]

Describe The Bug:

Homebridge logs show this message repeatedly:

This plugin slows down Homebridge. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info

To Reproduce:

Install and configure plugin.

Expected behavior:

The plugin should not slow down Homebridge.

Logs:

[10/2/2023, 3:54:16 PM] [homebridge-sharkiq] This plugin slows down Homebridge. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
[10/2/2023, 3:54:22 PM] [homebridge-sharkiq] This plugin slows down Homebridge. The read handler for the characteristic 'Active' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[10/2/2023, 3:54:28 PM] [homebridge-sharkiq] This plugin slows down Homebridge. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

Plugin Config:

{
    "bridge":
    {
        "name": "Homebridge",
        "username": "<redacted>",
        "port": 51877,
        "pin": "<redacted>"
    },
    "accessories":
    [],
    "platforms":
    [
        {
            "name": "Config",
            "port": 8561,
            "platform": "config"
        },
        {
            "name": "SharkIQ",
            "email": "<redacted>",
            "password": "<redacted>",
            "vacuums":
            [
                "<redacted>",
                "<redacted>"
            ],
            "invertDockedStatus": false,
            "platform": "SharkIQ"
        }
    ]
}

Screenshots:

Environment:

• Plugin Version: 1.0.9
• Homebridge Version: 1.6.1
• Node.js Version: 18.16.0
• NPM Version: 9.5.1
• Operating System: Docker

[Bubba8291]

I haven't had a lot of time to look at it this week, but I think it has to do with the http client that it is using.

[Bubba8291]

Just pushed v1.1.0. It should fix this issue.