2019-02-16 23:25:23 +01:00
|
|
|
|
Getting Started with ESPHome through Hass.io
|
|
|
|
|
============================================
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2018-11-14 22:12:27 +01:00
|
|
|
|
.. seo::
|
2019-02-16 23:25:23 +01:00
|
|
|
|
:description: Getting Started guide for installing ESPHome as a Hass.io Add-on and creating a basic configuration.
|
2018-11-19 18:32:16 +01:00
|
|
|
|
:image: home-assistant.png
|
2018-11-14 22:12:27 +01:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
ESPHome is the perfect solution for creating custom firmwares for
|
2018-06-01 18:10:00 +02:00
|
|
|
|
your ESP8266/ESP32 boards. In this guide we’ll go through how to setup a
|
2018-11-26 16:50:50 +01:00
|
|
|
|
basic "node" by use of the Hass.io add-on.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
But first, here's a very quick introduction of how ESPHome works:
|
|
|
|
|
ESPHome is a *tool* which reads in YAML configuration files (just like Home Assistant)
|
2018-06-01 18:10:00 +02:00
|
|
|
|
and creates custom firmwares. The tool also has many helpers that simplify flashing devices
|
|
|
|
|
and aims to make managing your ESP boards as simple as possible. Once you have added devices
|
2019-02-16 23:25:23 +01:00
|
|
|
|
or sensors in ESPHome's configuration, they will even automatically show up in Home
|
2018-06-01 18:10:00 +02:00
|
|
|
|
Assistant's UI.
|
|
|
|
|
|
|
|
|
|
Installation
|
2018-10-12 16:33:22 +02:00
|
|
|
|
------------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
Installing the ESPHome Hass.io add-on is easy. Just navigate to the Hass.io
|
|
|
|
|
panel in your Home Assistant frontend and add the ESPHome add-on repository:
|
|
|
|
|
https://github.com/esphome/hassio
|
2019-01-16 11:30:50 +01:00
|
|
|
|
|
2018-06-01 18:10:00 +02:00
|
|
|
|
.. figure:: images/hassio_repo.png
|
|
|
|
|
|
|
|
|
|
After that, wait a bit until the add-on is installed (this can take a while) and
|
|
|
|
|
go to the add-on page. Start the add-on and then click "Open Web UI".
|
|
|
|
|
|
|
|
|
|
.. figure:: images/hassio_addon.png
|
|
|
|
|
:align: center
|
|
|
|
|
:width: 75.0%
|
|
|
|
|
|
|
|
|
|
You should now be greeted by a nice introduction wizard which will step you through
|
|
|
|
|
creating your first configuration.
|
|
|
|
|
|
|
|
|
|
.. figure:: images/hassio_start.png
|
|
|
|
|
:align: center
|
|
|
|
|
:width: 95.0%
|
|
|
|
|
|
|
|
|
|
Dashboard Interface
|
2018-10-12 16:33:22 +02:00
|
|
|
|
-------------------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
Assuming you created your first configuration file with the wizard, let's take a quick
|
2019-02-16 23:25:23 +01:00
|
|
|
|
tour of the ESPHome dashboard interface.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
.. figure:: images/hassio_interface.png
|
|
|
|
|
:align: center
|
|
|
|
|
:width: 95.0%
|
|
|
|
|
|
|
|
|
|
On the front page you will see all configurations for nodes you created. For each file,
|
|
|
|
|
there are three basic actions you can perform:
|
|
|
|
|
|
|
|
|
|
- **UPLOAD**: This compiles the firmware for your node and uploads it using any connected
|
2019-02-07 13:54:45 +01:00
|
|
|
|
USB device or, if no USB devices are connected, over-the-air using the :doc:`/components/ota`.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
.. warning::
|
|
|
|
|
|
2018-11-26 16:50:50 +01:00
|
|
|
|
The Hass.io Add-On is currently not capable of discovering new USB ports after the add-on
|
2018-06-01 18:10:00 +02:00
|
|
|
|
has started due to some docker restrictions. Please go to the add-on details page
|
2019-01-06 18:58:06 +01:00
|
|
|
|
and restart the add-on if a new USB device is not automatically found. If the USB device
|
|
|
|
|
is still not found, try changing the USB cable and restarting the add-on.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
- **SHOW LOGS**: With this command you can view all the logs the node is outputting. If a USB device is
|
2019-02-17 12:28:17 +01:00
|
|
|
|
connected, it will attempt to use the serial connection. Otherwise it will use the built-in OTA logs.
|
2019-02-16 23:25:23 +01:00
|
|
|
|
|
2018-06-01 18:10:00 +02:00
|
|
|
|
- **COMPILE**: This command compiles the firmware and gives you the option of downloading the generated
|
|
|
|
|
binary so that you can upload it yourself from your computer.
|
|
|
|
|
|
2018-11-05 22:03:08 +01:00
|
|
|
|
.. note::
|
|
|
|
|
|
|
|
|
|
If you're having problems with flashing over USB, you can always download the firmware using the
|
2019-02-16 23:25:23 +01:00
|
|
|
|
``COMPILE`` button and flash the firmware using :ref:`ESPHome-flasher <esphome-flasher>`.
|
2018-11-05 22:03:08 +01:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
The configuration files for ESPHome can be found and edited under ``<HOME_ASSISTANT_CONFIG>/esphome/``.
|
|
|
|
|
For example the configuration for the node in the picture above can be found
|
|
|
|
|
in ``/config/esphome/livingroom.yaml``.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
Now go ahead and use one of the :ref:`devices guides <devices>` to extend your configuration for the device you
|
2019-02-16 23:25:23 +01:00
|
|
|
|
intend to flash an ESPHome firmware onto. Then proceed with uploading the first firmware using the
|
2018-06-01 18:10:00 +02:00
|
|
|
|
upload button.
|
|
|
|
|
|
|
|
|
|
Adding some (basic) features
|
2018-10-12 16:33:22 +02:00
|
|
|
|
----------------------------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
So now you should have a file called ``/config/esphome/livingroom.yaml`` (or similar).
|
2019-02-07 13:54:45 +01:00
|
|
|
|
Go open that file in and add a :doc:`simple GPIO switch </components/switch/gpio>`
|
2018-06-01 18:10:00 +02:00
|
|
|
|
to the configuration like this:
|
|
|
|
|
|
2018-11-19 18:32:16 +01:00
|
|
|
|
.. code-block:: yaml
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
switch:
|
|
|
|
|
- platform: gpio
|
2018-10-20 15:10:26 +02:00
|
|
|
|
name: "Living Room Dehumidifier"
|
2018-06-01 18:10:00 +02:00
|
|
|
|
pin: 5
|
|
|
|
|
|
2019-01-06 18:58:17 +01:00
|
|
|
|
In above example, we're simply adding a switch that's called "Living Room Dehumidifier" (could control
|
2018-06-01 18:10:00 +02:00
|
|
|
|
anything really, for example lights) and is connected to the pin ``GPIO5``.
|
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
Now when you go to the Home Assistant "Integrations" screen (under "Configuration" panel), you
|
|
|
|
|
should see the ESPHome device show up in the discovered section (can take up to 5 minutes).
|
|
|
|
|
Alternatively, you can manually add the device by clicking "CONFIGURE" on the ESPHome integration
|
|
|
|
|
and entering "<NODE_NAME>.local" as the host.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-07 13:54:45 +01:00
|
|
|
|
.. figure:: /components/switch/images/gpio-ui.png
|
2018-06-01 18:10:00 +02:00
|
|
|
|
:align: center
|
|
|
|
|
:width: 75.0%
|
|
|
|
|
|
|
|
|
|
After the first upload, you will probably never need to use the USB
|
2019-02-16 23:25:23 +01:00
|
|
|
|
cable again, as all features of ESPHome are enabled remotely as well.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
No more opening hidden boxes stowed in places hard to reach. Yay!
|
|
|
|
|
|
|
|
|
|
Adding A Binary Sensor
|
2018-10-12 16:33:22 +02:00
|
|
|
|
----------------------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
Next, we’re going to add a very simple binary sensor that periodically
|
|
|
|
|
checks a GPIO pin whether it’s pulled high or low - the :doc:`GPIO Binary
|
2019-02-07 13:54:45 +01:00
|
|
|
|
Sensor </components/binary_sensor/gpio>`.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2018-11-19 18:32:16 +01:00
|
|
|
|
.. code-block:: yaml
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
binary_sensor:
|
|
|
|
|
- platform: gpio
|
|
|
|
|
name: "Living Room Window"
|
|
|
|
|
pin:
|
|
|
|
|
number: 16
|
|
|
|
|
inverted: True
|
|
|
|
|
mode: INPUT_PULLUP
|
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
This is an advanced feature of ESPHome, almost all pins can
|
2018-06-01 18:10:00 +02:00
|
|
|
|
optionally have a more complicated configuration schema with options for
|
|
|
|
|
inversion and pinMode - the :ref:`Pin Schema <config-pin_schema>`.
|
|
|
|
|
|
|
|
|
|
This time when uploading, you don’t need to have the device plugged in
|
2019-02-07 13:54:45 +01:00
|
|
|
|
through USB again. The upload will magically happen :doc:`"over the air" </components/ota>`.
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-07 13:54:45 +01:00
|
|
|
|
.. figure:: /components/binary_sensor/images/gpio-ui.png
|
2018-06-01 18:10:00 +02:00
|
|
|
|
:align: center
|
|
|
|
|
:width: 75.0%
|
|
|
|
|
|
|
|
|
|
Where To Go Next
|
2018-10-12 16:33:22 +02:00
|
|
|
|
----------------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
Great 🎉! You’ve now successfully setup your first ESPHome project
|
|
|
|
|
and uploaded your first ESPHome custom firmware to your node. You’ve
|
2018-06-01 18:10:00 +02:00
|
|
|
|
also learned how to enable some basic components via the configuration
|
|
|
|
|
file.
|
|
|
|
|
|
2019-02-16 23:25:23 +01:00
|
|
|
|
So now is a great time to go take a look at the :doc:`Components Index </index>`.
|
|
|
|
|
Hopefully you’ll find all sensors/outputs/… you’ll need in there. If you’re having any problems or
|
2018-06-01 18:10:00 +02:00
|
|
|
|
want new features, please either create a new issue on the `GitHub issue
|
2019-02-16 23:25:23 +01:00
|
|
|
|
tracker <https://github.com/esphome/issues/issues>`__ or find us on the
|
|
|
|
|
`Discord chat <https://discord.gg/KhAMKrd>`__ (also make sure to read the :doc:`FAQ <faq>`).
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
|
|
|
|
See Also
|
2018-10-12 16:33:22 +02:00
|
|
|
|
--------
|
2018-06-01 18:10:00 +02:00
|
|
|
|
|
2019-02-07 13:54:45 +01:00
|
|
|
|
- :doc:`ESPHome index </index>`
|
2018-06-01 18:10:00 +02:00
|
|
|
|
- :doc:`getting_started_command_line`
|
2019-02-07 13:54:45 +01:00
|
|
|
|
- :ghedit:`Edit`
|