Flash OpenBeken Firmware on Ledvance Sun@Home Lamp

User question

Step-by-step instructions on how to flash OpenBeken to a Ledvance Sun@Home lamp

Artificial Intelligence Response

Direct answer to the question

• Shortest path for most Ledvance Sun@Home lamps (Planon Plus panels, Panan Floor, etc.) is OTA flashing with Tuya-cloudcutter, then finishing setup in OpenBeken. If OTA is blocked on your unit, use a UART wired flash (3.3 V) with BK7231 GUI Flash Tool or ltchiptool.
• Typical Sun@Home/Planon Plus driver uses a Tuya WB3S (BK7231T). After flashing, set pins: P6 = PWM_n (Warm), P8 = PWM (Cool), then enable the appropriate LED flags. Confirmed cloudcutter profiles and pairing steps are below. (elektroda.com)

Key points

• Try OTA first (no disassembly). Use “oem_bk7231s_light_ty” with BK7231T on firmware 1.1.6 or 2.9.16; put lamp in slow‑blink pairing mode by power‑cycling 10× at ~1 Hz. (elektroda.com)
• If OTA fails, wire TX1/RX1/GND/3V3 (+ optional CEN reset) and flash with BK7231 GUI Flash Tool or ltchiptool; back up the full 2 MB before writing. (github.com)
• Current OpenBeken stable (Dec 5, 2025) is 1.18.225; use the BK7231T or BK7231N build to match your module. (github.com)

Detailed problem analysis

• Platform inside Sun@Home: Community teardowns of LEDVANCE SMART+/Sun@Home Planon Plus show a Tuya WB3S module (BK7231T) on the driver PSU board. The same driver has been observed in Sun@Home variants, so steps and pin mapping carry over. OTA flashing succeeded on stock firmwares 1.1.6 and 2.9.16 using Tuya‑cloudcutter. (elektroda.com)
• Why OTA first: It avoids mains exposure and soldering, and has been validated on these panels; after takeover, OpenBeken’s web UI exposes pin/flag configuration for Tunable White. (elektroda.com)
• When wired is required: If the vendor firmware is patched or your model differs, use UART flashing. LibreTiny docs detail stable wiring (TX1=P11, RX1=P10, reset via CEN; powered from a solid 3.3 V supply). BK7231 GUI Flash Tool automates backup + write and supersedes older bkWriter/hid_download_py. (docs.libretiny.eu)
• Post‑flash mapping for Sun@Home/Planon Plus: two PWM channels (CCT). Warm is inverted on P6, hence PWM_n; Cool is P8. Community templates confirm this CCT wiring and explain why PWM_n is required. (elektroda.com)

Current information and trends

• Confirmed cloudcutter workflow and profile for LEDVANCE panels; documented slow‑blink (10 × 0.5 s off / 0.5 s on) pairing timing. (elektroda.com)
• OpenBeken release cadence remains active; latest stable as of December 5, 2025 is 1.18.225. Prefer latest stable binaries for BK7231T/N. (github.com)
• Tools: BK7231 GUI Flash Tool (Windows/Mono) consolidates backup, flash, and GPIO extraction; ltchiptool provides cross‑platform CLI for dumps/writes. (github.com)

Supporting explanations and details

• PWM vs PWM_n: Some Tuya drivers wire a MOSFET high‑side/low‑side such that duty must be inverted. OpenBeken’s PWM_n role corrects slider behavior (0% truly off). Templates for LEDVANCE panels show P6 = PWM_n (Warm), P8 = PWM (Cool). (elektroda.com)
• Reset and boot capture: BK72xx uses UART1 for flashing; asserting CEN low briefly (or power‑cycling 3.3 V) lets the flasher “get bus.” Good cabling and a stable 3.3 V source matter more than baud rate. (docs.libretiny.eu)

Ethical and legal aspects

• Flashing third‑party firmware voids the manufacturer’s warranty, and OTA takeover permanently detaches the device from the vendor cloud. Proceed only if you accept this. (reddit.com)
• Work de‑energized; these luminaires are mains powered. If you must open the driver for UART access, ensure isolation and discharged capacitors. (General safety standards apply; see vendor safety notes.) (ledvance.com)

Practical guidelines

Step‑by‑step (Method A: OTA with Tuya‑cloudcutter) 1) Prepare environment

