Skip to content

Update TH3D EZPlug Plus documentation - #1742

Draft
MidnightLink wants to merge 1 commit into
esphome:mainfrom
MidnightLink:patch-1
Draft

Update TH3D EZPlug Plus documentation#1742
MidnightLink wants to merge 1 commit into
esphome:mainfrom
MidnightLink:patch-1

Conversation

@MidnightLink

Copy link
Copy Markdown

Updated date published, corrected spelling mistakes, modified voltage divider value, adjusted configuration settings, and improved comments for clarity.

Brief description of the changes

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.

Updated date published, corrected spelling mistakes, modified voltage divider value, adjusted configuration settings, and improved comments for clarity.
@netlify

netlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Deploy Preview for esphome-devices ready!

Name Link
🔨 Latest commit bf46f23
🔍 Latest deploy log https://app.netlify.com/projects/esphome-devices/deploys/6a68048565399c0009ef3ef1
😎 Deploy Preview https://deploy-preview-1742--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.

@esphome esphome Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ 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/TH3D-EZPlug-Plus/index.md


Need help? See the Adding Devices guide.

@esphome
esphome Bot marked this pull request as draft July 28, 2026 01:24
@esphome

esphome Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

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.

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