mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-16 05:46:52 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
a5bc04ee3c
3
.github/workflows/lock.yml
vendored
3
.github/workflows/lock.yml
vendored
@ -6,6 +6,9 @@ on:
|
||||
|
||||
jobs:
|
||||
lock:
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: dessant/lock-threads@v3
|
||||
|
||||
3
.github/workflows/stale.yml
vendored
3
.github/workflows/stale.yml
vendored
@ -6,6 +6,9 @@ on:
|
||||
|
||||
jobs:
|
||||
stale:
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/stale@v5
|
||||
|
||||
@ -1,5 +1,7 @@
|
||||
{
|
||||
"filters": {},
|
||||
"filters": {
|
||||
"comments": true
|
||||
},
|
||||
"rules": {
|
||||
"common-misspellings": {
|
||||
"ignore": ["Proove", "Alot"]
|
||||
|
||||
@ -107,8 +107,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2022
|
||||
current_minor_version: 6
|
||||
current_patch_version: 6
|
||||
date_released: 2022-06-14
|
||||
current_patch_version: 7
|
||||
date_released: 2022-06-22
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
1602
package-lock.json
generated
1602
package-lock.json
generated
File diff suppressed because it is too large
Load Diff
@ -2,17 +2,17 @@
|
||||
"name": "home-assistant.io",
|
||||
"description": "Home Assistant Website & Documentation",
|
||||
"version": "1.0.0",
|
||||
"dependencies": {},
|
||||
"devDependencies": {
|
||||
"remark-cli": "^10.0.1",
|
||||
"remark-cli": "^11.0.0",
|
||||
"remark-frontmatter": "^4.0.1",
|
||||
"remark-lint": "^9.1.1",
|
||||
"remark-lint-fenced-code-flag": "^3.1.1",
|
||||
"remark-lint-no-shell-dollars": "^3.1.1",
|
||||
"remark-stringify": "^10.0.2",
|
||||
"textlint": "^12.1.1",
|
||||
"textlint": "^12.2.1",
|
||||
"textlint-filter-rule-comments": "^1.2.2",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^3.0.1"
|
||||
"textlint-rule-terminology": "^3.0.2"
|
||||
},
|
||||
"resolutions": {
|
||||
"minimist": ">=1.2.5"
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Alarm Panel card allows you to arm and disarm your alarm contr
|
||||
The Alarm Panel card allows you to arm and disarm your [alarm control panel](/integrations/#alarm) integrations.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_alarm_panel_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
<img src='/images/dashboards/alarm_panel_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
Screenshot of the Alarm Panel card.
|
||||
</p>
|
||||
|
||||
@ -66,7 +66,7 @@ Title example:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_alarm_panel_title_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
<img src='/images/dashboards/alarm_panel_title_card.gif' alt='Screenshot of the alarm panel card'>
|
||||
Screenshot of the Alarm Panel card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Area card gives control of your entities in a specified area."
|
||||
The Area card lets you control and monitor an individual area.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-12/area-card.png' alt='Screenshot of the Area card'>
|
||||
<img src='/images/dashboards/area-card.png' alt='Screenshot of the Area card'>
|
||||
Screenshot of the Area card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Button card allows you to add buttons to perform tasks."
|
||||
The Button card allows you to add buttons to perform tasks.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_button_card.png' alt='Screenshot of three Button Cards'>
|
||||
<img src='/images/dashboards/entity_button_card.png' alt='Screenshot of three Button Cards'>
|
||||
Screenshot of three Button Cards.
|
||||
</p>
|
||||
|
||||
@ -135,6 +135,6 @@ tap_action:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_button_complex_card.png' alt='Screenshot of the Button card with Script Service'>
|
||||
<img src='/images/dashboards/entity_button_complex_card.png' alt='Screenshot of the Button card with Script Service'>
|
||||
Screenshot of the Button card with Script Service.
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The calendar card displays your calendar entities in a month, day
|
||||
The Calendar card displays your [calendar](/integrations/#calendar) entities in a month, day and list view.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_calendar_card.png' alt='Screenshot of the
|
||||
<img src='/images/dashboards/calendar_card.png' alt='Screenshot of the
|
||||
calendar card'>
|
||||
Screenshot of the Calendar card.
|
||||
</p>
|
||||
|
||||
@ -398,7 +398,7 @@ entities:
|
||||
Above the divider are regular entity rows, below one of type `buttons`. Note that regular entity rows automatically show the entity name, whereas for buttons you have to explicitly specify a label / name.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_row_buttons.jpg' alt='Screenshot of buttons row'>
|
||||
<img src='/images/dashboards/entity_row_buttons.jpg' alt='Screenshot of buttons row'>
|
||||
Screenshot of buttons row.
|
||||
</p>
|
||||
|
||||
@ -419,7 +419,7 @@ entities:
|
||||
### Other special rows
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_row_special.jpg' alt='Screenshot of other special rows'>
|
||||
<img src='/images/dashboards/entity_row_special.jpg' alt='Screenshot of other special rows'>
|
||||
Screenshot of other special rows.
|
||||
</p>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ The Entity Filter card allows you to define a list of entities that you want to
|
||||
This type of card can also be used together with rest of cards that allow multiple entities, allowing you to use [glance](/dashboards/glance/) or [picture-glance](/dashboards/picture-glance/). By default it uses [entities](/dashboards/entities/) card model.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_filter.png' alt='Screenshot of the Entity Filter card'>
|
||||
<img src='/images/dashboards/entity_filter.png' alt='Screenshot of the Entity Filter card'>
|
||||
Screenshot of the Entity Filter card.
|
||||
</p>
|
||||
|
||||
@ -124,7 +124,7 @@ card:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_filter_glance.png' alt='Entity filter combined with glance card'>
|
||||
<img src='/images/dashboards/entity_filter_glance.png' alt='Entity filter combined with glance card'>
|
||||
Entity filter combined with glance card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Entity card gives you a quick overview of your entity's state"
|
||||
The Entity card gives you a quick overview of your entity's state.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_entity_card.png' alt='Screenshot of the entity card'>
|
||||
<img src='/images/dashboards/entity_card.png' alt='Screenshot of the entity card'>
|
||||
Screenshot of the Entity card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,12 +8,12 @@ description: "The Gauge card is a basic card that allows visually seeing sensor
|
||||
The Gauge card is a basic card that allows visually seeing sensor data.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_gauge_card.gif' alt='Screenshot of the Gauge card'>
|
||||
<img src='/images/dashboards/gauge_card.gif' alt='Screenshot of the Gauge card'>
|
||||
Screenshot of the Gauge card.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_gauge_needle_card.png' alt='Screenshot of the Gauge card in needle mode'>
|
||||
<img src='/images/dashboards/gauge_needle_card.png' alt='Screenshot of the Gauge card in needle mode'>
|
||||
Screenshot of the Gauge card in needle mode.
|
||||
</p>
|
||||
|
||||
@ -108,7 +108,7 @@ entity: sensor.cpu_usage
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_gauge_card.gif' alt='Screenshot of the gauge card with custom title and unit of measurement'>
|
||||
<img src='/images/dashboards/gauge_card.gif' alt='Screenshot of the gauge card with custom title and unit of measurement'>
|
||||
Screenshot of the gauge card with custom title and unit of measurement.
|
||||
</p>
|
||||
|
||||
@ -128,7 +128,7 @@ severity:
|
||||
Multiple segments:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_gauge_segments.png' alt='Screenshot of the gauge card with multiple colored segments.'>
|
||||
<img src='/images/dashboards/gauge_segments.png' alt='Screenshot of the gauge card with multiple colored segments.'>
|
||||
Screenshot of the gauge card with multiple colored segments.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Glance card is useful to group multiple sensors in a compact o
|
||||
The Glance card is useful to group multiple sensors in a compact overview. Keep in mind that this can be used together with [entity-filter](/dashboards/entity-filter/) cards to create dynamic cards.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_glance_card.png' alt='Screenshot of the glance card'>
|
||||
<img src='/images/dashboards/glance_card.png' alt='Screenshot of the glance card'>
|
||||
Screenshot of the Glance card.
|
||||
</p>
|
||||
|
||||
@ -129,7 +129,7 @@ entities:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_glance_card.png' alt='Screenshot of the glance card with custom title'>
|
||||
<img src='/images/dashboards/glance_card.png' alt='Screenshot of the glance card with custom title'>
|
||||
Screenshot of the glance card with custom title.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Grid card allows you to show multiple cards in a grid."
|
||||
The Grid card allows you to show multiple cards in a grid. It will first fill the columns, automatically adding new rows as needed.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_grid.png' alt='Screenshot of the grid card'>
|
||||
<img src='/images/dashboards/grid.png' alt='Screenshot of the grid card'>
|
||||
Screenshot of the Grid card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,12 +8,12 @@ description: "The History Graph card allows you to display a graph for each of t
|
||||
The History Graph card allows you to display a graph for each of the entities listed.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_history_graph.png' alt='Screenshot of the history graph card for entities without a unit_of_measurement'>
|
||||
<img src='/images/dashboards/history_graph.png' alt='Screenshot of the history graph card for entities without a unit_of_measurement'>
|
||||
Screenshot of the History Graph card, when the sensor has no `unit_of_measurement` defined.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_history_graph_lines.png' alt='Screenshot of the history graph card for entities with a unit_of_measurement'>
|
||||
<img src='/images/dashboards/history_graph_lines.png' alt='Screenshot of the history graph card for entities with a unit_of_measurement'>
|
||||
Screenshot of the History Graph card, when the sensor has a `unit_of_measurement` defined.
|
||||
</p>
|
||||
|
||||
|
||||
@ -39,6 +39,6 @@ cards:
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_horizontal_stack.PNG' alt='Two picture cards in a horizontal stack card'>
|
||||
<img src='/images/dashboards/horizontal_stack.png' alt='Two picture cards in a horizontal stack card'>
|
||||
Two Picture cards in a Horizontal Stack card.
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Humidifier card gives control of your humidifier entity, allow
|
||||
The Humidifier card lets you control and monitor humidifiers, dehumidifiers, and hygrostat devices.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_humidifier_card.png' alt='Screenshot of the humidifier card'>
|
||||
<img src='/images/dashboards/humidifier_card.png' alt='Screenshot of the humidifier card'>
|
||||
Screenshot of the humidifier card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ You can't embed sites using HTTP if you are using HTTPS for your Home Assistant.
|
||||
</div>
|
||||
|
||||
<p class='img'>
|
||||
<img width="500" src='/images/dashboards/lovelace_iframe.png' alt='Windy weather radar as Webpage'>
|
||||
<img width="500" src='/images/dashboards/iframe.png' alt='Windy weather radar as Webpage'>
|
||||
Windy weather radar as Webpage.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Light card allows you to change the brightness of the light."
|
||||
The Light card allows you to change the brightness of the light.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_light_card.png' alt='Screenshot of the Light card'>
|
||||
<img src='/images/dashboards/light_card.png' alt='Screenshot of the Light card'>
|
||||
Screenshot of the Light card.
|
||||
</p>
|
||||
|
||||
@ -71,6 +71,6 @@ name: My Office
|
||||
```
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_light_complex_card.png' alt='Screenshot of the Light card'>
|
||||
<img src='/images/dashboards/light_complex_card.png' alt='Screenshot of the Light card'>
|
||||
Screenshot of the Light card names.
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Logbook card displays entries from the logbook for specific en
|
||||
The Logbook card displays entries from the logbook for specific entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_logbook.png' alt='Screenshot of the logbook card'>
|
||||
<img src='/images/dashboards/logbook.png' alt='Screenshot of the logbook card'>
|
||||
Screenshot of the Logbook card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Map card that allows you to display entities on a map"
|
||||
The Map card that allows you to display entities on a map
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_map_card.png' alt='Screenshot of the map card'>
|
||||
<img src='/images/dashboards/map_card.png' alt='Screenshot of the map card'>
|
||||
Screenshot of the map card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ The Markdown card is used to render [Markdown](https://commonmark.org/help/).
|
||||
The renderer uses [Marked.js](https://marked.js.org), which supports [several specifications of Markdown](https://marked.js.org/#specifications), including CommonMark, GitHub Flavored Markdown (GFM) and `markdown.pl`.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_markdown.png' alt='Screenshot of the markdown card'>
|
||||
<img src='/images/dashboards/markdown.png' alt='Screenshot of the markdown card'>
|
||||
Screenshot of the Markdown card.
|
||||
</p>
|
||||
|
||||
@ -125,7 +125,7 @@ You can also use our [\`ha-alert\`](https://design.home-assistant.io/#components
|
||||
Example:
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_markdown_ha-alert.png' alt='Screenshot of the ha-alert elements in a markdown card'>
|
||||
<img src='/images/dashboards/markdown_ha-alert.png' alt='Screenshot of the ha-alert elements in a markdown card'>
|
||||
Screenshot of the ha-alert elements in a markdown card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Media Control card is used to display media player entities on
|
||||
The Media Control card is used to display [Media Player](/integrations/#media-player) entities on an interface with easy to use controls.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_mediaplayer.png' alt='Screenshot of the media player control card'>
|
||||
<img src='/images/dashboards/mediaplayer.png' alt='Screenshot of the media player control card'>
|
||||
Screenshot of the Media Control card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ The Picture Elements card is one of the most versatile types of cards.
|
||||
The cards allow you to position icons or text and even services on an image based on coordinates. Imagine floor plan, imagine [picture-glance](/dashboards/picture-glance/) with no restrictions!
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_picture_elements.gif' alt='A functional floorplan powered by picture elements'>
|
||||
<img src='/images/dashboards/picture_elements.gif' alt='A functional floorplan powered by picture elements'>
|
||||
A functional floorplan powered by picture elements.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: The Picture Entity card displays an entity in the form of an image.
|
||||
The Picture Entity card displays an entity in the form of an image. Instead of images from URL, it can also show the picture of `camera` entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_picture_entity.gif' alt='Picture entity card'>
|
||||
<img src='/images/dashboards/picture_entity.gif' alt='Picture entity card'>
|
||||
Background changes according to the entity state.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Picture Glance card shows an image and corresponding entity st
|
||||
The Picture Glance card shows an image and corresponding entity states as an icon. The entities on the right side allow toggle actions, others show the more information dialog.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_picture_glance.gif' alt='Picture glance card for a living room'>
|
||||
<img src='/images/dashboards/picture_glance.gif' alt='Picture glance card for a living room'>
|
||||
Picture glance card for a living room.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Picture card allows you to set an image to use for navigation
|
||||
The Picture card allows you to set an image to use for navigation to various paths in your interface or to call a service.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_picture.png' alt='Screenshot of the picture card'>
|
||||
<img src='/images/dashboards/picture.png' alt='Screenshot of the picture card'>
|
||||
Screenshot of the picture card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Plant Status card is for all the lovely botanists out there."
|
||||
The Plant Status card is for all the lovely botanists out there.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_plant_card.png' alt='Screenshot of the plant status card'>
|
||||
<img src='/images/dashboards/plant_card.png' alt='Screenshot of the plant status card'>
|
||||
Screenshot of the plant status card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Sensor card gives you a quick overview of your sensors state w
|
||||
The Sensor card gives you a quick overview of your sensors state with an optional graph to visualize change over time.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_sensor.png' alt='Screenshot of the sensor card'>
|
||||
<img src='/images/dashboards/sensor.png' alt='Screenshot of the sensor card'>
|
||||
Screenshot of the sensor card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ The Shopping List card allows you to add, edit, check-off, and clear items from
|
||||
Setup of the [Shopping List integration](/integrations/shopping_list/) is required.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_shopping_list_card.gif' alt='Screenshot of the shopping list card'>
|
||||
<img src='/images/dashboards/shopping_list_card.gif' alt='Screenshot of the shopping list card'>
|
||||
Screenshot of the Shopping List card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -12,12 +12,12 @@ Statistics are gathered every hour for sensors that support it. It will either k
|
||||
If your sensor doesn't work with statistics, check [this](/more-info/statistics/).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_statistics_graph_line.png' alt='Screenshot of the statistics graph card for power entities'>
|
||||
<img src='/images/dashboards/statistics_graph_line.png' alt='Screenshot of the statistics graph card for power entities'>
|
||||
Screenshot of the Statistics Graph card with none metered entities and `chart_type` `line`.
|
||||
</p>
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_statistics_graph_bar.png' alt='Screenshot of the statistics graph card for energy entities'>
|
||||
<img src='/images/dashboards/statistics_graph_bar.png' alt='Screenshot of the statistics graph card for energy entities'>
|
||||
Screenshot of the Statistics Graph card with a metered entity and `chart_type` `bar`.
|
||||
</p>
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Thermostat card gives control of your climate entity, allowing
|
||||
The Thermostat card gives control of your [climate](/integrations/#climate) entity, allowing you to change the temperature and mode of the entity.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
<img src='/images/dashboards/thermostat_card.gif' alt='Screenshot of the thermostat card'>
|
||||
Screenshot of the Thermostat card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ cards:
|
||||
```
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/dashboards/lovelace_vertical-stack.png" alt="Picture- and entities-card in a stack">
|
||||
<img src="/images/dashboards/vertical-stack.png" alt="Picture- and entities-card in a stack">
|
||||
Picture and entities-card in a stack.
|
||||
</p>
|
||||
|
||||
@ -66,6 +66,6 @@ cards:
|
||||
```
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/dashboards/lovelace_vertical-horizontal-stack.png" alt="Create a grid layout using vertical and horizontal stack">
|
||||
<img src="/images/dashboards/vertical-horizontal-stack.png" alt="Create a grid layout using vertical and horizontal stack">
|
||||
Create a grid layout using vertical and horizontal stack.
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ description: "The Weather Forecast card displays the weather. Very useful to inc
|
||||
The Weather Forecast card displays the weather. Very useful to include on interfaces that people display on the wall.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/dashboards/lovelace_weather.png' alt='Screenshot of the weather card'>
|
||||
<img src='/images/dashboards/weather.png' alt='Screenshot of the weather card'>
|
||||
Screenshot of the Weather card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ The following describes trigger data associated with all platforms.
|
||||
| Template variable | Data |
|
||||
| ---- | ---- |
|
||||
| `trigger.id` | Optional trigger `id`, or index of the trigger.
|
||||
| `trigger.idx` | Index of the trigger.
|
||||
| `trigger.idx` | Index of the trigger. (The first trigger idx is `0`.)
|
||||
|
||||
### Calendar
|
||||
|
||||
|
||||
@ -695,8 +695,8 @@ See: https://docs.python.org/3/library/struct.html
|
||||
|
||||
- Filter `value | pack(format_string)` will convert a native type to a `bytes` type object. This will call function `struct.pack(format_string, value)`. Returns `None` if an error occurs or when `format_string` is invalid.
|
||||
- Function `pack(value, format_string)` will convert a native type to a `bytes` type object. This will call function `struct.pack(format_string, value)`. Returns `None` if an error occurs or when `format_string` is invalid.
|
||||
- Filter `value | unpack(format_string, offset=0)` will try to convert a `bytes` object into a native Python object. The `offset` parameter defines the offset position in bytes from the start of the input `bytes` based buffer. This will call function `struct.unpack_from(format_string, value, offset=offset)`. Returns `None` if an error occurs or when `format_string` is invalid.
|
||||
- Function `unpack(value, format_string, offset=0)` will try to convert a `bytes` object into a native Python object. The `offset` parameter defines the offset position in bytes from the start of the input `bytes` based buffer. This will call function `struct.unpack_from(format_string, value, offset=offset)`. Returns `None` if an error occurs or when `format_string` is invalid.
|
||||
- Filter `value | unpack(format_string, offset=0)` will try to convert a `bytes` object into a native Python object. The `offset` parameter defines the offset position in bytes from the start of the input `bytes` based buffer. This will call function `struct.unpack_from(format_string, value, offset=offset)`. Returns `None` if an error occurs or when `format_string` is invalid. Note that the filter `unpack` will only return the first `bytes` object, despite the function `struct.unpack_from` supporting to return multiple objects (e.g. with `format_string` being `">hh"`.
|
||||
- Function `unpack(value, format_string, offset=0)` will try to convert a `bytes` object into a native Python object. The `offset` parameter defines the offset position in bytes from the start of the input `bytes` based buffer. This will call function `struct.unpack_from(format_string, value, offset=offset)`. Returns `None` if an error occurs or when `format_string` is invalid. Note that the function `unpack` will only return the first `bytes` object, despite the function `struct.unpack_from` supporting to return multiple objects (e.g. with `format_string` being `">hh"`.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -705,8 +705,8 @@ Some examples:
|
||||
|
||||
- `{{ 0xDEADBEEF | pack(">I") }}` - renders as `b"\xde\xad\xbe\xef"`
|
||||
- `{{ pack(0xDEADBEEF, ">I") }}` - renders as `b"\xde\xad\xbe\xef"`
|
||||
- `{{ 0xDEADBEEF | pack(">I") | unpack("">I") }}` - renders as `0xDEADBEEF`
|
||||
- `{{ 0xDEADBEEF | pack(">I") | unpack("">H", offset=2) }}` - renders as `0xBEEF`
|
||||
- `{{ "0x%X" % 0xDEADBEEF | pack(">I") | unpack(">I") }}` - renders as `0xDEADBEEF`
|
||||
- `{{ "0x%X" % 0xDEADBEEF | pack(">I") | unpack(">H", offset=2) }}` - renders as `0xBEEF`
|
||||
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@ -16,6 +16,7 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
|
||||
- [Upgrade instructions using Linux](https://github.com/kpine/zwave-js-server-docker/wiki/700-series-Controller-Firmware-Updates-(Linux))
|
||||
- [Upgrade instructions using Windows (Aeotec)](https://help.aeotec.com/support/solutions/articles/6000252296-update-z-stick-7-with-windows)
|
||||
- [Upgrade instructions using Windows (Zooz)](https://www.support.getzooz.com/kb/article/931-how-to-perform-an-ota-firmware-update-on-your-zst10-700-z-wave-stick/)
|
||||
- [Upgrade instructions using Windows/Linux (Z-Wave.Me)](https://z-wave.me/support/uzbrazberry-firmwares/)
|
||||
|
||||
</div>
|
||||
|
||||
@ -24,8 +25,8 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
|
||||
- Aeotec Z-Pi 7 Raspberry Pi HAT/Shield (ZWA025)
|
||||
- Silicon Labs UZB-7 USB Stick (Silabs SLUSB7000A / SLUSB001A)
|
||||
- Zooz S2 Stick 700 (ZST10 700)
|
||||
- ZWave.me RaZberry 7 (ZME_RAZBERRY7)
|
||||
- ZWave.me RaZberry 7 Pro (ZMEERAZBERRY7_ANT or ZMEURAZBERRY7_ANT)
|
||||
- Z-Wave.Me RaZberry 7 (ZME_RAZBERRY7)
|
||||
- Z-Wave.Me RaZberry 7 Pro (ZMEERAZBERRY7_ANT or ZMEURAZBERRY7_ANT)
|
||||
|
||||
- 500 series controllers
|
||||
- Aeotec Z-Stick Gen5 (see note below)
|
||||
@ -33,11 +34,13 @@ Users should upgrade the firmware on all 700 series controllers to version 7.17.
|
||||
- GoControl HUSBZB-1 stick
|
||||
- Sigma Designs UZB stick
|
||||
- Vision USB stick - Gen5
|
||||
- ZWave.me UZB1 stick
|
||||
- Z-Wave.Me UZB1 stick
|
||||
|
||||
- Rasberry Pi Modules
|
||||
- Aeotec Z-Pi 7 (700 series)
|
||||
- ZWave.me Razberry Board (500 series)
|
||||
- Z-Wave.Me RaZberry 7 (700 series)
|
||||
- Z-Wave.Me RaZberry 7 Pro (700 series)
|
||||
- Z-Wave.Me Razberry 2 (500 series)
|
||||
|
||||
If you are just starting out, we recommend that you purchase a 500 series controller.
|
||||
|
||||
@ -52,6 +55,7 @@ The alternative to a stick is a hub that supports Z-Wave. Home Assistant support
|
||||
- [Vera](/integrations/vera/)
|
||||
- [Fibaro](/integrations/fibaro/)
|
||||
- [SmartThings](/integrations/smartthings/)
|
||||
- [Z-Wave.Me Z-Way](/integrations/zwave_me)
|
||||
|
||||
## Controller Notes
|
||||
|
||||
|
||||
@ -5,9 +5,9 @@ Best practice for updating a Home Assistant installation:
|
||||
1. Backup your installation{% if page.installation == "os" or page.installation == "supervised" %}, using the backup functionality Home Assistant offers{% endif %}.
|
||||
1. Check the release notes for breaking changes on [Home Assistant release notes](/blog/categories/core/). Be sure to check all release notes between the version you are running and the one you are upgrading to. Use the search function in your browser (`CTRL + f` / `CMD + f`) and search for **Breaking Changes**.
|
||||
{% if page.installation == "os" or page.installation == "supervised" %}
|
||||
1. Check your configuration using the [Check Home Assistant configuration](/addons/check_config/) add-on.
|
||||
1. If the check passes, you can safely update. If not, update your configuration accordingly.
|
||||
1. Select "Create backup before updating" in case you encounter an issue that requires a rollback.
|
||||
1. Update Home Assistant.
|
||||
1. Review persistent notifications and log to see if there are any issues with your configuration that need to be addressed.
|
||||
{% endif %}
|
||||
|
||||
{% if page.installation == "os" or page.installation == "supervised" %}
|
||||
|
||||
@ -10,14 +10,13 @@ The steps would be:
|
||||
- Wait for some time until your NAS has pulled the image
|
||||
- Move to the "Image"-section of the Docker-app
|
||||
- Click on "Launch"
|
||||
- Within "Network" select "Use same network as Docker Host" and click Next
|
||||
- Choose a container-name you want (e.g., "homeassistant")
|
||||
- Click on "Advanced Settings"
|
||||
- Set "Enable auto-restart" if you like
|
||||
- Within "Volume" click on "Add Folder" and choose either an existing folder or add a new folder. The "mount path" has to be "/config", so that Home Assistant will use it for the configs and logs. It is therefore recommended that the folder you choose should be named "config" or "homeassistant/config" to avoid confusion when referencing it within service calls.
|
||||
- Within "Network" select "Use same network as Docker Host"
|
||||
- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
|
||||
- Confirm the "Advanced Settings"
|
||||
- Click on "Next" and then "Apply"
|
||||
- Click on "Advanced Settings". To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). Click Save to exit Advanced Settings.
|
||||
- Click Next
|
||||
- Within "Volume Settings" click on "Add Folder" and choose either an existing folder or add a new folder (e.g. in "docker" shared folder, add new folder named "homeassistant" and then within that new folder add another new folder "config"), then click Select. Then edit the "mount path" to be "/config". This configures where Home Assistant will store configs and logs.
|
||||
- Ensure "Run this container after the wizard is finished" is checked and click Done
|
||||
- Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Synology NAS IP address - for example `http://192.168.1.10:8123`)
|
||||
|
||||
If you are using the built-in firewall, you must also add the port 8123 to allowed list. This can be found in "Control Panel -> Security" and then the Firewall tab. Click "Edit Rules" besides the Firewall Profile dropdown box. Create a new rule and select "Custom" for Ports and add 8123. Edit Source IP if you like or leave it at default "All". Action should stay at "Allow".
|
||||
|
||||
@ -157,6 +157,25 @@ _Select and copy the URL or use the "copy" button that appear when you hover it.
|
||||
3. Power the system on.
|
||||
|
||||
- Wait for the Home Assistant welcome banner to show up in the console of the generic-x86-64 system.
|
||||
|
||||
<div class="note">
|
||||
|
||||
If the machine complains about not being able to find a bootable medium, you might need to specify the EFI entry in your BIOS.
|
||||
This can be accomplished either by using a live operating system (e.g. Ubuntu) and running the following command (replace `<drivename>` with the appropriate drive name assigned by Linux, typically this will be `sda` or `nvme0n1` on NVMe SSDs):
|
||||
|
||||
```text
|
||||
efibootmgr --create --disk /dev/<drivename> --part 1 --label "HAOS" \
|
||||
--loader \EFI\BOOT\bootx64.efi
|
||||
```
|
||||
|
||||
Or else, the BIOS might provide you with a tool to add boot options, there you can specify the path to the EFI file:
|
||||
|
||||
```text
|
||||
\EFI\BOOT\bootx64.efi
|
||||
```
|
||||
|
||||
</div>
|
||||
|
||||
{% else %}
|
||||
|
||||
1. Insert the boot media ({{site.installation.types[page.installation_type].installation_media}}) you just created.
|
||||
|
||||
@ -86,7 +86,7 @@ stream_source:
|
||||
default: snapshot
|
||||
ffmpeg_arguments:
|
||||
description: >
|
||||
Extra options to pass to ffmpeg, e.g.,
|
||||
Extra options to pass to FFmpeg, e.g.,
|
||||
image quality or video filter options.
|
||||
required: false
|
||||
type: string
|
||||
|
||||
@ -16,6 +16,8 @@ This platform allows you to detect presence by looking at connected devices to a
|
||||
Supported devices (tested):
|
||||
|
||||
- Aruba AP-105
|
||||
- Aruba IAP-335
|
||||
- Aruba Instant IAP-275
|
||||
|
||||
<div class='note warning'>
|
||||
This device tracker needs telnet to be enabled on the router.
|
||||
|
||||
@ -99,7 +99,7 @@ The following are some examples showing how to correctly make service calls usin
|
||||
|
||||
### Snap Picture and Save Locally
|
||||
|
||||
This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](/integrations/camera#service-snapshot)
|
||||
This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in Home Assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](/integrations/camera#service-snapshot)
|
||||
|
||||
```yaml
|
||||
alias: "Blink Snap Picture"
|
||||
|
||||
@ -33,7 +33,7 @@ Ignore CEC:
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/dashboards/entities/#cast) to your dashboards, or by calling the `cast.show_lovelace_view` service. The service takes the path of a dashboard view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your dashboard's YAML for each view, as outlined in the [views documentation](/dashboards/views/#path). The `dashboard_path` is the part of the dashboard URL that follows the defined `base_url`, typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/dashboards/entities/#cast) to your dashboards, or by calling the `cast.show_lovelace_view` service. The service takes the path of a dashboard view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your dashboard's YAML for each view, as outlined in the [views documentation](/dashboards/views/#path). The `dashboard_path` is the part of the dashboard URL that follows the defined `base_url`, typically "`lovelace`". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
|
||||
```yaml
|
||||
cast_downstairs_on_kitchen:
|
||||
|
||||
@ -47,4 +47,13 @@ Due to a limitation in the Cloudflare API, you can not use this integration with
|
||||
|
||||
#### Record types
|
||||
|
||||
This integration can only update A records.
|
||||
This integration can only update A records.
|
||||
|
||||
#### Zones
|
||||
|
||||
This integration can only have 1 instance and manage 1 Zone/TLD.
|
||||
|
||||
#### Reconfiguration
|
||||
|
||||
This integration must be deleted and re-added to change the Zone and A record selection.
|
||||
You cannot view which records were selected or view the API Token once the integration is configured.
|
||||
|
||||
@ -90,5 +90,6 @@ sensor:
|
||||
The list above indicates all supported sensors. It is recommended to only include the ones you need.
|
||||
|
||||
<div class='note'>
|
||||
Note that it's not possible to have multiple connection to the bridge at the same time. This integration will keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically.
|
||||
Note that multiple connections to the bridge only work version >= U1.2.6 of the ComfoConnect LAN C bridge.
|
||||
In older versions it's not possible to have multiple connections to the bridge at the same time. This integration will then keep the connection open, and if you open the app, it will ask you to disconnect Home Assistant. If you close the app again, Home Assistant will reconnect automatically.
|
||||
</div>
|
||||
|
||||
@ -37,7 +37,7 @@ sensor:
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: "API Subscription key needed to access De Lijn API's."
|
||||
description: "API Subscription key needed to access De Lijn APIs."
|
||||
required: true
|
||||
type: string
|
||||
next_departure:
|
||||
|
||||
@ -11,6 +11,10 @@ ha_domain: mqtt
|
||||
|
||||
The `mqtt` device tracker platform allows you to define new device_trackers through [manual YAML configuration](#yaml-configuration) in `configuration.yaml` and also to automatically discover device_trackers [using the MQTT Discovery protocol](#using-the-discovery-protocol).
|
||||
|
||||
<div class='note info'>
|
||||
At the moment, manual configured device trackers can only reloaded by restarting Home Assistant.
|
||||
</div>
|
||||
|
||||
## Configuration
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -149,7 +149,7 @@ labels:
|
||||
|
||||
## Supported labels
|
||||
|
||||
Both detectors "default" and "tensorflow" use the labels in [this file](https://raw.githubusercontent.com/amikelive/coco-labels/master/coco-labels-2014_2017.txt).
|
||||
Both detectors `default` and `tensorflow` use the labels in [this file](https://raw.githubusercontent.com/amikelive/coco-labels/master/coco-labels-2014_2017.txt).
|
||||
|
||||
## Sample configuration
|
||||
|
||||
|
||||
@ -103,15 +103,15 @@ datepattern = ^%%Y-%%m-%%d %%H:%%M:%%S
|
||||
|
||||
#### Map log file directories
|
||||
|
||||
First, we need to make sure that fail2ban log can be passed to Home Assistant and that the Home Assistant log can be passed to fail2ban. When starting the Let's Encrypt docker, you need to add the following argument (adjust paths based on your setup):
|
||||
First, we need to make sure that fail2ban log can be passed to Home Assistant and that the Home Assistant log can be passed to fail2ban. When starting the Let's Encrypt Docker, you need to add the following argument (adjust paths based on your setup):
|
||||
|
||||
```txt
|
||||
/mnt/user/appdata/home-assistant:/hass
|
||||
```
|
||||
|
||||
This will map the Home Assistant configuration directory to the Let's Encrypt docker, allowing `fail2ban` to parse the log for failed login attempts.
|
||||
This will map the Home Assistant configuration directory to the Let's Encrypt Docker, allowing `fail2ban` to parse the log for failed login attempts.
|
||||
|
||||
Now do the same for the Home Assistant docker, but this time we'll be mapping the `fail2ban` log directory to Home Assistant so that the fail2ban sensor is able to read that log:
|
||||
Now do the same for the Home Assistant Docker, but this time we'll be mapping the `fail2ban` log directory to Home Assistant so that the fail2ban sensor is able to read that log:
|
||||
|
||||
```txt
|
||||
/mnt/user/appdata/letsencrypt/log/fail2ban:/fail2ban
|
||||
|
||||
@ -17,7 +17,7 @@ The platform does not directly interact with the buttons, *but communicates with
|
||||
|
||||
## Service setup
|
||||
|
||||
If you are using Hass.io, you can run the service locally by [installing](/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons).
|
||||
If you are using the Home Assistant Operating System, you can run the service locally by [installing](/hassio/installing_third_party_addons/) the flicd add-on from [pschmitt's repository](https://github.com/pschmitt/hassio-addons).
|
||||
|
||||
For instructions on how to install the service manually, visit the GitHub repository of the service for [Linux](https://github.com/50ButtonsEach/fliclib-linux-hci), [macOS](https://github.com/50ButtonsEach/flic-service-osx) or [Windows](https://github.com/50ButtonsEach/fliclib-windows).
|
||||
|
||||
|
||||
@ -71,7 +71,7 @@ Parameters:
|
||||
- **eventId** (*Optional*): The event the user is checking in to.
|
||||
- **shout** (*Optional*): A message about your check-in. The maximum length of this field is 140 characters.
|
||||
- **mentions** (*Optional*): Mentions in your check-in. This parameter is a semicolon-delimited list of mentions. A single mention is of the form "start,end,userid", where start is the index of the first character in the shout representing the mention, end is the index of the first character in the shout after the mention, and userid is the userid of the user being mentioned. If userid is prefixed with "fbu-", this indicates a Facebook userid that is being mention. Character indices in shouts are 0-based.
|
||||
- **broadcast** (*Optional*): "Who to broadcast this check-in to. Accepts a comma-delimited list of values: private (off the grid) or public (share with friends), Facebook share on Facebook, Twitter share on twitter, followers share with followers (celebrity mode users only), If no valid value is found, the default is public."
|
||||
- **broadcast** (*Optional*): "Who to broadcast this check-in to. Accepts a comma-delimited list of values: private (off the grid) or public (share with friends), Facebook share on Facebook, Twitter share on Twitter, followers share with followers (celebrity mode users only), If no valid value is found, the default is public."
|
||||
- **ll** (*Optional*): Latitude and longitude of the user's location. Only specify this field if you have a GPS or other device reported location for the user at the time of check-in.
|
||||
- **llAcc** (*Optional*): Accuracy of the user's latitude and longitude, in meters.
|
||||
- **alt** (*Optional*): Altitude of the user's location, in meters.
|
||||
|
||||
@ -78,16 +78,29 @@ When a device is not responding correctly the update interval will increase to 1
|
||||
|
||||
## Energy dashboard
|
||||
|
||||
Recommended energy dashboard configuration for meter location in feed in path (`Meter location: 0`):
|
||||
|
||||
- For `Grid consumption` use the meters `Energy real consumed` entity.
|
||||
- For `Return to grid` use the meters `Energy real produced` entity.
|
||||
- For `Solar production`:
|
||||
- If no battery is connected to an inverter: Add each inverters `Energy total` entity.
|
||||
- If a battery is connected to an inverter: Use [Riemann sum](/integrations/integration/) over `Power photovoltaics` entity (from power_flow endpoint found in your `SolarNet` device)
|
||||
- `Battery systems` aren't supported directly. Use [Template](/integrations/template) to split and invert negative values of `Power battery` entity (from power_flow) for charging power (W) and positive values for discharging power (W). Then use [Riemann sum](/integrations/integration/) to integrate each into energy values (kWh).
|
||||
- For `Devices` use the Ohmpilots `Energy consumed` entity.
|
||||
|
||||
The energy meter integrated with Fronius devices can be installed (and configured) in two different installation positions: _"feed in path"_ (`meter_location` = 0) or _"consumption path"_ (`meter_location` = 1). In the first case, the meter provides all data you need but, in the second case, it doesn't so you need to calculate some of them by using helpers.
|
||||
|
||||
### Feed in path meter
|
||||
|
||||
Recommended energy dashboard configuration for meter location in feed in path:
|
||||
|
||||
- For `Grid consumption` use the meters `Energy real consumed` entity.
|
||||
- For `Return to grid` use the meters `Energy real produced` entity.
|
||||
|
||||
### Consumption path meter
|
||||
|
||||
Recommended energy dashboard configuration for meter location in consumption path:
|
||||
|
||||
- The "Power Grid" entity provided by the Fronius API is positive on import and negative on export. Split it up into import- and export-power entities by using helpers with templates `max(states(sensor.power_grid) | float, 0)` and `max(0 - states(sensor.power_grid) | float, 0)`.
|
||||
- Then use [Riemann sum](/integrations/integration/) to integrate these import-/export-power entities into energy values (kWh).
|
||||
- Use these energy entities for `Grid consumption` and `Return to grid` in the energy dashboard configuration.
|
||||
|
||||
## Note
|
||||
|
||||
Fronius often provides firmware updates for the datamanager interfaces and the devices in their system, it's recommended to check and apply them regularly. This integration relies on functionality present in rather recent firmware.
|
||||
|
||||
@ -31,7 +31,7 @@ This section explains how to generate a Client ID and Client Secret on
|
||||
1. When it gets to the Page titled _Add credentials to your project_ just click cancel.
|
||||
1. Navigate to APIs & Services (left sidebar) > Credentials
|
||||
1. Click on the field on the right of the screen, 'CONFIGURE CONSENT SCREEN', select "External" and create.
|
||||
1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest "Home-Assistant".
|
||||
1. Set the 'Application Name' (the name of the application asking for consent) to anything you want. We suggest `Home-Assistant`.
|
||||
1. You then need to select a `Support email`. To do this, simply click the drop down box and select your email address.
|
||||
1. You finally need to complete the section: `Developer contact information`. To do this, simply enter your email address (same as above is fine).
|
||||
1. Scroll to the bottom and click `save`. (You don't have to fill out anything else)
|
||||
|
||||
@ -47,7 +47,7 @@ Home Assistant can group multiple binary sensors, covers, fans, lights, locks, m
|
||||
In short, when any group member entity is `on`, the group will also be `on`. A complete overview of how groups behave:
|
||||
|
||||
- The group state is `unavailable` if all group members are `unavailable`.
|
||||
- Otherwise, the group state is `unknown` if all group members are `unknown`.
|
||||
- Otherwise, the group state is `unknown` if all group members are `unknown` or `unavailable`.
|
||||
- Otherwise, the group state is `on` if at least one group member is `on`.
|
||||
- Otherwise, the group state is `off`.
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ Read more about this in their [shutdown notice](https://www.hivehome.com/us/supp
|
||||
|
||||
</div>
|
||||
|
||||
This Hive integration uses the same username and password you use on the [Hive website](https://sso.hivehome.com) to configure it within Home Assistant, 2FA authentication is also supported. Once configured Home Assistant will detect and add all Hive devices, including support for multi-zone heating.
|
||||
This Hive integration uses the same username and password you use on the [Hive website](https://sso.hivehome.com) to configure it within Home Assistant, 2FA authentication must be enabled to use this integration. Once configured Home Assistant will detect and add all Hive devices, including support for multi-zone heating.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -209,7 +209,7 @@ Resolving names can take some time. So when you start Home Assistant you won't s
|
||||
|
||||
### Multiple hosts
|
||||
|
||||
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and IP), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
|
||||
This does *not* affect the entities in Home Assistant. They all use their own connection and work as expected.
|
||||
|
||||
|
||||
@ -153,7 +153,7 @@ If you want to use Home Assistant to host or serve static files then create a di
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Files served from the `www` folder (`/local/` url), aren't protected by the Home Assistant authentication. Files stored in this folder, if the URL is known, can be accessed by anybody without authentication.
|
||||
Files served from the `www` folder (`/local/` URL), aren't protected by the Home Assistant authentication. Files stored in this folder, if the URL is known, can be accessed by anybody without authentication.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@ If two-step authentication is enabled for your iCloud account, some time after H
|
||||
|
||||
## In case of troubleshooting
|
||||
|
||||
Go into your Home Assistant configuration `.storage` folder and delete the "icloud" folder, then retry.
|
||||
Go into your Home Assistant configuration `.storage` folder and delete the `icloud` folder, then retry.
|
||||
|
||||
## Platforms
|
||||
|
||||
|
||||
@ -50,8 +50,8 @@ Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`,
|
||||
| `entity_id` | yes | Target a specific media player. To target all media players, use `all`. |
|
||||
| `media_content_id` | no | A media identifier. The format of this is integration dependent. For example, you can provide URLs to Sonos and Cast but only a playlist ID to iTunes. |
|
||||
| `media_content_type` | no | A media type. Must be one of `music`, `tvshow`, `video`, `episode`, `channel` or `playlist`. For example, to play music you would set `media_content_type` to `music`. |
|
||||
| `enqueue` | yes | How the new media should interact with the queue. Must be one of `add`, `next`, `play`, `replace`. |
|
||||
| `announce` | yes | Set to `true` to request the media player to temporarily stop playing music to announce this media and then resume.
|
||||
| `enqueue` | yes | How the new media should interact with the queue. Must be one of `add`, `next`, `play`, `replace`. If the media player doesn't support this feature, the new media will play and the `enqueue` directive is ignored. |
|
||||
| `announce` | yes | Set to `true` to request the media player to temporarily stop playing media to announce this media and then resume. If the media player doesn't support this feature, the announcement will play but the media player and will not resume playing the interrupted media once the announcement finishes.
|
||||
| `extra` | yes | Extra dictionary data to send, e.g., title, thumbnail. Possible values can be found below.
|
||||
|
||||
##### Extra dictionary data
|
||||
|
||||
@ -79,7 +79,7 @@ timeout:
|
||||
default: 5
|
||||
type: integer
|
||||
type:
|
||||
description: Type of communication. Possible values are `tcp` Modbus messages with Modbus TCP frame on TCP/IP, `udp` Modbus messages with Modbus TCP frame on UDP, `rtuovertcp` Modbus messages with a wrapper TCP/IP simulating a serial line.
|
||||
description: Type of communication. Possible values are `tcp` Modbus messages with Modbus TCP frame on TCP/IP, `udp` Modbus messages with Modbus TCP frame on UDP, `rtuovertcp` Modbus messages with a wrapper TCP/IP simulating a serial line, 'serial' Modbus serial (RS485).
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -63,7 +63,7 @@ To use HomeKit Controller:
|
||||
|
||||
If you want the devices to be accessible via HomeKit, create a HomeKit Bridge using the following steps:
|
||||
|
||||
- Go to {% my integrations title="Settings >> Devices & Servicess" %} in the Home Assistant UI.
|
||||
- Go to {% my integrations title="Settings >> Devices & Services" %} in the Home Assistant UI.
|
||||
- Click the button with + sign, and from the list of integrations, select ***HomeKit***.
|
||||
- Create a bridge for the `cover` domain.
|
||||
- Follow the instructions to pair with the bridge.
|
||||
|
||||
@ -53,7 +53,7 @@ Raw configurable scan options for Nmap:
|
||||
|
||||
### Linux capabilities
|
||||
|
||||
On Linux systems (such as Hass.io) you can extend the functionality of Nmap, without having to run it as root, by using *Linux capabilities*. Be sure to specify the full path to wherever you installed Nmap:
|
||||
On Linux systems (such as the Home Assistant Operating System) you can extend the functionality of Nmap, without having to run it as root, by using *Linux capabilities*. Be sure to specify the full path to wherever you installed Nmap:
|
||||
|
||||
```bash
|
||||
sudo setcap cap_net_raw,cap_net_admin,cap_net_bind_service+eip /usr/bin/nmap
|
||||
|
||||
@ -65,7 +65,7 @@ output.voltage.nominal: 120
|
||||
```
|
||||
|
||||
Use the values from the left hand column. Support is included for most
|
||||
values with 'ups', 'battery', 'input' and 'output' prefixes.
|
||||
values with `ups`, `battery`, `input` and `output` prefixes.
|
||||
|
||||
## UPS Status - human-readable version
|
||||
|
||||
|
||||
@ -80,8 +80,12 @@ Supported sensors:
|
||||
|
||||
If the OctoPrint host is equipped with a web camera it is possible to add this as well using the [`MJPEG IP Camera`](/integrations/mjpeg) integration. Use `http://YOUR_OCTOPRINT_HOST_IP/webcam/?action=stream` for the MJPEG URL and `http://YOUR_OCTOPRINT_HOST_IP/webcam/?action=snapshot` as the still image URL.
|
||||
|
||||
<!-- textlint-disable -->
|
||||
|
||||
{% my config_flow_start badge domain="mjpeg" %}
|
||||
|
||||
<!-- textlint-enable -->
|
||||
|
||||
## Buttons
|
||||
|
||||
The OctoPrint integration provides the following buttons.
|
||||
|
||||
@ -77,7 +77,7 @@ The Point only supports a Arm/Disarm action, so it is only `Arm Away` that is im
|
||||
|
||||
Each Point exposes the following binary sensors:
|
||||
|
||||
- **alarm**: `On` means alarm sound was recognised, `Off` means normal
|
||||
- **alarm**: `On` means alarm sound was recognized, `Off` means normal
|
||||
- **battery**: `On` means low, `Off` means normal
|
||||
- **button_press**: `On` means the button was pressed, `Off` means normal
|
||||
- **cold**: `On` means cold, `Off` means normal
|
||||
|
||||
@ -28,12 +28,28 @@ When the profile is complete, Profiler will generate a Python `cprof` and a `cal
|
||||
|
||||
The `cprof` file can be viewed with:
|
||||
|
||||
[SnakeViz](https://jiffyclub.github.io/snakeviz/)
|
||||
[Gprof2dot](https://github.com/jrfonseca/gprof2dot)
|
||||
* [SnakeViz](https://jiffyclub.github.io/snakeviz/)
|
||||
* [Gprof2dot](https://github.com/jrfonseca/gprof2dot)
|
||||
|
||||
Additionally, the profiler will generate a `callgrind.out` file that can be viewed with:
|
||||
|
||||
[kcachegrind](https://kcachegrind.github.io/) or qcachegrind
|
||||
* [KCachegrind or QCachegrind](https://kcachegrind.github.io/)
|
||||
* [Gprof2dot](https://github.com/jrfonseca/gprof2dot)
|
||||
|
||||
The gprof2dot tool generates [DOT](http://www.graphviz.org/doc/info/lang.html) files, which can be converted to images using the `dot` tool from [Graphviz](http://www.graphviz.org/) or viewed directly using [xdot](https://github.com/jrfonseca/xdot.py). The `-e` and `-n` parameters can be used to set the minimum percentage required to include a function in the output file. Observe these examples:
|
||||
|
||||
```bash
|
||||
# Generating the .dot files:
|
||||
gprof2dot -f pstats -e 0.05 -n 0.25 profile.1234567890123456.cprof -o profile.dot
|
||||
gprof2dot -f callgrind -e 0.05 -n 0.25 callgrind.out.1234567890123456 -o callgrind.dot
|
||||
|
||||
# Converting to SVG and PNG formats:
|
||||
dot callgrind.dot -Tsvg -o callgrind.svg
|
||||
dot callgrind.dot -Tpng -o callgrind.png
|
||||
|
||||
# Alternatively, both commands in a single line:
|
||||
gprof2dot -f pstats profile.1234567890123456.cprof | dot -Tsvg -o profile.svg
|
||||
```
|
||||
|
||||
### Service `profiler.memory`
|
||||
|
||||
|
||||
@ -121,7 +121,7 @@ Privileges can be either applied to Groups or Roles.
|
||||
1. Click `Datacenter`
|
||||
2. Open `Permissions` and click `Groups`
|
||||
3. Click the `Create` button above all the existing groups
|
||||
4. Name the new group (e.g., "HomeAssistant")
|
||||
4. Name the new group (e.g., `HomeAssistant`)
|
||||
5. Click `Create`
|
||||
|
||||
### Add Group Permissions to all Assets
|
||||
@ -143,7 +143,7 @@ Creating a dedicated user for Home Assistant, limited to only to the access just
|
||||
1. Click `Datacenter`
|
||||
2. Open `Permissions` and click `Users`
|
||||
3. Click `Add`
|
||||
4. Enter a username (e.g., "hass")
|
||||
4. Enter a username (e.g.,` hass`)
|
||||
5. Set the realm to "Proxmox VE authentication server"
|
||||
6. Enter a secure password (it can be complex as you will only need to copy/paste it into your Home Assistant configuration)
|
||||
7. Select the group just created earlier (`HomeAssistant`) to grant access to Proxmox
|
||||
|
||||
@ -362,6 +362,12 @@ pip3 install mysqlclient
|
||||
|
||||
After installing the dependencies, it is required to create the database manually. During the startup, Home Assistant will look for the database specified in the `db_url`. If the database doesn't exist, it will not automatically create it for you.
|
||||
|
||||
```bash
|
||||
SET GLOBAL default_storage_engine = 'InnoDB';
|
||||
CREATE DATABASE DB_NAME CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
|
||||
```
|
||||
Where `DB_NAME` is the name of your database
|
||||
|
||||
Once Home Assistant finds the database, with the right level of permissions, all the required tables will then be automatically created and the data will be populated accordingly.
|
||||
|
||||
### PostgreSQL
|
||||
|
||||
@ -74,7 +74,7 @@ icon:
|
||||
required: false
|
||||
type: template
|
||||
json_attributes:
|
||||
description: A list of keys to extract values from a JSON dictionary result and then set as sensor attributes. If the endpoint returns XML with the "text/xml", "application/xml" or "application/xhtml+xml" content type, it will automatically be converted to JSON according to this [specification](https://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html)
|
||||
description: "A list of keys to extract values from a JSON dictionary result and then set as sensor attributes. If the endpoint returns XML with the `text/xml`, `application/xml` or `application/xhtml+xml` content type, it will automatically be converted to JSON according to this [specification](https://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html)"
|
||||
required: false
|
||||
type: [string, list]
|
||||
json_attributes_path:
|
||||
|
||||
@ -94,7 +94,7 @@ action:
|
||||
|
||||
### Text message with an attachment from a URL
|
||||
|
||||
To attach files from outside of HomeAssistant, the URLs must be added to the [`allowlist_external_urls`](/docs/configuration/basic/#allowlist_external_urls) list.
|
||||
To attach files from outside of Home Assistant, the URLs must be added to the [`allowlist_external_urls`](/docs/configuration/basic/#allowlist_external_urls) list.
|
||||
|
||||
Note there is a 50MB size limit for attachments retrieved via URLs. You can also set `verify_ssl` to `false` to ignore SSL errors (default `true`).
|
||||
|
||||
|
||||
@ -70,7 +70,8 @@ You will need a USB GSM stick modem or device like SIM800L v2 connected via USB
|
||||
Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/convert-huawei-e3372h-153-from.html))
|
||||
- [Huawei E3531](https://www.amazon.com/Modem-Huawei-Unlocked-Caribbean-Desbloqueado/dp/B011YZZ6Q2/ref=sr_1_1?keywords=Huawei+E3531&qid=1581447800&sr=8-1)
|
||||
- [Huawei E3272](https://www.amazon.com/Huawei-E3272s-506-Unlocked-Americas-Europe/dp/B00HBL51OQ)
|
||||
|
||||
- [SIM800C](https://www.amazon.com/gp/product/B087Z6F953/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1)
|
||||
- ZTE K3565-Z
|
||||
|
||||
### List of modems known to NOT work
|
||||
|
||||
@ -80,13 +81,17 @@ Need to unlock it using [this guide](http://blog.asiantuntijakaveri.fi/2015/07/c
|
||||
|
||||
Search in the [Gammu database](https://wammu.eu/phones/) for modems with AT connection.
|
||||
|
||||
### Huawei modems on Raspberry Pi (and similar) devices
|
||||
### Huawei/ZTE modems (and similar) devices - NOT applicable for users of Home Assistant OS, Container or Supervised.
|
||||
|
||||
For some unknown reason, the rule that converts these modems from storage devices into serial devices does not run automatically. To work around this problem, follow the procedure to create `udev` rule on a configuration USB stick for the device to switch to serial mode.
|
||||
For some unknown reason, the rule that converts these modems from storage devices into serial devices may not run automatically. To work around this problem, follow the procedure below to change the modem mode and (optionally) create `udev` rule on a configuration USB stick for the device to switch to serial mode persistently.
|
||||
|
||||
0. Try disable virtual cd-rom and change work mode "only modem". After this modem correct work on Raspberry Pi without 'udev' rule.
|
||||
1. Install the `usb_modeswitch` software to switch the modem operational mode (for Debian/Ubuntu distros):
|
||||
|
||||
1. Run `lsusb`, its output looks like this:
|
||||
```bash
|
||||
sudo apt update && sudo apt install usb-modeswitch -y
|
||||
```
|
||||
|
||||
2. Run `lsusb`, its output should be similar to this:
|
||||
|
||||
```bash
|
||||
bus 000 device 001: ID 1FFF:342a
|
||||
@ -97,6 +102,15 @@ bus 000 device 002: ID 1232:15ca
|
||||
|
||||
Identify the brand for your GSM modem, copy the `brand_Id` and `product_id` (In this case `brand_id = 12d1` and `product_Id = 15ca`)
|
||||
|
||||
3. Try disabling virtual cd-rom and change work mode to "only modem":
|
||||
|
||||
```bash
|
||||
sudo /sbin/usb_modeswitch -X -v 12d1 -p 15ca
|
||||
```
|
||||
Re-plug the device. After this the modem correct should work without the following 'udev' rule.
|
||||
|
||||
4. (Optional) Configure the udev rule to persist the correct modem configuration even after disconnecting it:
|
||||
|
||||
Set this content in file `udev\10-gsm-modem.rules` in the [configuration USB](https://github.com/home-assistant/operating-system/blob/master/Documentation/configuration.md#automatic):
|
||||
(Replace `brand_Id` and `product_id` for the numbers reported by `lsusb`)
|
||||
|
||||
@ -116,7 +130,7 @@ ACTION=="add" \
|
||||
, RUN+="/sbin/usb_modeswitch -X -v 12d1 -p 15ca"
|
||||
```
|
||||
|
||||
Plug the USB stick, reboot the device, run `lsusb` again.
|
||||
Re-plug the USB stick, reboot the device, run `lsusb` again.
|
||||
The resulting product id now should be different and the brand id should be the same.
|
||||
And `ls -l /dev/*USB*` should now report your device.
|
||||
|
||||
|
||||
@ -19,6 +19,6 @@ ha_integration_type: integration
|
||||
|
||||
The Soma integration will allow users to integrate their Soma Smarthome devices into Home Assistant using the Soma Connect hub.
|
||||
|
||||
You can build a Soma Connect yourself if you have a spare Raspberry Pi. You just need to follow the [ official instructions](https://somasmarthome.zendesk.com/hc/en-us/articles/360035521234-Install-SOMA-Connect-software-on-SOMA-Connect-Raspberry-Pi). After you have the SD card plug in the Pi and use an ethernet cable or [set up Wi-Fi](https://somasmarthome.zendesk.com/hc/en-us/articles/360026210333-Configuring-Wi-Fi-access). Then find the IP address by checking your routers DHCP table (we will work on this step).
|
||||
You can build a Soma Connect yourself if you have a spare Raspberry Pi. You just need to follow the [ official instructions](https://support.somasmarthome.com/hc/en-us/articles/360035521234-Install-SOMA-Connect-software). After you have the SD card plug in the Pi and use an ethernet cable or [set up Wi-Fi](https://support.somasmarthome.com/hc/en-us/articles/360026210333). Then find the IP address by checking your routers DHCP table (we will work on this step).
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -58,7 +58,7 @@ It can also be used to target a Squeezebox from IFTTT (or Dialogflow, Alexa...).
|
||||
|
||||
For example, to play an album from your collection, create an IFTTT applet like this:
|
||||
|
||||
- Trigger: Google assistant, with sentence: `I want to listen to album $`
|
||||
- Trigger: Google Assistant, with sentence: `I want to listen to album $`
|
||||
- Action: JSON post query with such JSON body:
|
||||
`{ "entity_id": "media_player.squeezebox_radio", "command": "playlist", "parameters": ["loadtracks", "album.titlesearch={{TextField}}"] }`
|
||||
|
||||
|
||||
@ -141,3 +141,44 @@ Wireless LAN adapter Wireless Network Connection:
|
||||
```
|
||||
|
||||
Where the name is `Wireless Network Connection`.
|
||||
|
||||
## All available resources
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with all entry types (delete/comment out as necessary)
|
||||
sensor:
|
||||
- platform: systemmonitor
|
||||
resources:
|
||||
- type: disk_use_percent
|
||||
arg: /config
|
||||
- type: disk_use
|
||||
- type: disk_free
|
||||
- type: memory_use_percent
|
||||
- type: memory_use
|
||||
- type: memory_free
|
||||
- type: swap_use_percent
|
||||
- type: swap_use
|
||||
- type: swap_free
|
||||
- type: load_1m
|
||||
- type: load_5m
|
||||
- type: load_15m
|
||||
- type: network_in
|
||||
arg: eth0
|
||||
- type: network_out
|
||||
arg: eth0
|
||||
- type: throughput_network_in
|
||||
arg: eth0
|
||||
- type: throughput_network_out
|
||||
arg: eth0
|
||||
- type: packets_in
|
||||
arg: eth0
|
||||
- type: packets_out
|
||||
arg: eth0
|
||||
- type: ipv4_address
|
||||
arg: eth0
|
||||
- type: ipv6_address
|
||||
arg: eth0
|
||||
- type: processor_use
|
||||
- type: processor_temperature
|
||||
- type: last_boot
|
||||
```
|
||||
|
||||
@ -45,6 +45,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- HS110 (supports consumption sensors)
|
||||
- KP105
|
||||
- KP115 (supports consumption sensors)
|
||||
- KP125 (supports consumption sensors)
|
||||
|
||||
### Strip (Multi-Plug)
|
||||
|
||||
|
||||
@ -50,16 +50,11 @@ time_memory:
|
||||
required: false
|
||||
type: integer
|
||||
default: 300
|
||||
base_url:
|
||||
description: A base URL to use *instead* of the one set in the Home Assistant [configuration](/docs/configuration/basic). It is used as-is by the `tts` component. In particular, you need to include the protocol scheme `http://` or `https://` and the correct port number. They will not be automatically added for you.
|
||||
required: false
|
||||
type: string
|
||||
default: value of internal URL
|
||||
service_name:
|
||||
description: Define the service name.
|
||||
required: false
|
||||
type: string
|
||||
default: The service name default set to <platform>_say. For example, for google_translate tts, its service name default is `google_translate_say`.
|
||||
default: The service name default set to <platform>_say. For example, for google_translate TTS, its service name default is `google_translate_say`.
|
||||
{% endconfiguration %}
|
||||
|
||||
The extended example from above would look like the following sample:
|
||||
@ -75,15 +70,6 @@ tts:
|
||||
service_name: google_say
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
|
||||
In the above example, `base_url` is custom to this particular TTS platform configuration. It is not suggesting that you use the internal URL that you have set for your core Home Assistant configuration. The reason you might need to do this is outlined in the next section.
|
||||
|
||||
</div>
|
||||
|
||||
## When do you need to set `base_url` here?
|
||||
|
||||
The general answer is "whenever the global internal URL set in the [configuration](/docs/configuration/basic/) of Home Assistant is not adequate to allow the `say` service to run". The `say` service operates by generating a media file that contains the speech corresponding to the text passed to the service. Then the `say` service sends a message to the media device with a URL pointing to the file. The device fetches the media file at the URL and plays the media. Some combinations of a media device, network configuration and Home Assistant configuration can make it so that the device cannot fetch the media file.
|
||||
|
||||
The following sections describe some of the problems encountered with media devices.
|
||||
|
||||
|
||||
@ -85,7 +85,7 @@ See the [device tracker integration page](/integrations/device_tracker/) for ins
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If you find that this never creates `known_devices.yaml`, or if you need more information on the communication chain between Home Assistant and OpenWRT, follow these steps to grab the packet stream and gain insight into what's happening.
|
||||
If you find that this never creates `known_devices.yaml`, or if you need more information on the communication chain between Home Assistant and OpenWrt, follow these steps to grab the packet stream and gain insight into what's happening.
|
||||
|
||||
### Increase Log Level
|
||||
|
||||
|
||||
@ -148,7 +148,7 @@ Number 3 sends an image from a local path.
|
||||
### Jabber File Message
|
||||
|
||||
|
||||
Number 4 sends a text-file, retrieved from Github, renamed to `Hass_Cheatsheet.txt` to be viewable on a mobile Android device, as most don't offer any application to view `.md` files. Optionally you can add a timeout for the HTTP upload in seconds.
|
||||
Number 4 sends a text-file, retrieved from GitHub, renamed to `Hass_Cheatsheet.txt` to be viewable on a mobile Android device, as most don't offer any application to view `.md` files. Optionally you can add a timeout for the HTTP upload in seconds.
|
||||
|
||||
```yaml
|
||||
# Example script.yaml entry
|
||||
|
||||
@ -424,8 +424,8 @@ When reporting issues, please provide the following information in addition to i
|
||||
|
||||
1. Debug logs for the issue, see [debug logging](#debug-logging)
|
||||
2. Model of Zigbee radio being used
|
||||
3. If issue is related to a specific Zigbee device, provide device Zigbee signature. Signature is available at
|
||||
**Settings** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
|
||||
3. If issue is related to a specific Zigbee device, provide both "Zigbee Device Signature" and "Diagnostics" information.
|
||||
* Both the "Zigbee Device Signature" and "Diagnostics" information can be found by clicking **Settings** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> Click "**Zigbee Device Signature**" and "**Download Diagnostics**" respectively.
|
||||
|
||||
### Debug logging
|
||||
|
||||
|
||||
@ -685,7 +685,7 @@ Once you have the Z-Wave server up and running, you need to install and configur
|
||||
|
||||
If you're running full Home Assistant with supervisor, you will be presented with a dialog that asks if you want to use the Z-Wave JS Supervisor add-on. You **must** uncheck this box if you are running the Z-Wave JS server in any manner other than the official Z-Wave JS add-on, including using Z-Wave JS to MQTT add-on.
|
||||
|
||||
If you're not running the supervisor or you've unchecked the above mentioned box, you will be asked to enter a websocket URL (defaults to ws://localhost:3000). It is very important that you fill in the correct (docker) IP/hostname here. For example for the Z-Wave JS to MQTT add-on this is `ws://a0d7b954-zwavejs2mqtt:3000`.
|
||||
If you're not running the supervisor or you've unchecked the above mentioned box, you will be asked to enter a websocket URL (defaults to ws://localhost:3000). It is very important that you fill in the correct (Docker) IP/hostname here. For example for the Z-Wave JS to MQTT add-on this is `ws://a0d7b954-zwavejs2mqtt:3000`.
|
||||
|
||||
## Frequently Asked Questions
|
||||
|
||||
|
||||
@ -135,7 +135,7 @@ automatically populates with entities of devices you have assigned
|
||||
to that specific area.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-12/area-card.png' alt='Screenshot of a new area Lovelace card'>
|
||||
<img src='/images/dashboards/area-card.png' alt='Screenshot of a new area Lovelace card'>
|
||||
Screenshot of a new area Lovelace card.
|
||||
</p>
|
||||
|
||||
|
||||
@ -65,6 +65,7 @@ Enjoy the release (and upcoming events)!
|
||||
- [Release 2022.6.4 - June 7](#release-202264---june-7)
|
||||
- [Release 2022.6.5 - June 10](#release-202265---june-10)
|
||||
- [Release 2022.6.6 - June 14](#release-202266---june-14)
|
||||
- [Release 2022.6.7 - June 22](#release-202267---june-22)
|
||||
- [Need help? Join the community!](#need-help-join-the-community)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
@ -637,6 +638,79 @@ The following integrations are now available via the Home Assistant UI:
|
||||
[yeelight docs]: /integrations/yeelight/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2022.6.7 - June 22
|
||||
|
||||
- Ensure metoffice daily are returned once daily ([@gordallott] - [#72440]) ([metoffice docs])
|
||||
- Fix thumbnail issues in Twitch integration ([@bergdahl] - [#72564]) ([twitch docs])
|
||||
- Bump aiobafi6 to 0.6.0 to fix logging performance ([@jfroy] - [#73517]) ([baf docs]) (dependency)
|
||||
- Use IP address instead of hostname in Brother integration ([@bieniu] - [#73556]) ([brother docs])
|
||||
- Bump growattServer to 1.2.2 ([@muppet3000] - [#73561]) ([growatt_server docs]) (dependency)
|
||||
- Handle offline generators in oncue ([@bdraco] - [#73568]) ([oncue docs])
|
||||
- Don't attempt to reload MQTT device tracker ([@emontnemery] - [#73577]) ([mqtt docs])
|
||||
- Fix handling of illegal dates in onvif sensor ([@emontnemery] - [#73600]) ([onvif docs])
|
||||
- Fix voltage and current values for Fritz!DECT smart plugs ([@mib1185] - [#73608]) ([fritzbox docs])
|
||||
- Fix MQTT config schema to ensure correct validation ([@jbouwh] - [#73619]) ([mqtt docs])
|
||||
- Fix calling permanent off with nexia ([@bdraco] - [#73623]) ([nexia docs]) (dependency)
|
||||
- Don't verify ssl certificates for ssdp/upnp devices ([@StevenLooman] - [#73647]) ([upnp docs]) ([ssdp docs])
|
||||
- Retry on SenseAPIException during sense config entry setup ([@bdraco] - [#73651]) ([sense docs])
|
||||
- Fix AmbiClimate services definition ([@maxgashkov] - [#73668]) ([ambiclimate docs])
|
||||
- Update aiomusiccast ([@micha91] - [#73694]) ([yamaha_musiccast docs]) (dependency)
|
||||
- Fix CSRF token for UniFi ([@Kane610] - [#73716]) ([unifi docs])
|
||||
- Insteon bug fixes ([@teharris1] - [#73791]) ([insteon docs])
|
||||
- Fix Plugwise migration error ([@frenck] - [#73812]) ([plugwise docs])
|
||||
|
||||
[#72440]: https://github.com/home-assistant/core/pull/72440
|
||||
[#72564]: https://github.com/home-assistant/core/pull/72564
|
||||
[#73517]: https://github.com/home-assistant/core/pull/73517
|
||||
[#73556]: https://github.com/home-assistant/core/pull/73556
|
||||
[#73561]: https://github.com/home-assistant/core/pull/73561
|
||||
[#73568]: https://github.com/home-assistant/core/pull/73568
|
||||
[#73577]: https://github.com/home-assistant/core/pull/73577
|
||||
[#73600]: https://github.com/home-assistant/core/pull/73600
|
||||
[#73608]: https://github.com/home-assistant/core/pull/73608
|
||||
[#73619]: https://github.com/home-assistant/core/pull/73619
|
||||
[#73623]: https://github.com/home-assistant/core/pull/73623
|
||||
[#73647]: https://github.com/home-assistant/core/pull/73647
|
||||
[#73651]: https://github.com/home-assistant/core/pull/73651
|
||||
[#73668]: https://github.com/home-assistant/core/pull/73668
|
||||
[#73694]: https://github.com/home-assistant/core/pull/73694
|
||||
[#73716]: https://github.com/home-assistant/core/pull/73716
|
||||
[#73791]: https://github.com/home-assistant/core/pull/73791
|
||||
[#73812]: https://github.com/home-assistant/core/pull/73812
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@StevenLooman]: https://github.com/StevenLooman
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bergdahl]: https://github.com/bergdahl
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@gordallott]: https://github.com/gordallott
|
||||
[@jbouwh]: https://github.com/jbouwh
|
||||
[@jfroy]: https://github.com/jfroy
|
||||
[@maxgashkov]: https://github.com/maxgashkov
|
||||
[@mib1185]: https://github.com/mib1185
|
||||
[@micha91]: https://github.com/micha91
|
||||
[@muppet3000]: https://github.com/muppet3000
|
||||
[@teharris1]: https://github.com/teharris1
|
||||
[ambiclimate docs]: /integrations/ambiclimate/
|
||||
[baf docs]: /integrations/baf/
|
||||
[brother docs]: /integrations/brother/
|
||||
[fritzbox docs]: /integrations/fritzbox/
|
||||
[growatt_server docs]: /integrations/growatt_server/
|
||||
[insteon docs]: /integrations/insteon/
|
||||
[metoffice docs]: /integrations/metoffice/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[nexia docs]: /integrations/nexia/
|
||||
[oncue docs]: /integrations/oncue/
|
||||
[onvif docs]: /integrations/onvif/
|
||||
[plugwise docs]: /integrations/plugwise/
|
||||
[sense docs]: /integrations/sense/
|
||||
[ssdp docs]: /integrations/ssdp/
|
||||
[twitch docs]: /integrations/twitch/
|
||||
[unifi docs]: /integrations/unifi/
|
||||
[upnp docs]: /integrations/upnp/
|
||||
[yamaha_musiccast docs]: /integrations/yamaha_musiccast/
|
||||
|
||||
## Need help? Join the community!
|
||||
|
||||
Home Assistant has a great community of users who are all more than willing
|
||||
|
||||
@ -499,3 +499,6 @@
|
||||
/integrations/yessssms /more-info/removed-integration 301
|
||||
/integrations/yweather /more-info/removed-integration 301
|
||||
/components/zwave /integrations/zwave_js
|
||||
|
||||
# Lovelace images
|
||||
/images/dashboards/lovelace_* /images/dashboards/:splat
|
||||
|
||||
@ -10,7 +10,7 @@ You can add a view to your user interface, by clicking the menu (three dots at t
|
||||
Click the `+` button in the top menu bar.
|
||||
|
||||
<p class="img">
|
||||
<img src="/images/dashboards/lovelace_views.png" alt="Views toolbar">
|
||||
<img src="/images/dashboards/views.png" alt="Views toolbar">
|
||||
Use titles and icons to describe the content of views.
|
||||
</p>
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 370 KiB After Width: | Height: | Size: 370 KiB |
|
Before Width: | Height: | Size: 495 KiB After Width: | Height: | Size: 495 KiB |
|
Before Width: | Height: | Size: 141 KiB After Width: | Height: | Size: 141 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 944 B After Width: | Height: | Size: 944 B |
|
Before Width: | Height: | Size: 3.9 KiB After Width: | Height: | Size: 3.9 KiB |
|
Before Width: | Height: | Size: 3.1 KiB After Width: | Height: | Size: 3.1 KiB |
|
Before Width: | Height: | Size: 1.8 KiB After Width: | Height: | Size: 1.8 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 35 KiB |
|
Before Width: | Height: | Size: 192 KiB After Width: | Height: | Size: 192 KiB |
|
Before Width: | Height: | Size: 3.8 KiB After Width: | Height: | Size: 3.8 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user