Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2025-02-02 23:31:30 +01:00
Code Issues Projects Releases Wiki Activity

Fix references

Browse Source
This commit is contained in:
Otto Winter 2019-02-07 18:07:16 +01:00
parent edeaa4ff34
commit e23dbe7fd9
No known key found for this signature in database
GPG Key ID: DB66C0BE6013F97E
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
changelog/v1.8.0.rst
View File

@ -57,7 +57,7 @@ This release mainly focuses on these new features:
- NFC/RFID Readers (:doc:`PN532 </components/pn532>` and :doc:`RDM6300 </components/rdm6300>`)
- New :doc:`ESP32 BLE integrations </components/esp32_ble_tracker>` like :doc:`Xiaomi MiFlora </components/sensor/xiaomi_miflora>`
- Core Changes like the addition of the :ref:`SPI bus <spi>` and :ref:`UART bus <uart>`
- Lots of new ::ref:`light effects <light-effects>` and support for cold-white/warm-white lights.
- Lots of new :ref:`light effects <light-effects>` and support for cold-white/warm-white lights.
- A LOGO FOR THIS PROJECT!!! Thanks a lot to `@messimore <https://github.com/messismore>`__ for
this visual masterpiece.

2
components/display/lcd_gpio.rst
View File

@ -60,7 +60,7 @@ Configuration variables:
Rendering Lambda
----------------
The LCD displays has a similar API to the fully fledged ::ref:`display-engine`, but it's only a subset as LCD displays
The LCD displays has a similar API to the fully fledged :ref:`display-engine`, but it's only a subset as LCD displays
don't have a concept of individual pixels. In the lambda you're passed a variable called ``it``
as with all other displays. In this case however, ``it`` is an ``LCDDisplay`` instance.

2
components/sensor/homeassistant.rst
View File

@ -29,7 +29,7 @@ Configuration variables:
- **name** (**Required**, string): The name of the sensor.
- **entity_id** (**Required**, string): The entity ID to import from Home Assistant.
- **id** (*Optional*,:ref:`config-id`): Manually specify the ID used for code generation.
- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.
- All other options from :ref:`Sensor <config-sensor>` and :ref:`MQTT Component <config-mqtt-component>`.
See Also

2
components/sensor/template.rst
View File

@ -37,7 +37,7 @@ Configuration variables:
Lambda to be evaluated every update interval to get the new value of the sensor
- **update_interval** (*Optional*, :ref:`config-time`): The interval to check the
sensor. Defaults to ``60s``.
- **id** (*Optional*,:ref:`config-id`): Manually specify the ID used for code generation.
- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.
- All other options from :ref:`Sensor <config-sensor>` and :ref:`MQTT Component <config-mqtt-component>`.
.. note::

2
components/text_sensor/homeassistant.rst
View File

@ -21,7 +21,7 @@ Configuration variables:
- **name** (**Required**, string): The name of the text sensor.
- **entity_id** (**Required**, string): The entity ID to import from Home Assistant.
- **id** (*Optional*,:ref:`config-id`): Manually specify the ID used for code generation.
- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.
- All other options from :ref:`Text Sensor <config-text_sensor>` and :ref:`MQTT Component <config-mqtt-component>`.
See Also

2
components/text_sensor/template.rst
View File

@ -33,7 +33,7 @@ Configuration variables:
Lambda to be evaluated every update interval to get the new value of the text sensor
- **update_interval** (*Optional*, :ref:`config-time`): The interval to check the
text sensor. Defaults to ``60s``.
- **id** (*Optional*,:ref:`config-id`): Manually specify the ID used for code generation.
- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.
- All other options from :ref:`Text Sensor <config-text_sensor>` and :ref:`MQTT Component <config-mqtt-component>`.
See Also