Temp changing doesn't work #72
Comments
|
I have the same issue on my Kaisai One 18. |
|
Same for my Midea Mission Inverter MB12N8D6WIK. Integration becomes unavailable after changing temperature. At least, with the recent update turnig it on or off as well as getting the current status seems to work more reliably. Here are some DEBUG logs in idle state (when AC is turned off and no command is being sent). I'm willing to provide logs in other circumstances (e.g. when changing temp) in order to improve the integration. |
On my side its going unavailable after turning it on/off for a couple of seconds. And then its back online again. Everything is working like turning it on/off, the fan speed, the choice for heating or cooling. Except the temp change isnt working. |
|
I just saw in HACS that there is a new version/update is out 8.11 with some good fixes. Will give it a try tonight! Thanks |
|
Still the same issue after updating. |
|
I have the same problem, temperature do not change. All other functions work like a charm. Eco mode, very important for me, works perfectly. hvac mode, and fan speed perfect too, power off perfect. Thanks for your effort. |
|
Also same issue here, temperature will not change. All other functions work. |
|
@Jurrjuna @marcoahp @besiktas97 do you have slider to change temperature? If so could you try to modify temperature while having debug logs active and paste logs here? |
|
No I dont have sliders to change the temp. I am using simple thermostat card from HACS. |
|
@nbogojevic In short:
|
|
I'm having the same issue |
|
Same here. Everything else work fine. |
|
Same here, OSK-105, Rotenso Versu AC, v0.8.11 |
|
I'm having the same issue with IDEMA AC |
|
Will there be a fix for this one? Otherwise I need to check for something else after my vacation to let it work. |
|
@peca89 thanks a lot for effort put in obtaining logs. It helped me understand why it works on some models. I've relied on reply from update command packet to read new state, but different models of air conditoners send reply in different formats. However, status query gives always same format, so now I'm re-issuing status query for all air conditioners. I'll do some additional testing to see if I can detect when reply already has known format, but that will be in another version. I'm also checking if I can correctly detect presets. @peca89 @jasniec @vinciee @besiktas97 @DevMig82 @Tijgerd can you try new version. I'd appreciate to get some debug logs if you have any issues. |
|
Thank you for your effort @nbogojevic. 2022-08-24 20:36:24.633 DEBUG (MainThread) [midea_beautiful] Library version=0.9.15 22-08-24 20:30:10.433 DEBUG (SyncWorker_8) [midea_beautiful.lan] From sn=000000P0000000Q130B23749******** id=1869169788**** address=192.168***** version=3, message=b'\x83p\x00@ \x01\x00\x00\xc4\xdf\xaf\x9ao\xce\x7f\xe7!7\xeeL\xb3\xabZ\xd5\x04^\xda\n\xfb\xd1EZM\xa2\xbe\xe2=9\xcf\x00)\xe9a\xac\xea\x08\x9cj\x129\xd6?Xra\x12\xadC\x18\x9a>\xb2\xb1\xcc\x00(\x05\xcb This is what I see when I am trying to change the fan mode: 22-08-24 20:44:12.170 DEBUG (SyncWorker_7) [midea_beautiful.lan] From sn=000000P0000000Q130B23749******** id=1869169788**** address=192.168***** version=3, message=b'\x83p\x00\x8e c\x8c This is what I see when I am trying to change the Preset mode to Sleep mode: 2022-08-24 20:50:50.768 DEBUG (SyncWorker_2) [midea_beautiful.lan] From sn=000000P0000000Q130B23749******** id=1869169788**** address=192.168***** version=3, message=b"\x83p\x00\x8e c\xba\xb6V>/>1\xde\x8e\xa0\x16&\x8b\xbb\x9b\xd1\x15\x1a'mow<\xabU\xd6Ic\n\xbe\xe9Kz\x95\xbd\xc2,2\x8c\xfc\xcbD\xa6=\x08Xi\xb4\xad\x1fq\xea!\xdd\x0e\x08\x96N-0\x06\xab!q\xf1\xbd\xe7\x1d\xa6\x83=J\x91\x00GXW\xef\xa9\x08\r\r\x9f\x0b\xb0*\xeeV?J\xd4\x95\x9d\xef5L\x01d^\xcfF\xc2\x928\xfb\xa8H<3\xf8$\x92\xdf\xe8\xf3/\x04\x8eu\x9bkr\xdd\xf4.\xd7\xb4\x94\x83m(\t\xeeO\x8c\xea\x95.\x83\xa5\x8ez\x0e\x1d" 2022-08-24 21:01:32.545 DEBUG (SyncWorker_8) [midea_beautiful.lan] From sn=000000P0000000Q130B23749******** id=1869169788**** address=192.168***** version=3, message=b'\x83p\x00\x8e c\x96\x0e\xd7\x17V\xe3\xb9\x8cSm\xc2\xafU\xfb\xc6\x1b\x98\x9cKiv\xba\x01\xac\xfe\x04\x94\xa9oG\xa6\xf3\xa9\x0c1\x00\xca\x1d\x04)o\xc9@\xd8p\x81.\n\xd9j\xd0G.7\xef\x19\xca95\x11\x99B\x9f\xfeT\xec\x96\xf4J\xe1\xeb|d\xee\x96\x1e\x1dg\xa6\xaeF_\xf3\x1d\x01]]0s\xe6&\xb9\x90\x82_\xc1`\xdb\xae\xda.\x9d\x0f\x1cQ\xb5T\xab\xc6\x13\xd4\xad\xda\x04\xf4\xad\x15\xfd\x93\xf9\xd2Br\xdb\x87Z\xf3\xb1\xc8+\x87\x8b\xc6\xd7\x1c\xdd/\xb1\x8b]i\xbf\x98\x15' |
|
Hi, thanks for following this issue, in my case, there is no change either. |
Hello, Add those lines to your configuration.yaml file and restart HA. logger: Begging of lines to addlogs: End of lines to addAfter HA has been restart, you need to go with samba share to your config folder and look at the filenam: Home assistant log.txt. In that file you can search for the name that begins with: midea_beautiful. |
|
Just tried to change temp from 20 to 18.5. After 2 sec. it changes back to 20. 2022-08-25 13:40:56.630 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_dehumidifier_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant |
|
Below is the default log what I now see in HA: This error originated from a custom integration. Logger: custom_components.midea_dehumidifier_lan.appliance_coordinator Error fetching Airco gang data: Unable to send data after 5 retries, last error timed out for 000000P0000000Q130B23749******** (1869169788****), will be trying again. |
@nbogojevic Thank you for the new version and your effort. However, the new version works a bit worse than previous :) Run status sporadically changes to false while AC is running steadily. My observations are below: Air conditioner running without any change, but run_status sometimes changes to false for no reason: At 10:09:44 status was reported correctly. At 10:10:00 target temperature was increased from 24 to 25 using remote controller. No immediate change reported, so I guess we need to wait for the next poll interval? At 10:10:44 run status incorrectly reports as false and target temperature also incorrectly reports 16. Next poll interval at 10:11:44 also reports incorrectly, whila the one at 10:12:44 finally updates correctly. At 10.21.04 i tried changing target temperature from 25 to 23 using HA card. It immediately jumped back to 25 and, of course, it did not change on AC. P.S. Local IP address is not obfuscated in discovery process [midea_beautiful.scanner]. I don't have any issues with sharing a private IP, so I have left it as is. |
|
Same issue here with midea airconditioner |
|
For me this issue can be closed. I found a better integration through HACS with more entities and full control of my AC. It works great also setting it up with auto discover is great. |
What is the other integration name |
This is the link to the integration: |
|
I don't think it is OK to close this! We have here put work into fixing this integration, not into resolving OPs problem. We should let the developper decide what to do with this issue. |
|
I may continue to work on the issue if there are people interested in it. The other integration seems to cover quite a number of midea devices and is very interesting for ACs. I propose people vote with up/down on this comment. Up if they want me to continue work on it/down if they think that switching to other integration is better way forward. |
Version of the custom_component
Configuration
Add your logs here.Describe the bug
A clear and concise description of what the bug is.
Every option for the AC is working except changing the temperature.
When I am changing it with HA, the new value isn't send to the AC. But when I change it with the app,
Also when I am changing the temp value with the app (mssmarthome) it doesn't change on HA side.
Debug log
The text was updated successfully, but these errors were encountered: