-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automation turning on Climate React changes Climate React configuration #148
Comments
Hi @mkrexp What automation are you running? Is it as simple as turning on the ClimateReact switch? Do you have the (new) ClimateReact Auto Setup turned on? If you are only switching ClimateReact on (or off) via Home app automation then I would expect it to not change the settings configured in the Sensibo app as you expect, however the new Auto Setup mode does “copy” your current settings. |
Hi,
my automations are very simple - has turn on or off climate react switch.
Both (turn on or off) override my setup.
Auto setup for climate react is turned off because it overrides my setup,
so I have turned it off.
W dniu wt., 30.07.2024 o 00:51 Ben ***@***.***> napisał(a):
… Hi @mkrexp <https://github.com/mkrexp>
What automation are you running? Is it as simple as turning on the
ClimateReact switch?
Do you have the (new) ClimateReact Auto Setup turned on?
If you are only switching ClimateReact on (or off) via Home app automation
then I would expect it to not change the settings configured in the Sensibo
app as you expect, however the new Auto Setup mode does “copy” your current
settings.
—
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6QYV5WD2R3HJCEE6Y23BCLZO3BNLAVCNFSM6AAAAABLUT6QOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGE2DEMBWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for the reply @mkrexp Do you have the Light switch enabled in your settings for this plugin? By the feel of it I think 'defaults' are being used by Sensibo... so if Light isn't set/sent by Home app / Homebridge Sensibo must default it to On. Similarly for Swing, Apple Home app doesn't support modes other than On / Off, so your setting of 'Fixed top' is being overwritten by the default of 'Stopped (auto)'. Please let me know your thoughts on this, will help direct further investigations (and any potential fix/changes). |
Thanks for the reply @benwebbbenwebb I have the light switch enabled in plugin config. I have asked Sensibo Support if they change anything in climate react settings and they do not change anything. Before updating from 2.3.4 to 2.5.1, configuration was not overwritten by described automation or when I turned climate react from home app, so I thought something is wrong with plugin, not Sensibo. |
Thanks @mkrexp Agree that it sounds logical for it to be the plugin, I’ll take another look at the code changes. Would you be able to toggle the light switch a few times, and then change it to your desired setting for ClimateReact (I think Off?) and see if turning on ClimateReact via Home still changes the desired Light setting? With the Swing mode, that one is going to be harder… Apple don’t support fixed swing positions (like Fixed top) so we don’t expose it. Will need to think about how best to achieve your desired outcome, but still allow others to setup and modify the ClimateReact settings via Home app (rather than having to use Sensibo app). |
Toggling light switch works as turning on/off AC but without turning it on or off, rather like 'settings switcher' - light is turned on/off but swing is also changed. For example, I have AC turned on with light on and swing set to fixed top. After toggle light switch in Home app, on my AC I have light switched to off and swing is changed to 'stopped (auto)'. In logs available in Sensibo app I can see entry 'API call API call(Michal) set the swing to stopped (auto)'. After next toggle of light switch in Sensibo app logs I can see entry 'API call API call API call(Michal) kept state on'. Maybe you should send only dedicated commands (i.e. 'turn climate react on') without any other parameters? I don't know if Sensibo API allows it, but I suppose that was done in version I used before updating to 2.5.1. It's very frustrating that I can configure automation for turning on features (like climate react) but I have to remember change climate react settings to my preferences simultaneously |
Thanks again @mkrexp for the added info Hi @seidnerj Specifically sending the whole ClimateReact object when enabling (or disabling). As Homebridge/Home app don’t support multiple swing positions the new implementation is overwriting the swing (and light?) setting… Would appreciate your thoughts on the best way to proceed @seidnerj. |
Sure, I'll fix that. Will update. |
Hey guys, I'm not sure when I'll get to this, I'm swamped at the moment, will work on this when I can. Sorry! |
My automation is configured to automatically turn on climate react at 10:00 PM. When automation is turning on Climate React , Climate React setup is changed automatically ('AC Light' and 'Swing').
My configuration before automation runs is shown below:
After automation runs configuration is changed as presented below:
The text was updated successfully, but these errors were encountered: