[WBR3] Feyree EV Charger teardown with adjustable charging via TuyaMCU

stonacek 10812 40

#31 21820945 27 Jan 2026 06:50

momo4 momo4

Level 2

Helpful post? (0)

Post #31
21820945 27 Jan 2026 06:50

Thank you for your article; it served as inspiration and a guide for me. I have replaced the WiFi module with ESP8266 (12F) and have gone with Tasmota. I have put effort to make sure the main functions work exactly as expected. So far I have Tasmota UI showing the V/A/P (some are in wrong scaling) and able to control start/stop charge and current (A) value. Also MQTT is set and in Home Assistant I have built a minimalistic dashboard which shows same data and allows same control. Then, as extra, I have created a scheduler (very basic) that can set the charge start and stop time for the low tariff hours. Also, I have added a keep alive function that kicks in every so to not let the car go in deep sleep as it prevents charging after that.

I will provide the Tasmota and HA configs once I consider they are finalized.
ADVERTISEMENT
#32 21821571 27 Jan 2026 20:38

jaccovdwijgaart jaccovdwijgaart

Level 2

Helpful post? (0)

Post #32
21821571 27 Jan 2026 20:38

>>21820945
This is perfect! You are touching all the aspects of my current struggles with my Feyree charger.

I was using Tuya Local to dynamically change the amps to follow the solar import, and also have the problem with my car going in sleep mode.

I have to add that I have a 3-phase variant of the charger.

Can't wait for your configs.
ADVERTISEMENT
#33 21821666 27 Jan 2026 21:47

stonacek stonacek

Level 7

Topic author Helpful post? (0)

Post #33
21821666 27 Jan 2026 21:47

Why wait? Just do it with OpenBeken - dynamically adjusting the charging amperes is exactly what the original post is about. You can even use OBK Berry scripts to manage the logic, if you don't want to use Home Assistant.
ADVERTISEMENT
#34 21821826 28 Jan 2026 07:04

jaccovdwijgaart jaccovdwijgaart

Level 2

Helpful post? (0)

Post #34
21821826 28 Jan 2026 07:04

>>21821666
In my head, the ESP is better and very available around me. How is the Wi-Fi on the CB3S compared to the WB3R and ESP? Because that is another struggle I have, the reception is piss-poor even though it is near my access point.

Oh, and keeping the car awake with OpenBeken, how can I do that? Sorry, I am new to all of this. I have flashed Tasmota to a switch years ago and that's all. I will try to source the CB3S.
#35 21821915 28 Jan 2026 09:35

stonacek stonacek

Level 7

Topic author Helpful post? (+1)

Post #35
21821915 28 Jan 2026 09:35

>>21821826

I don't have any problems with the wifi over 30+ meters on the beken chips, but I have enterprise APs, small mhz channel allocated for these devices, and virtually no competing noise.

but openbeken runs on ESP varieties as well:

https://github.com/openshwprojects/OpenBK7231T_App
#36 21824024 30 Jan 2026 09:44

momo4 momo4

Level 2

Helpful post? (0)

Post #36
21824024 30 Jan 2026 09:44

Hello all,

I have released the configs and guidelines for the Feyree / ESP8266 / Tasmota / HA setup:

https://github.com/plam40/Feyree-EV-charger/blob/main/README.md

Keep-alive automation is not completed, but working on it
#37 21825357 31 Jan 2026 18:09

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #37
21825357 31 Jan 2026 18:09

@momo4 your readme looks suspicious, is it AI generated? It contains nonsense. I would suggest taking it down and doing a manual revision, before uploading it again.

Tasmota runs on ESP, it does not support WBR3...

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.
#38 21825620 01 Feb 2026 00:52

momo4 momo4

Level 2

Helpful post? (0)

Post #38
21825620 01 Feb 2026 00:52

>>21825357

Hi P. and thanks for spotting those and for all your hard work on the non-ESP chips - yes it is AI-generated - and at the end... the idea of open source is - people can contribute and correct some things that others have overlooked - I have done the changes - but you could also submit a correction PR - it would be much more productive compared to the advice to take it down . It is provided as is and others are welcome to provide improvements. If I had kept it to myself and kept checking - it might have never gone out.
ADVERTISEMENT
#39 21836282 11 Feb 2026 23:29

ruisjm1 ruisjm1

Level 3

Helpful post? (0)

Post #39
21836282 11 Feb 2026 23:29

Hi, can I remove Wi-Fi Tuya chip board and keep charger working in standalone, or it need have Tuya Wi-Fi module?
#40 21836362 12 Feb 2026 06:55

jaccovdwijgaart jaccovdwijgaart

Level 2

Helpful post? (0)

Post #40
21836362 12 Feb 2026 06:55

It works just fine without the Wi-Fi chip using local controls.
#41 21836415 12 Feb 2026 08:25

ruisjm1 ruisjm1

Level 3

Helpful post? (0)

