aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorKaufman Home Automation <[email protected]>2022-12-08 10:53:25 -0700
committerGitHub <[email protected]>2022-12-08 10:53:25 -0700
commitb9b04f96932c2d54de52b6175ee0f415131f9f02 (patch)
tree4ebefd75fef21b18fa2f5225953eac32627332b4
parentf488a11c5f822341277604d7661f481cfa5bdacf (diff)
downloadPLF10-b9b04f96932c2d54de52b6175ee0f415131f9f02.tar.gz
PLF10-b9b04f96932c2d54de52b6175ee0f415131f9f02.zip
rename for consistency
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 87dadb0..852a2d2 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
The recommended way to import a plug into your ESPHome dashboard is through the dashboard import feature. The plug should show up in the ESPHome dashboard as being available to adopt. Below is the minimum necessary yaml, which can be used to manually add your device instead. Change the name and friendly_name substitutions to fit your use case. Adding a [`use_address:`](https://esphome.io/components/wifi.html?highlight=use_address#configuration-variables) under `wifi:` will allow you to point the ESPHome dashboard to the device on your network for flashing OTA.
-The friendly_name substitution is recommended and will not be automatically created by the ESPHome dashboard import. If you use the ESPHome dashboard adopt feature, we recommend that you add a friendly_name substitution to rename all of the entities in Home Assistant in one line of yaml.
+The friendly_name substitution is recommended and will not be automatically created by the ESPHome dashboard import. If you use the ESPHome dashboard import feature, we recommend that you add a friendly_name substitution to rename all of the entities in Home Assistant in one line of yaml.
```
substitutions: