Replies: 5 comments
-
Hello, to my knowledge most of the HVAC devices always sent all codes together. So as in original codebase, first on, then setting mode. Was you HVAC ON, when you tried to set fan mode? If not, do you think, that sending only fan mode code would also set your unit on? I am just preparing PR to handle situation with any missing code more graceful. I can include changes for your case. |
Beta Was this translation helpful? Give feedback.
-
Not yet solving double beep, but this is little bit reordered your original code for fan only mode , without requirements for target temperature and with checking of the codes:
|
Beta Was this translation helpful? Give feedback.
-
@litinoveweedle Thanks for your time and attention. I will test this later today and will report back. |
Beta Was this translation helpful? Give feedback.
-
Ok, based on what I just learned here #PR 1200 it seems that on/off bit can be set in any IR code, and then you do not need explicitly first send HVAC on (first beep) and then set mode, fan and temperature (second beep). This is BTW the way, how it was done in the original code SmartIR:
I did modified my previous example, which had anyway duplicate check there. For your test please remove dedicated 'on' code from your device codes file. Please be aware, than you have to have 'on' bit set in all other codes to make this work coherently. ;-) I corrected and also reformatted whole code, to make it more obvious, as I missed the this intentions with 'on' command as well at first:
|
Beta Was this translation helpful? Give feedback.
-
Hi, I merged proposed change into my fork and I will release it soon. You can test it and report back. |
Beta Was this translation helpful? Give feedback.
-
Hi!
I have a couple of Midea AC's, custom profile. All is working properly, but I noticed an error message in HA for when I was enabling fan only mode. It was complaining about target_temperature.
Looking at the code I understood that for fan_only mode it was expected to have temperature values, which I don't have in my profile. Are temperature values really affecting the operation of fan_only mode?!?
I've hacked the climate.py code a bit to not send target_temperature if operating_mode = fan_only, which works just fine, but I get now a double beep from the AC. I guess it is related to the "on" command and the "fan_only" command. Any way I can skip that?
Beta Was this translation helpful? Give feedback.
All reactions