logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
UV printer on your desk?
UV printer on your desk? Discover eufyMake E1 »
ADVERTISEMENT
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

[BK7231T] Anslut Halo LED (42cm/22w, 29cm/14w) programming guide/template

mblieden 1455 0

TL;DR

  • Anslut halo LED light teardown covers the 42 cm 22 W model and also applies to the 29 cm 14 W version.
  • The fixture uses a BK7231T chipset and was flashed over UART with OpenBK.
  • OpenBK version 1.17.398 was used successfully for the flashing process.
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • About Author
    mblieden
    Level 2  
    Offline 
    mblieden wrote 2 posts with. Been with us since 2024 year.
  • ADVERTISEMENT
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law
Today's popular

FAQ

TL;DR: For Anslut Halo LED owners, the 42 cm / 22 W teardown shows a BK7231T on a WB3S board, and the published template says "also applies" to the 29 cm / 14 W model. Flash OpenBK 1.17.398 over UART, then use pin 6 = PWM;5 and pin 8 = PWM;4 for the shared setup. [#20907082]

Why it matters: This gives a reusable starting point for flashing and templating two Anslut ceiling-light variants with one known-good OpenBK mapping.

Model Size Power Chip Board Shared template note
Anslut Halo LED 42 cm 22 W BK7231T WB3S Published teardown/template
Anslut Halo LED 29 cm 14 W BK7231T-based template claim WB3S-based template claim Marked as also applicable

Key insight: The strongest takeaway is template reuse: the post presents one BK7231T/WB3S JSON mapping and explicitly says it covers both the 42 cm / 22 W and 29 cm / 14 W lamps.

Quick Facts

  • The published device identity is Anslut Halo LED (42cm/22w, 29cm/14w), which directly ties one template to two lamp sizes and power ratings. [#20907082]
  • The controller section is identified as BK7231T on a WB3S board, which is the core hardware pairing the template targets. [#20907082]
  • The OpenBK pin map assigns pin 6 → PWM;5 and pin 8 → PWM;4, giving two explicit PWM outputs to match lamp channels. [#20907082]
  • The lamp was flashed over UART using OpenBK version 1.17.398, so the post documents a wired flashing path, not an OTA workflow. [#20907082]
  • Matching keywords include plafon, ceiling lamp, and plafond-led-024724, which help identify the correct product entry and template. [#20907082]

How do I flash an Anslut Halo LED 42cm 22W ceiling lamp with a BK7231T chip over UART using OpenBK 1.17.398?

You flash it the way the post documents: over UART with OpenBK 1.17.398. 1. Open the 42 cm / 22 W lamp and confirm the controller hardware. 2. Flash the BK7231T-based WB3S module over UART. 3. Apply the published template with pin 6 = PWM;5 and pin 8 = PWM;4. The thread does not include wiring photos or UART voltage details, so only that high-level process is confirmed. [#20907082]

What pin configuration should I use in OpenBK for the Anslut Halo LED 42cm/22W and 29cm/14W models with the WB3S board?

Use the published OpenBK mapping: pin 6 = PWM;5 and pin 8 = PWM;4. The JSON template names the chip as BK7231T and the board as WB3S, and the post says the same setup also applies to the 29 cm / 14 W model. No other GPIO assignments are listed in the thread. [#20907082]

Which parts of the Anslut Halo LED programming template are shared between the 42cm 22W model and the 29cm 14W model?

The shared parts are the device family, chip class, board type, and PWM pin mapping. The post states that the 42 cm / 22 W teardown “also applies to 29cm 14w model,” and the JSON keeps one hardware definition: BK7231T, WB3S, pin 6 = PWM;5, and pin 8 = PWM;4. That is the thread’s explicit compatibility scope. [#20907082]

What is the BK7231T chipset, and how is it used inside smart LED ceiling lights like the Anslut Halo LED?

"BK7231T" is a Wi‑Fi-enabled controller chip that runs the lamp’s smart functions, and in this thread it is the identified chipset inside the Anslut Halo LED. The post does not describe its internal architecture, but it does show that OpenBK was flashed onto a BK7231T-based light and paired with PWM outputs for lamp control. [#20907082]

What is a WB3S board in Tuya-style devices, and why does it matter when creating an OpenBK template?

"WB3S" is a plug-in controller board that carries the smart-device chipset, and in this thread it matters because the OpenBK template is written for that exact board designation. The JSON names the board as WB3S, so matching that board helps you apply the same pin map, especially pin 6 and pin 8. [#20907082]

Why is UART flashing used for the Anslut Halo LED instead of other flashing methods, and what steps are involved?

UART is used here because that is the only flashing method the post explicitly reports. The thread says the lamp was “Flashed over uart with version 1.17.398 of OpenBK,” but it does not compare UART with OTA, cloud, or other methods. The confirmed sequence is simple: open the lamp, flash over UART, then apply the published JSON mapping. [#20907082]

Where are the PWM channels mapped on the Anslut Halo LED template, and how do PWM;5 and PWM;4 affect the lamp output?

The PWM channels are mapped to pin 6 and pin 8. The template assigns pin 6 to PWM;5 and pin 8 to PWM;4, which means the lamp exposes two PWM-controlled outputs in OpenBK. The post does not label them as warm, cool, ring, or center channels, so only the numeric mapping is confirmed. [#20907082]

How can I identify whether my Anslut plafond LED light contains a BK7231T before attempting to flash it?

Open the lamp and inspect the control board, because the thread identifies the hardware by teardown. The post shows a teardown of the Anslut 42 cm / 22 W halo LED, says it also applies to the 29 cm / 14 W model, and names the chipset as BK7231T on a WB3S board. That hardware match is the thread’s basis for using the template. [#20907082]

What should I check if an Anslut Halo LED flashed with OpenBK does not respond correctly to the PWM pin assignments?

Check that you used the exact published pins and that your lamp matches the documented hardware. The thread gives only two PWM assignments, pin 6 = PWM;5 and pin 8 = PWM;4, for a BK7231T device on a WB3S board. If the lamp still behaves differently, the post provides no alternate pinout, which is the main limitation and failure case in this source. [#20907082]

How do I create or import a JSON device template for an Anslut Halo LED in OpenBK?

Create or import the template by copying the published JSON fields into OpenBK’s device template workflow. The thread provides the essential entries: vendor Anslut, device name, chip BK7231T, board WB3S, keywords, image, wiki link, and the two pin mappings. If you build from scratch, those fields are the reference set the post actually confirms. [#20907082]

What does OpenBK version 1.17.398 add or change when working with BK7231T-based lighting devices?

The thread does not list any new features or changes for version 1.17.398. It only confirms one concrete result: this Anslut Halo LED was flashed successfully over UART using OpenBK 1.17.398 on a BK7231T-based WB3S board. That makes the version a tested reference point, not a documented changelog in this source. [#20907082]

How does the Anslut Halo LED 42cm/22W compare with the 29cm/14W model when it comes to teardown layout and firmware template compatibility?

The thread presents them as template-compatible, not as separate hardware projects. It says the 42 cm / 22 W teardown “also applies to 29cm 14w model,” which is the clearest compatibility statement in the post. That means the shared OpenBK JSON is intended for both sizes, although the thread does not show a second teardown photo set. [#20907082]

Which safety precautions matter most when opening and programming a mains-powered Anslut ceiling lamp over UART?

The thread does not state any safety precautions. It only shows that a mains-powered ceiling lamp was opened, torn down, and flashed over UART, so the source confirms the operation happened but gives no step-by-step safety checklist, isolation method, or measurement values. For this FAQ, that absence is an important limit to note. [#20907082]

What keywords or product identifiers help match the correct OpenBK template for the Anslut plafond-led-024724 lamp?

Use the identifiers from the JSON and product link: Anslut, Halo LED, plafond-led-024724, plafon, and ceiling lamp. The thread also ties those terms to the two model sizes, 42 cm / 22 W and 29 cm / 14 W, which helps separate this template from other Anslut lights. Those keywords are the source-backed matching set. [#20907082]

If the published Anslut Halo LED template is incomplete, how can I verify the board pins and build a working template from scratch?

Verify the hardware first, then rebuild only the fields the post confirms. Check the module for BK7231T and WB3S, start from the two known outputs on pin 6 and pin 8, and keep the product identifiers aligned with the published JSON. The thread does not provide extra pins, so a scratch build from this source starts with just those confirmed mappings and expands only after board inspection. [#20907082]
ADVERTISEMENT