OpenWonderLabs / homebridge-switchbot

The Homebridge SwitchBot plugin allows you to access your SwitchBot Device(s) from HomeKit. Homebridge.
https://openwonderlabs.github.io/homebridge-switchbot/
ISC License
248 stars 54 forks source link

SwitchBot] Bot: Amplifier Device internal error due to device states not synchronized with server, or command format is invalid, statusCode: 190 #1095

Open doogfa opened 1 month ago

doogfa commented 1 month ago

Describe Your Problem

Cannot use switch bot suddelny, any help? statusCode: 190 With the Switchbot app everything works. but getting an error with homekit.

Relevant log output

[26/10/2024, 12:05:33] [SwitchBot] Bot: Amplifier Device internal error due to device states not synchronized with server, or command format is invalid, statusCode: 190

Config for homebridge-switchbot

{
    "name": "SwitchBot",
    "credentials": {
        "token": "sensitive removed",
        "secret": "sensitive removed",
        "notice": "Keep your token a secret!"
    },
    "options": {
        "devices": [
            {
                "configDeviceName": "Amplifier",
                "deviceId": "sensitive removed",
                "configDeviceType": "Bot",
                "connectionType": "OpenAPI",
                "type": "switch",
                "mode": "switch"
            }
        ]
    },
    "_bridge": {
        "username": "sensitive removed",
        "port": 43432
    },
    "platform": "SwitchBot"
}

Screenshots

No response

Device & Model

HUB Plus F4 and SwitchBot V4.8

Node.js Version

v20.18.0

NPM Version

10.9.0

Homebridge Version

v1.8.4

Homebridge SwitchBot Plugin Version

4.62.0

Homebridge Config UI X Plugin Version

4.62.0

Operating System

Windows 10 64bit

doogfa commented 1 month ago

Anyone? :/

doogfa commented 3 weeks ago

Still looking for a solution :/

cattastrophe0 commented 3 weeks ago

I’m seeing this too, I tried to clean up some extra accessories from my cache and now nothing works. I’ve also tried rolling back a few versions and the issue persists.

Update: rolled back even further to 3.8.2 and we’re back in business.

cattastrophe0 commented 3 weeks ago

adding additional information: upgraded to version 4.1.0 after restoring my setup and it working properly on 3.8.2 and the bot became unresponsive again. No error messages in the logs, but that may be because it’s grouped with a bunch of other accessories. It seems like something breaks between 3.8.2 and later versions but it’s hard to tell what without a lot of testing.

doogfa commented 3 weeks ago

Thanks! I've rolled back to v3.5.0 and its working now!

cattastrophe0 commented 3 weeks ago

@doogfa can you change the label on this to bug? i’m going to try to get some extra logs to file a new issue but if it’s happening to both of us there is probably a bigger problem

github-actions[bot] commented 1 week ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

badxhabit commented 3 days ago

I am also getting the issue with my curtains.