Moes thermostat TS0601 - (_TZE200_ye5jkfsb) showing incorrect room temperature

[welo78]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

Hello, it seems that a Moes electric heating thermostat has two issues.

1. Temperature is incorrectly displayed as 0 Celsius (or wrongly parsed/calculated) or 2 degrees when temperature is 22 in the room
2. Home assistant picks it up as increments of 0,5 degree when it can only make 1 degree steps

Thermostat in question: https://www.aliexpress.com/item/1005005963529004.html?spm=a2g0o.order_list.order_list_main.11.406c1802Nirlz9

Steps to reproduce the behavior

1. Log into Conbee gateway
2. Check thermostat tab
3. Thermostat showing incorrect temperature

Expected behavior

1. Display correct room temperature
2. Make increments of 1 degree step instead of 0,5 in home assistant (can be fixed in HA)

Screenshots

Environment

• Host system: Raspberry Pi 4
• Running method: Raspbian + Home Assistent deCONZ Add-on
• Firmware version:26400500
• deCONZ version: 2.28.1
• Device: RaspBee I
• Is there any other USB or serial devices connected to the host system? If so: Z-Wave dongle

deCONZ Logs

2024-11-27 09:51:39.666 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"id":"23","lastannounced":null,"lastseen":"2024-11-27T08:50Z","manufacturername":"_TZE200_ye5jkfsb","mode":1,"modelid":"TS0601","name":"Thermostat 23","swversion":"1.0.1","type":"ZHAThermostat","uniqueid":"58:3b:c2:ff:fe:90:22:8b-01-ef00"},"e":"changed","id":"23","r":"sensors","t":"event","uniqueid":"58:3b:c2:ff:fe:90:22:8b-01-ef00"}
2024-11-27 09:51:40.797 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"id":"23","lastannounced":null,"lastseen":"2024-11-27T08:51Z","manufacturername":"_TZE200_ye5jkfsb","mode":1,"modelid":"TS0601","name":"Thermostat 23","swversion":"1.0.1","type":"ZHAThermostat","uniqueid":"58:3b:c2:ff:fe:90:22:8b-01-ef00"},"e":"changed","id":"23","r":"sensors","t":"event","uniqueid":"58:3b:c2:ff:fe:90:22:8b-01-ef00"}

Additional context

I am all up for testing any DDF if this is a unsupported device at the moment. However as it picked it up I kinda thought it is supported.

[Smanar]

Perhaps Koenkk/zigbee2mqtt#11980 ?

But it seem working for somes users, but not all.

We can try editing the DDF devices\moes\Moes_TZE200_ztvwu4nk_thermostat.json
How many TRV have you ? because editing direclty this file will impact ALL yours devices using the same DDF

And can you check the value returned by your device ?

It's visible on logs in Deconz/help/Debug view, I think the flag "DDF" will be enought to see the value used by the device.

[welo78]

Hello @Smanar thank you for the reply. I added the debug message to the original post.

I have 1 of this device for testing purposes. I am looking for swapping non-smart thermostat for zigbee operated.

As for DDF when I enabled debug view and ticked DDF it started dumping all kinds of DDFs it knows in a long list. Will this suffice?

[Smanar]

Yes it's the good DDF, but I m sure wich one formulea to use, the code is here

        {
          "name": "state/temperature",
          "parse": {"fn": "tuya", "dpid": 24, "eval": "Item.val = Attr.val * 10;"},
          "read": {"fn": "none"}
        },

But need to see wich one value your device is sending.
Go on deconz/help/Debug view, with flag "DDF", and heat the device with your hand, you will see something usefull on logs about "dpid 24".
It 's more precise with flag "info" and "info_l2" but more talkative, not sure you will see the line.