Post #41
21836415 12 Feb 2026 08:25

I will remove it to test it, because I want to install it in a place without Wi-Fi; I only want plug-and-charge, and keep the Tuya board for testing ESPHome in other chargers.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Topic summary

The discussion centers on the teardown and OpenBeken firmware integration of the Feyree Dynamic Load Balancing EVSE (Electric Vehicle Supply Equipment) with TuyaMCU control, specifically model F-OBZ2-AC-1P32, a 240V 32A single-phase charger purchased from an Aliexpress vendor. The device is easily opened and features a secondary current transformer (CT) clamp for input wiring monitoring. The main goal is to enable dynamic adjustment of charging current via MQTT or Home Assistant during active EV charging using OpenBeken. Current firmware supports integer channel types only; string data types for TuyaMCU channels are not yet implemented but may be considered for future updates. The device exposes certain data points (dpIDs), such as dpID 113 (DeviceMaxSetA), which is read-only and limits maximum supported current, preventing hardware current rating changes via software. Charging current can be adjusted dynamically between 6A and 32A, reflected by PWM modulation on the pilot signal per IEC 61851 standards. The pilot signal stops charging by lowering voltage and disconnecting relays, but no pause state exists. RFID functionality is limited and not fully accessible via TuyaMCU; monitoring specific dpIDs can track RFID events but lacks advanced features like identity or billing. Recent OpenBeken updates allow custom data point processing using the Berry scripting language, enhancing flexibility in handling TuyaMCU data. User experiences note immediate charging start behavior and relay switching sequences that may not optimally protect the vehicle. Overall, the Feyree EVSE with TuyaMCU and OpenBeken offers a cost-effective, modifiable charging solution with some firmware and hardware limitations regarding string data handling, maximum current configuration, and RFID integration.
Summary generated by the language model.

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
[WBR3] Feyree EV Charger teardown with adjustable charging via TuyaMCU

FAQ

