[Zigbee] Software change in thermometer TY0201 (RSH-HS03)

@GUTEK@ 1335 4

TL;DR

Ty0201/RSH-HS03 Zigbee thermometer with Tuya factory firmware was reflashed over OTA to pvvx ZigbeeTLc.
The update used Zigbee2MQTT's manual file selection, with 1141-0203-10923001-ZTY0201z_v0134.zigbee for the first OTA and the button held to stop sleep.
The stock firmware had very short range, 30-minute temperature updates, and 800 mAh batteries lasting just over six months.
After reconfiguration, Z2M detected temperature, humidity, and battery level, but advanced ZigbeeTLc settings were still unsupported.

Generated by the language model.

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Report a violation of the law

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

» | Topic author Helpful post? (+9)

Helpful post
Post #1
21845614 22 Feb 2026 11:49

Hello,
in this topic I will present a software change via OTA in a Zigbee thermometer. Why am I changing this software over at all? Well, while it is very cool in appearance, has a display and is powered by two AAA batteries, unfortunately the factory software is an example of how softwares should not be written for Zigbee.

So:
- Very short range - the device in practice needs to be a few metres from the Zigbee router. Placing it in another room often results in a loss of connection (changing the firmware here won't help - such is the design).
- Temperature update every 30 minutes - regardless of whether the temperature changes or not.
- Possibility to manually refresh at the press of a button, but... the button simultaneously switches between °C/°F units.
- Rapid battery drain - 800 mAh rechargeable batteries last just over six months.

What is the model, anyway?
Well, take your pick:
- TZ3000_bjawzodf
- TS0201
- RSH-HS03 (printed on board)
- TY0201
Such markings can be found regarding this thermometer, while the manufacturer does not seem to acknowledge this, simply Tuya.

The device comes in two versions, of course it may be sold in some other version in a while.
- the first contains only the Zigbee ZTU module with the TLSR8258 chip - and this can be reprogrammed easily via OTA
- the second one has an additional MRT08S (SO-8) chip, which does not know what it does - if you have this version, you have to solder this chip and make jumpers in place of the missing resistors R2 and R3 (in the version without the additional chip these resistors are there and are 0Ω). This is shown here: https://pvvx.github.io/TY0201_TZ3000_bjawzodf/

I had version one, so I didn't have to do anything.
Only to be safe I made a copy of the original software. This isn't necessary of course, but as the alternative software has only just been released I preferred to be able to revert to the original should the need arise.
To do this I used https://github.com/pvvx/TlsrComSwireWriter and a USB-COM adapter on a CP1202 chip. I made a couple of copies and compared if I was sure the contents matched.

Ok, it's now time to do the update. I'm changing the firmware to the ZigbeeTlc version written by pvvx, just this month this thermometer model started to be supported by them https://pvvx.github.io/TY0201_TZ3000_bjawzodf/
Admittedly the version released is still marked as beta, but it fully supports this model.
Also a couple of weeks ago there was a major change to the OTA support module in Zigbee2MQTT. The ability to manually select the file to be updated has been added. So you don't have to fiddle with creating the relevant configuration files to specify the right file. Simply download it to disk and select it in the browser window.

This is the list of versions of this firmware from pvvx. The relevant file should be downloaded from the bin directory on github: https://github.com/pvvx/ZigbeeTLc/tree/master/bin
There are 3 versions:
- 1141-0203-10923001-ZTY0201z_v0134.zigbee - the first one is the one to use in this case, it is used to perform an OTA update from the original firmware
- 1141-0230-01343001-ZTY0201.zigbee - the second one is the one to use for OTA updates when ZigbeTlc is already installed on the device
- ZTY0201_v0134.bin - the third is a traditional binary for programmer uploads

Ok, so I specified this file, the update seemingly started and an error occurred, timeout. From what I read on github https://github.com/pvvx/ZigbeeTLc/issues/107
It is the case with this thermometer that you have to press the button on the case all the time during the update (for about 15min of the update!), so that this one doesn't go to sleep. Another example of how the factory software is messed up.
Well, nothing, after those several minutes of clicking, the update reached 100% and the thermometer reset. Now we had to click on the Z2M in the device tab "Reconfiguration" to have it redetected.
And here's where another glitch, it turns out that the device is unsupported. Not really surprising, after all this software has only just been released and presumably with one of the next Z2M updates support will be added.
At the moment, however, I don't have any settings available, and there are quite a few in this firmware, such as calibrating the display - both on the display and via Zigbee, setting the update frequency or disabling the display.
Fortunately, the basic Z2M item detected, namely temperature, humidity and battery level.

It remains to test how this firmware will perform. I think it should sensationally because I already use it in the Xiaomi LYWSD03MMC thermometer ( https://pvvx.github.io/ATC_MiThermometer/ ), this tiny model, also with a display is powered by a CR2032 battery and has worked for me on it for over a year!
Below you can see what settings are available for the ZigbeeTlc firmware and a diagram of the CR2032 battery in the thermometer - here the beginning is unfortunately missing because I changed the name of the thermometer, but it has been running since January 2025.

Cool? Ranking DIY
About Author
@GUTEK@ @GUTEK@

Level 31
Offline

Joined: 29 Apr 2005

Posts: 1558

Help: 163

Posts rating: 365

Points: 3165
@GUTEK@ wrote 1558 posts with rating 365, helped 163 times. Live in city Gliwice. Been with us since 2005 year.
ADVERTISEMENT
#2 21845993 22 Feb 2026 18:18

krzbor krzbor

Level 29

» | Helpful post? (0)

Post #2
21845993 22 Feb 2026 18:18

Very interesting article. I am using OTA on my Z2M, but an upgrade from the manufacturer. This is where I have a question - don't the manufacturers of Zigbee devices sign off their upgrades? I was surprised that you can upload your own/alternative firmware.
ADVERTISEMENT
#3 21846033 22 Feb 2026 18:55

gulson gulson

System Administrator

» | Helpful post? (0)

Post #3
21846033 22 Feb 2026 18:55

Super! You've removed a problem that was bothering me terribly - constant battery changes. I myself didn't know why in the opening sensor the small battery lasts 2 years, and in this thing a change of AAA every six months.
ADVERTISEMENT
#4 21846098 22 Feb 2026 20:22

@GUTEK@ @GUTEK@

Level 31

» | Topic author Helpful post? (0)

Post #4
21846098 22 Feb 2026 20:22

>>21845993 Yes some people sign firmware, but this is hardly the case for cheap Chinese devices under Tuya. Certainly Sonoff has its updates signed and here, to first change the firmware to alternative ones you need to use a programmer. This is the case with miniswitches from them. However, even if the firmware is protected then with this option on the Z2M it will be easy to revert to an older version if any manufacturer's update proves to be faulty.
Probably something more on this could be said by @p.kaczmarek2

>>21846033 Whether it will be better with power management is yet to be tested. I will be able to say more in a few months. I hope that yes, it will be better. There is additionally some kind of inverter there - probably to power this BL55072 screen driver, because its minimum voltage is 2.5V. And it too can drain the battery.

#5 21847740 24 Feb 2026 19:54

@GUTEK@ @GUTEK@

Level 31

Post #5

21847740 24 Feb 2026 19:54

I made up the configuration under this thermometer and pvvx software. I don't know if it is correct, but it works. You can turn off the display, change the update frequency, calibrate the temperature and humidity - these calibrations also apply to the displayed values.
In the directory with the Z2M configuration (i.e. where you have the configuration.yaml file) you need to create an additional directory "external_converters" and in it "jakisplik.js" with this content:

const {Zcl} = require("zigbee-herdsman");
const m = require("zigbee-herdsman-converters/lib/modernExtend");

const gutek_zcl = {
    enableDisplay: m.binary({
        name: "enable_display",
        valueOn: [true, 0],
        valueOff: [false, 1],
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0106, type: Zcl.DataType.ENUM8},
        description: "Whether to enable the device display.",
    }),
    temperatureDisplayMode: m.enumLookup({
        name: "temperature_display_mode",
        lookup: {celsius: 0, fahrenheit: 1},
        cluster: "hvacUserInterfaceCfg",
        attribute: "tempDisplayMode",
        description: "The unit of the temperature displayed on the device screen.",
    }),
    comfortSmiley: m.binary({
        name: "comfort_smiley",
        valueOn: [true, 0],
        valueOff: [false, 1],
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0002, type: Zcl.DataType.ENUM8},
        description: "Whether to show a comfort indicator on the device screen.",
    }),
    comfortTemperatureMin: m.numeric({
        name: "comfort_temperature_min",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0102, type: Zcl.DataType.INT16},
        description: "Minimum temperature that is considered comfortable (default 20.00°C).",
        unit: "°C",
        valueMin: -50.0,
        valueMax: 120.0,
        valueStep: 0.01,
        scale: 100,
    }),
    comfortTemperatureMax: m.numeric({
        name: "comfort_temperature_max",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0103, type: Zcl.DataType.INT16},
        description: "Maximum temperature that is considered comfortable (default 25.00°C).",
        unit: "°C",
        valueMin: -50.0,
        valueMax: 120.0,
        valueStep: 0.01,
        scale: 100,
    }),
    comfortHumidityMin: m.numeric({
        name: "comfort_humidity_min",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0104, type: Zcl.DataType.UINT16},
        description: "Minimum relative humidity that is considered comfortable (default 40.00%)",
        unit: "%",
        valueMin: 0,
        valueMax: 100,
        scale: 100,
    }),
    comfortHumidityMax: m.numeric({
        name: "comfort_humidity_max",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0105, type: Zcl.DataType.UINT16},
        description: "Maximum relative humidity that is considered comfortable (default 60.00%).",
        unit: "%",
        valueMin: 0,
        valueMax: 100,
        scale: 100,
    }),
    temperatureCalibration: m.numeric({
        name: "temperature_calibration",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0100, type: Zcl.DataType.INT16},
        description: "Offset to add/subtract to the reported temperature (default 0°C).",
        unit: "°C",
        valueMin: -50.0,
        valueMax: 50.0,
        valueStep: 0.01,
        scale: 100,
    }),
    humidityCalibration: m.numeric({
        name: "humidity_calibration",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0101, type: Zcl.DataType.INT16},
        description: "Offset to add/subtract to the reported relative humidity (default 0%).",
        unit: "%",
        valueMin: -50.0,
        valueMax: 50.0,
        valueStep: 0.01,
        scale: 100,
    }),
    measurementInterval: m.numeric({
        name: "measurement_interval",
        cluster: "hvacUserInterfaceCfg",
        attribute: {ID: 0x0107, type: Zcl.DataType.UINT8},
        description: "Configure sensor measurement interval (default 10 seconds).",
        unit: "s",
        valueMin: 3,
        valueMax: 255,
    }),
};

