TOMZN TOMPD-63-LW Wifi Multi Function (DIN) WB3S (BK7231T)

crash1912 14 Aug 2023 18:52 134 31992 Cool? (+3)

📢 Listen (AI):

TL;DR

TOMZN TOMPD-63-LW 63A WiFi DIN power meter targets dual-line cutoff and uses a WB3S/BK7231T platform.
It supports remote on/off, live current, voltage, leakage current, and total kWh monitoring, plus timer control in the SmartLife Tuya app.
The configurable protections include 230V 50/60Hz operation, 140V-210V undervoltage, 225V-295V overvoltage, and 1A-63A overcurrent limits.
OpenBK compatibility remains unresolved, and no forum thread confirming this exact model working correctly was found.

Generated by the language model.

Hello, I recently bought this DIN power meter, it looks good, does anyone have this model with OpenBK working correctly?
I have searched a lot in the forum and I have not found anything related to this model, so I open a thread.

The brand of the device is TOMZN and the model is TOMPD-63LW 63A, apparently it is similar to TOMZN TOML-VA 63A.

I'm new to this and need some initial help.

Specs:
The product can cut off L and N both.
Rated voltage: 230V; Frequency: 50Hz/60HZ
1. Remote control ON/OFF at anytime from anywhere by phone.
2. Review current, voltage, leakage current, total kWh on phone.
3. Timer function in smartlife TUYA app.
4. Can set over voltage/under voltage/over current/leakage current in app or can set these by manual.
5. Under voltage protection 140V-210V (adjustable) (default: 170V).
6. Over voltage protection 225V-295V (adjustable) (default: 265).
7. Over current protection 1A-63A (adjustable) (default: 40A).
8. Reconnect time (delay on time): 1s-500s (default: 30s).
9. Voltage/current/kW calibration: -9.9%-9.9%.
10. Action time: 1-30s (default 1s).
11. Power consumption less than 2W.
12. White backlight.

Here are all the images he was able to collect.

About Author

crash1912 wrote 15 posts with rating 3 . Live in city Extremadura. Been with us since 2023 year.

Comments

Add a comment

p.kaczmarek2 14 Aug 2023 21:04

I guess it's a TuyaMCU device, so it will work without any problem. Do you know how to do UART data capture in a safe manner? This device is mains powered, so doing capture may be dangerous. We could... [Read more]

DeDaMrAz 14 Aug 2023 21:21

@crash1912 Can you take a better picture, maybe of the bottom board? And if possible, maybe include the markings from the LCD controller? [Read more]

crash1912 14 Aug 2023 22:39

Thanks for answering, I'm new to this, I have a moment of mental garbage with a lot of information, openbk, tasmota, esphome... but I'm advancing little by little. I don't know how to do UART data capture... [Read more]

p.kaczmarek2 14 Aug 2023 22:54

What is under capacitor here: https://obrazki.elektroda.pl/3855322500_1692046358_thumb.jpg This is WB3S bot: https://obrazki.elektroda.pl/9001953900_1692046409_thumb.jpg (Bottom view, not... [Read more]

DeDaMrAz 14 Aug 2023 22:56

@crash1912 There is a similar post you can read - https://www.elektroda.com/rtvforum/viewtopic.php?p=20686225#20686225 Also, you can check this post on how to do UART capture safely - https://www.elektroda.com/rtvforum/viewtopic.php?p=20667319#20667319 And... [Read more]

p.kaczmarek2 14 Aug 2023 23:53

You may be right. I can see UART traces there. They go through resistors. https://obrazki.elektroda.pl/6372361200_1692049934_thumb.jpg That would mean that one would have to desolder them to temporary... [Read more]

crash1912 15 Aug 2023 12:11

With a multimeter, I can't find continuity between TX1, RX1, and any other board connection pin, only VDD and GND. I think I'll need to solder wires on TX1 and RX1... Under the capacitor, I can see: HC89F0541... [Read more]

p.kaczmarek2 15 Aug 2023 13:19

Well, no surprises here, considering that it clearly looks like TX1 and RX1 go through resistors to MCU: https://obrazki.elektroda.pl/7348413800_1692098093_thumb.jpg It's TuyaMCU. https://obrazki.elektroda.pl/6677601000_1692098172_thumb.jpg... [Read more]

crash1912 17 Aug 2023 15:02

You are right, without a bridge between pin 22 and GND, you cannot read/write anything. Using a little mini hook, I can create a bridge without soldering. For TX/RX, I held male pins to the board using... [Read more]

p.kaczmarek2 17 Aug 2023 15:05

2MB flash can contain your SSID if you paired it. Please post if you can, if not, please post only Tuya JSON. See how to extract JSON: This will tell us which baud rate is your device using. [Read more]

crash1912 17 Aug 2023 15:34

The device is new, never used, does not contain any personal data configured for me. If it contains anything, it is from the factory (any device key or anything, I don't know). I have attached a backup... [Read more]

p.kaczmarek2 17 Aug 2023 15:55

That's good enough. Well done. So baud rate is the default, slow-speed one. Okay, so let's start with this autoexec.bat: // start TuyaMCU driver startDriver TuyaMCU // always force 0x04 WiFi state... [Read more]

crash1912 17 Aug 2023 19:37

Ok now driver is already loaded: https://obrazki.elektroda.pl/6551659400_1692293974_thumb.jpg Yes, i can toggle relay from physical button. In the recording tab, the data is very abundant, these... [Read more]

p.kaczmarek2 17 Aug 2023 21:47

There isn't much in the logs, but they seem to suggest that dpID 16 is a boolean, it may be a relay. So, now autoexec.bat should look like: // start TuyaMCU driver startDriver TuyaMCU // always... [Read more]

crash1912 18 Aug 2023 17:31

Correct, DP16 is a power switch relay! and using configuration from EAMPDW-TY63 now can see more data! but some is wrong... OverVoltage, UnderVoltage, Current and Leakage values appears 0, but OverVoltage... [Read more]

p.kaczmarek2 18 Aug 2023 23:47

How does your current web app log looks like? Which dpIDs are working? You've jumped quickly to very advanced config and I am not sure if it's entirely correct. Have you tried to use tuyaMcu_sendQueryState... [Read more]

crash1912 20 Aug 2023 13:09

Ok, well I think so too, I've gone too fast :) tuyaMcu_sendQueryState force refresh arbitrary? this looks good!! I like this!! Works great!! ¿Can refresh each 5~10s automatically? ok, now let's... [Read more]

p.kaczmarek2 20 Aug 2023 13:56

Repeating event can be used to do some action periodically: // NOTE: addRepeatingEvent [RepeatTime] [RepeatCount] // code below will forever toggle relay every 15 seconds addRepeatingEvent... [Read more]

crash1912 21 Aug 2023 14:56

Repeating event is wonderful, i added "addRepeatingEvent 10 -1 tuyaMcu_sendQueryState" and works amazing. Possible stupid question: if channels are like variable and dpID's are same as constant... [Read more]

FAQ

TL;DR: With a 2 MB flash backup first, this breaker can run OpenBeken reliably; as one expert put it, "It’s TuyaMCU". This FAQ helps TOMZN TOMPD-63-LW owners flash WB3S/CBU versions, decode dpIDs, fix slow updates, and restore full relay and metering behavior. [#20694223]

Why it matters: This thread turns a hard-to-flash Tuya DIN breaker into a documented OpenBeken target with known wiring, dpIDs, and working refresh tricks.

Option	Best fit	Main advantage	Main drawback
OpenBeken	TOMPD-63-LW with TuyaMCU	Full local control, dpID mapping, custom UI	Requires UART flashing and setup
ESPHome	Users already on HA	Familiar YAML workflow	Thread did not map this model fully
Tasmota	Users comparing ecosystems	Popular tooling	Thread provided no complete TOMPD-63-LW config

Key insight: The critical hurdle is not the Wi-Fi module itself. It is the secondary TuyaMCU link on UART, which must be isolated by reset or trace separation during flashing, then mapped correctly in OpenBeken.

Quick Facts

The breaker is rated 230 V, 50/60 Hz, up to 63 A, and the product description listed adjustable thresholds such as undervoltage 140–210 V, overvoltage 225–295 V, overcurrent 1–63 A, reconnect delay 1–500 s, and action time 1–30 s. [#20693422]
A successful flash path on the WB3S version used a full 2 MB backup, bk7231flasher_1.1.1, and OpenBK7231T_UA_1.17.221.bin; grounding pin 22 of the HC89F0541 reset line enabled UART read/write without permanent board cutting. [#20697176]
dpID 16 was confirmed as the main relay, dpID 6 carries the combined voltage/current/power packet, dpID 1 is total energy, and dpID 9 is the fault bitmap rather than a single numeric alarm. [#20697712]
The Tuya cloud model exposed at least 20 dpIDs on later units, including 104 power factor, 105 supply frequency, 106 refresh, 116 voltage, 117 current, and 118 active power, beyond the earlier basic set. [#20837470]
Default reporting was slow enough to frustrate users, but adding addRepeatingEvent 10 -1 tuyaMcu_sendQueryState produced practical refreshes every 10 s instead of waiting for the long factory interval. [#20702297]

How do you safely flash OpenBeken onto a TOMZN TOMPD-63-LW with a WB3S or CBU module, including backup, UART wiring, and handling the TuyaMCU connection?

Yes—make a full backup first, then flash over UART with the TuyaMCU isolated. 1. Connect 3.3 V, GND, TX1, RX1 to the WB3S or CBU pads and read a 2 MB backup. 2. Keep the mains side isolated and disable the secondary MCU, usually by reset or temporarily breaking its UART path. 3. Flash OpenBeken, reboot, then restore from backup if needed. On the WB3S unit, this worked with bk7231flasher_1.1.1 and OpenBK7231T_UA_1.17.221.bin. [#20697176]

What is TuyaMCU in the TOMZN TOMPD-63-LW, and how does it communicate with the WB3S or CBU Wi-Fi module?

"TuyaMCU" is a secondary control MCU that reads measurements, drives the front panel, and exchanges datapoints over UART with the Wi-Fi module. In this breaker, the Wi-Fi board is only one part of the design; the HC89F0541-class MCU handles protection logic and LCD tasks. OpenBeken talks through that UART link, so dpIDs come from TuyaMCU rather than directly from the relay hardware. That is why flashing and runtime mapping depend on the UART relationship between TuyaMCU and WB3S or CBU. [#20694223]

What is RAW_TAC2121C_VCP in OpenBeken, and how does it decode voltage, current, and power from dpID 6 on the TOMPD-63-LW?

RAW_TAC2121C_VCP is OpenBeken’s parser for the 8-byte Tuya raw packet on dpID 6. It splits one packet into voltage, current, and active power channels automatically. The Tuya model describes the format as 2 bytes voltage at 0.1 V, 3 bytes current at 0.001 A, and 3 bytes power at 0.0001 kW. The thread later confirmed the packet decodes exactly that way, which is why removing the mapping made channels 2, 3, and 4 fall back to zero. [#20707655]

Why do some TOMZN TOMPD-63-LW units need the HC89F0541 reset pin tied to GND before UART read/write will work?

They need it because the TuyaMCU shares the same UART lines used for flashing the Wi-Fi module. If the HC89F0541 stays active, it drives or listens on that bus and blocks clean UART read/write. One successful workaround grounded pin 22, the reset pin, during backup and flashing. That let UART access work without desoldering the resistor links between the TuyaMCU and the WB3S module. [#20694223]

How can I use tuyaMcu_sendQueryState or addRepeatingEvent to force faster refresh updates on a TOMPD-63-LW that otherwise reports very slowly?

Use tuyaMcu_sendQueryState directly, or schedule it with addRepeatingEvent. The working example was addRepeatingEvent 10 -1 tuyaMcu_sendQueryState, which polls every 10 seconds. That solved the complaint that power values updated only about every 2 minutes under the stock behavior. The command can also be triggered manually from the Web App command area when you want an immediate state dump. [#20702297]

Which dpIDs have been identified for the TOMZN TOMPD-63-LW, and what do dpIDs 1, 6, 9, 11, 12, 13, 14, 15, 16, 17, 18, 19, 21, 101, 104, and 105 mean?

The key dpIDs are known. 1 total energy, 6 phase A V/I/P raw packet, 9 fault bitmap, 11 prepayment switch, 12 clear prepaid energy, 13 balance energy, 14 charge energy, 15 leakage current, 16 relay switch, 17 alarm_set_1, 18 alarm_set_2, 19 breaker ID, 21 leakage test, 101 clear all energy, 104 power factor, and 105 supply frequency. Later cloud data also exposed 106 refresh, 116 voltage, 117 current, and 118 active power on newer units. [#20854635]

How do channels and dpIDs differ in OpenBeken, and how should linkTuyaMCUOutputToChannel be used correctly on a TuyaMCU breaker?

dpIDs are fixed Tuya datapoints; channels are OpenBeken variables you assign yourself. You can map any suitable dpID to any free channel, but the meaning and type of the dpID do not change. The correct syntax is linkTuyaMCUOutputToChannel [dpId] [varType] [channelID]. In practice, the thread used mappings like linkTuyaMCUOutputToChannel 16 bool 1 for the relay and linkTuyaMCUOutputToChannel 1 val 5 for total energy. [#20700864]

Why does dpID 9 on the TOMPD-63-LW behave like a bitmap, and how can its fault bits be mapped to alarms such as overload, leakage, overvoltage, undervoltage, or low balance?

dpID 9 is a bitmap because each bit represents one fault flag, not one numeric state. Testing showed values such as 4, 8, and 32768, matching single-bit alarms rather than sequential IDs. The Tuya model labels include overload, leakage current alarm, overvoltage, undervoltage, and no-balance alarm. For example, a leakage self-test produced 8, which matched the self-test or leakage-related bit position, while low balance matched a high-order bit. [#20842982]

How can I decode and use alarm_set_1 and alarm_set_2 raw packets from dpIDs 17 and 18 for protection thresholds on the TOMPD-63-LW?

Decode them as 4-byte records per protection: byte 1 = protection code, byte 2 = trip mode, bytes 3–4 = threshold. The thread decoded dpID 17 payloads like 04 01 00 1E as leakage protection enabled, trip-on-fault, threshold 30 mA. dpID 18 grouped three protections in 12 bytes, for example overcurrent, overvoltage, and undervoltage. These packets are mainly useful for reading or writing thresholds, but the actual active fault state still reports through dpID 9. [#20849043]

What is the best way to remove leftover buttons or fields from the OpenBeken web UI after changing or clearing autoexec.bat on this breaker?

Set the old channels back to Channel Type = none in the Web App. Clearing autoexec.bat alone does not remove previously stored UI channel types, so the empty controls remain visible. The fix was confirmed after manually resetting those channel types to default, which cleaned the main interface without a hard reset. If you change autoexec layouts often, clear channel types before assuming the script failed. [#20710443]

How do you get the full Tuya data model and dpID list for a TOMZN TOMPD-63-LW from the Tuya developer platform or cloud explorer?

Use Tuya Developer, not guesswork. 1. Create a Tuya developer project and bind the device. 2. Copy the device ID from the cloud device page. 3. In Cloud Explorer, run the Query Things Data Model request to return the full model JSON with abilityId, access mode, code, scale, and units. This method exposed items like dpIDs 104, 105, 106, 116, 117, and 118 that were not obvious from the early UART logs alone. [#20854635]

OpenBeken vs ESPHome vs Tasmota for a TuyaMCU-based DIN breaker like the TOMZN TOMPD-63-LW: which approach fits best and why?

OpenBeken fits best when the device is TuyaMCU-based and you want full local datapoint control. The thread began with users comparing OpenBeken, Tasmota, and ESPHome, but all concrete progress happened with OpenBeken: successful flashing, dpID discovery, custom autoexec files, fault decoding, and faster polling. One user did mention a similar breaker already flashed with ESPHome, but no equivalent TOMPD-63-LW mapping was developed there. For this exact model, OpenBeken is the only fully documented path in the thread. [#20693722]

Why can leakage current, current, and VCP-based channels interfere in some OpenBeken versions, and what changed with LeakageCurrent_div1000 and RAW_TAC2121C_VCP fixes?

They can interfere because older VCP handling wrote values into channels by channel type, creating race conditions when more than one current-like channel existed. That caused leakage current to mirror the main current or swap values unpredictably. The thread led to two fixes: a dedicated LeakageCurrent_div1000 type and later RAW_TAC2121C_VCP changes so multi-phase and shared-current cases behaved correctly. The maintainer explicitly merged a fix so VCP would only target the intended current channel. [#20871205]

What steps can bring the TOMPD-63-LW screen back if screen bright time was accidentally set to off and the display is no longer visible?

You can recover it blindly from the front keys. 1. Power-cycle the breaker so the menu state is predictable. 2. Long-press the set key, then press the up arrow about 10 times to raise screen bright time above zero. 3. Long-press set again to save. A flashlight may help on the older monochrome LCD, but the blind sequence alone was confirmed to restore a fully dark screen on this model. [#21615685]

How can the TOMZN TOMPD-63-LW be configured to stay off after power-up and only energize the relay after a web, MQTT, or API command?

The thread does not provide a finished power-up-off recipe for this breaker, so there is no confirmed TOMPD-63-LW startup command sequence here. What is confirmed is that relay state is exposed as dpID 16 and mapped in OpenBeken with a toggle channel, so any solution must act on that relay channel after boot. A later user asked for exactly this behavior, but no tested answer was posted in the thread. [#21740935]

Generated by the language model.