Minor change - Remove compatibility warning for LSC smart plug with BK7231N - #1750
Minor change - Remove compatibility warning for LSC smart plug with BK7231N#1750WolfWildWeird wants to merge 17 commits into
Conversation
Removed warning about compatibility with ESPHome for LSC smart plug 2578685.
✅ Deploy Preview for esphome-devices ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![esphome[bot]](https://avatars.githubusercontent.com/in/247347?s=60&v=4){kind=small}
There was a problem hiding this comment.
❌ Device configuration checks failed
The automated checks for the device pages in this pull request found 2 issues. Please address the items below and push an update — this review refreshes automatically and will be dismissed once the checks pass.
src/docs/devices/LSC-Plug-2578685/LSC-Plug-BK7231T.yaml
- line 24 — invalid yaml: duplicated mapping key
src/docs/devices/LSC-Plug-2578685/index.md
- line 46 — first yaml fence must reference
config.yaml(sawLSC-Plug-BK7231T.yaml)
Need help? See the Adding Devices guide.
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Added configuration for LSC Plug BK7231N including WiFi, sensors, and relay control.
Updated the LSC Plug configuration to set a specific name and friendly name. Added status LED configuration and modified WiFi settings.
Add "yaml file" intégration format Clean and check BK7231N YAML files to be more simple
Updated the fallback hotspot SSID for LSC Plug configuration.
Updated Wifi LSC Plug configuration.
Updated configuration instructions for BK7231T and BK7231N.
Removed unused logger, web_server, and captive_portal sections from the config. 🙄
Removed unnecessary line breaks in YAML code block.
|
Personal, public monologue (or Self Note) |
There was a problem hiding this comment.
❌ Device configuration checks failed
The automated checks for the device pages in this pull request found 2 issues. Please address the items below and push an update — this review refreshes automatically and will be dismissed once the checks pass.
`src/docs/devices/LSC-Plug-2578685/config.yaml````
- unable to read: ENOENT: no such file or directory, open '/home/runner/work/devices.esphome.io/devices.esphome.io/src/docs/devices/LSC-Plug-2578685/config.yaml```'
src/docs/devices/LSC-Plug-2578685/index.md
- line 46 — first yaml fence must reference
config.yaml(saw `config.yaml````)
Need help? See the Adding Devices guide.
Device configuration checks now pass — dismissing.
1 participant
Brief description of the changes
Type of changes
Checklist:
The rules below are enforced in CI by
npm run validate-devicesandnpm run validate-yaml. The full reference is at Configuration YAML files..yamlfile alongsideindex.mdand is pulled into the page with a fenced block of the form```yaml file=<name>.yaml— no inline yaml on added or modified pages.file=fence on the page referencesconfig.yaml.config.yamlis hardware-only: no top-levelapi:,ota:,mqtt:,web_server:,web_server_idf:,improv_serial:,captive_portal:,bluetooth_proxy:, ordashboard_import:, and noplatform: homeassistant,platform: mqtt, orplatform: templateanywhere in the tree.config.yamlhas awifi:block, it contains only radio tunables (country,power_save_mode,output_power, …) — nossid,password,networks,manual_ip,eap, oruse_address. An emptyap:block is allowed.!secret) onpassword:,*_password:, orpsk:keys, and no!secretreferences anywhere in any example yaml.made-for-esphome: truein frontmatter: at least one```yaml url=…fence points at a.yamlfile in the manufacturer's GitHub repo (github.com/<owner>/<repo>/(blob|raw)/<ref>/<path>.yamlor theraw.githubusercontent.comequivalent) so the rendered page shows the upstream config live.