Merge branch 'current' into next

This commit is contained in:
Otto Winter 2019-06-03 15:23:24 +02:00
commit 8f53910677
No known key found for this signature in database
GPG Key ID: DB66C0BE6013F97E
7 changed files with 27 additions and 15 deletions

View File

@ -38,7 +38,7 @@ PROJECT_NAME = "ESPHome"
# could be handy for archiving the generated documentation or if some version # could be handy for archiving the generated documentation or if some version
# control system is used. # control system is used.
PROJECT_NUMBER = 1.13.2 PROJECT_NUMBER = 1.13.3
# Using the PROJECT_BRIEF tag one can provide an optional one line description # Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer a # for a project that appears at the top of each page and should give viewer a

View File

@ -1,5 +1,5 @@
ESPHOME_PATH = ../esphome ESPHOME_PATH = ../esphome
ESPHOME_REF = v1.13.2 ESPHOME_REF = v1.13.3
.PHONY: html html-strict cleanhtml deploy help webserver Makefile netlify netlify-api api netlify-dependencies svg2png copy-svg2png .PHONY: html html-strict cleanhtml deploy help webserver Makefile netlify netlify-api api netlify-dependencies svg2png copy-svg2png

View File

@ -1 +1 @@
1.13.2 1.13.3

View File

@ -146,6 +146,19 @@ Release 1.13.2 - May 31
- esphome: Fix i2c setup priority :esphomepr:`585` - esphome: Fix i2c setup priority :esphomepr:`585`
- docs: add note for asynchronously update of adc :docspr:`259` by :ghuser:`escoand` - docs: add note for asynchronously update of adc :docspr:`259` by :ghuser:`escoand`
Release 1.13.3 - June 1
-----------------------
- esphome: List the correct boards when building for ESP32 :esphomepr:`589` by :ghuser:`macourteau`
- esphome: Fix addressable effects :esphomepr:`590`
- esphome: Fix scripts circular dependency :esphomepr:`591`
- esphome: Fix timezone detection for timezones without daylight savings time :esphomepr:`586`
- esphome: Fix remote_receiver binary_sensor :esphomepr:`592`
- docs: Add missing filter name for ct_clamp :docspr:`258` by :ghuser:`jesserockz`
- esphome: Fix flicker light effect turning itself off :esphomepr:`594`
- esphome: Fix medium fan speed :esphomepr:`595`
- esphome: Fix dashboard for Py3 installs :esphomepr:`596`
All changes All changes
----------- -----------

View File

@ -147,17 +147,16 @@ is already set up. You can however change this using the ``priority`` parameter.
Configuration variables: Configuration variables:
- **priority** (*Optional*, float): The priority to execute your custom initialization code. A higher value (for example - **priority** (*Optional*, float): The priority to execute your custom initialization code. A higher value
positive values) mean a high priority and thus also your code being executed earlier. So for example negative priorities means a high priority and thus also your code being executed earlier. Please note this is an esphome-internal
are executed very late. Defaults to ``-10``. Priorities (you can use any value between them too): value and any change will not be marked as a breaking change. Defaults to ``-10``. Priorities (you can use any value between them too):
- ``100``: This is where all hardware initialization of vital components is executed. For example setting switches - ``800.0``: This is where all hardware initialization of vital components is executed. For example setting switches
to their initial state. to their initial state.
- ``50.0``: This is where most sensors are set up. - ``600.0``: This is where most sensors are set up.
- ``10``: At this priority, WiFi is initialized. - ``250.0``: At this priority, WiFi is initialized.
- ``7.5``: MQTT initialization takes place at this priority. - ``200.0``: Network connections like MQTT/native API are set up at this priority.
- ``-5.0``: The individual frontend counterparts for the backend components are configured at this priority - ``-100.0``: At this priority, pretty much everything should already be initialized.
- ``-10.0``: At this priority, pretty much everything should already be initialized.
- See :ref:`Automation <automation>`. - See :ref:`Automation <automation>`.

View File

@ -6,8 +6,8 @@ Integration Sensor
:image: sigma.png :image: sigma.png
The ``integration`` sensor is a helper sensor that can integrate values from other sensors over The ``integration`` sensor is a helper sensor that can integrate values from other sensors over
time. This can for example be useful to integrate the values of a water flow sensor (in m^2/s) over time. This can for example be useful to integrate the values of a water flow sensor (in m^3/s) over
time (result is in m^2). time (result is in m^3).
This component can be considered a more-generic version of the :doc:`total_daily_energy`. This component can be considered a more-generic version of the :doc:`total_daily_energy`.

View File

@ -72,7 +72,7 @@ author = 'Otto Winter'
# The short X.Y version. # The short X.Y version.
version = '1.13' version = '1.13'
# The full version, including alpha/beta/rc tags. # The full version, including alpha/beta/rc tags.
release = '1.13.2' release = '1.13.3'
# The language for content autogenerated by Sphinx. Refer to documentation # The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages. # for a list of supported languages.