Add IQS 'internal' (#6417)

This commit is contained in:
Fabian Affolter 2018-10-01 22:45:52 +02:00 committed by GitHub
parent cf23a4e263
commit cbcba8f2a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
26 changed files with 31 additions and 9 deletions

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.38
ha_qa_scale: internal
---
The `alert` component is designed to notify you when problematic issues arise.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: "Other"
ha_qa_scale: internal
---
The `api` component exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This component depends on the [`http` component](/components/http/).

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Other
ha_release: 0.73
ha_qa_scale: internal
---
This component creates the endpoints for the [authentication system](/docs/authentication/) that is built into Home Assistant. There are no configuration options for this component directly as it relies on the auth system in the core.

View File

@ -11,11 +11,10 @@ logo: home-assistant.png
ha_category: Utility
ha_iot_class: "Local Polling"
ha_release: 0.57
ha_qa_scale: internal
---
The `random` binary sensor platform is creating random states (`true`, 1, `on`
or `false`, 0, `off`). This can be useful if you want to test automation rules.
It generates a new state every time it is polled.
The `random` binary sensor platform is creating random states (`true`, 1, `on` or `false`, 0, `off`). This can be useful if you want to test automation rules. It generates a new state every time it is polled.
## {% linkable_title Configuration %}
@ -34,6 +33,3 @@ name:
type: string
{% endconfiguration %}
See the [entity component options](/docs/configuration/platform_options/)
to control how often the main component polls the random binary sensor.
The default is 30 seconds.

View File

@ -11,6 +11,7 @@ ha_category: Utility
logo: home-assistant.png
ha_release: 0.28
ha_iot_class: "Local Push"
ha_qa_scale: internal
---
The `trend` platform allows you to create sensors which show the trend of

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Front end
ha_release: 0.39
ha_qa_scale: internal
---
The `config` component is designed to display panels in the frontend to configure and manage parts of Home Assistant.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Other
ha_qa_scale: internal
---
<p class='note'>

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.53
ha_qa_scale: internal
---
The `counter` component allows one to count occurrences fired by automations.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Other
ha_qa_scale: internal
---
Home Assistant can discover and automatically configure [zeroconf](https://en.wikipedia.org/wiki/Zero-configuration_networking)/[mDNS](https://en.wikipedia.org/wiki/Multicast_DNS) and [uPnP](https://en.wikipedia.org/wiki/Universal_Plug_and_Play) devices on your network. Currently the `discovery` component can detect:

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: "Other"
ha_qa_scale: internal
---
This offers the official frontend to control Home Assistant.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Automation
ha_qa_scale: internal
---
The `input_boolean` component allows the user to define boolean values that can be controlled via the frontend and can be used within conditions of automation. This can for example be used to disable or enable certain automations.

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.55
ha_qa_scale: internal
---
The `input_datetime` component allows the user to define date and time values

View File

@ -11,6 +11,7 @@ logo: home-assistant.png
ha_category: Automation
ha_release: 0.55
redirect_from: /components/input_slider/
ha_qa_scale: internal
---
<p class='note'>

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.13
ha_qa_scale: internal
---
The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selects a new item, a state transition event is generated. This state event can be used in an `automation` trigger.

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.53
ha_qa_scale: internal
---
The `input_text` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the value stored in the text box generate state events. These state events can be utilized as `automation` triggers as well. It can also be configured in password mode (obscured text).

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Other
ha_qa_scale: internal
---
The introduction component will show a card in the UI with 'Welcome Home!' and steps on how to get started. It will also print the same message to the console when starting up.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: "Other"
ha_qa_scale: internal
---
This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/components/device_tracker/) documentation.

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Other
ha_release: 0.23
ha_qa_scale: internal
---
The `persistent_notification` can be used to show a message on the frontend that has to be dismissed by the user.

View File

@ -11,6 +11,7 @@ ha_category: Utility
ha_release: 0.65
ha_iot_class: "Local Push"
logo: home-assistant.png
ha_qa_scale: internal
---
The `filter` platform enables sensors that process the states of other entities.

View File

@ -11,6 +11,7 @@ logo: home-assistant.png
ha_category: Utility
ha_iot_class: "Local Polling"
ha_release: 0.32
ha_qa_scale: internal
---
@ -48,6 +49,3 @@ unit_of_measurement:
type: string
{% endconfiguration %}
See the [entity component options][entity-docs] to control how often the main component polls the random sensor. The default is 30 seconds.
[entity-docs]: /docs/configuration/platform_options/

View File

@ -11,6 +11,7 @@ logo: home-assistant.png
ha_category: Utility
ha_iot_class: "Local Polling"
ha_release: "0.30"
ha_qa_scale: internal
---

View File

@ -10,6 +10,7 @@ footer: true
logo: home-assistant.png
ha_category: Automation
ha_release: 0.57
ha_qa_scale: internal
---
The `timer` component aims to simplify automations based on (dynamic) durations.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Other
ha_qa_scale: internal
---
The `updater` component will check daily for new releases. It will show a badge in the frontend if a new version is found. As [Hass.io](/hassio/) has its own schedule for release it doesn't make sense to use this component on Hass.io.

View File

@ -9,6 +9,7 @@ sharing: true
footer: true
logo: home-assistant.png
ha_category: Organization
ha_qa_scale: internal
---
Zones allow you to specify certain regions on earth (for now). When a device tracker sees a device to be within a zone, the state will take the name from the zone. Zones can also be used as a [trigger](/getting-started/automation-trigger/#zone-trigger) or [condition](/getting-started/automation-condition/#zone-condition) inside automation setups.

View File

@ -29,3 +29,7 @@ This is a solid integration that is able to survive poor conditions and can be c
Best of the best. The integration is completely async, meaning it's super fast and gives you an excellent user experience.
## {% linkable_title Internal 🏠 %}
All integrations which are marked as **internal** are part of Home Assistant.

View File

@ -37,6 +37,8 @@
🥇 (gold)
{% elsif page.ha_qa_scale == 'silver' %}
🥈 (silver)
{% elsif page.ha_qa_scale == 'internal' %}
🏠 (internal)
{% endif %}
</a>
</div>