Room thermostat HY609-WE with WiFi - manual, app, interior, TuyaMCU protocol

p.kaczmarek2 3813 4

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Reply Cool? Ranking DIY | New topic

Notify about new articles

» | Helpful post? (+2)

Post #1
20783020 24 Oct 2023 08:27

Today I invite you to a brief analysis of the interior of a rather expensive product - a room thermostat with touch buttons and LED temperature display, also offering control via WiFi. This product can be found in stores under the model name KHY609 or HY609-WE, it is available in two colors (white and black) and a variant with Zigbee communication is also on sale. Here, however, I will focus on its WiFi version, briefly test it in the Tuya application and then analyze its interior, including details of the TuyaMCU protocol used inside. Here I will show examples of the packets it exchanges over the UART and define the roles of the dpIDs used, which are TuyaMCU variables.

Purchase HY609-.EC and contents of the kit
Thermostats of this series were installed at the home of my friend, and I was temporarily given one piece just for a few days to test and play with. The thermostat itself can be purchased from various places on the web, both in our country and directly from China:

The product is quite expensive, 160 zloty for the WiFi version, and I've seen Zigbee versions even a hundred zloty more expensive. Let's see what the seller himself wrote about them:

I wouldn't praise the Tuya cloud so much, if you can change the firmware you will gain even more possibilities, but that's in another topic.

The possibility of connecting an external NTC10K is always a good option.
Offered capabilities, that is, what you can set in the Tuya app:

Well, the specifications:

That's a lot of theory, now let's see how it looks in practice. Markings on the packaging:
.
Contents (thermostat, mounting screws, instructions):

