Tado Different Modes not Working

03397 commented 3 years ago

The problem

I have successfully integrated Tado with home assistant but I cannot use other modes except cool and heat, For example dry mode, fan only mode do not work inside home assistant but they work just fine inside the Tado app. I have tried the following with the same result

service: climate.set_hvac_mode
target:
  entity_id: climate.kitchen
data:
  hvac_mode: fan_only

Is this an integration issue or something else? Copying the attributes supported:

hvac_modes: off, auto, heat, cool, heat_cool, dry, fan_only min_temp: 10 max_temp: 30 target_temp_step: 1 fan_modes: auto, high, medium, low preset_modes: away, home swing_modes: ON, OFF current_temperature: 27.1 temperature: 27.1 current_humidity: 37 fan_mode: off hvac_action: off preset_mode: home swing_mode: OFF offset_celsius: 0 offset_fahrenheit: 0 friendly_name: Kitchen supported_features: 57

What is version of Home Assistant Core has the issue?

2021.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Tado

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tado/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 3 years ago

Hey there @michaelarnauts, @bdraco, @noltari, mind taking a look at this issue as its been labeled with an integration (tado) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

03397 commented 3 years ago

Just want to add if I start the dry mode from the tado app the home assistant thermostat state is changed accordingly and correctly.

Yippy commented 3 years ago

ezgif-2-5caab0289779

I have this issue, where modes cannot be set, there is not log errors. I've used a custom template to show tado, but the main object using the mode function yet nothing is registered.

[Edit] Gif was too short to show, the full process is now shown.

Updated HASS to 2021.6.5, this use to work several version ago. But I've forgotten to record the last version it worked.

Kall0 commented 3 years ago

I have this issue too. Not apple to set any other modes than "off" or "auto". All the other modes are not working from HA. If set in Tado, they show up correctly in HA. I also was able to change fan speed, but sense updated Tado "remote" those options are now gone.

Kall0 commented 3 years ago

Seems to be same problem kinda like with #45989, but disabling the fallback mode doesn't help.

03397 commented 3 years ago

Just to add a little more to this. I have three devices, the two uses the same remote control for this which is a Daikin compatible and both have this issue. The third one uses a completely different remote and all the modes work just fine. All my three a/cs and the remotes from tado support all these modes in question.

So this issue is related with the device added to tado.

Kall0 commented 3 years ago

Any chance somebody could take a look at this issue? Atm the integration cannot be used, not a huge problem atm, but would be nice to be able to automate stuff when heating season starts.

michaelarnauts commented 3 years ago

This is working fine here. Have you configured multiple blocks for each day? I think this has been described somewhere in this issue or a linked issue.

Kall0 commented 3 years ago

I've tried with multiple blocks on tado, with one block, with fallback enable and disabled. All works good from tado-->HA, but from HA-->tado nothing happens unless it's the "off" or "auto" command. And it all started when I reinstalled the device on tado and it came with more settings than it used to. (horizontal and vertical swing).

03397 commented 3 years ago

Guys see my comments above. This is not related with the blocks but rather with the type of the remote you have configured the ac in the first place.

That is why one of my setup works correctly and the other two not

Kall0 commented 3 years ago

Agree with 03397, and would fit my situation aswell.

michaelarnauts commented 3 years ago

Guys see my comments above. This is not related with the blocks but rather with the type of the remote you have configured the ac in the first place.

That is why one of my setup works correctly and the other two not

I see. I only have a "working" setup, so I can't really help out here.

palazzem commented 3 years ago

I'm currently experiencing the same issue where I can only use [Off, Cool, Auto] modes. I've investigated a bit the issue and I wanted to share the outcome with you all, to understand the difference between a working and not working setup.

Setup: I've cloned the core repository, moving to the latest release (at the time of writing 2021.8.6 tag). Tado integration has been installed and configured. My setup includes multiple heaters and AC. I'm using directly the repo so I can easily tweak the code to triage the problem I'm experiencing.

In my test, I've added an AC entity to the Lovelace UI and used this one to move from an Off state to a Dry state. I changed python-tado code to propagate errors to Home Assistant logs and this is what I get:

2021-08-13 14:30:23 WARNING (SyncWorker_3) [PyTado.interface] {'errors': [{'code': 'setting.notSupported', 'title': 'fan speed not in supported fan speeds [AUTO, HIGH, LOW, MIDDLE]'}]}

I took a look at the code and I figured out that the method used to change the state, sends the fan speed (and swing) only if the temperature is set (code). In this case, Dry and Fan modes don't require the temperature and so HA doesn't pass these values (and it should continue to not pass these values).

At this point I tried a simple snippet to reproduce the problem, by using python-tado library directly (HA is entirely bypassed). With the following snippet, I receive the same error:

from PyTado.interface import Tado
tado = Tado(username, password)
# Zone 8 is the AC used in the HA test above
tado.setZoneOverlay(8, "MANUAL", deviceType="AIR_CONDITIONING", fanSpeed="AUTO", mode="DRY", swing="OFF")

# Returns:
# {'errors': [{'code': 'setting.notSupported', 'title': 'fan speed not in supported fan speeds [AUTO, HIGH, LOW, MIDDLE]'}]}

If I change the code to send swing and fanSpeed regardless of the setTemp value (TL;DR I move them outside of the if clause), it works as expected in the snippet and in Home Assistant.

Here are some of my thoughts:

I don't think HA and Tado integration have an issue here, considering I was capable to make it work by changing the library code.
That said, in this thread, some of you reported that it works well, so I guess (it's an hypothesis that I can't confirm right now) we registered devices with 2 different types. The type that works, has an API that doesn't require to set fan speed and swing to enable all the modes. The type that doesn't work instead, requires such values to be set.
This explains also why Cool or Auto mode works, because temperature is set for both by HA.
There is also a possibility that I'm experiencing a problem totally different from you, but with the same side effect.

I'd like to get some of your thoughts to see if this investigation is misleading, or if you have more details that I'm missing. I'm opening an issue on the library repo because to be honest, I don't know the implication of the change (I'm not sure there are enough tests to verify if it breaks something). Thank you very much for any help or suggestion you may have!

michaelarnauts commented 3 years ago

@palazzem Wow, that's an extensive report. I do remember there was an issue where the fan speed could not be set when the temperature wasn't given, but I couldn't reproduce it myself (since I have a gas boiler, with no fans). I think you should be able to find the related issue on the Home Assistant issue tracker. It's probably from a few years ago though. Maybe some of the involved persons back then know more about it.

palazzem commented 3 years ago

Great, thank you very much for the pointer! I'll check the tracker to find more clues and will update this thread if I discover more stuff.

Thanks again!

Kall0 commented 3 years ago

@palazzem Did you find anything :)

drubens commented 3 years ago

Hi dears, I've a similar issue with TADO AC and I can just activate Scheduled mode or switch off the split. I see that HA update the state when I command split from TADO. No way to use TADO from HA so. Let me know if you need something to investigate. Grazie

ElBalsero commented 3 years ago

Hi all,

I’m having the same issue with my Tado AC units and I think that @palazzem is totally right.

I made some tests to confirm it. Remember that Tado allows two different configurations for your AC units: “Standard” and “Thermostat”.

The standard one tries to bring as many features as possible to your Tado controls. Depending on you AC model and how well integrated it’s with Tado, it will give you heat, cool, ventilator, dehumidification… and so. It will also let you control the fan speed, horizontal and vertical blades position… and so. Of course also temperature. When setting my AC in this mode in the Tado app, all those options appear also in HA. However, only Off and Program options work. Any other choice just does nothing. Probably due to the issue found by @palazzem where Tado expects to receive the fan speed.

If I configure that very same AC unit in Tado as “Thermostat”, the Tado really simplifies the configuration. The only available options in Tado app and HA will then be “Heat”, “Cool” and temperature. No possibility to control anything else. In this case the integration works. But of course only in this very limited way.

Could someone please have a look and make sure that when all options are available HA sends all the information required by Tado?

