TS0601 / _TZE200_b6wax7g0 - Moes BRT-100 Thermostat

Hi @w35l3y

The driver works, but I am missing some off the available datapoints.

These are the missing datapoints I’ve tested with the generic driver that I know work:

  • Setting Thermostat Mode (Enum 1, 0=Run Program, 1=Manual mode, 2=Temporary manual mode, 3= Holiday mode)
  • Boost Heating (Boolean 4 = On/Off)
  • Child lock (Boolean 13 = Lock/Unlock)
  • Set Thermostaat to Eco Mode (Boolean 106 = On/Off)
  • Set thermostat maximum temperature (Value 108)
  • Set thermostat minimum temperature (Value 109)
  • Feedback of the Valve position (Value 104 = 0-100%)
  • Boost Heating Countdown Value 5) Boost Heating is on Countdown in minutes starting from 5 (300 seconds)
  • boost Heating Countdown Time Set (Value 103) Set Boost Heating countdown timer in Seconds (currently 300, so that matches to the 5 minutes)

These are the datapoint i know they are there, but i don’t now how they work:

  • Reset (Enum 7)
  • Schedule (Raw 101)
  • Window Detection Funktion_A2 (Boolean 8 On/Off) *Turns on/off the “Window detection” when room temp drops below N (5-25°C???) * 00=close/01=open
  • Window Detection (Enum 9 On/Off) I think this is feedback on the “Window detection”
  • Thermostat temperature calibration (Value 105)
  • Set Temperatur Eco mode (Value?? 107) I didn’t see this datapoint, but according to the code on github it should be there to set the eco temperature, I think the value must be multiplied by 10

I’ve tried to understand this code, but I’m not a programmer, maybe you can do a little more with this?


Datapoint Capability Writable Duplicate
Thermostat Mode thermostatMode 0=auto,1=manual,2=?,3=? Yes? No
Boost Heating switch 0=off?,1=on? Yes? Yes
Child lock lock 0=off?,1=on? Yes No
Eco Mode switch 0=off?,1=on? Yes Yes
Maximum temperature thermostatHeatingSetpoint ? Yes Yes
Minimum temperature thermostatHeatingSetpoint ? Yes Yes
Valve position ? No? No?

Other than the first one, ST doesn’t seem to have native capabilities for the other functionalities.
I could add them in the settings, but they wouldn’t be available in automations.
Also, duplicate capabilities would require separate components.

  • Thermostat Mode is writable, so if you put in the value ‘2’ the thermostat will switch to ‘manual’mode
    - 0= auto (It wil run the weekly programming you put in)
    - 1=manual
    - 2=temporary manual, so it wil returns to the weekly programming mode (0) in the next time period.
    after a while
    - 3= holiday mode, I believe it will automatically switchback to 0 after 10 days?

  • Child lock is writable (True/False), if Child lock is true, you cannot use the buttons on the valve to set temp ect

  • Eco Mode is writable (True/False), it will set the thermostat to Eco mode

  • Maximum temperature thermostatHeatingSetpoint, I think it is writable, so you can set the upper temperature limit.

  • Minimum temperature thermostatHeatingSetpoint, I think it is writable, so you can set the lower temperature limit

  • Valve position (%) not writable, it wil give you feedback on the position off the valve. So when the value is 100, it means the valve is fully open (100%)

  • Boost Heating, I think it is writable (True/False) and you can use this function if you want to heat up the room quickly. When you turn on this function countdown timer will start Time Setting (datapoint 103) 100 sec - 900 sec, (default = 300 sec)

They must meet the options available in the native capabilities referenced in the links.
“temporary manual” and “holiday mode” aren’t available options.

Even though boolean are true/false, but they are represented as 1 or 0.
Usually, 0 = false and 1 = true, but it isn’t always true. Confirmation is needed.

Eco Mode and Boost Heating seem to be part of Thermostat Mode

I think when u use the vale in smartthings, you will only use manual mode. The other 3 modes are used when u use the weekly programming. So you can always automaticly write 1 so that you overrule the program.

Boost mode I think is used if you want to quickly heat up a room for x seconds (Countdown timer), so the valve will open more quickly in this mode.

Eco mode can be used to set a lower room temperature. My Nest Thermostat has the same mode

I tested the boolean true/false functions in the generic mode with a switch datapoint

@JDRoberts , could you split into another thread from post #282 until #288, please ?
The subject could be TS0601 / _TZE200_b6wax7g0 - Moes BRT-100



I Found this Standard Status Set on the Tuya IoT Development Platform


