CK-BL602-SWP1-01 configuration: eWeLink, Home Assistant, OpenBeken, energy metering

User question

how configure CK-BL602-SWP1-01?

Artificial Intelligence Response

Direct answer to the question

• Two reliable ways to “configure” CK‑BL602‑SWP1‑01: 1) Keep the stock eWeLink firmware and pair it in the eWeLink app; optionally integrate with Home Assistant via the SonoffLAN custom integration. This is quickest, but energy sensing and “local” behavior have limitations for this BL602 model. (github.com) 2) Replace the firmware with OpenBeken (OpenBL602) for full local control (MQTT/HA) and predictable sensor updates. Enter BL602 UART boot mode (strap GPIO8 HIGH at reset), flash over UART0 (RX=GPIO7, TX=GPIO16), then map pins in OpenBeken. (elektroda.com)
• Key points
  • Stock path: 2.4 GHz Wi‑Fi only; pair via eWeLink; HA via SonoffLAN “auto” mode works best. Some CK‑BL602 variants don’t expose “Energy” in HA and may update power only when the eWeLink mobile app is open. (github.com)
  • OpenBeken path: flash the BL602 image, join its AP, set Wi‑Fi, then assign pin roles for relay, LED, button, and (if present) power‑metering chip lines. (github.com)

Detailed problem analysis

• What this device is
  • CK‑BL602‑SWP1‑01 (often shown in HA/SonoffLAN as “(182)”) is a CoolKit/eWeLink smart plug/switch built on Bouffalo Lab BL602 (RISC‑V, Wi‑Fi/BLE). BL602 uses a ROM UART bootloader on UART0 and a BOOT strap pin to select flashing vs normal boot. (lupyuen.org)
• Stock firmware + HA integration behavior you should expect
  • Many users report:
  • “Local mode” in SonoffLAN frequently unavailable on CK‑BL602‑SWP1‑01; “auto” (LAN+cloud) or “cloud” works, but strictly “local” can make entities unavailable. (github.com)
  • Energy entity often missing for this exact model in HA. (github.com)
  • Live power/voltage/current values may stop updating unless the eWeLink mobile app is open; the app appears to “request” updates, then forwards them cloud‑side. This is a common pattern reported for BL602‑based devices. (forum.ewelink.cc)
  • Implication: If you need dependable, frequent, local power telemetry in HA, stock firmware may not meet requirements.
• OpenBeken (OpenBL602) as an engineering alternative
  • OpenBeken is an actively maintained, multi‑platform “Tasmota/ESPHome‑style” firmware with BL602 support and frequent releases, providing local MQTT/HTTP/HA integration. Flashing replaces the vendor stack and removes the cloud/app polling dependency for telemetry. (github.com)
• Electrical details that matter for flashing
  • BL602 UART boot mode: hold GPIO8 HIGH during reset/power‑up; ROM bootloader listens on UART0 (RX=GPIO7, TX=GPIO16). This differs from Espressif chips that often use a BOOT‑to‑GND strap. (lupyuen.org)
  • Tools: Bouffalo BLDevCube (GUI) or “bflb‑mcu‑tool” (CLI, PyPI) are reliable; start at 2,000,000 baud and fall back to 115,200 if handshakes fail. (elektroda.com)
• Current HA/SonoffLAN context for BL602 family
  • SonoffLAN maintainers periodically adjust power‑request handling for BL602‑based SKUs (e.g., CK‑BL602‑SWP1‑02 fixes in v3.9.3), underscoring that BL602 models need special handling and may vary by UIID. (github.com)

Current information and trends

• As of February 8, 2026:
  • eWeLink forum posts in January 2026 again note power telemetry from CK‑BL602‑SWP1‑01 ceasing in HA unless the phone app is active. (forum.ewelink.cc)
  • OpenBeken continues to publish BL602 binaries in regular releases. (newreleases.io)
  • SonoffLAN continues to refine support for BL602 variants; use the latest release if you stay stock. (github.com)

Supporting explanations and details

