Smart Thermostat not showing Temperature or Control

Configuration
1

Hi there,
I am relatively new to Home Aissistant but was able to find workaround or solutions to nearly all of my problems thanks to community entries or youtube tutorials.

There is one problem however I am unable to find a solution for and i hope thta you guys can help me.

I ordered a Hama smart Thermostats Starter Kit (https://de.hama.com/00176592/hama-smartes-heizkoerperthermostat-fuer-hama-heizungssteuerung-wlan).

I configured the Zigbee Gateway with Tuya Smart Home in order to use it within HA using the Tuya integration. I added the thermostat as subddevice and can control it via app. I also added the new devices to my Tuya CLoud projekt to make them available in HA like I did with some smart switches with work perfectly.

I also get a new climate Instance within HA. The Problem is i cannot see the temperatur nor control anything besides turning the device of/on.

image
Within the developer tools i see the following attributes for the entity:

hvac_modes:
  - 'off'
  - heat_cool
min_temp: 7
max_temp: 35
target_temp_step: 1
current_temperature: null
friendly_name: Schlafzimmer
supported_features: 0

In the debug log however i see that the device is sending the correct informations:

 "active_time": 1677599914,
      "biz_type": 18,
      "category": "wk",
      "create_time": 1677599914,
      "icon": "smart/icon/ay1531739836474naEnL/d79f56f3658342ab930bd537cfefe6f8.png",
      "id": "*******",
      "ip": "***",
      "lat": "***",
      "local_key": "***",
      "lon": "***",
      "model": "smart TRV",
      "name": "Schlafzimmer",
      "node_id": "********",
      "online": true,
      "owner_id": "*******",
      "product_id": "h4cgnbzg",
      "product_name": "176592/176593",
      "status": [
        {
          "code": "work_state",
          "value": "standy"
        },
        {
          "code": "window_check",
          "value": true
        },
        {
          "code": "frost",
          "value": true
        },
        {
          "code": "temp_correction",
          "value": 0
        },
        {
          "code": "child_lock",
          "value": true
        },
        {
          "code": "switch",
          "value": true
        },
        {
          "code": "current_temp",
          "value": 192
        },
        {
          "code": "set_temp",
          "value": 180
        },
        {
          "code": "motor_opening",
          "value": 0
        },
        {
          "code": "battery_power",
          "value": 0
        },
        {
          "code": "a_key_home",
          "value": false
        },
        {
          "code": "prog_mode",
          "value": ""
        },
        {
          "code": "prog_switch",
          "value": false
        },
        {
          "code": "prog_data",
          "value": ""
        },

The only thing i noticed is that the device is expecting “set_temp” and delivering “current_temp” while the entity has attributes with “temperatrure”.

I am not sure what I am doing wrong here or what else to try. Or am i facing a bug here? According to the tuya implementation in github the controls should be there if the device is recognized as “wk” which it is.

Thanks in advance

1 Like
2

It probably should work

Try and pair it again?
Perhaps it’s an issue with Tuya?

3

Hi, Thanks for the reply.

I tried reconnecting and also added a second thermostat. Unfortunately the second one has the exact same behaviour. I do not use zigbee2mqqt i use the Tuya gateway and the official Tuya intgertaion within HA. Buying a Zigbee Stick and using mqqt would be another thing I could try. But if there is a possibility to get it running with Tuya integration i would prefer that :slight_smile:

4

Ok also todays update of HA core did not change anything :frowning: are there any more steps i could try?

5

I don’t know. I don’t use Tuya.

6

Hey I have a similar problem with the sensor getting a „null“ value.

Where did you get this log from? Run debug protocol in the Tuya integration?

I’m relative new two HA too. But trying to dig deeper to that problem.