diff --git a/_static/apple-touch-icon.png b/_static/apple-touch-icon.png new file mode 100644 index 000000000..4eff01ca2 Binary files /dev/null and b/_static/apple-touch-icon.png differ diff --git a/_static/favicon-16x16.png b/_static/favicon-16x16.png new file mode 100644 index 000000000..20664720d Binary files /dev/null and b/_static/favicon-16x16.png differ diff --git a/_static/favicon-32x32.png b/_static/favicon-32x32.png new file mode 100644 index 000000000..aa4a794a3 Binary files /dev/null and b/_static/favicon-32x32.png differ diff --git a/_static/favicon.ico b/_static/favicon.ico new file mode 100644 index 000000000..5aaaf3fb2 Binary files /dev/null and b/_static/favicon.ico differ diff --git a/_static/logo-full.png b/_static/logo-full.png new file mode 100644 index 000000000..454124f3e Binary files /dev/null and b/_static/logo-full.png differ diff --git a/_static/logo.png b/_static/logo.png new file mode 100644 index 000000000..554230067 Binary files /dev/null and b/_static/logo.png differ diff --git a/_static/safari-pinned-tab.svg b/_static/safari-pinned-tab.svg new file mode 100644 index 000000000..c94badf49 --- /dev/null +++ b/_static/safari-pinned-tab.svg @@ -0,0 +1,84 @@ + + + + +Created by potrace 1.11, written by Peter Selinger 2001-2013 + + + + + + diff --git a/conf.py b/conf.py index 9876430d8..a5a5ad09a 100644 --- a/conf.py +++ b/conf.py @@ -114,10 +114,23 @@ html_theme = 'alabaster' # documentation. # html_theme_options = { - 'github_user': 'OttoWinter', - 'github_repo': 'esphomelib', + # 'logo': 'logo-full.png', + 'logo_name': False, + 'touch_icon': 'apple-touch-icon.png', + # 'github_user': 'OttoWinter', + # 'github_repo': 'esphomelib', + 'show_related': False, + 'sidebar_collapse': True, + 'fixed_sidebar': True, } +html_logo = '_static/logo-full.png' +html_favicon = '_static/favicon.ico' +html_copy_source = True +html_show_sourcelink = False +html_last_updated_fmt = None +html_use_smartypants = False + # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". @@ -130,8 +143,9 @@ html_static_path = ['_static'] # refs: http://alabaster.readthedocs.io/en/latest/installation.html#sidebars html_sidebars = { '**': [ - 'relations.html', # needs 'show_related': True theme option to display + # 'about.html', 'searchbox.html', + 'localtoc.html', ] } diff --git a/esphomeyaml/components/binary_sensor/index.rst b/esphomeyaml/components/binary_sensor/index.rst index 06f8bfc85..a9e7cd1c8 100644 --- a/esphomeyaml/components/binary_sensor/index.rst +++ b/esphomeyaml/components/binary_sensor/index.rst @@ -66,6 +66,7 @@ They are similar to :ref:`Sensor Filters `. } else { return {}; } + - heartbeat: 5s Supported filters: @@ -81,6 +82,8 @@ Supported filters: - **lambda**: Specify any :ref:`lambda ` for more complex filters. The input value from the binary sensor is ``x`` and you can return ``true`` for ON, ``false`` for OFF, and ``{}`` to stop the filter chain. +- **heartbeat**: Periodically send out the last received value from the binary sensor with the given + interval. All state changes are still immediately published. Binary Sensor Automation ------------------------ diff --git a/esphomeyaml/components/esphomeyaml.rst b/esphomeyaml/components/esphomeyaml.rst index 510c6924e..b6573f707 100644 --- a/esphomeyaml/components/esphomeyaml.rst +++ b/esphomeyaml/components/esphomeyaml.rst @@ -22,7 +22,7 @@ Configuration variables: can use the same name. It can also only contain upper/lowercase characters, digits and underscores. - **platform** (**Required**, string): The platform your board is on, - either ``ESP32`` or ``ESP8266``. See :ref:`using_latest_arduino_framework`. + either ``ESP32`` or ``ESP8266``. See :ref:`esphomeyaml-arduino_version`. - **board** (**Required**, string): The board esphomeyaml should specify for platformio. For the ESP32, choose the appropriate one from `this list `__ @@ -31,22 +31,15 @@ Configuration variables: Advanced options: -- **library_uri** (*Optional*, string): You can manually specify the - `version of esphomelib `__ to - use here. Accepts all parameters of `platformio lib - install `__. - Use ``https://github.com/OttoWinter/esphomelib.git`` for the latest - (unstable) build. Defaults to the latest stable version. -- **simplify** (*Optional*, boolean): Whether to simplify the - auto-generated code, i.e. whether to remove unused variables, use - ``auto`` types and so on. Defaults to ``true``. -- **use_build_flags** (*Optional*, boolean): If esphomeyaml should manually set - build flags that specifically set what should be included in the binary. Most of - this is already done automatically by the linker but this option can help with - shrinking the firmware size while slowing down compilation. Defaults to ``true``. +- **esphomelib_version** (*Optional*): The version of the C++ `esphomelib framework `__ + to use. See :ref:`esphomeyaml-esphomelib_version`. +- **arduino_version** (*Optional*): The version of the arduino framework to link the project against. + See :ref:`esphomeyaml-arduino_version`. - **build_path** (*Optional*, string): Customize where esphomeyaml will store the build files for your node. By default, esphomeyaml puts all platformio project files under a folder ``/``, but you can customize this behavior using this option. +- **use_custom_code** (*Optional*, boolean): Whether to configure the project for writing custom components. + This sets up some flags so that custom code should compile correctly Automations: @@ -54,28 +47,113 @@ Automations: when the node starts. See :ref:`esphomeyaml-on_boot`. - **on_shutdown** (*Optional*, :ref:`Automation `): An automation to perform right before the node shuts down. See :ref:`esphomeyaml-on_shutdown`. +- **on_loop** (*Optional*, :ref:`Automation `): An automation to perform + on each ``loop()`` iteration. See :ref:`esphomeyaml-on_loop`. -.. _using_latest_arduino_framework: +.. _esphomeyaml-esphomelib_version: -Using the latest Arduino framework version ------------------------------------------- +``esphomelib_version`` +---------------------- -The default version of the arduino framework distributed through platformio is usually quite old -and the latest staging versions of the framework can in some cases increase stability a lot. +With the ``esphomelib_version`` parameter you can tell esphomeyaml which version of the C++ framework +to use when compiling code. For example, you can configure using the most recent (potentially unstable) +version of esphomelib straight from github. Or you can configure the use of a local copy of esphomelib +using this configuration option. -To use the latest version of the arduino framework with esphomeyaml, specify an URL pointing to -the staging version using the ``platform:`` parameter. - -For the ESP32, this URL is https://github.com/platformio/platform-espressif32.git#feature/stage. -And for the ESP8266, the URL is https://github.com/platformio/platform-espressif8266.git#feature/stage. +First, you can configure the use of either the latest esphomelib stable release (``latest``), +the latest development code from GitHub (``dev``), or a specific version number (``1.8.0``). .. code:: yaml # Example configuration entry esphomeyaml: - name: livingroom - platform: 'https://github.com/platformio/platform-espressif32.git#feature/stage' - board: nodemcu-32s + # ... + # Use the latest esphomelib stable release + esphomelib_version: latest + + # Or use the latest code from github + esphomelib_version: dev + + # Use a specific version number + esphomelib_version: 1.8.0 + +Alternatively, if you want to develop for esphomelib, you can download the +`latest code from GitHub `, extract the contents, +and point esphomeyaml to your local copy. Then you can modify the esphomelib to your needs or to fix bugs. + +.. code:: yaml + + # Example configuration entry + esphomeyaml: + # ... + # Use a local copy of esphomelib + esphomelib_version: + local: path/to/esphomelib + +And last, you can make esphomeyaml use a specific branch/commit/tag from a remote git repository: + +.. code:: yaml + + # Example configuration entry + esphomeyaml: + # ... + # Use a specific commit/branch/tag from a remote repository + esphomelib_version: + # Repository defaults to https://github.com/OttoWinter/esphomelib.git + repository: https://github.com/OttoWinter/esphomelib.git + branch: master + + esphomelib_version: + repository: https://github.com/somebody/esphomelib.git + commit: d27bac9263e8a0a5a00672245b38db3078f8992c + + esphomelib_version: + repository: https://github.com/OttoWinter/esphomelib.git + tag: v1.8.0 + +.. _esphomeyaml-arduino_version: + +``arduino_version`` +------------------- + +esphomelib uses the arduino framework internally to handle all low-level interactions like +initializing the WiFi driver and so on. Unfortunately, every arduino framework version often +has its own quirks and bugs, especially concerning WiFi performance. With the ``arduino_version`` +option you can tell esphomeyaml which arduino framework to use for compiling. + +.. code:: yaml + + # Example configuration entry + esphomeyaml: + # ... + # Default: use the recommended version, usually this equals + # the latest version. + arduino_version: recommended + + # Use the latest stable version + arduino_version: latest + + # Use the latest staged version from GitHub, try this if you have WiFi problems + arduino_version: dev + + # Use a specific version + arduino_version: 2.3.0 + +For the ESP8266, you currently can manually pin the arduino version to these values (see the full +list of arduino frameworks `here `__): + +* `2.4.2 `__ (the latest version) +* `2.4.1 `__ +* `2.4.0 `__ +* `2.3.0 `__ (tasmota uses this) + +.. warning:: + + Over-the-Air update passwords do not work with the arduino framework + version 2.3.0 + +For the ESP32, there's currently only one arduino framework version: +`1.0.0 `__. .. _esphomeyaml-on_boot: @@ -137,6 +215,21 @@ too many WiFi/MQTT connection attempts, Over-The-Air updates being applied or th Configuration variables: See :ref:`Automation `. +.. _esphomeyaml-on_loop: + +``on_loop`` +----------- + +This automation will be triggered on every ``loop()`` iteration (usually around every 16 milliseconds). + +.. code:: yaml + + esphomeyaml: + # ... + on_loop: + then: + # do something + See Also -------- diff --git a/esphomeyaml/components/i2c.rst b/esphomeyaml/components/i2c.rst index de77638f5..ca55613ba 100644 --- a/esphomeyaml/components/i2c.rst +++ b/esphomeyaml/components/i2c.rst @@ -30,7 +30,7 @@ Configuration variables: .. note:: If you're using the ESP32 and i2c frequently is showing errors in the logs, try with the latest - version of the Arduino framework. See :ref:`using_latest_arduino_framework` for information on how to do this. + version of the Arduino framework. See :ref:`esphomeyaml-arduino_version` for information on how to do this. See Also -------- diff --git a/esphomeyaml/components/sensor/custom.rst b/esphomeyaml/components/sensor/custom.rst index a1deec633..3ebf7e783 100644 --- a/esphomeyaml/components/sensor/custom.rst +++ b/esphomeyaml/components/sensor/custom.rst @@ -77,8 +77,7 @@ slow down build times a bit: esphomeyaml: # ... - use_build_flags: False - simplify: False + use_custom_code: True You've just created your first esphomelib sensor 🎉. It doesn't do very much right now and is never registered, but it's a first step. diff --git a/esphomeyaml/components/time.rst b/esphomeyaml/components/time.rst index 622ffa771..ab6d38c29 100644 --- a/esphomeyaml/components/time.rst +++ b/esphomeyaml/components/time.rst @@ -29,7 +29,8 @@ Configuration variables: `__ (warning: the format is quite complicated). esphomeyaml tries to automatically infer the timezone string based on the timezone of the computer that is running esphomeyaml, but this might not always be accurate. - +- **on_time** (*Optional*, :ref:`Automation `): Automation to run at specific intervals using + a cron-like syntax. See :ref:`time-on_time`. .. note:: @@ -163,6 +164,133 @@ with the current time representation of that format option. ``%%`` A literal ``%`` character % ============= ============================================================== ========================= +.. _time-on_time: + +``on_time`` +----------- + +This powerful automation can be used to run automations at specific intervals at +specific times of day. The syntax is a subset of the `crontab `__ syntax. + +There are two ways to specify time intervals: Either with using the ``seconds:``, ``minutes:``, ... +keys as seen below or using a cron expression like ``* /5 * * * *``. + +Basically, the automation engine looks at your configured time schedule every second and +evaluates if the automation should run. + +.. code:: yaml + + time: + - platform: sntp + # ... + on_time: + # Every 5 minutes + - seconds: 0 + minutes: /5 + then: + - switch.toggle: my_switch + + # Every morning on weekdays + - seconds: 0 + minutes: 30 + hours: 7 + days_of_week: MON-FRI + then: + - light.turn_on: my_light + + # Cron syntax, trigger every 5 minutes + - cron: '* /5 * * * *' + then: + - switch.toggle: my_switch + +Configuration variables: + +- **seconds** (*Optional*, string): Specify for which seconds of the minute the automation will trigger. + Defaults to ``*`` (all seconds). Range is from 0 to 59. +- **minutes** (*Optional*, string): Specify for which minutes of the hour the automation will trigger. + Defaults to ``*`` (all minutes). Range is from 0 to 59. +- **hours** (*Optional*, string): Specify for which hours of the day the automation will trigger. + Defaults to ``*`` (all hours). Range is from 0 to 23. +- **days_of_month** (*Optional*, string): Specify for which days of the month the automation will trigger. + Defaults to ``*`` (all hours). Range is from 1 to 31. +- **months** (*Optional*, string): Specify for which months of the year to trigger. + Defaults to ``*`` (all months). The month names JAN to DEC are automatically substituted. + Range is from 1 (January) to 12 (December). +- **days_of_week** (*Optional*, string): Specify for which days of the week to trigger. + Defaults to ``*`` (all days). The names SUN to SAT are automatically substituted. + Range is from 1 (Sunday) to 7 (Saturday). +- **cron** (*Optional*, string): Alternatively, you can specify a whole cron expression like + ``* /5 * * * *``. Please note years and some special characters like ``L``, ``#`` are currently not supported. + +- See :ref:`Automation `. + +In the ``seconds:``, ``minutes:``, ... fields you can use the following operators: + +- .. code:: yaml + + seconds: 0 + + An integer like ``0`` or ``30`` will make the automation only trigger if the current + second is **exactly** 0 or 30, respectively. +- .. code:: yaml + + seconds: 0,30,45 + + You can combine multiple expressions with the ``,`` operator. This operator makes it so that + if either one of the expressions separated by a comma holds true, the automation will trigger. + For example ``0,30,45`` will trigger if the current second is either ``0`` or ``30`` or ``45``. +- .. code:: yaml + + days_of_week: 2-6 + # same as + days_of_week: MON-FRI + # same as + days_of_week: 2,3,4,5,6 + # same as + days_of_week: MON,TUE,WED,THU,FRI + + The ``-`` (hyphen) operator can be used to create a range of values and is shorthand for listing all + values with the ``,`` operator. +- .. code:: yaml + + # every 5 minutes + seconds: 0 + minutes: /5 + + # every timestamp where the minute is 5,15,25,... + seconds: 0 + minutes: 5/10 + + The ``/`` operator can be used to create a step value. For example ``/5`` for ``minutes:`` makes an + automation trigger only when the minute of the hour is 0, or 5, 10, 15, ... The value in front of the + ``/`` specifies the offset with which the step is applied. + +- .. code:: yaml + + # Every minute + seconds: 0 + minutes: * + + Lastly, the ``*`` operator matches every number. In the example above, ``*`` could for example be substituted + with ``0-59``. + + +.. warning:: + + Please note the following automation would trigger for each second in the minutes 0,5,10,15 and not + once per 5 minutes as the seconds variable is not set: + + .. code:: yaml + + time: + - platform: sntp + # ... + on_time: + - minutes: /5 + then: + - switch.toggle: my_switch + + See Also -------- diff --git a/esphomeyaml/guides/automations.rst b/esphomeyaml/guides/automations.rst index 51df07406..e5b17d1ea 100644 --- a/esphomeyaml/guides/automations.rst +++ b/esphomeyaml/guides/automations.rst @@ -302,6 +302,7 @@ All Triggers - :ref:`binary_sensor.on_double_click ` - :ref:`esphomeyaml.on_boot ` - :ref:`esphomeyaml.on_shutdown ` +- :ref:`esphomeyaml.on_loop ` All Actions ~~~~~~~~~~~ diff --git a/esphomeyaml/guides/changelog.rst b/esphomeyaml/guides/changelog.rst index 9ebe24708..07892ff6a 100644 --- a/esphomeyaml/guides/changelog.rst +++ b/esphomeyaml/guides/changelog.rst @@ -13,9 +13,9 @@ Version 1.8.0 -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- `MAX7219`_ `LCD Display`_ `RCSwitch Integration`_ -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -|SPI Bus|_ |UART Bus|_ |RTC Time|_ +|SPI Bus|_ |UART Bus|_ |Real Time Clock|_ -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -`SPI Bus`_ `UART Bus`_ `RTC Time`_ +`SPI Bus`_ `UART Bus`_ `Real Time Clock`_ -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- |Uptime Sensor|_ |PN532|_ |RDM6300|_ -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- @@ -66,9 +66,9 @@ Version 1.8.0 .. |UART Bus| image:: /esphomeyaml/images/uart.svg :class: component-image .. _UART Bus: /esphomeyaml/components/uart.html -.. |RTC Time| image:: /esphomeyaml/images/clock-outline.svg +.. |Real Time Clock| image:: /esphomeyaml/images/clock-outline.svg :class: component-image -.. _RTC Time: /esphomeyaml/components/time.html +.. _Real Time Clock: /esphomeyaml/components/time.html .. |Uptime Sensor| image:: /esphomeyaml/images/timer.svg :class: component-image .. _Uptime Sensor: /esphomeyaml/components/sensor/uptime.html @@ -138,6 +138,8 @@ This release mainly focuses on these new features: - New :doc:`ESP32 BLE integrations ` like :doc:`Xiaomi MiFlora ` - Core Changes like the addition of the :ref:`SPI bus ` and :ref:`UART bus ` - Lots of new ::ref:`light effects ` and support for cold-white/warm-white lights. +- A LOGO FOR THIS PROJECT!!! Thanks a lot to `@messimore `__ for + this visual masterpiece. And if you find esphomelib great and have some of your projects using it, please do spread the word online (like `Christoph Dahlen did `__) @@ -147,18 +149,25 @@ awesome projects ☀️ Special thanks to all the contributors for this release: -- `@exxamalte `__ -- `@per1234 `__ -- `@nunofgs `__ -- `@lobradov `__ -- `@janpieper `__ -- `@aequitas `__ -- And last but not least: `@brandond `__ for his awesome work on the new - time component +- esphomeyaml: Add ‘only-generate’ parameter to generate command to only generate the C++ code `#84 `__ by `@apeeters `__ +- esphomeyaml: Fix esphomeyaml logs for tls enabled mqtt brokers `#118 `__ by `@johnerikhalse `__ +- esphomelib: Add Samsung IR codes `#141 `__ by `@escoand `__ +- esphomelib: Add support for SNTP and RTC `#76 `__ by `@brandond `__ +- esphomelib: Run travis jobs in parallel `#123 `__ by `@lobradov `__ +- esphomelib: Fix typo in dallas error message `#125 `__ by `@janpieper `__ +- esphomelib: Fix esphomelib examples `#124 `__ by `@lobradov `__ +- esphomelib: Fix panic in binary_sensor template `#111 `__ by `@nunofgs `__ +- esphomelib: Add ESP8266 library dependency to Arduino IDE instructions `#99 `__ by `@per1234 `__ +- esphomelib: Fixing I2C readings `#98 `__ by `@exxamalte `__ +- esphomedocs: Note added about resetting the ESP after serial upload before OTA upload `#14 `__ by `@exxamalte `__ +- esphomedocs: Add cookbook for dual relay cover `#10 `__ by `@aequitas `__ -And in more personal news, I'm currently getting ready for my trip to Japan 🇯🇵 to be part of team Austria -in this year's `international olympiad in informatics (IOI) `__ (hence also the relatively -short release notes). If you'll be attending too, come say hi :) +And in some more personal news, you might have noticed that I was not very active in online communications (github, discord, ...) +and that's partly been due to me concentrating on other stuff (university applications, work and +`this year's international olympiad of informatics `__). +But admittedly I must say being constantly active online is just very exhausting. As the next few weeks (or even months) +will leave me with little time to due to the start of my studies, I plan on primarily focusing on GitHub communications. +Plus I want to put an extra focus on reviewing PRs so that code submitters don't have to wait for weeks. Other notable changes ********************* @@ -180,28 +189,46 @@ Other notable changes - Fixed gas resistance readings from BME680s - Fixed HTU21D readings only working in very verbose mode - Sometimes the ESP would create a WiFi hotspot even though it was not configured to do so. That should be fixed now. +- You can now also have conditional actions. See :ref:`if_action`. +- The esphomeyaml dashboard and HassIO add-on now can be configured with a password. +- Fixed YAML anchors not working (you can now prefix keys with ``.`` to make esphomeyaml ignore them) +- Made Dallas and DHT temperature sensor a bit more reliable by making the code a bit more efficient and thus resolving some timing issues. +- A ``heartbeat`` filter has been added to :ref:`binary sensors `. +- The :ref:`esphomeyaml-on_loop` trigger has been added. +- esphomeyaml now know about more ESP8266/ESP32 boards, so now you can use the board-specific pin + names with even more board types. +- The mqtt client has a new option ``shutdown_message`` which will be sent when the board shuts down safely. + - In actions, instead of .. code:: yaml on_...: - switch.turn_on: - id: my_switch + then: + - switch.turn_on: + id: my_switch You can now write: .. code:: yaml on_...: - switch.turn_on: my_switch -- You can now also have conditional actions. See :ref:`if_action`. -- The esphomeyaml dashboard and HassIO add-on now can be configured with a password. -- Fixed YAML anchors not working (you can now prefix keys with ``.`` to make esphomeyaml ignore them) -- Made Dallas and DHT temperature sensor a bit more reliable by making the code a bit more efficient and thus resolving some timing issues. + then: + - switch.turn_on: my_switch + + Or even shorter: + + .. code:: yaml + + on_...: + - switch.turn_on: my_switch Breaking Changes **************** +- The :doc:`core configuration ` has been reworked a bit to a) + make using different arduino framework version easier and b) make editing your local esphomelib + copy easier. - Light Effects now need to be manually declared in the config and will no longer show up automatically. Please see :ref:`light-effects` - MAX6675 has been migrated to use the new SPI bus (and fixed!). Please see the docs for how to use it now. diff --git a/esphomeyaml/guides/contributing.rst b/esphomeyaml/guides/contributing.rst index 283d17534..be1800753 100644 --- a/esphomeyaml/guides/contributing.rst +++ b/esphomeyaml/guides/contributing.rst @@ -272,6 +272,9 @@ Standard for the esphomelib codebase: implementations. - Please test your changes :) +For editing a local copy of esphomelib within the esphomeyaml ecosystem please see +:ref:`esphomeyaml.esphomelib_version `option. + Contributing to esphomeyaml ^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/esphomeyaml/guides/faq.rst b/esphomeyaml/guides/faq.rst index 6a1cc13e6..bd0883d44 100644 --- a/esphomeyaml/guides/faq.rst +++ b/esphomeyaml/guides/faq.rst @@ -71,7 +71,7 @@ That's no good. Here are some steps that resolve some problems: - **Clean the platformio cache**: Sometimes the build cache leaves behind some weird artifacts. Try running ``platformio run -d -t clean``. - **Try with the latest Arduino framework version**: - See :ref:`this `. + See :ref:`this `. - **Still an error?** Please file a bug report over in the `esphomelib issue tracker `__. I will take a look at it as soon as I can. Thanks! @@ -123,18 +123,18 @@ takes up to 2 hours!). To install the dev version of esphomeyaml: - From docker: Run ``docker pull ottowinter/esphomeyaml:dev`` and use ``ottowinter/esphomeyaml:dev`` in all commands. -Next, if you want to use the latest version of esphomelib too: +Next, if you want to use the latest version of the esphomelib C++ framework too: .. code:: # Sample configuration entry esphomeyaml: name: ... - library_uri: 'https://github.com/OttoWinter/esphomelib.git' + esphomelib_version: dev # ... In some cases it's also a good idea to use the latest Arduino framework version. See -:ref:`this `. +:ref:`this `. Does esphomelib support [this device/feature]? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -166,7 +166,7 @@ Some steps that can help with the issue: - Use the most recent version of th arduino framework. The platformio arduino package always takes some time to update and the most recent version often includes some awesome - patches. See :ref:`using_latest_arduino_framework`. + patches. See :ref:`esphomeyaml-arduino_version`. - The issue seems to be happen with cheap boards more frequently. Especially the "cheap" NodeMCU boards from eBay sometimes have quite bad antennas. - Play around with the ``keepalive`` option of the :doc:`MQTT client `, sometimes diff --git a/esphomeyaml/v1.8.0.csv b/esphomeyaml/v1.8.0.csv index e75717583..8a5b529bd 100644 --- a/esphomeyaml/v1.8.0.csv +++ b/esphomeyaml/v1.8.0.csv @@ -8,7 +8,7 @@ RCSwitch Integration, components/switch/remote_transmitter.html#rcswitch-remote- SPI Bus, components/spi, spi.svg UART Bus, components/uart, uart.svg -RTC Time, components/time, clock-outline.svg +Real Time Clock, components/time, clock-outline.svg Uptime Sensor, components/sensor/uptime, timer.svg PN532, components/pn532, pn532.jpg