mthode-public/Home-Assistant-Dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated Creating Your First Device in Home Assistant ‐ ESPHome (markdown)

Dave Williams | DitroniX | G8PUO
2026-05-30 05:07:21 +01:00
parent cadebc9bfd
commit 4856809050
1 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Creating-Your-First-Device-in-Home-Assistant-‐-ESPHome.md
+14 -4
@@ -20,7 +20,9 @@ Using Home Assistant, with integrated ESPHome, you are easily able to create a n
Home Assistant (ESPHome), devices use .yaml code, which is initially flashed to the board via USB cable. Home Assistant (ESPHome), devices use .yaml code, which is initially flashed to the board via USB cable.
Once flashed (so the board is 'talking' to Home Assistant'), you can then subsequently easily reflash to the board using OTA, Over-The-Air, via Wi-Fi. USB re-flashing remains an option if needed. Once flashed (so the board is 'talking' to Home Assistant'), you can then subsequently easily reflash to the board using OTA, Over-The-Air, via Wi-Fi.
USB re-flashing remains an option if needed.
![Example of New Device](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Example%20of%20Device%20in%20Dash%20and%20Online.png) ![Example of New Device](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Example%20of%20Device%20in%20Dash%20and%20Online.png)
@@ -37,7 +39,7 @@ DitroniX External Components are located in
#### DitroniX Component Development #### DitroniX Component Development
During DitroniX Home Assistant Code Development, the required device 'Component', is simply connected to the DitroniX git repository, as an external component. During DitroniX Home Assistant Code Development, the required device 'Component', is simply connected to the DitroniX git (GitHub), repository, as an external component.
You could of course, always 'clone' this component and make your own. You could of course, always 'clone' this component and make your own.
@@ -74,7 +76,7 @@ ESPHome configuration for a device lives in a .yaml file. Within this YAML file
If not already configured, I would recommend you setup your 'secrets' file. Within YAML , this is `<<: !include ../secrets.yaml` If not already configured, I would recommend you setup your 'secrets' file. Within YAML , this is `<<: !include ../secrets.yaml`
To configure the secrets file, you need to To configure the secrets file, you need to:
![ESPHome Secrets](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Home%20Assistant%20-%20ESPHome%20-%20Secrets.png) ![ESPHome Secrets](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Home%20Assistant%20-%20ESPHome%20-%20Secrets.png)
@@ -84,7 +86,7 @@ Edit the Wi-Fi settings and lick 'Save'. That is it, all done!
#### YAML #### YAML
YAML is designed to be human-readable and easy to edit. However, like all programming languages, it has it oddities and quirky YAML is designed to be human-readable and easy to edit. However, like all programming languages, it has it's oddities and quirky gotchas.
- You can **only use spaces** for indentation - You can **only use spaces** for indentation
- Using the `**[Tab] key is strictly forbidden** and can cause parser errors or unexpected block merges - Using the `**[Tab] key is strictly forbidden** and can cause parser errors or unexpected block merges
@@ -179,3 +181,11 @@ You may now add the device to your normal Home Assistant dash and select require
![](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Example%20of%20added%20Device%20Info.png) ![](https://github.com/DitroniX/Home-Assistant-Dev/blob/main/Datasheets%20and%20Information/Example%20of%20added%20Device%20Info.png)
#### Finally, once your device is up and running, you can always tweak or edit the YAML code, then reflash, at any time.
You can even duplicate the code for another device.
Remember though, each device has it's own unique 'api key', 'ota password' and 'ap fallback password'. The rest of the code can be duplicated across your devices, where needed.