Air Conditioner Temp is one degree off #148
Comments
mill1000
added
bug
|
Can you enable debug logs and post them here? |
|
Not totally sure if I enabled logging correctly or not. I added this to my configuration.yaml Im not seeing a lot of output from midea_ac. All Im seeing is this on startup: and I can see the fetches:
|
|
You can turn it on from the integration page in Home Assistant. I find that easier. Here's the full configuration you'll need for the YAML |
|
Gotcha. I see the more robust logging now. Here's a snippet of it. I'm not sure if any of this will be helpful though. Is there something specific you're looking for in the logs? Aside from the issue I posted about the integration works fine so I wouldn't expect to see any errors. I actually have two of these ACs and they both do it. It was happening before I paired the second one too. They're the .89 and .37 IPs |
|
I did more testing and found the "problem" temp is 63. If the temp is 64 or higher the AC and the integration show the same temp. When I lower temp on the integration from 64 to 63 the AC temp actually lowers from 64 to 62. The integration still says 63. So it's only a problem at 63 degrees and under. Still pretty weird |
|
Thanks for that additional detail. Temperatures below 17 C (approx 62-63 F) are handled by a different section of code. So it's possible there's a latent bug. |
|
Could you provide 2 logs, one when set to 64, the other when set to 63? |
|
Sure. Here is the log going from 64 to 63 using the integration. This is where it actually sets the AC temp from 64 to 62, which causes the mismatch. And heres the log going from 63 to 64 which fixes the mismatch |
|
Ok. Thanks.
In this log the target temperature is 17 C (62.6 F)
In this log the target temperatures is 18 C (64.4 F) In these logs you haven't set the temperature low enough to enable the "alternate" temperature bits (< 17 C). I'm wondering if there's an issue with how the fractional term (.5 degree C) is being handled. Can you post the full logs? I need to see the commands we're sending to determine if the correct fractional temperature information is present. |
|
Hi, the climate is like this at Fahrenheit degrees :( It depends on which device rounds from what. Especially if you have an air conditioner that can't be set to whole degrees in Celsius. Midea didn't explain this well because it specifically converts every Fahrenheit value to Celsius, sets it, and then converts this Celsius value back to Fahrenheit for feedback. Check for any oddities at higher Fahrenheit values as well, if this is the issue: |
|
Don't know if this will help because it is in java for another program, but I had issues setting some temperatures in F degrees. This fixed it; The temperature is in C, but was converted from a whole number degrees F like the table above. So 63 f =17.22*2 = 34/2 = 17 masked the last 4 are 0001 & 34/2 is an even 17, so no 0.5 (00000001) which is actually 62.6 F. 62 is going to 16.5 and 64 is going to be 18 |
|
Similar logic is applied here midea-ac-py/custom_components/midea_ac/climate.py Lines 297 to 298 in 3666189 |
|
I only commented to help on the issue and used 63 F because that was mentioned. The issue is likely that the calc is coming up with 17.5 which is 63.5 and is getting rounded to 64. My example gets 17 which is 62.6 that rounds to 63 (and that's what my device sets to with the IR). I think it is the dot calculation that needs to be checked. Also I was hoping you would see my question on the LED. Thanks for that. I'll close that one |
Pretty much what the title says. My midea air conditioner is set to 60 degrees but the integration is saying it's set to 61. If I set it to 62 it reports 61.
It's a midea u shape ac.
The text was updated successfully, but these errors were encountered: