Duplicate accessories now exist for Climate React #149
Comments
|
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 Otherwise please follow these steps from the release notes:
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. |
|
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): Click to expand Logs: |
|
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. |
|
Finally had the time now over the break to look into this. Re-added the Climate React switches (disable/enabled) and set up again with my automations, but still had issue with Climate React successfully staying on when enabled from Homekit as it would immediately turn off again (Kitchen AC): After checking the Climate React settings as per this screenshot, there was no low temp setting as I was relying on HomeKit automations for heating based on the condition of Climate React switch on. Would be good to have this fixed as a non-requirement, so long as one of the options for cool or heat is enabled under Climate React... but at least now it works. Comparison logs for success: |
|
Thanks for the detailed update @nashw83, if I understand you correctly once you had set a "When temperature goes below" action in the Sensibo app for your Kitchen unit the issue turning on (or off) the Climate React [smart mode] stopped occurring? I'm also looking at your feedback and will see if I can tweak the behaviour within this Homebridge plugin to allow it to still work when only one of Above OR Below is set. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: