diff --git a/source/_components/counter.markdown b/source/_components/counter.markdown index 123ebee79d9..7c64913880b 100644 --- a/source/_components/counter.markdown +++ b/source/_components/counter.markdown @@ -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. diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 5ab929d212e..4f4ef7f5a74 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -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: diff --git a/source/_components/frontend.markdown b/source/_components/frontend.markdown index 9f6ab7ee33b..09941498172 100644 --- a/source/_components/frontend.markdown +++ b/source/_components/frontend.markdown @@ -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. diff --git a/source/_components/input_boolean.markdown b/source/_components/input_boolean.markdown index 68f75566ba4..b5ff27a3f0c 100644 --- a/source/_components/input_boolean.markdown +++ b/source/_components/input_boolean.markdown @@ -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. diff --git a/source/_components/input_datetime.markdown b/source/_components/input_datetime.markdown index be7024142a2..b7a45611eff 100644 --- a/source/_components/input_datetime.markdown +++ b/source/_components/input_datetime.markdown @@ -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 diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown index 299543428d4..f2301243db0 100644 --- a/source/_components/input_number.markdown +++ b/source/_components/input_number.markdown @@ -11,6 +11,7 @@ logo: home-assistant.png ha_category: Automation ha_release: 0.55 redirect_from: /components/input_slider/ +ha_qa_scale: internal ---
diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown index dec70767fd1..5948d9d1ac1 100644 --- a/source/_components/input_select.markdown +++ b/source/_components/input_select.markdown @@ -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. diff --git a/source/_components/input_text.markdown b/source/_components/input_text.markdown index 187f08a0e46..9833541ba37 100644 --- a/source/_components/input_text.markdown +++ b/source/_components/input_text.markdown @@ -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). diff --git a/source/_components/introduction.markdown b/source/_components/introduction.markdown index 759142229dc..83a39cc1612 100644 --- a/source/_components/introduction.markdown +++ b/source/_components/introduction.markdown @@ -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. diff --git a/source/_components/map.markdown b/source/_components/map.markdown index deacb922222..c7a5e90eefe 100644 --- a/source/_components/map.markdown +++ b/source/_components/map.markdown @@ -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. diff --git a/source/_components/persistent_notification.markdown b/source/_components/persistent_notification.markdown index 9fac3ddc0cf..a0bf7abfb78 100644 --- a/source/_components/persistent_notification.markdown +++ b/source/_components/persistent_notification.markdown @@ -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. diff --git a/source/_components/sensor.filter.markdown b/source/_components/sensor.filter.markdown index a0a07337a70..fec73f0facd 100644 --- a/source/_components/sensor.filter.markdown +++ b/source/_components/sensor.filter.markdown @@ -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. diff --git a/source/_components/sensor.random.markdown b/source/_components/sensor.random.markdown index e3515333eab..8b1bb11cfbf 100644 --- a/source/_components/sensor.random.markdown +++ b/source/_components/sensor.random.markdown @@ -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/ diff --git a/source/_components/sensor.statistics.markdown b/source/_components/sensor.statistics.markdown index d28f73eabee..509e7f8db3c 100644 --- a/source/_components/sensor.statistics.markdown +++ b/source/_components/sensor.statistics.markdown @@ -11,6 +11,7 @@ logo: home-assistant.png ha_category: Utility ha_iot_class: "Local Polling" ha_release: "0.30" +ha_qa_scale: internal --- diff --git a/source/_components/timer.markdown b/source/_components/timer.markdown index eb6db877f36..dad6227958e 100644 --- a/source/_components/timer.markdown +++ b/source/_components/timer.markdown @@ -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. diff --git a/source/_components/updater.markdown b/source/_components/updater.markdown index b87d554bb91..2b6c2997a7a 100644 --- a/source/_components/updater.markdown +++ b/source/_components/updater.markdown @@ -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. diff --git a/source/_components/zone.markdown b/source/_components/zone.markdown index c97d06657ff..fd6280eccfc 100644 --- a/source/_components/zone.markdown +++ b/source/_components/zone.markdown @@ -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. diff --git a/source/_docs/quality_scale.markdown b/source/_docs/quality_scale.markdown index 6abe5ce2150..d2c818a30da 100644 --- a/source/_docs/quality_scale.markdown +++ b/source/_docs/quality_scale.markdown @@ -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. + diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html index 91be8e8155a..a165fe95e16 100644 --- a/source/_includes/asides/component_navigation.html +++ b/source/_includes/asides/component_navigation.html @@ -37,6 +37,8 @@ 🥇 (gold) {% elsif page.ha_qa_scale == 'silver' %} 🥈 (silver) + {% elsif page.ha_qa_scale == 'internal' %} + 🏠 (internal) {% endif %}