module.exports = [
    {
        zigbeeModel: ["TY0201-z"],
        model: "TS0201",
        vendor: "Tuya",
        description: "Temperature and Humidity Monitor (pvvx/ZigbeeTLc)",
        extend: [
            m.temperature({reporting: {min: "10_SECONDS", max: "1_HOUR", change: 10}}),
            m.humidity(),
            gutek_zcl.enableDisplay,
            gutek_zcl.temperatureDisplayMode,
            gutek_zcl.temperatureCalibration,
            gutek_zcl.humidityCalibration,
            gutek_zcl.measurementInterval,
            m.battery({
                voltage: true,
            }),
        ],
        ota: true,
    },
];

EDIT: a small fix to display the device icon correctly and the original batch ripped.

Attachments:

TY0201_org_fw.zip (87.91 KB) You must be logged in to download this attachment.

Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Report a violation of the law

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Guides
/
[Zigbee] Software change in thermometer TY0201 (RSH-HS03)

FAQ

TL;DR: Flash the TY0201/TZ3000 (RSH‑HS03) over-the-air with pvvx ZigbeeTLc to fix 30‑minute default reporting; during OTA, "press the button for about 15 minutes" to stop sleep. Expect temp/humidity/battery in Z2M and add an external converter for full settings. [Elektroda, @GUTEK@, post #21845614]

Why it matters: This FAQ shows how to stabilise updates, reduce battery churn, and expose pro features on a low-cost Tuya Zigbee thermometer for Home Assistant/Zigbee2MQTT users.

Quick Facts

Model aliases: TZ3000_bjawzodf / TS0201 / RSH‑HS03 (PCB) / TY0201; Tuya-branded, display, 2×AAA cells. [Elektroda, @GUTEK@, post #21845614]
Two hardware variants: TLSR8258‑only (OTA-ready) and a version with MRT08S requiring chip removal and R2/R3 0Ω jumpers for reflash. [Elektroda, @GUTEK@, post #21845614]
pvvx firmware files: 1141‑0203‑10923001‑ZTY0201z_v0134.zigbee (stock→ZigbeeTLc OTA), 1141‑0230‑01343001‑ZTY0201.zigbee (OTA→OTA), ZTY0201_v0134.bin (programmer). [Elektroda, @GUTEK@, post #21845614]
OTA tip: keep the front button held throughout the ~15‑minute transfer to prevent sleep timeouts. [Elektroda, @GUTEK@, post #21845614]
After flash: Z2M exposes temperature, humidity, and battery; add an external_converter to enable display, calibration, and measurement‑interval controls (3–255 s; default 10 s). [Elektroda, @GUTEK@, post #21847740]

What is Tuya?

Tuya is an IoT platform vendor that supplies white‑label smart‑home hardware and firmware, enabling brands to ship low‑cost devices quickly, often under multiple model aliases. [Elektroda, @GUTEK@, post #21845614]

What is Zigbee2MQTT (Z2M)?

Zigbee2MQTT is a gateway software that connects Zigbee devices to MQTT brokers, allowing Home Assistant and other clients to control and monitor sensors with flexible OTA and converter support. [Elektroda, @GUTEK@, post #21845614]

What is OTA firmware update?

OTA firmware update is a wireless upgrade method that transfers a new firmware image to a device via its Zigbee radio, avoiding physical programmers while preserving network pairing. [Elektroda, @GUTEK@, post #21845614]

What is the TLSR8258?

TLSR8258 is a Telink SoC for 2.4 GHz radios that integrates a microcontroller and Zigbee stack support, enabling compact, low‑power sensor designs like the TY0201. [Elektroda, @GUTEK@, post #21845614]

What is an external converter in Z2M?

An external converter is a JavaScript module that extends device support in Z2M by mapping custom clusters and attributes to user‑friendly settings without modifying core Z2M code. [Elektroda, @GUTEK@, post #21847740]

How do I flash the TY0201/TZ3000 thermometer over OTA?

Use Z2M’s manual file selection with 1141‑0203‑10923001‑ZTY0201z_v0134.zigbee. Hold the device button during the ~15‑minute transfer. After 100%, click Reconfigure in Z2M. 1. Select file. 2. Press‑and‑hold button. 3. Reconfigure device. [Elektroda, @GUTEK@, post #21845614]

Which pvvx firmware file should I pick for my scenario?

From stock firmware, use 1141‑0203‑10923001‑ZTY0201z_v0134.zigbee. From ZigbeeTLc to a newer ZigbeeTLc, use 1141‑0230‑01343001‑ZTY0201.zigbee. For a wired programmer, use ZTY0201_v0134.bin. [Elektroda, @GUTEK@, post #21845614]

Do I really have to keep the button pressed during OTA?

Yes. This model sleeps unless the front button is held, causing timeouts; hold it for the entire ~15‑minute update. “Press the button all the time during the update.” [Elektroda, @GUTEK@, post #21845614]

Why is my stock TY0201 range so short, and can firmware fix it?

The stock unit often needs to be within a few metres of a router due to its RF design; firmware does not change the radio front‑end. Place a Zigbee router closer for stability. [Elektroda, @GUTEK@, post #21845614]

Why does the battery drain fast on stock firmware?

User tests report 800 mAh AAA rechargeables lasting just over six months, worsened by a display driver needing ≥2.5 V via an onboard inverter. Reducing display use and interval helps. [Elektroda, @GUTEK@, post #21846098]

What features appear in Z2M after flashing ZigbeeTLc?

Z2M immediately shows temperature, humidity, and battery. Add an external_converter to unlock display on/off, °C/°F, calibration offsets, and a 3–255 s measurement interval (default 10 s). [Elektroda, @GUTEK@, post #21847740]

How do I enable advanced settings for TY0201 in Z2M?

Create an external_converters folder next to configuration.yaml and add a converter JS file defining uiCfg attributes (display, units, calibration, interval). Restart Z2M to apply. [Elektroda, @GUTEK@, post #21847740]

What if Z2M says the device is unsupported after flashing?

Click Reconfigure on the device page and use the provided external_converter to map attributes. This restores controls while upstream support catches up. [Elektroda, @GUTEK@, post #21845614]

Can I revert to stock firmware later?

Yes. Back up the original image first using TlsrComSwireWriter with a CP1202 USB‑UART. You can then restore via programmer if needed. [Elektroda, @GUTEK@, post #21845614]

Are Tuya Zigbee OTA updates signed, and is custom OTA allowed?

Many low‑cost Tuya devices accept unsigned images, enabling community firmware via Z2M. Sonoff typically signs updates; their miniswitches need a programmer for alternates. [Elektroda, @GUTEK@, post #21846098]

What internal hardware differences affect flashing?

Variant 1 uses only a ZTU module with TLSR8258 and supports easy OTA. Variant 2 adds an MRT08S; to reflash, remove it and bridge R2/R3 with 0 Ω jumpers. [Elektroda, @GUTEK@, post #21845614]

What are the default and configurable reporting intervals?

Stock firmware reports temperature every 30 minutes. ZigbeeTLc exposes a measurement_interval of 3–255 s with a 10 s default via the converter. [Elektroda, @GUTEK@, post #21847740]

Why does the manual refresh button toggle °C/°F on stock firmware?

The stock UI multiplexes refresh and unit toggle on one button, so a press both refreshes and switches units, which is fixed by ZigbeeTLc controls. [Elektroda, @GUTEK@, post #21845614]

How can I calibrate temperature and humidity?

Use the external_converter attributes temperature_calibration and humidity_calibration to apply ±50.00 units with 0.01‑step precision; values affect reports and on‑screen display. [Elektroda, @GUTEK@, post #21847740]

Will battery life definitely improve after ZigbeeTLc?

Results are pending; the author notes power management needs months to evaluate. Plan to disable display and tune intervals for savings. [Elektroda, @GUTEK@, post #21846098]

Stock vs. pvvx ZigbeeTLc: what changes after flashing?

Feature	Stock TY0201	ZigbeeTLc (pvvx)
Temp report interval	30 minutes fixed	3–255 s, default 10 s
Manual refresh button	Also toggles °C/°F	Separate unit control
Display control	None	Enable/disable, comfort icon
Z2M status post‑flash	May show unsupported	Works via external_converter
Battery life claim	~6+ months on 800 mAh	To be tested/optimized

[Elektroda, @GUTEK@, post #21847740]

Who verified these steps and results?

User @GUTEK@ documented the full process, files, timeouts, and Z2M configuration, with photos and code; other users confirmed interest and issues like short battery life. [Elektroda, @GUTEK@, post #21845614]

Can I quote an expert tip from the thread?

Yes: “Press the button all the time during the update (for about 15min).” This prevents the device sleeping and avoids OTA timeouts. [Elektroda, @GUTEK@, post #21845614]

What immediate readings will I see in Z2M after flashing?

You’ll see temperature (°C), relative humidity (%), and battery level (%/voltage if enabled). Advanced options require the external converter. [Elektroda, @GUTEK@, post #21845614]