• Linux host (PC or Raspberry Pi) with Wi‑Fi AP capability; install and follow cloudcutter’s setup. (elektroda.com) 2) Put lamp in slow‑blink pairing mode
• Power cycle exactly 10 times at about 1 Hz (≈0.5 s OFF, 0.5 s ON). You should see slow blinking afterward. If timing is off, repeat. (elektroda.com) 3) Run cloudcutter
• Select BK7231T / “oem_bk7231s_light_ty” for Planon Plus/Sun@Home driver with WB3S (BK7231T). Let cloudcutter perform the exploit and install OpenBeken. (elektroda.com) 4) First boot and Wi‑Fi
• Connect to the OpenBeken AP, browse to 192.168.4.1, enter your 2.4 GHz SSID/password, reboot. (elektroda.com) 5) Configure pins and flags
• In Web UI: set P6 = PWM_n (Warm), P8 = PWM (Cool). If your unit follows the common LEDVANCE mapping, this will yield correct CW/WW control. Enable the LED CW mode flag if required by your UI/driver behavior; test sliders. (elektroda.com) 6) Update to latest OBK
• Use OBK’s OTA page to update to the current stable build for BK7231T. (github.com)

Step‑by‑step (Method B: Wired UART if OTA is blocked) 1) Disassemble safely

• Remove panel/floor‑lamp housing to reach the driver PCB. Identify the Tuya module (WB3S=BK7231T or CB2S=BK7231N). Disconnect from mains. (elektroda.com) 2) Wire UART
• Connect USB‑UART (3.3 V logic) to BK7231 UART1: PC RX → TX1 (P11), PC TX → RX1 (P10), GND→GND, and power with a stable 3.3 V. Optionally bring out CEN for reset. (docs.libretiny.eu) 3) Backup flash
• With ltchiptool or BK7231 GUI Flash Tool, make a full 2 MB dump before any writes. (docs.libretiny.eu) 4) Flash OBK
• Use BK7231 GUI Flash Tool “Backup and flash new” (select BK7231T or N to match your module) or ltchiptool write. Reset (CEN low briefly) when tool waits for “getting bus.” (github.com) 5) First boot + config
• As in OTA method: connect to OBK AP, add Wi‑Fi, set pins P6 = PWM_n (Warm), P8 = PWM (Cool), test, then OTA‑update to the latest stable. (elektroda.com)

Troubleshooting

• OTA exploit fails: Re‑do the 10× slow‑blink sequence precisely; if still failing your firmware may be patched—fall back to UART. (elektroda.com)
• No serial link: Use a better 3.3 V supply; many USB‑UART modules cannot source enough current. Verify RX/TX crossed and try resetting via CEN during “get bus.” (docs.libretiny.eu)
• Warm/Cool reversed or dimming odd: Swap PWM roles or ensure PWM_n on P6; enable the LED CW mode flag if your driver expects “alternate CW.” (elektroda.com)
• After first boot, can’t find device: Connect to its AP again or check your router’s DHCP leases; then update via OBK’s OTA page to current stable. (github.com)

Possible disclaimers or additional notes

• Some LEDVANCE Wi‑Fi devices are Tuya‑based but vendor‑locked; the Sun@Home Planon/Panan families documented here were successfully freed with cloudcutter, but model/firmware variations exist. If your unit differs (e.g., different module), pin mapping may change. (reddit.com)
• Older tooling (bkWriter 1.60 / hid_download_py) is now superseded by BK7231 GUI Flash Tool—prefer the newer workflow. (github.com)

Suggestions for further research

• Check OpenBeken’s Supported Devices/teardowns list and forum threads for your exact GTIN/model to confirm module type and a ready‑made template. (openbekeniot.github.io)
• Review LibreTiny BK72xx notes for power/grounding best practices during flashing, and for dual‑UART (logs vs flashing) guidance. (docs.libretiny.eu)

Brief summary

• For Ledvance Sun@Home lamps/panels, first attempt OTA flashing with Tuya‑cloudcutter using the documented slow‑blink (10× at ~1 Hz) and BK7231T “oem_bk7231s_light_ty” profile; this is proven to work on Planon Plus and applies to Sun@Home variants sharing the same driver. Post‑flash, set P6=PWM_n (Warm) and P8=PWM (Cool) and finish OTA‑updating OpenBeken to the latest stable (1.18.225 on Dec 5, 2025). If OTA is patched, wire up UART1 at 3.3 V and use BK7231 GUI Flash Tool or ltchiptool, backing up the full 2 MB first. (elektroda.com)

If you can share the exact Sun@Home model (e.g., Planon Plus 300×300, 600×600, or Panan Floor) and a photo of the driver PCB/module, I can provide the exact pin/flag template and confirm whether your firmware is likely cloudcutter‑flashable.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.