Core: Problems with Tuya Heater (Eurom Alutherm 2000 WiFi)

Created on 23 Sep 2019  路  19Comments  路  Source: home-assistant/core

I am having a few issues using a Tuya Heater (Eurom Alutherm 2000 WiFi) in Home Assistant and over Google Home (via Nabu Casa).

Issue 1
The only operation mode in Home Assistant is Off while there obviously is also "heat".
https://i.imgur.com/I9Jmu2D.png

Issue 2
Service climate.turn_on does not work, at all.
Service climate.turn_off toggles the device between on and off instead of just turning it off.

Issue 3
Device is not controllable using Nabu Casa. Yes I did the integration correctly.
This is also the screen even when it is on.
https://i.imgur.com/yqqG9zV.jpg

Home Assistant 0.97.0 running in Docker.
Has never worked before for me.

Thank you all in advance!

tuya

Most helpful comment

Issue still persists in 0.111.4... We've advanced 14 versions now

All 19 comments

Just wanted to update that this is still the case in 0.100.2

I have the 1500 Watt version of the same heater and I can confirm all your problems exist for that model as well; the action mode having only Off and the on/off services not working. This used to work several version ago (0.93 is the last I remember but I might be of a couple).

Also, the room temperature has never showed up, always shows as N/A (while the Tuya app does show it).

Hello, I bought 2000W version, today. HA version 0.100.3. Connected trough smart_life platform.

In Loverance I can see only mode off, too.
I can turn on/off heater calling service climate.set_hvac_mode with hvac_mode: heat or hvac_mode: off.
Setting temperature with climate.set_temperature works.

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Just updated to version 0.105.4 and the issue is definitely still there.

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Anyone found a solution to this? I've been experiencing this issue with a tuya heater that only presents "off" as a mode. Thanks

Yeah the issue definitely persists, just updated to 0.109.6 and I still can't select any other mode than "off" and climate.turn_off still toggles it.
Still not controllable through Google Assistant at all.

How long has this been happening for you? I wonder if homebridge integration would be experiencing the same problem.

How long has this been happening for you? I wonder if homebridge integration would be experiencing the same problem.

It's never worked before, but I did set up an automation that gets triggered by an Input Boolean so I can forcefully turn it off.

- id: '9864654891654'
  alias: 'Turn off nick_climate_heater'
  trigger:
  - platform: state
    entity_id: input_boolean.turn_off_nick_climate_heater
    to: 'on'
  condition:
  - condition: state
    entity_id: climate.nick_climate_heater
    state: unknown
  action:
  - data:
      entity_id: climate.nick_climate_heater
    service: climate.turn_off

Any update on this issue? Heaters/coolers that are added with Tuya to Home Assistant don't show any HVAC modes only off. With the summer coming cooling is one of the most important automations

No. I still think it doesnt work. As I wanted it more for homekit, I ended up getting the specific device ID and using it with homebridge. It appears to talk directly to the device, rather than through Tuya's cloud/account. I'm guessing theres some sort of custom add on for home assistant to use this device ID. This is the homebridge plugin and directions I used: https://github.com/AMoo-Miki/homebridge-tuya-lan

Issue still persists in 0.111.4... We've advanced 14 versions now

I have the same issue with a heater from another brand

I used a homemade patch: D
I used simple-thermostat.js and set 2 different colors blue off red on so I know when it's on

I used a homemade patch: D
I used simple-thermostat.js and set 2 different colors blue off red on so I know when it's on

--st-mode-background:#f21200
--paper-item-icon-color,#44739e

Still have the same issue with ikohs IK-EU 2000W wifi! Integrated in Home Assistant via Tuya Integration by Smart Life App. And the same issue like mentioned before.

I think the issue not being fixed might have something to do with nobody who owns one of those heaters offering a pull request to get it to work :)

I can't make any promises yet, but I just bought one of those heaters and can't wait to hack it :)

Actually there's a fix since last updates. I can now see the auto mode and works fine and also can turn off without that toggle weird situation.
Nice improves!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aweb-01 picture aweb-01  路  3Comments

sogeniusio picture sogeniusio  路  3Comments

neonandu picture neonandu  路  3Comments

MartinHjelmare picture MartinHjelmare  路  3Comments

i-am-shodan picture i-am-shodan  路  3Comments