Closed skyderman closed 7 months ago
jmcollin78
commented
9 months ago Hello,
Underlying climate climate.152832116552564_climate changed. Event.new_hvac_mode is off
Your underlying climate have turn to off itself. So Vtherm is following this and turns off also. You have to find why the underlying is turning off without request from VTherm: another controller (Scheduler, automation, the device itself, ...)
skyderman
commented
9 months ago Thank you for your return.
I looking for this way.
I just see, if I put 'Heat' on the Vtherm with HA web interface, AC get 'Heat' mode right the way, but If I use API, the vterm turn on "heat", but AC stay "off" ( and so vtherm go Off after few time).
Do you have an idea why set_hvac mode on Vtherm for API doesn't start AC ?
Thank you in advance.
skyderman
commented
9 months ago I find how to reproduce the issue.
If we send, climate/set_hvac_mode and then climate/set_temperature, Vtherm turn on AC, and turn it off. If you add 1 second sleep between the 2 command, it's ok.
Do you need I create a new issue for this or do you need any help for fix ?
jmcollin78
commented
9 months ago Hello @skyderman ,
What is the brand of you AC device ? I will list it as not compatible.
VTherm never turn on and set target temperature at the same time explicitly. It is possible that the command are send with a veryt short delay but it is a race condition and not explicite in the code. I guess this is a consequence of the self-regulation which starts when you turn on the device.
So it is not so easy to add a sleep(1 sec) between the 2 commands. I don't want to degrade the behavior for all users also, but I will have a look of what is possible.
skyderman
commented
9 months ago Hello,
The AC brand is "Airwell", used with integration "Midea AC LAN".
Just for people who have the same problem, timing of 1 sec between 2 orders on the Vtherm seems fix the issue. ( I have only this brand, so I don't know if the issue is only for this brand )
jmcollin78
commented
7 months ago I have added incompatibilty in the README. Thank for the report.
Version of the custom_component 5.4.1
Configuration
My VTherm attributes are the following ( BEFORE ):
AFTER
Describe the bug
Randomly the composant Vtherm, go on OFF mode. If I set on heating, the composant go on off after few second, and sometime stay "on".
It seen it's happen, when I use HA API to set the composant
For It, I use the 2 URL ( 1 to set mode and one for the temperature )
http://URLHA/api/services/climate/set_hvac_mode with Args : {"entity_id":"climate.thermostat_c05","hvac_mode":"heat"}
Then : http://URLHA/api/services/climate/set_temperature
with Args : {"entity_id":"climate.thermostat_c05","temperature":22}
I'm trying to: Use Vtherm, witch stay on, unless I Put manualy on OFF
And I expect: Stay On
To reproduce the issue, I put set thermostat to OFF via API (15h12) , I set to Heat ( via API ), and Set temperature ( via URL ) ( 15h13), after 1 minute, the Vtherm is set to OFF ( 15h14 )
Debug log