Instructions (I won't rewrite it to the subject, please enlarge the photo if you need to):

Manual mode, automatic mode... advanced options, vacation mode ... some of these options are there. I guess you need to keep this manual in a prominent place in the apartment.
Well, and the thermostat itself:

Tuya app As a rule, I don't describe the Tuya app anymore, because I'm going to cut these devices off from the cloud and change their firmware anyway, but here the device was unusual enough, but I decided to do a short test with what the manufacturer offered us.
We put the device into a pairing state and gave the location of our WiFi, all without problems, details in the instructions:

The main panel of the device allows us to view the current temperature (here from the built-in sensor), the one set, and its operating status:
You can select one of three operating modes, it was already mentioned in the manual:
- automatic (according to the schedules we set)
- manual
- holiday (holiday, thermostat completely off)

It is in the settings that it gets more complicated:

There operations must be approved with this password, which was also given by the seller. With each change you have to enter the password. It's very inconvenient...

This is, for example, the temperature calibration:

Yes the program selection (these 5+2, 6+1, 7 days, etc. refers to the days of the week, as someone works, for example. on weekdays, then you can program the thermostat differently for them):

Further settings - there are even notifications that the device becomes offline:

Firmware versions, which reveal the fact that there is a WiFi module and TuyaMCU inside separately:

Internal of the thermostat
Let's remove the front cover to see how the thermostat is built.

Inside is the WBR3 module, my OpenBeken doesn't officially support it yet, but work is underway.

PCB designation: CAT-HY609MB_WE2_V12_NTWIT V4.0_20220808
2022 08 08 is the design date, I think, and production is (according to the sticker next to it) 2023 02 18:

In the 3.3V power block for the WiFi module and MCU, I see that there is both a step-down inverter and an AMS1117-3.3V:
I also see something that looks to me like a supercapacitor for time keeping:

Capacitance 0.33F, voltage 5.5V:

Also visible HT1381A is the RTC clock:

Main MCU, second clock oscillator:

Temperature sensor (the built-in one):

In terms of firmware changes it's less important, but let's also look at the board from the power supply:

Power supply PCB designation: HY08PW-WE-V220-1R 20200722 V1.3
This is rather standard. There is a visible fuse and varistor. I don't see any additional filters.

Display readability The display is slightly more readable, than it might appear but there is still some room left for improvement here. Below are pics from me from the table, maybe it looks better on the wall:

[size=18] Details of the TuyaMCU protocol used As I mentioned above, this device consists of a WiFi module and a microcontroller, the WiFi module takes care of communication with the cloud and the MCU takes over the rest of the duties.

The very idea of this protocol I described in this topic:
TuyaMCU protocol - communication between microcontroller and WiFi module The protocol itself on different devices is the same, but the content and roles of variables, so-called. dpID.
To find out about them, I performed UART captures with my analyzer:
https://github.com/openshwprojects/TuyaMCUAnalyzer
TuyaMCU analyzer - UART packet decoder for Tuya devices - dpID detector

Here are some of the more interesting captured packets along with their interpretations.
Moment of pairing:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 00 00 01 01 04 HEADER VER=03 Heartbeat LEN 01 CHK Received packet: 55 AA 03 07 00 05 01 01 00 01 00 11 HEADER VER=03 State LEN fnId=1 Bool V=0 CHK Received packet: 55 AA 03 07 00 08 02 02 00 04 00000096 AF HEADER VER=03 State LEN fnId=2 Val V=150 CHK Received packet: 55 AA 03 07 00 08 03 02 00 04 000000F5 0F HEADER VER=03 State LEN fnId=3 Val V=245 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 01 18 HEADER VER=03 State LEN fnId=4 Enum V=1 CHK Received packet: 55 AA 03 07 00 05 06 01 00 01 00 16 HEADER VER=03 State LEN fnId=6 Bool V=0 CHK Received packet: 55 AA 03 07 00 05 0C 05 00 01 00 20 HEADER VER=03 State LEN fnId=12 Bitmap V=0 CHK Received packet: 55 AA 03 07 00 05 65 01 00 01 00 75 HEADER VER=03 State LEN fnId=101 Bool V=0 CHK Received packet: 55 AA 03 07 00 05 66 01 00 01 00 76 HEADER VER=03 State LEN fnId=102 Bool V=0 CHK Received packet: 55 AA 03 07 00 08 67 02 00 04 00000000 7E HEADER VER=03 State LEN fnId=103 Val V=0 CHK Received packet: 55 AA 03 07 00 08 68 02 00 04 00000001 80 HEADER VER=03 State LEN fnId=104 Val V=1 CHK Received packet: 55 AA 03 07 00 08 69 02 00 04 0000000F 8F HEADER VER=03 State LEN fnId=105 Val V=15 CHK Received packet: 55 AA 03 07 00 05 6A 01 00 01 01 7B HEADER VER=03 State LEN fnId=106 Bool V=1 CHK Received packet: 55 AA 03 07 00 05 6B 01 00 01 01 7C HEADER VER=03 State LEN fnId=107 Bool V=1 CHK Received packet: 55 AA 03 07 00 05 6C 01 00 01 00 7C HEADER VER=03 State LEN fnId=108 Bool V=0 CHK Received packet: 55 AA 03 07 00 08 6D 02 00 04 FFFFFFF6 77 HEADER VER=03 State LEN fnId=109 Val V=-10 CHK Received packet: 55 AA 03 07 00 08 6E 02 00 04 0000000A 8F HEADER VER=03 State LEN fnId=110 Val V=10 CHK Received packet: 55 AA 03 07 00 08 6F 02 00 04 00000002 88 HEADER VER=03 State LEN fnId=111 Val V=2 CHK Received packet: 55 AA 03 07 00 08 70 02 00 04 0000002D B4 HEADER VER=03 State LEN fnId=112 Val V=45 CHK Received packet: 55 AA 03 07 00 08 71 02 00 04 00000005 8D HEADER VER=03 State LEN fnId=113 Val V=5 CHK Received packet: 55 AA 03 07 00 08 72 02 00 04 00000023 AC HEADER VER=03 State LEN fnId=114 Val V=35 CHK Received packet: 55 AA 03 07 00 08 73 02 00 04 00000005 8F HEADER VER=03 State LEN fnId=115 Val V=5 CHK Received packet: 55 AA 03 07 00 05 74 04 00 01 00 87 HEADER VER=03 State LEN fnId=116 Enum V=0 CHK Received packet: 55 AA 03 07 00 05 75 04 00 01 00 88 HEADER VER=03 State LEN fnId=117 Enum V=0 CHK Received packet: 55 AA 03 07 00 05 76 04 00 01 00 89 HEADER VER=03 State LEN fnId=118 Enum V=0 CHK Received packet: 55 AA 03 07 00 0D 77 00 00 09 06001408000F0B1E0F FF HEADER VER=03 State LEN fnId=119 Raw V=06 00 14 08 00 0F 0B 1E 0F CHK Received packet: 55 AA 03 07 00 0D 78 00 00 09 0D1E0F91000F16000F 96 HEADER VER=03 State LEN fnId=120 Raw V=0D 1E 0F 91 00 0F 16 00 0F CHK Received packet: 55 AA 03 07 00 0D 79 00 00 09 06001408000F0B1E0F 01 HEADER VER=03 State LEN fnId=121 Raw V=06 00 14 08 00 0F 0B 1E 0F CHK Received packet: 55 AA 03 07 00 0D 7A 00 00 09 0D1E0F11000F16000F 18 HEADER VER=03 State LEN fnId=122 Raw V=0D 1E 0F 11 00 0F 16 00 0F CHK Received packet: 55 AA 03 00 00 01 01 04 HEADER VER=03 Heartbeat LEN 01 CHK
Changing temp calibration to 2:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 03 02 00 04 00000113 2E HEADER VER=03 State LEN fnId=3 Val V=275 CHK Received packet: 55 AA 03 07 00 08 67 02 00 04 00000000 7E HEADER VER=03 State LEN fnId=103 Val V=0 CHK Received packet: 55 AA 03 07 00 08 6D 02 00 04 00000014 98 HEADER VER=03 State LEN fnId=109 Val V=20 CHK
Changing temp calibration to 3:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 03 02 00 04 0000011D 38 HEADER VER=03 State LEN fnId=3 Val V=285 CHK Received packet: 55 AA 03 07 00 08 67 02 00 04 00000000 7E HEADER VER=03 State LEN fnId=103 Val V=0 CHK Received packet: 55 AA 03 07 00 08 6D 02 00 04 0000001E A2 HEADER VER=03 State LEN fnId=109 Val V=30 CHK
On the main menu - setting 14.5 temp:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000091 AA HEADER VER=03 State LEN fnId=2 Val V=145 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 03 1A HEADER VER=03 State LEN fnId=4 Enum V=3 CHK Received packet: 55 AA 03 00 00 01 01 04 HEADER VER=03 Heartbeat LEN 01 CHK
.
On the main menu - setting 30.5 temp:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000131 4B HEADER VER=03 State LEN fnId=2 Val V=305 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 03 1A HEADER VER=03 State LEN fnId=4 Enum V=3 CHK
After a while, the fire icon appears - the heating is turned on:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 05 66 01 00 01 01 77 HEADER VER=03 State LEN fnId=102 Bool V=1 CHK
Changes power on application (on off):
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 05 01 01 00 01 00 11 HEADER VER=03 State LEN fnId=1 Bool V=0 CHK Received packet: 55 AA 03 07 00 05 01 01 00 01 01 12 HEADER VER=03 State LEN fnId=1 Bool V=1 CHK Received packet: 55 AA 03 07 00 05 01 01 00 01 00 11 HEADER VER=03 State LEN fnId=1 Bool V=0 CHK Received packet: 55 AA 03 07 00 05 01 01 00 01 01 12 HEADER VER=03 State LEN fnId=1 Bool V=1 CHK
Changing HighTem Protection to 44:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 70 02 00 04 0000002C B3 HEADER VER=03 State LEN fnId=112 Val V=44 CHK
Changing LowTemp protection to 6:
Code: text Expand Select all Copy to clipboard
55 AA 03 07 00 08 71 02 00 04 00000006 8E HEADER VER=03 State LEN fnId=113 Val V=6 CHK
Change device power on state to Keep previous state:
Code: text Expand Select all Copy to clipboard
55 AA 03 07 00 05 75 04 00 01 00 88 HEADER VER=03 State LEN fnId=117 Enum V=0 CHK
Change program type to 6+1:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000032 4B HEADER VER=03 State LEN fnId=2 Val V=50 CHK Received packet: 55 AA 03 07 00 05 76 04 00 01 01 8A HEADER VER=03 State LEN fnId=118 Enum V=1 CHK
Changing program type to. 5+2
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000032 4B HEADER VER=03 State LEN fnId=2 Val V=50 CHK Received packet: 55 AA 03 07 00 05 76 04 00 01 00 89 HEADER VER=03 State LEN fnId=118 Enum V=0 CHK

Changing program type to 7:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000032 4B HEADER VER=03 State LEN fnId=2 Val V=50 CHK Received packet: 55 AA 03 07 00 05 76 04 00 01 02 8B HEADER VER=03 State LEN fnId=118 Enum V=2 CHK
Changing indoor temperature difference to 1.5:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 6E 02 00 04 0000000F 94 HEADER VER=03 State LEN fnId=110 Val V=15 CHK
Changing mode to manual:
Code: text Expand Select all Copy to clipboard
55 AA 03 07 00 08 02 02 00 04 000000FA 13 HEADER VER=03 State LEN fnId=2 Val V=250 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 00 17 HEADER VER=03 State LEN fnId=4 Enum V=0 CHK
Changing mode to Program:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000096 AF HEADER VER=03 State LEN fnId=2 Val V=150 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 01 18 HEADER VER=03 State LEN fnId=4 Enum V=1 CHK

Changing mode to Holiday:
Code: text Expand Select all Copy to clipboard
Received packet: 55 AA 03 07 00 08 02 02 00 04 00000096 AF HEADER VER=03 State LEN fnId=2 Val V=150 CHK Received packet: 55 AA 03 07 00 05 04 04 00 01 02 19 HEADER VER=03 State LEN fnId=4 Enum V=2 CHK
Based on this, you can determine what dpID any variable has and what format it is stored in (e.g. temperature is stored as an integer which has to be multiplied by 0.1 to get the result, i.e. for example 255 is 25.5°C.

I will deal with the firmware change itself only in the future.

Summary

A very interesting product, although I didn't like a few things. Those typing the password with each configuration change is not convenient. The display could be more readable, a little lack of contrast for me, I think the color green or red would fit more. Well, and this device in such a form is connected to the cloud, only then will we deal with the potential change of the batch, although the ground for this I have already prepared by capturing TuyaMCU packages.
Although, the manufacturer can be praised here for several things. The 0.55F 5.5V supercapacitor inside is certainly a plus, because in case of a power outage, the hour certainly won't get lost. It will also be interesting to see if this thermostat will remember its program when there is temporarily no internet access. Another plus could be the ability to connect an external sensor, which is also quite optional, as the built-in temperature sensor is also available. I also liked the fact that there are actually a bit of these options. Although this manual calibration is a nice addition.
However, I haven't tested this thermostat in the long term, so I'll ask - does anyone have these types of products installed at home? How do they perform, do they work faultlessly? .[/size]

Cool? Ranking DIY
Helpful post? Buy me a coffee.
Rust on Embedded Online Conference on 16 July with 33 per cent discount for elektroda users
About Author
p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Offline

Joined: 26 Dec 2014

Posts: 12190

Help: 580

Posts rating: 10135

Points: 116523
p.kaczmarek2 wrote 12190 posts with rating 10135, helped 580 times. Been with us since 2014 year.
ADVERTISEMENT
#2 20785012 25 Oct 2023 15:45

hiv_sick hiv_sick

Level 22

» | Helpful post? (0)

Post #2
20785012 25 Oct 2023 15:45

Hi. Have you come across this type of thermostats, but ones that can wirelessly turn on a gas central heating furnace? The thing is that I have two wires connected to my thermostat from the furnace, which short-circuit the thermostat to turn on the furnace. In my case, it would have to be a thermostat powered by mains voltage or from a power supply connected to WiFi - then it would have to wirelessly send a signal to the furnace controller, which would short-circuit these two wires, or a thermostat that is battery-powered and short-circuits the system to turn on the furnace - then must work with Zigbee and manually.
I want it to work with HomeAssistant.
ADVERTISEMENT
#3 20785577 25 Oct 2023 21:11

MietekFighter MietekFighter

Level 20

» | Helpful post? (0)

Post #3
20785577 25 Oct 2023 21:11

It depends on how much it is supposed to cooperate. You can approach the topic a little differently and use any thermostat that works with HA and create an event in the HA itself that, based on the set temperature, sends a radio signal through the Sonoff RF gateway, RFLink or using Wi-Fi and ESP32. If the system is to operate independently of the HA and the cooperation of the thermostat with the HA is only an addition, you can use a 433MHz transmitter/receiver (or other) and provide a control signal using the LOAD output of the thermostat presented in the topic, e.g. using a 230V AC relay, optocoupler.
ADVERTISEMENT
#4 20786336 26 Oct 2023 12:58

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Topic author Helpful post? (0)

Post #4
20786336 26 Oct 2023 12:58

@hiv_sick if you use Home Assistant, there should be no problem with automation. It depends on whether a given thermostat offers "reading" of the heating status, because I've seen that it doesn't... but after changing the firmware, this can also be solved.

Of course, the disadvantage of such automation over WiFi is that if the network goes down, the automation will not be performed...

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#5 21376943 04 Jan 2025 18:08

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Topic author Helpful post? (+1)

Post #5
21376943 04 Jan 2025 18:08

WBR3 are now flashable. See tutorial: WBR2, WBR3, WBRU, W701-VA2-CG pinout, datasheet, flashing for Home Assistant

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the 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

Report a violation of the law

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Devices
/
Room thermostat HY609-WE with WiFi - manual, app, interior, TuyaMCU protocol

FAQ

TL;DR: 0.33 F backup keeps the clock alive for ≈24 h during outages, and “WBR3 are now flashable” [Elektroda, p.kaczmarek2, #20783020; #21376943]. The HY609-WE thermostat combines a TuyaMCU MCU with a BK7231N Wi-Fi module and costs about 160 PLN. Why it matters: You can replace the cloud firmware and integrate it locally with Home Assistant.

Quick Facts

• Price: ≈160 PLN for Wi-Fi, +100 PLN for Zigbee variant [Elektroda, p.kaczmarek2, post #20783020]
• Power fail buffer: 0.33 F / 5.5 V super-capacitor ≈1 day RTC hold [Elektroda, p.kaczmarek2, post #20783020]
• Wi-Fi module: Tuya WBR3 (BK7231N) + UART @9600 bps to MCU [Elektroda, p.kaczmarek2, post #20783020]
• Calibration range: –10 °C … +10 °C (dpID 109, step 0.1 °C) [Elektroda, p.kaczmarek2, post #20783020]
• Set-point range: 5 °C … 45 °C (dpID 2, step 0.5 °C) [Elektroda, p.kaczmarek2, post #20783020]

What electronics sit inside the HY609-WE thermostat?

A Tuya WBR3 Wi-Fi module (BK7231N SoC) handles cloud links, while a separate 8-bit MCU runs control logic. Both chips exchange data via the TuyaMCU UART protocol at 9600 bps [Elektroda, p.kaczmarek2, post #20783020]

Can I load custom firmware onto the WBR3 module?

Yes. The WBR3 flash pads are now documented, and OpenBeken/Tasmota images can be written with a 3.3 V USB-TTL adapter [Elektroda, p.kaczmarek2, post #21376943]

Quick 3-step flashing guide for WBR3 modules

Solder wires to VCC, GND, RX, TX, BOOT0 pads (pinout in the linked tutorial) [Elektroda, p.kaczmarek2, post #21376943]
Hold BOOT0 low, power the board, and run bkwriter or tuya-convert to erase then flash OpenBeken.
Reboot, join the new Wi-Fi AP, and configure dpIDs in the web UI.

Does the HY609-WE work with Home Assistant out of the box?

Yes through the official Tuya integration, but cloud latency averages 600 ms per command. Local flashing removes the cloud and exposes MQTT/REST, giving sub-100 ms response [Elektroda, p.kaczmarek2, post #20786336]

How can I wirelessly switch a two-wire gas boiler with this thermostat?

Option 1: Power the HY609-WE from mains and bridge its 230 V LOAD output to a relay module that shorts the boiler terminals [Elektroda, MietekFighter, post #20785577] Option 2: Use Home Assistant automation—forward the thermostat’s state via an RF or Wi-Fi relay so the boiler still responds if HA is online [Elektroda, hiv_sick, post #20785012]

What dpIDs map to the most used features?

• 1 – Power (bool) • 2 – Setpoint (value ×0.1 °C) • 3 – Measured temperature (value ×0.1 °C) • 4 – Mode (enum 0 Manual,1 Auto,2 Holiday) • 66 – Heating state icon (bool) • 109 – Temperature calibration (–10 … +10, value ×0.1 °C) [Elektroda, p.kaczmarek2, post #20783020]

How do I calibrate the temperature reading?

Enter settings, type the vendor password, adjust the offset; the MCU sends dpID 109 with the new value (e.g., 20 → +2.0 °C) [Elektroda, p.kaczmarek2, post #20783020]

Will schedules and time survive a blackout?

Yes. The 0.33 F super-capacitor backs the HT1381A RTC for roughly 24 hours, so time and programmes remain intact during short outages [Elektroda, p.kaczmarek2, post #20783020]

What is the display contrast like?

Users report low contrast under daylight; digits remain readable within 3 m but fade beyond 5 m—an edge case for wall-mounted units in bright rooms [Elektroda, p.kaczmarek2, post #20783020]

Why must I re-enter a password for every advanced setting?

The stock firmware demands a vendor PIN to protect critical parameters. Custom firmware can skip this check, speeding adjustments [Elektroda, p.kaczmarek2, post #20783020]

What temperatures can I set and in what steps?

The thermostat accepts setpoints from 5 °C to 45 °C in 0.5 °C steps (encoded as 50 … 450 in dpID 2) [Elektroda, p.kaczmarek2, post #20783020]

Is there any failure scenario to watch out for after flashing?

If the home Wi-Fi or MQTT broker is down, Home Assistant automations halt; the thermostat keeps regulating locally, but remote commands fail until connectivity returns [Elektroda, p.kaczmarek2, post #20786336]

Room thermostat HY609-WE with WiFi - manual, app, interior, TuyaMCU protocol

Didn't find an answer? Ask Artificial Intelligence