I am going to try to take a look at the logic. My feeling is they did change the protocol. @badfrogg mentioned his came with the TCWBRCU1 dongle (TCWBRCU1 datasheet-Tuya Developer Platform-Tuya Developer)
I am guessing @Refuge also came with this dongle. Mine( and I’m assuming yours?) came with the TCWBR-US3 (TCWBR-US3 Adapter Board Datasheet-Tuya Developer Platform-Tuya Developer)
it seems this change in dongles was pretty recent as the replacement modules for wyt series listed on the pioneer website are still the TCWBRCU1 model.
Wow, that’s crazy. I assumed I had the TCWBRCU1. I haven’t checked what I do have, but I bought it in November 2025 so it’s probably the TCWBR-US3, as you say. I was already extremely lucky I read this forum before plugging the SLWF-01pro into it – because who in their right mind changes the pinout of a USB-A-shaped socket to be dangerously incompatible with a standard USB-A device?!
It seems they did change communication. I have started to upload logic captures and commands here and will continue to upload the various functions as found in squidpickles and mike’s repositories. If any contributors or @mikesmitty can make use of these(or if you need specific captures let me know) to make a version compatible with the new dongle, you will make progress faster than me I’m sure.
1 Like
I just got my SLWF-01 flashed and installed and very excited to have it working. I’m just wondering what to add to the Yaml to get all the other options like direct horizontal and vertical louver control as well as Eco, sleep, display and buzzer control, or really all of the control capabilities added. I can see it all listed in mikesmitty’s source code but don’t know how to format it to include in the Yaml.
the attached pictures show the Local Tuya integration with all the options, and the ESP home integration which has very basic control.
@shosta3 , I just started looking at my newly purchased WYT, and mine is clearly the new uart settings. 115200, 8N1. I am capuring packets to an esp32 I has sititng around. I cannot seem to make much sense of many of the packets. But here is what i did fgure out… All packets start with A5. the length of the packet seems to be in either byte 6 or 7 (0 based). I am only listening, not sending any commands yet.
2 types of packets…
TYPE 1
| 03-13-2026 | 10:20:45 | 000000 | 017 | a5 | fa | 10 | 00 | 05 | 00 | 10 | 00 | 00 | a1 | 02 | 00 | 01 | aa | d7 | 68 | 5a |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 03-13-2026 | 10:20:46 | 000001 | 017 | a5 | fa | 11 | 00 | 05 | 00 | 10 | 00 | 00 | a1 | 01 | 00 | 01 | 3c | ac | be | 5a |
| 03-13-2026 | 10:20:46 | 000002 | 017 | a5 | fa | 10 | 00 | 05 | 20 | 10 | 00 | 00 | a1 | 02 | 00 | 01 | aa | 70 | 94 | 5a |
| 03-13-2026 | 10:20:46 | 000003 | 017 | a5 | fa | 11 | 00 | 05 | 20 | 10 | 00 | 00 | a1 | 01 | 00 | 01 | 3c | 0b | 42 | 5a |
| 03-13-2026 | 10:20:46 | 000004 | 017 | a5 | fa | 12 | 00 | 05 | 00 | 10 | 00 | 00 | a1 | 04 | 00 | 01 | f0 | 0d | a4 | 5a |
| 03-13-2026 | 10:20:46 | 000005 | 017 | a5 | fa | 13 | 00 | 05 | 00 | 10 | 00 | 00 | a1 | 04 | 00 | 01 | fb | bf | ba | 5a |
| 03-13-2026 | 10:20:47 | 000006 | 017 | a5 | fa | 12 | 00 | 05 | 20 | 10 | 00 | 00 | a1 | 04 | 00 | 01 | f0 | aa | 58 | 5a |
| 03-13-2026 | 10:20:47 | 000007 | 017 | a5 | fa | 13 | 00 | 05 | 20 | 10 | 00 | 00 | a1 | 04 | 00 | 01 | fb | 18 | 46 | 5a |
| 03-13-2026 | 10:20:47 | 000008 | 017 | a5 | fa | 14 | 00 | 05 | 00 | 10 | 00 | 00 | a0 | 03 | 00 | 01 | 00 | 12 | f9 | 5a |
| 03-13-2026 | 10:20:47 | 000009 | 017 | a5 | fa | 15 | 00 | 05 | 00 | 10 | 00 | 00 | a0 | 06 | 00 | 01 | 00 | ad | c9 | 5a |
| These are all 17 byte length start with A5, bytes 1&2 seem to be a packet counter, byte 6 length+1? |
TYPE 2
|3/13/2026 3:27:18 PM|14|A5|01|01|21|ED|00|00|42|73|6E|0C|0C|00|01|01|00|02|00|00|09|60|00|03|00|00|09|C4|00|05|00|00|0C|00|00|0D|00|00|0E|08|00|11|08|00|12|04|00|DF|00|00|C9|00|00|17|00|00|1E|01|02|27|00|00|00|4B|01|48|01|||||||||||||||||||||||
|3/13/2026 3:27:19 PM|15|A5|01|01|21|EE|00|00|5B|22|2A|0C|0C|00|22|00|00|25|01|00|27|00|00|2D|00|00|35|00|00|38|00|00|5C|00|00|0C|E4|00|39|13|02|03|07|08|09|0B|0C|0D|15|17|1F|21|24|27|28|2A|2B|30|31|00|5E|00|00|60|00|00|07|6C|00|64|00|00|01|F4|00|65|00|00|00|12|00|72|00|00|00|00|00|73|01|
These all start with A5, 01, 01. Byte 4 is some sort of command or packet counter, byte 7 is clearly the packet length. Similar to your caputures. Im not sure where to look next.
Ignore my first 3 columns on the type 1. Datetime, my packet counter, packet length. and ignore first 2 on type 2. Datetime, my packet counter.
I have been able to set modes, change temps, fan speeds there are still status values that need some work. I haven’t been able to start the remote control decoding yet. This is one of the main reasons for my want of the integration is being able to feed in the follow me values.
Well I just updated my esphome for the AC unit and it no longer works like it did before…
I can still press commands in the home assistant UI, and the unit beeps in response, but doesn’t do what I set it to do…
I keep getting this in the web console:
16:28:45 [D] [uart_debug:157]
>>> "\xBB\x00\x01\x04\x02\x01\x00\xBD"
16:28:47 [E] [uart:014]
Reading from UART timed out at byte 0!
16:28:47 [E] [pioneer.climate:163]
ugh I wish I hadn’t updated…
=========
EDIT: It started to work again…
So on my WT009GLSI25HLH, it definitely uses the TCWBR-US3. I have a SLWF-01pro to flash, once I get the wiring pinned right. Can anyone give me a tip to separate the white and blue connector from the PCB board? Is there a catch/latch that I have to push on so I can release it and then re-pin it.
You need to remove the blue plastic cover. It prevents you from pushing in the white handle.
What yaml config wil you use?
Thank you. My TCWBR-US3 dongle coincidentally stopped responding. Could not make discover able (using either the remote sequence or power off) or on bluetooth one day. Pioneer warranty support sent me a replacement TCWBR-US1. That TCWBR-US1 now pairs okay to Home Assistant using Tuya Local (the TCWBR-US3 would always fail). So for now, I’m going to stick with the Tuya Local integration w/TCWBR-US1 and monitor this thread for stability.
I have an older Pioneer WYT unit and have been reverse engineering the protocol independently of this thread (wish I had seen sooner, would have saved loads of time). Manually mapped the data compared to Tuya app, then vibe-coded an ESPHome component. Only tested on one unit but working as expected - feel free to use.
Your code looks great did you just flash the stock unit with this?
Yep, I first backed it up using esptool dump just in case, then just directly flashed over the breakout pins. I knew going into it that if I messed anything up I could just buy a replacement wifi board for about $30