TL;DR: Control a Feyree 32 A single‑phase EVSE via TuyaMCU/OpenBeken; "This can be done with OpenBeken." Safe flashing, dpIDs, MQTT/HA templates, and pilot behavior included. [Elektroda, stonacek, post #21289899]

Why it matters: DIYers and Home Assistant users can live-adjust charge current, automate start/stop, and avoid cloud lock‑in while staying safe.

Quick Facts

Model F‑OBZ2‑AC‑1P32: 240 V, 32 A single‑phase, GD32F303RCT6 MCU, RN7302 meter. [Elektroda, stonacek, post #21289899]
Current control: dpID 115 sets 8–32 A; TuyaMCU can reach 6 A; after replug it may reset to 20 A. [Elektroda, stonacek, post #21289899]
Start/stop: dpID 124 = Charge(0)/Stop(1); it reverts to Ready(2). Use OnChannelChange to refresh. [Elektroda, stonacek, post #21600344]
Pilot behavior: stop by dropping pilot then relay; dynamic PWM allows 6–32 A live adjustment. [Elektroda, stonacek, post #21541705]
Safety: 8 screws, no seal; isolate power and tools; RX/TX header VDD is 12 V—don’t use; EN pin has 3.3 V. [Elektroda, stonacek, post #21289899]

What hardware is inside this Feyree EVSE?

It’s a Feyree F‑OBZ2‑AC‑1P32, 240 V/32 A single‑phase EVSE. The logic board uses a GigaDevice GD32F303RCT6 microcontroller and an RN7302 metering chip. The enclosure opens with eight rubber‑sealed screws and contains a separate logic board and relay section. A secondary external CT clamp is present at the input end. The unit includes buttons and a TFT display on the logic controller side. These specifics help when mapping TuyaMCU dpIDs and understanding metering accuracy. [Elektroda, stonacek, post #21289899]

How do I open and power the logic board safely for flashing?

Open the case via eight sealed screws. Remove the logic board from mains and power it with an isolated bench supply at 3.3 V or 12 V via proper VDD headers. Avoid the convenient RX/TX header’s VDD, as it carries 12 V. Fully isolate USB and your laptop. “Do not attempt to tinker when plugged into mains.” These steps reduce shock risk and protect modules during serial capture or flashing. [Elektroda, stonacek, post #21289899]

How do I flash or swap the Tuya module (WBR3/CB3S)?

WBR3 flashing is now supported, but the process requires lifting the chip. Many users still swap to a CB3S pre‑flashed with OpenBeken, since it’s mostly pin‑compatible. Only six pins are used: GND, VCC, RX, TX, RST, EN. EN (pin 3) has 3.3 V; either use a module that tolerates it or cut the trace. The visible RX/TX/RST/GND header’s VDD is 12 V—do not use it. Isolate all equipment during work. [Elektroda, stonacek, post #21289899]

Which TuyaMCU dpIDs matter for control and telemetry?

Core dpIDs: 124 (ChargingOperation), 14 (work_mode), 18 (switch), 101 (DeviceState), 102–104 (Voltage/10), 105–107 (Current/10), 109 (kW/10), 110 (Temp/10), 112 (Session kWh/10), 113 (DeviceMaxSetA, read‑only), 114/115 (set current by capability), 118/119 (timers), 120–122 (timer strings), 123 (RFID). These cover start/stop, mode selection, currents, voltages, power, temperatures, energy, and status mapping for MQTT/HA. [Elektroda, stonacek, post #21289899]

What charging current range can I set, and does it stick?

Through the Tuya app, minimum is 8 A. Via TuyaMCU, some EVs accept as low as 6 A. You can change current dynamically during charging. After a 6 A session and replugging, the value can reset to 20 A. Values are integer steps, no floats. This behavior affects automations that persist current limits between sessions. [Elektroda, stonacek, post #21289899]

Can I change the device’s maximum supported current (DeviceMaxSetA)?

No. dpID 113 (DeviceMaxSetA) is read‑only and reflects hardware capability (e.g., 16 A, 32 A). Attempts to send a different enum don’t persist. You can set a higher charging current value, but the hardware likely enforces its limit. “Aside from the hardware clearly being scoped for the model … it doesn’t seem possible to do via TuyaMCU.” [Elektroda, stonacek, post #21506288]

Is the external CT clamp integrated into TuyaMCU data?

Captures suggest the external CT clamp for import/load balance is not integrated into TuyaMCU communications, despite data model references. Its app interaction is unclear. If you need load‑based throttling, manage amps via OpenBeken + MQTT and meter elsewhere. The author tracks EV power with an internal sensor and ignores the external CT. [Elektroda, stonacek, post #21289899]

How does the pilot signal behave on start/stop and during current changes?

The EVSE stops by pulling the pilot low to signal stop, then it opens the AC relay. The vehicle’s relays click before the charger’s relay when stopping. The charger remains at state B (vehicle detected), so issuing a new start command resumes charging. Current changes from 6–32 A adjust the pilot PWM dynamically during charging. [Elektroda, stonacek, post #21541705]

Any known edge cases with pilot timing or auto‑start?

One report: the unit starts charging immediately on plug‑in even if the car’s schedule disallows immediate charging, and the car stops it after ~10 seconds. Another: stopping on the EVSE cuts the three‑phase relay before the car stops, which is undesirable. These behaviors may affect session counting and vehicle wear. [Elektroda, kvogel, post #21541847]

Why don’t my string dpIDs (e.g., timers) show as text in OpenBeken?

OpenBeken channels are currently integers; TextField also sends integers. True string channels aren’t implemented. “Channels are currently integers, there is no string support yet.” You can still publish strings without channels using linkTuyaMCUOutputToChannel … MQTT, and DPs list should display strings, since it’s channel‑independent. [Elektroda, p.kaczmarek2, post #21292868]

Can I script custom dpID handling (like parsing strings) in OpenBeken?

Yes. Recent OpenBeken updates add Berry scripting for fully custom dpID processing. See the Berry guide and self tests for examples. Note that scripting can’t recover data never sent by TuyaMCU. Use Berry to transform, route, or combine dpIDs before MQTT/HTTP publishing for advanced automations. [Elektroda, p.kaczmarek2, post #21540509]

How do I control this charger from Home Assistant over MQTT?

Map OBK channels to dpIDs, then expose them as MQTT select/number entities. For example, map dpID 124 to a select (Charge/Stop/Ready) and dpID 14 to Working Mode. Map current to a number with 6–32 A range. Add an event handler to refresh after sending commands: OnChannelChange 24 tuyaMcu_sendQueryState. Then use HA templates to translate enums to labels. [Elektroda, stonacek, post #21600344]

What serial settings and scaling should I use in OpenBeken?

Set TuyaMCU baud rate to 9600. Map dpID 102 to Voltage_div10 and 105 to Current_div100 (multiply by 10 in link to get A). Map dpID 109 (kW/10) to Power and multiply by 100 to publish W. Map dpID 110 to Temperature_div10 and 112 to EnergyTotal_kWh_div100 with a ×10 multiplier in link. Query state after changes. [Elektroda, stonacek, post #21289899]

How do I start a charge if it seems stuck in “Ready”? (3‑step)

Set work_mode (dpID 14) to charge_now (0) to override timers.
Send Stop (1) on dpID 124 to end any stale session.
Send Charge (0) on dpID 124; auto‑refresh using OnChannelChange 24 tuyaMcu_sendQueryState. [Elektroda, stonacek, post #21600344]

Is there a workaround to publish Tuya string values today?

Yes. Use linkTuyaMCUOutputToChannel 120 MQTT to publish strings directly, bypassing channels. You can also inspect raw DP values via /cm?cmnd=DP when TuyaMCU flag 46 is enabled. This helps surface strings like timers (e.g., “00:04:20”) in your MQTT broker for Home Assistant parsing. [Elektroda, stonacek, post #21292395]