mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Merge branch 'current' into next
This commit is contained in:
commit
68a391074e
2
.github/workflows/test.yml
vendored
2
.github/workflows/test.yml
vendored
@ -57,7 +57,7 @@ jobs:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2
|
||||
- name: Setting up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1.64.1
|
||||
uses: ruby/setup-ruby@v1.65.0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Setup Ruby Gems cache
|
||||
|
@ -58,7 +58,7 @@ cover:
|
||||
required: exclusive
|
||||
type: template
|
||||
position_template:
|
||||
description: Defines a template to get the state of the cover. Legal values are numbers between `0` (closed) and `100` (open). [`value_template`](#value_template) and [`position_template`](#position_template) cannot be specified concurrently.
|
||||
description: Defines a template to get the position of the cover. Legal values are numbers between `0` (closed) and `100` (open). [`value_template`](#value_template) and [`position_template`](#position_template) cannot be specified concurrently.
|
||||
required: exclusive
|
||||
type: template
|
||||
icon_template:
|
||||
@ -189,7 +189,7 @@ This example allows you to control two or more covers at once.
|
||||
homeassistant:
|
||||
customize:
|
||||
cover_group:
|
||||
assume_state: true
|
||||
assumed_state: true
|
||||
|
||||
cover:
|
||||
- platform: template
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Flux
|
||||
description: Instructions on how to have switches call command line commands.
|
||||
description: Instructions on how to automate the color temperature of your lights based on the time of day with Home Assistant
|
||||
ha_category:
|
||||
- Automation
|
||||
ha_release: 0.21
|
||||
@ -17,7 +17,7 @@ The integration will update your lights based on the time of day. It will only a
|
||||
|
||||
During the day (in between `start time` and `sunset time`), it will fade the lights from the `start_colortemp` to the `sunset_colortemp`. After sunset (between `sunset_time` and `stop_time`), the lights will fade from the `sunset_colortemp` to the `stop_colortemp`. If the lights are still on after the `stop_time` it will continue to change the light to the `stop_colortemp` until the light is turned off. The fade effect is created by updating the lights periodically.
|
||||
|
||||
The color temperature is specified kelvin, and accepted values are between 1000 and 40000 kelvin. Lower values will seem more red, while higher will look more white.
|
||||
The color temperature is specified in kelvin, and accepted values are between 1000 and 40000 kelvin. Lower values will seem more red, while higher will look more white.
|
||||
|
||||
If you want to update at variable intervals, you can leave the switch turned off and use automation rules that call the service `switch.<name>_update` whenever you want the lights updated, where `<name>` equals the `name:` property in the switch configuration.
|
||||
|
||||
|
@ -16,6 +16,4 @@ The `Internet Printing Protocol (IPP)` integration allows you to read current da
|
||||
|
||||
It provides information about the printer's state and remaining ink levels.
|
||||
|
||||
## Configuration
|
||||
|
||||
To add `Internet Printing Protocol (IPP)` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Internet Printing Protocol (IPP)**.
|
||||
{% include integrations/config_flow.md %}
|
||||
|
@ -132,3 +132,7 @@ Please check your logs if there are any warnings. When there is a message about
|
||||
### There is a warning about a bad response but everything works as expected
|
||||
|
||||
Do you have a stale robot in your configuration? Try to [look into your account](https://neatorobotics.com) and delete any stale robots. If these warnings are about actively used robots, please report an issue to help us solving this problem.
|
||||
|
||||
### Server got itself in trouble
|
||||
|
||||
If you see this message after trying to set up Neato, please check if the setup still worked or not. If not, try again and make sure you start the process only once. Do not click the "Open External Page" button if a page has already opened by itself. Be patient and wait for the setup to complete.
|
||||
|
@ -86,13 +86,15 @@ nodes:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
Example with multiple VMs and no containers:
|
||||
Example with multiple VMs, no containers, self-signed certificate and pve realm for the user setup described below:
|
||||
|
||||
```yaml
|
||||
proxmoxve:
|
||||
- host: IP_ADDRESS
|
||||
username: USERNAME
|
||||
password: PASSWORD
|
||||
verify_ssl: false
|
||||
realm: pve
|
||||
nodes:
|
||||
- node: NODE_NAME
|
||||
vms:
|
||||
@ -110,38 +112,39 @@ The created sensor will be called `binary_sensor.NODE_NAME_VMNAME_running`.
|
||||
|
||||
To be able to retrieve the status of VMs and containers, the user used to connect must minimally have the `VM.Audit` privilege. Below is a guide to how to configure a new user with the minimum required permissions.
|
||||
|
||||
### Create Home Assistant Role
|
||||
### Create Home Assistant Group
|
||||
|
||||
Before creating the user, we need to create a permissions role for the user.
|
||||
Before creating the user, we need to create a group for the user.
|
||||
Privileges can be either applied to Groups or Roles.
|
||||
|
||||
1. Click `Datacenter`
|
||||
2. Open `Permissions` and click `Roles`
|
||||
3. Click the `Create` button above all the existing roles
|
||||
4. name the new role (e.g., "home-assistant")
|
||||
5. Click the arrow next to privileges and select `VM.Audit` in the dropdown
|
||||
6. Click `Create`
|
||||
2. Open `Permissions` and click `Groups`
|
||||
3. Click the `Create` button above all the existing groups
|
||||
4. Name the new group (e.g., "HomeAssistant")
|
||||
5. Click `Create`
|
||||
|
||||
### Add Group Permissions to all Assets
|
||||
|
||||
For the group to access the VMs we need to grant it the auditor role
|
||||
|
||||
1. Click `Datacenter`
|
||||
2. Click `Permissions`
|
||||
3. Open `Add` and click `Group Permission`
|
||||
4. Select "/" for the path
|
||||
5. Select your Home Assistant group (`HomeAssistant`)
|
||||
6. Select the Auditor role (`PVEAuditor`)
|
||||
7. Make sure `Propagate` is checked
|
||||
|
||||
### Create Home Assistant User
|
||||
|
||||
Creating a dedicated user for Home Assistant, limited to only the role just created is the most secure method. These instructions use the `pve` realm for the user. This allows a connection, but ensures that the user is not authenticated for SSH connections. If you use the `pve` realm, just be sure to add `realm: pve` to your configuration.
|
||||
Creating a dedicated user for Home Assistant, limited to only to the access just created is the most secure method. These instructions use the `pve` realm for the user. This allows a connection, but ensures that the user is not authenticated for SSH connections. If you use the `pve` realm, just be sure to add `realm: pve` to your configuration.
|
||||
|
||||
1. Click `Datacenter`
|
||||
2. Open `Permissions` and click `Users`
|
||||
3. Click `Add`
|
||||
4. Enter a username (e.g., "hass")
|
||||
5. Set the realm to "Proxmox VE authentication server"
|
||||
Enter a secure password (it can be complex as you will only need to copy/paste it into your Home Assistant configuration)
|
||||
6. Ensure `Enabled` is checked and `Expire` is set to "never"
|
||||
7. Click `Add`
|
||||
|
||||
### Add User Permissions to Assets
|
||||
|
||||
To apply the user and role just created, we need to give it permissions
|
||||
|
||||
1. Click `Datacenter`
|
||||
2. Click `Permissions`
|
||||
3. Open `Add` and click `User Permission`
|
||||
4. Select "/" for the path
|
||||
5. Select your Home Assistant user (`hass`)
|
||||
6. Select the Home Assistant role (`home-assistant`)
|
||||
7. Make sure `Propagate` is checked
|
||||
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
|
||||
8. Ensure `Enabled` is checked and `Expire` is set to "never"
|
||||
9. Click `Add`
|
||||
|
@ -23,7 +23,7 @@ The Sonos integration makes various custom services available.
|
||||
|
||||
### Service `sonos.snapshot`
|
||||
|
||||
Take a snapshot of what is currently playing on one or more speakers. This service, and the following one, are useful if you want to play a doorbell or notification sound and resume playback afterwards. If no `entity_id` is provided, all speakers are snapshotted.
|
||||
Take a snapshot of what is currently playing on one or more speakers. This service, and the following one, are useful if you want to play a doorbell or notification sound and resume playback afterwards.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -38,7 +38,7 @@ The queue is not snapshotted and must be left untouched until the restore. Using
|
||||
|
||||
### Service `sonos.restore`
|
||||
|
||||
Restore a previously taken snapshot of one or more speakers. If no `entity_id` is provided, all speakers are restored.
|
||||
Restore a previously taken snapshot of one or more speakers.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -66,7 +66,7 @@ Group players together under a single coordinator. This will make a new group or
|
||||
|
||||
### Service `sonos.unjoin`
|
||||
|
||||
Remove one or more speakers from their group of speakers. If no `entity_id` is provided, all speakers are unjoined.
|
||||
Remove one or more speakers from their group of speakers.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
|
99
source/_posts/2021-02-26-community-highlights.markdown
Normal file
99
source/_posts/2021-02-26-community-highlights.markdown
Normal file
@ -0,0 +1,99 @@
|
||||
---
|
||||
title: "Community Highlights: 10th edition"
|
||||
description: "Try the new ApexCharts card, build your own switch panel and get inspiration for your own Lovelace dashboard."
|
||||
date: 2021-02-26 00:00:00
|
||||
date_formatted: "February 26, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-02-26-community-highlights/social.png
|
||||
---
|
||||
|
||||
Oh yeah! This is already the 10th edition of the Home Assistant Community Highlights!
|
||||
Some interesting things popped up around our community, we thought was worth sharing.
|
||||
|
||||
Do you want to share something for the next edition? Information on [how to share](#got-a-tip-for-the-next-edition).
|
||||
|
||||
./Klaas
|
||||
|
||||
## Apexcharts Card
|
||||
|
||||
Would you like to map data in graphs? Then you should definitely try the new
|
||||
[ApexCharts card](https://github.com/RomRider/apexcharts-card) from [RomRider](https://github.com/RomRider),
|
||||
the graphs in this card are based on the ApexChartsJS and that looks pretty cool.
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<object type="image/svg+xml" data="https://gh-card.dev/repos/RomRider/apexcharts-card.svg?link_target=_blank"></object>
|
||||
</div>
|
||||
<br>
|
||||
<a href="https://github.com/RomRider/apexcharts-card" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-02-26-community-highlights/apexcharts.png'
|
||||
alt="What you can make with ApexCharts card"
|
||||
style='border: 0;box-shadow: none;'
|
||||
/>
|
||||
</a>
|
||||
|
||||
If you would like to stay informed of the developments, you could also follow
|
||||
[this topic](https://community.home-assistant.io/t/apexcharts-card-a-highly-customizable-graph-card/272877) on our forum.
|
||||
|
||||
## Home Assistant switch panel
|
||||
|
||||
Last week, [amauryverschooren](https://github.com/amauryverschooren) shared his
|
||||
own version of a HA Switch Plate, so that you can operate your Home Assistant via
|
||||
a physically small touch panel, which you can place in a specific room, for example.
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<object type="image/svg+xml" data="https://gh-card.dev/repos/amauryverschooren/HASP-LVGL.svg?link_target=_blank"></object>
|
||||
</div>
|
||||
<br>
|
||||
<a href="https://github.com/amauryverschooren/HASP-LVGL" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-02-26-community-highlights/hasp.png'
|
||||
alt="The fysical switch panel"
|
||||
style='border: 0;box-shadow: none;'
|
||||
/>
|
||||
</a>
|
||||
|
||||
## Lovelace dashboard inspiration
|
||||
|
||||
Still looking for some new inspiration for your Lovelace dashboards? Last week we
|
||||
came across some beautiful Lovelace dashboards on our [Home Assistant subreddit][reddit]
|
||||
page of [swake88](https://www.reddit.com/user/swake88/). Who knows, there might be something fun for you to make.
|
||||
|
||||
You can find [here](https://www.reddit.com/r/homeassistant/comments/lqo7wr/ha_2_years_later_and_what_ive_built_so_far/) the related Reddit topic.
|
||||
|
||||
<blockquote class="imgur-embed-pub" lang="en" data-id="a/8BHxBVN" ><a href="//imgur.com/a/8BHxBVN">Home Assistant - Feb 2021</a></blockquote><script async src="//s.imgur.com/min/embed.js" charset="utf-8"></script>
|
||||
|
||||
Which card in Lovelace are you most proud of? Share it with us!
|
||||
|
||||
## Hidden garage
|
||||
|
||||
Do you have a vacuum cleaning robot but you don't know where to place the charging
|
||||
station? Maybe you can hide these behind a plinth, like what [ialex87](https://www.reddit.com/user/ialex87/) did.
|
||||
|
||||
<blockquote class="reddit-card" data-card-created="1614344206"><a href="https://www.reddit.com/r/homeassistant/comments/l4wsyk/my_vacuum_hidden_garage_under_the_kitchen/">My vacuum hidden garage under the kitchen</a> from <a href="http://www.reddit.com/r/homeassistant">r/homeassistant</a></blockquote>
|
||||
<script async src="//embed.redditmedia.com/widgets/platform.js" charset="UTF-8"></script>
|
||||
|
||||
## Got a tip for the next edition?
|
||||
|
||||
Have you seen (or made) something awesome, interesting, unique, amazing,
|
||||
inspirational, unusual or funny, using Home Assistant?
|
||||
|
||||
[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
|
||||
|
||||
Also, don't forget to share your creations with us via Social Media:
|
||||
|
||||
- Twitter it! Be sure to mention [@home_assistant][twitter]
|
||||
- Share it on our [Facebook group][facebook-group]
|
||||
- Post it to our [subreddit][reddit]
|
||||
- Tag [@homeasssistant][instagram] on Instagram
|
||||
- Or via chat, drop us a line in the [#lounge at Discord][chat]
|
||||
|
||||
See you next edition!
|
||||
|
||||
[chat]: https://www.home-assistant.io/join-chat
|
||||
[facebook-group]: https://www.facebook.com/groups/HomeAssistant/
|
||||
[instagram]: https://www.instagram.com/homeassistant/
|
||||
[reddit]: https://www.reddit.com/r/homeassistant
|
||||
[twitter]: https://www.twitter.com/home_assistant
|
Binary file not shown.
After Width: | Height: | Size: 68 KiB |
BIN
source/images/blog/2021-02-26-community-highlights/hasp.png
Normal file
BIN
source/images/blog/2021-02-26-community-highlights/hasp.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 2.2 MiB |
BIN
source/images/blog/2021-02-26-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-02-26-community-highlights/social.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 313 KiB |
14
source/more-info/pwned-passwords.markdown
Normal file
14
source/more-info/pwned-passwords.markdown
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
title: "Pwned passwords and secrets"
|
||||
description: "More information on detected pwned secrets in Home Assistant."
|
||||
---
|
||||
|
||||
We are using the [Have I Been Pwned (HIBP)](https://haveibeenpwned.com/Passwords) service for detecting leaked or compromised secrets, like passwords.
|
||||
|
||||
If you get a warning about it, it means that you are using secrets in your configuration which have been leaked and are publicly known. It is strongly advised to change these secrets with a more secure alternative as soon as possible.
|
||||
|
||||
Please note; this feature does not send out your secrets to check this. Your secrets and privacy is guaranteed by a [K-Anonymity][k-anonymity]. Your secrets are hashed, the first 5 characters of the hash result are used to query Have I Been Pwned. Have I Been Pwned returns the results of possible password hashes that match, we check the last part of the password hash against this list locally.
|
||||
|
||||
[Read more about K-Anonymity on this CloudFlare blog post][k-anonymity].
|
||||
|
||||
[k-anonymity]: https://blog.cloudflare.com/validating-leaked-passwords-with-k-anonymity/
|
Loading…
x
Reference in New Issue
Block a user