Open nashw83 opened 1 month ago
Hi @nashw83
Sorry for the trouble!
Have you restarted Homebridge (or host computer) since the plugin was updated? Some previously cached accessories/services may only get removed on restart. Also, have you recently made any changes to the options in your settings, such as climateReactSwitchInAccessory
, since the upgrade?
Otherwise please follow these steps from the release notes:
Note: If you experience any issues with controls or switches appearing twice, or not working as expected, try temporarily disabling that control or switch via settings.json in Homebridge, save and restart Homebridge, and then finally re-enable the control or switch.
Unfortunately, this may mean you need to rename and/or re-add the switch to any automations but it's probably the easiest way to clean up the duplicate.
Please let me know how you go.
Thanks for the quick reply, definitely restarted Homebridge and the host OS recently and haven’t touched the option. Rebooted just now again and still same result. I’ll give the option off then on again a go soon, will just want to add a dummy switch to the scenes/automations first so that I can track to add them back - so may be a couple of days before I can get to this.
Removed the Climate React option and re-added, however now when it is switched on from HomeKit it switches back off again shortly after.
Seems to work ok when enabled/disabled from Sensibo app, but takes a moment.
Logs (turn on Bedroom AC Climate React accessory from Home app):
Hi @nashw83
Thanks for the logs, looks like there is an error when the plugin is trying to turn on the smartMode (Climate React), specifically when creating the API payload.
I think it's due to the two values below being null...
{
"enabled": false,
"type": "temperature",
"deviceUid": "9z4HxdVi",
"lowTemperatureThreshold": null, // this
"highTemperatureThreshold": 26,
"lowTemperatureState": null, // and this
"highTemperatureState": {
"on": true,
"targetTemperature": 25,
"temperatureUnit": "C",
"mode": "cool",
"fanLevel": "auto",
"swing": "rangeFull",
"horizontalSwing": "stopped"
},
"lowTemperatureWebhook": null,
"highTemperatureWebhook": null,
"sync_with_ac_power": false
}
Can you please share a screenshot of the 'Climate React' settings within your Sensibo app?
Also, while in there, if you set the "When temperature goes below" section (and save it) that could fix the issue in Homebridge / Home app.
Please let me know how you go.
Two Sensibo Sky units connected via Homebridge, which have been renamed as Climate Control and displayed as a fan so that they are displayed under Climate area of Home app. However recently I’ve noticed that there is now a duplicate of this switch, one as a fan and one as a switch, both with the same name. When enabling Climate React the Switch accessory is enabled, however the automations and scenes are linked to the Fan accessory. Switches work independently.
Sensibo for Homebridge v2.5.1 Homebridge v1.8.4 Node.js v20.15.1