homebridge-switchbot: Bot stops working after latest plugin update
Describe Your Problem
Bot says “pressing” in HomeKit but doesn’t move. There is no response in Homebridge log. I also updated the Switchbot firmware which may contribute to the issue. However, even with the new firmware v2.14.0 of the plugin works as expected.
Relevant log output
After updating to v4.0.0 Switchbot stops responding. When I press the appropriate button in the Home app to activate the bot there is no response.
Config for homebridge-switchbot
{
"name": "SwitchBot",
"credentials": {
"token": "correct token",
"secret": "correct secret",
"notice": "Keep your Token & Secret a secret!"
},
"options": {
"devices": [
{
"deviceId": "64E833E4BE64",
"configDeviceName": "SwitchBot Hub 2",
"configDeviceType": "Hub 2",
"lock": {
"activate_latchbutton": false
},
"history": true,
"firmware": "1.5-1.0",
"refreshRate": 360
},
{
"deviceId": "D2353334687D",
"configDeviceName": "SwitchBot Bot",
"configDeviceType": "Bot",
"connectionType": "OpenAPI",
"bot": {
"mode": "press",
"deviceType": "door",
"allowPush": true,
"doublePress": 1
},
"lock": {
"activate_latchbutton": false
},
"firmware": "6.6",
"refreshRate": 360,
"external": false
}
],
"refreshRate": 360
},
"_bridge": {
"username": "0E:60:3D:E2:5A:D4",
"port": 34884
},
"platform": "SwitchBot"
}
Screenshots
nothing to show because there is no response in the logs after activation. This is what got looks like in 2.14. [1/31/2024, 3:46:43 PM] [SwitchBot] Bot: SwitchBot Bot Set TargetPosition: 100 [1/31/2024, 3:46:55 PM] [SwitchBot] Bot: SwitchBot Bot Set TargetPosition: 0 [1/31/2024, 3:53:54 PM] [BathR Heater Timer] Setting switch to false [1/31/2024, 3:55:30 PM] [SwitchBot] Bot: SwitchBot Bot Set TargetPosition: 100
Device & Model
Hub 2 and Bot
Node.js Version
v18.19.0
NPM Version
v??
Homebridge Version
v1.7.0
Homebridge SwitchBot Plugin Version
v3.0.0.
Homebridge Config UI X Plugin Version
v4.55.1
Operating System
Docker
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 16
Fixed with v3.1.0