Regards,

Daniel

J-Rod-16 commented 2 years ago

Hi, just wanted to share that I was having similar issues with air conditioner control - status was updating but HA could only use auto or off. I setup my tado device again in the tado app as thermostat with only cool/heat/off modes and now it works in HA. Not perfect but better than before and sufficient for my needs. Regards Jarrad

J-Rod-16 commented 2 years ago

Forgot to mention above - one weird thing for my install is that it takes about 15 seconds for a "cool" command to go from HA or the tado app to the device where the air con beeps and turns on. Turning A/C off is instantaneous. I thought it wasn't working at first so anyone trying this method should be patient. HA shows "idle" in this 15 sec period and then changes to "cooling" Regards Jarrad

Kall0 commented 2 years ago

Changed to Sensibo, works great 😅

J-Rod-16 commented 2 years ago

Changed to Sensibo, works great 😅

Yeah I looked at that one too but my wife is terrible with technology so I wanted one with controls on the device itself, which the tado does have.

MacrosorcH commented 2 years ago

@michaelarnauts Hi, any chance to have the issue fixed or is Sensibo the only chance to have a fully working AC control in HA? 😅 I'd love to stay with Tado but the broken HA integration is a deal-breaker.

michaelarnauts commented 2 years ago

@michaelarnauts Hi, any chance to have the issue fixed or is Sensibo the only chance to have a fully working AC control in HA? 😅 I'd love to stay with Tado but the broken HA integration is a deal-breaker.

I have very little free time, and this integration isn't high on my priority list I'm afraid. If the (for your usecase) broken integration in Home Assistant really is a deal-breaker for you, I think you should switch services or learn to code yourself :)

I don't want to be a jerk or something, just trying to give correct expectations.

bdraco commented 2 years ago

If you are using IR control Sensibo (cloud) or lookin (local) will likely be a better experience

MacrosorcH commented 2 years ago

@michaelarnauts Hi, any chance to have the issue fixed or is Sensibo the only chance to have a fully working AC control in HA? 😅 I'd love to stay with Tado but the broken HA integration is a deal-breaker.

I have very little free time, and this integration isn't high on my priority list I'm afraid. If the (for your usecase) broken integration in Home Assistant really is a deal-breaker for you, I think you should switch services or learn to code yourself :)

I don't want to be a jerk or something, just trying to give correct expectations.

Got it, thanks for taking the time to reply.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

03397 commented 2 years ago

Issue still there

ElBalsero commented 2 years ago

This has not been fixed at all

El El mié, 6 jul 2022 a las 9:00, 03397 @.***> escribió:

Issue still there

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/51062#issuecomment-1175854334, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG3G2EUIMMD3SXW4VOC6Q6TVSUVJVANCNFSM45PA66MQ . You are receiving this because you commented.Message ID: @.***>

ghost commented 2 years ago

Still not fixed :-( Gimme at least a workaround :-(

toedtling commented 1 year ago

still not fixed :)

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

03397 commented 1 year ago

Issue still exists for fan speed and swing.

drubens commented 1 year ago

On HA into virtual machine and tado AC smart controll all is working. I'm really impressed. Thanks a lot everyone. Only heat/cool mode is not working but heat and cool separated, are working sweetly. Dry and fan and schedule as well.

Home Assistant 2023.2.5 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230202.0 - latest

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

03397 commented 1 year ago

Issue still exists for fan speed and swing. Please guys at least a workaround.

ElBalsero commented 1 year ago

It is partially solved. The airco can now be switched on an off in different modes. Yet to be done:

Set duration
Set fan speed
Set swing mode

290989 commented 1 year ago

It would be a big comfort win to get the choose of fan speed & swing.

Would it be possible to implement?

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

03397 commented 1 year ago

Still there

issue-triage-workflows[bot] commented 11 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

03397 commented 11 months ago

Still there

issue-triage-workflows[bot] commented 8 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ElBalsero commented 8 months ago

No. Unfortunately this is not yet working

issue-triage-workflows[bot] commented 5 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core