I figured out the Temperature compensation Value 105 (-9°C … +9°C)

  • -9°C = Value 4294967287
  • -8°C = Value 4294967288
  • -7°C = Value 4294967289
  • -6°C = Value 4294967290
  • -5°C = Value 4294967291
  • -4°C = Value 4294967292
  • -3°C = Value 4294967293
  • -2°C = Value 4294967294
  • -1°C = Value 4294967295
  • 0°C = Value 0
  • 1°C = Value 1
  • 2°C = Value 2
  • 3°C = Value 3
  • 4°C = Value 4
  • 5°C = Value 5
  • 6°C = Value 6
  • 7°C = Value 7
  • 8°C = Value 8
  • 9°C = Value 9

and Energy saving mode temperature Value 107 (5-35°C)

@w35l3y I’m still trying to figure out how to test this, but I think I need some help. How can i test if a boolean is using 0 and 1? the “switches” datapoint to change the true or false. Is there anny other way to test this wheter it use 0 and 1?

Boolean type always use 0 and 1 internally.

But how can I test how true and false are changed for the boolean datapoints? I don’t understand how i can test this for you

Create a Switch in the settings for each boolean DP. Probably they will be disabled by default.
For example: Switches 4,8,13,106
Modify the settings related to these DPs from the device and take note of changes displayed in the app. It will enable the child in the app.

By default, the driver will interpret 0 as false and 1 as true.
But you may, for example, enable child lock from the device and the app show as disabled/off.
Then you will understand logic is inverted for child lock.

Just to make sure… do you know I have already added this device for the driver, don’t you ?
It’s been there for at least 3 weeks.

I only added 4 capabilities:

  • thermostatHeatingSetpoint (2)
  • temperatureMeasurement (3)
  • thermostatOperatingState (1)
  • battery (14)
1 Like

Hi Wesley, I had indeed seen that you added the device to the driver, but I wanted to check out the other data points for you. I don’t know if it is possible foor you can add it to the driver? Last night I also figured out how datapoint 101 works. I woke up in the middle of the night and I suddenly knew how datapoint 101 works. The “/x” are separators and the two characters after that are Hexadecimal. I have added the explanation of datapoit 101 to the Word document i send you earlier, so I will also send it to you. I’ll see if I can get the boolean addresses figuredout tonight.

\xNN is a way to represent a byte in hexadecimal.
It can be any value from \x00 to \xFF

I would like to know how DP 101 is shown in the app.
Because it is a recent update to display “raw data”
Before the modification, it was showing as “nil”

I may add the DPs that can match with native capabilities.

When the thermostat is turned on for the first time (out off the box), the value of data point 101 is “nil”. Only when I entered a weekly schedule via the buttons on the thermostat, was this value visible. In others, if no weekly schedule is entered, then the value is “nil” once you entered a weekly schedule for the first time, then value of datapoint 101 changes.

Here are some screenshots of how it appears in the app.

1 Like

I have created 4 child switches as you asked, for datapoint 4,8,13,106

Then i have done some tests in this order:

  1. When I look at the datapoints in the app, all 4 child switches in smarthings are “on” if the value of the data point is “true” and “off” if the value of the data point is “false”.
  2. Then I pressed the 4 child switches in the smartthings app, after which the value of datapoint 4,13, and 106 changed from “true” to “false” and vice versa. Datapoint 8 does not change the value, so I cannot operate datapoint 8 from the smartthings app using the child switch.
  3. Via the buttons on the thermostat I turned “boost heating” on and off, so I see the value of data point 4 change from “true” to “false”. I also see the child switch going on and off. Where “true” is on and “false” is off
  4. Via the buttons on the thermostat I turned “windows detection” on and off, so I see the value of data point 8 change from “true” to “false”. But the child switch does not change state. The child is turned “on” by default, but it stays on when the value changes to “false”
  5. Via the buttons on the thermostat I turned “child lock” on and off, so I see the value of data point 13 change from “true” to “false”. I also see the child switch going on and off. Where “true” is on and “false” is off
  6. Via the buttons on the thermostat I turned “child lock” on and off, so I see the value of data point 13 change from “true” to “false”. I also see the child switch going on and off. Where “true” is on and “false” is off
  7. Via the buttons on the thermostat I turned “eco mode” on and off, so I see the value of data point 13 change from “true” to “false”. I also see the child switch going on and off. Where “true” is on and “false” is off

To summarize:
The value of datapoint 4,13,106 can be changed using a child switch. When the child switch is operated, the status of the data point changes from “true” to “false”, where “true” is on and “false” is off. Also if I change the value of datapoint 4,13,106 via the thermostat, the state of child switches will changes to “on” when the value is “true” and “off” when the value if “False”
Datapoint 8 cannot be opperated using the child switch, and also the child switch does not change it’s state when the value of the datapoint is changed from “true” to “false”

1 Like