• Minimal, correct BL602 flashing wiring (3.3 V logic only)
  • USB‑UART TX → BL602 RX (GPIO7)
  • USB‑UART RX → BL602 TX (GPIO16)
  • 3V3 → VDD, GND → GND
  • Strap GPIO8 HIGH (to 3.3 V, e.g., 10 kΩ) and then reset/power‑up to enter bootloader. Remove strap for normal boot. (lupyuen.org)
• Why telemetry depends on the app with stock firmware
  • For several BL602 devices, the vendor firmware doesn’t push metering periodically by itself; the app triggers/polls and forwards to cloud. Without the app, HA may show only stale values. This isn’t a SonoffLAN bug; it’s device firmware behavior. (forum.ewelink.cc)

Ethical and legal aspects

• Safety with mains hardware
  • Never connect UART tools to a board that is simultaneously connected to AC. Use isolation and work only at extra‑low voltage when flashing. If you open the enclosure, you invalidate certifications and assume responsibility for electrical safety and compliance (UL/CE). Local electrical codes may prohibit modified mains devices in permanent installations.
• Cloud privacy
  • Keeping stock firmware means cloud connectivity by design; replacing firmware moves control/telemetry local but also shifts maintenance responsibility to you.

Practical guidelines

• Path A: Stock eWeLink + Home Assistant (no soldering) 1) Pair in eWeLink (2.4 GHz Wi‑Fi). Name your device. 2) In HA, install SonoffLAN via HACS; add the integration with your eWeLink account; leave Mode = auto. (github.com) 3) If device shows unavailable in “local” mode, switch back to “auto” or “cloud.” For missing Energy sensor on this model, that is expected. (github.com) 4) If power values don’t update, open the eWeLink app to trigger reporting; consider automations based on relay state rather than instantaneous power. (forum.ewelink.cc)
• Path B: Fully local with OpenBeken (engineering route) 1) Disassemble safely; identify BL602 pads: 3V3, GND, RX(GPIO7), TX(GPIO16), BOOT(GPIO8). 2) Wire USB‑UART (3.3 V). Strap GPIO8 HIGH; power cycle to enter bootloader. (lupyuen.org) 3) Flash OpenBeken BL602 image using BLDevCube or bflb‑mcu‑tool (try 2,000,000 baud; fall back to 115,200 if needed). (elektroda.com) 4) First boot: connect to the OpenBL602 AP; browse 192.168.4.1; set Wi‑Fi; then map pins:
  • Assign Relay, Button, LED roles; test by toggling to find the relay GPIO if undocumented.
  • If the plug has a metering IC (e.g., BL0937/HLW8012/BL0942), enable the matching driver and assign CF/CF1/SEL pins; set baud where applicable (e.g., BL0942). (newreleases.io) 5) Enable MQTT or use OpenBeken’s native HA discovery; verify state/telemetry update frequency from your broker/HA. (github.com) 6) Burn‑in test with a resistive load first; validate relay temperature rise and measurement stability before real use.

Possible disclaimers or additional notes

• Not all CK‑BL602‑SWP1‑01 PCBs use the same GPIO mapping for relay/LED/button; take clear PCB photos and trace if needed. OpenBeken has device lists/templates, but variants exist. (github.com)
• SonoffLAN updates sometimes improve BL602 handling for specific SKUs, but constraints of the stock firmware persist, especially for periodic power telemetry without the app. (github.com)

Suggestions for further research

• Share a high‑resolution PCB photo (both sides) to identify exact GPIOs for relay, LED, button, and metering IC pins.
• Check the OpenBeken devices list and recent releases for templates close to your board revision. (github.com)
• Review SonoffLAN README and open issues before relying on “local” mode for this SKU. (github.com)

Brief summary

• If you want a quick, cloud‑backed setup: use eWeLink and HA SonoffLAN in “auto” mode and accept energy telemetry limitations on CK‑BL602‑SWP1‑01. (github.com)
• If you need consistent, fully local telemetry and control: flash OpenBeken. For BL602, strap GPIO8 HIGH at reset to enter bootloader; use UART0 (RX=GPIO7, TX=GPIO16) to program; then map pins and enable the appropriate power‑meter driver. (lupyuen.org)

If you tell me whether you prefer the stock/cloud route or the OpenBeken/local route—and, ideally, share a PCB photo—I can provide exact pin roles and a ready‑to‑paste OpenBeken template for this board.

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.