Skip to content

Add LSC Smart Connect Smart Floor Lamp - #1754

Open
rauchiger-byte wants to merge 23 commits into
esphome:mainfrom
rauchiger-byte:main
Open

Add LSC Smart Connect Smart Floor Lamp#1754
rauchiger-byte wants to merge 23 commits into
esphome:mainfrom
rauchiger-byte:main

Conversation

@rauchiger-byte

@rauchiger-byte rauchiger-byte commented Jul 31, 2026

Copy link
Copy Markdown

Brief description of the changes

Adds device LSC Smart Connect Smart Floor Lamp (Article No. 3221699), a BK7238-based RGB floor lamp sold by Action.

Includes:

Confirmed GPIO pinout for the addressable main light, RGBW base lighting, IR receiver, and capacitive touch button
Step-by-step UART flashing guide
Hardware disassembly instructions with reference photos
UART programming pad pinout (RX1, TX1, GND)
ESPHome configuration for both independently controllable lighting zones
Product photo and internal PCB reference images

Type of changes

  • New device (a single device only — one device per pull request)
  • Update existing device
  • Removing a device
  • General cleanup
  • Other

Checklist:

The rules below are enforced in CI by npm run validate-devices and npm run validate-yaml. The full reference is at Configuration YAML files.

  • Adding a new device adds a single device only — one device per pull request.
  • Each example yaml lives in its own .yaml file alongside index.md and is pulled into the page with a fenced block of the form ```yaml file=<name>.yaml — no inline yaml on added or modified pages.
  • The first file= fence on the page references config.yaml.
  • config.yaml is hardware-only: no top-level api:, ota:, mqtt:, web_server:, web_server_idf:, improv_serial:, captive_portal:, bluetooth_proxy:, or dashboard_import:, and no platform: homeassistant, platform: mqtt, or platform: template anywhere in the tree.
  • If config.yaml has a wifi: block, it contains only radio tunables (country, power_save_mode, output_power, …) — no ssid, password, networks, manual_ip, eap, or use_address. An empty ap: block is allowed.
  • No passwords (literal or !secret) on password:, *_password:, or psk: keys, and no !secret references anywhere in any example yaml.
  • For pages with made-for-esphome: true in frontmatter: at least one ```yaml url=… fence points at a .yaml file in the manufacturer's GitHub repo (github.com/<owner>/<repo>/(blob|raw)/<ref>/<path>.yaml or the raw.githubusercontent.com equivalent) so the rendered page shows the upstream config live.

@netlify

netlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploy Preview for esphome-devices ready!

Name Link
🔨 Latest commit a362095
🔍 Latest deploy log https://app.netlify.com/projects/esphome-devices/deploys/6a6d3a1ea5fb990008d878ae
😎 Deploy Preview https://deploy-preview-1754--esphome-devices.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 100 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant