Revise eWelink Inching Relay documentation

[nouser2013]

Added note indicating a change in the hardware making the use of ESPhome impossible. Link to further information added.

Brief description of the changes

Added link to description of newer hardware -incompatible with ESPhome- on this device.

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]

✅ Deploy Preview for esphome-devices ready!

Name	Link
🔨 Latest commit	7917bfb
🔍 Latest deploy log	https://app.netlify.com/projects/esphome-devices/deploys/6a3528aeec8dcb0008eb4ce5
😎 Deploy Preview	https://deploy-preview-1679--esphome-devices.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
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.

[Copilot]

Pull request overview

Updates the device documentation for the eWelink 5V/12V Inching Relay to warn readers that newer hardware revisions are no longer ESP-based and therefore cannot run ESPHome.

Changes:

• Adds an “IMPORTANT” note describing the newer Bouffalo-based variant (e.g., BL602 / EWL-B04) and ESPHome incompatibility.
• Links to an external thread with more details on the hardware change and alternatives.

[esphome]

❌ Device configuration checks failed

The automated checks for the device pages in this pull request found 1 issue. Please address the items below and push an update — this review refreshes automatically and will be dismissed once the checks pass.

src/docs/devices/eWelink-5V-12V-Inching-Relay/index.md

• line 46 — added or modified device pages must use file=- or url=-based yaml fences — inline yaml is no longer accepted; move the config into a sibling yaml file and reference it. See https://devices.esphome.io/devices/adding-devices#configuration-yaml-files

---

Need help? See the Adding Devices guide.

[esphome]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.