mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-16 22:06:50 +00:00
Merge branch 'current' into next
This commit is contained in:
commit
f90b6c7433
@ -116,6 +116,10 @@ script:
|
|||||||
|
|
||||||
In the above example, two codes will be captured for the power command, and will be sent alternately each time the command is called.
|
In the above example, two codes will be captured for the power command, and will be sent alternately each time the command is called.
|
||||||
|
|
||||||
|
#### Learned codes storage location
|
||||||
|
|
||||||
|
The learned commands are stored in folder `\configuration\.storage` in a file called `broadlink_remote_xxxxxxxxxxx_codes.json`. From here, you can copy the codes for use in e.g., a Broadlink switch. Warning: files in the .storage folder should never be edited manually, so just view the file.
|
||||||
|
|
||||||
### Send command
|
### Send command
|
||||||
|
|
||||||
Use the `remote.send_command` service to send commands.
|
Use the `remote.send_command` service to send commands.
|
||||||
|
@ -49,6 +49,11 @@ The following sensors are supported.
|
|||||||
- **Extract temperature:** Air temperature of the air extracted from the house.
|
- **Extract temperature:** Air temperature of the air extracted from the house.
|
||||||
- **Exhaust temperature:** Exhausted air temperature.
|
- **Exhaust temperature:** Exhausted air temperature.
|
||||||
- **Remaining filter lifetime:** Remaining filter lifetime measured in percent.
|
- **Remaining filter lifetime:** Remaining filter lifetime measured in percent.
|
||||||
|
- **Humidity:** Relative humidity in percent.
|
||||||
|
- **Fan step:** Fan step.
|
||||||
|
- **Exhaust fan speed:** Exhausted fan speed.
|
||||||
|
- **Supply fan speed:** Supply fan speed.
|
||||||
|
- **Dial battery:** Dial bettery level in percent.
|
||||||
|
|
||||||
## Switch
|
## Switch
|
||||||
|
|
||||||
|
@ -66,7 +66,7 @@ To get AVM Fritzbox switch and thermostat follow the instructions above.
|
|||||||
|
|
||||||
### Attributes
|
### Attributes
|
||||||
|
|
||||||
The are several attributes that can be useful for automations and templates.
|
There are several attributes that can be useful for automations and templates.
|
||||||
|
|
||||||
| Attribute | Description |
|
| Attribute | Description |
|
||||||
| --------- | ----------- |
|
| --------- | ----------- |
|
||||||
@ -88,7 +88,7 @@ To get AVM Fritzbox temperature sensor (e.g. FRITZ!DECT Repeater 100) follow the
|
|||||||
|
|
||||||
### Attributes
|
### Attributes
|
||||||
|
|
||||||
The are several attributes that can be useful for automations and templates.
|
There are several attributes that can be useful for automations and templates.
|
||||||
|
|
||||||
| Attribute | Description |
|
| Attribute | Description |
|
||||||
| --------- | ----------- |
|
| --------- | ----------- |
|
||||||
|
@ -58,6 +58,7 @@ and has been confirmed to work with the following models:
|
|||||||
- DS-2CD2142FWD-I
|
- DS-2CD2142FWD-I
|
||||||
- DS-2CD2155FWD-IS
|
- DS-2CD2155FWD-IS
|
||||||
- IPC-D140H(-M)
|
- IPC-D140H(-M)
|
||||||
|
- DS-7616NI-K2 (NVR)
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
|
@ -119,34 +119,39 @@ automation:
|
|||||||
To dynamically set the `input_datetime` you can call
|
To dynamically set the `input_datetime` you can call
|
||||||
`input_datetime.set_datetime`. The values for `date` and `time` must be in a certain format for the call to be successful. (See service description above.)
|
`input_datetime.set_datetime`. The values for `date` and `time` must be in a certain format for the call to be successful. (See service description above.)
|
||||||
If you have a `datetime` object you can use its `strftime` method. Of if you have a timestamp you can use the `timestamp_custom` filter.
|
If you have a `datetime` object you can use its `strftime` method. Of if you have a timestamp you can use the `timestamp_custom` filter.
|
||||||
The following example can be used in an automation rule:
|
The following example shows the different methods in an automation rule:
|
||||||
|
|
||||||
{% raw %}
|
{% raw %}
|
||||||
```yaml
|
```yaml
|
||||||
# Example configuration.yaml entry
|
# Example configuration.yaml entry
|
||||||
# Sets input_datetime to '05:30' when an input_boolean is turned on.
|
# Shows different ways to set input_datetime when an input_boolean is turned on
|
||||||
automation:
|
automation:
|
||||||
trigger:
|
trigger:
|
||||||
platform: state
|
platform: state
|
||||||
entity_id: input_boolean.example
|
entity_id: input_boolean.example
|
||||||
to: 'on'
|
to: 'on'
|
||||||
action:
|
action:
|
||||||
|
# Sets time to '05:30:00
|
||||||
- service: input_datetime.set_datetime
|
- service: input_datetime.set_datetime
|
||||||
entity_id: input_datetime.bedroom_alarm_clock_time
|
entity_id: input_datetime.bedroom_alarm_clock_time
|
||||||
data:
|
data:
|
||||||
time: '05:30:00'
|
time: '05:30:00'
|
||||||
|
# Sets time to time from datetime object (current time in this example)
|
||||||
- service: input_datetime.set_datetime
|
- service: input_datetime.set_datetime
|
||||||
entity_id: input_datetime.another_time
|
entity_id: input_datetime.another_time
|
||||||
data_template:
|
data_template:
|
||||||
time: "{{ now().strftime('%H:%M:%S') }}"
|
time: "{{ now().strftime('%H:%M:%S') }}"
|
||||||
|
# Sets date to date from timestamp (current date in this example)
|
||||||
- service: input_datetime.set_datetime
|
- service: input_datetime.set_datetime
|
||||||
entity_id: input_datetime.another_date
|
entity_id: input_datetime.another_date
|
||||||
data_template:
|
data_template:
|
||||||
date: "{{ as_timestamp(now())|timestamp_custom('%Y-%m-%d') }}"
|
date: "{{ as_timestamp(now())|timestamp_custom('%Y-%m-%d') }}"
|
||||||
|
# Sets date and time to date and time from datetime object (current date and time in this example)
|
||||||
- service: input_datetime.set_datetime
|
- service: input_datetime.set_datetime
|
||||||
entity_id: input_datetime.date_and_time
|
entity_id: input_datetime.date_and_time
|
||||||
data_template:
|
data_template:
|
||||||
datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
|
datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
|
||||||
|
# Sets date and time to date and time from timestamp (current date and time in this example)
|
||||||
- service: input_datetime.set_datetime
|
- service: input_datetime.set_datetime
|
||||||
data_template:
|
data_template:
|
||||||
entity_id: input_datetime.date_and_time
|
entity_id: input_datetime.date_and_time
|
||||||
|
@ -95,7 +95,7 @@ And you can set up the device tracker as
|
|||||||
```yaml
|
```yaml
|
||||||
- platform: nmap_tracker
|
- platform: nmap_tracker
|
||||||
hosts: 192.168.1.1-25
|
hosts: 192.168.1.1-25
|
||||||
scan_options: " --privileged -sP "
|
scan_options: " --privileged -sn "
|
||||||
```
|
```
|
||||||
|
|
||||||
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.
|
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.
|
||||||
|
@ -19,7 +19,7 @@ The `tensorflow` image processing platform allows you to detect and recognize ob
|
|||||||
|
|
||||||
## Setup
|
## Setup
|
||||||
|
|
||||||
You need to install the `tensorflow` Python packages with: `$ pip3 install tensorflow==1.13.2`. The wheel is not available for all platforms. See [the official install guide](https://www.tensorflow.org/install/) for other options. Hass.io is not yet supported but an addon is under development.
|
You need to install the `tensorflow` Python packages with: `$ pip3 install tensorflow==1.13.2`. The wheel is not available for all platforms. See [the official install guide](https://www.tensorflow.org/install/) for other options. The required packages are included in Home Assistant Supervised installations but only supported on amd64 architecture.
|
||||||
|
|
||||||
This integration requires files to be downloaded, compiled on your computer, and added to the Home Assistant configuration directory. These steps can be performed using the sample script at [this gist](https://gist.github.com/hunterjm/6f9332f92b60c3d5e448ad936d7353c3). Alternatively, if you wish to perform the process manually, the process is as follows:
|
This integration requires files to be downloaded, compiled on your computer, and added to the Home Assistant configuration directory. These steps can be performed using the sample script at [this gist](https://gist.github.com/hunterjm/6f9332f92b60c3d5e448ad936d7353c3). Alternatively, if you wish to perform the process manually, the process is as follows:
|
||||||
|
|
||||||
|
81
source/_posts/2020-01-31-community-highlights.markdown
Normal file
81
source/_posts/2020-01-31-community-highlights.markdown
Normal file
@ -0,0 +1,81 @@
|
|||||||
|
---
|
||||||
|
title: "Community Highlights, first edition!"
|
||||||
|
description: "A different take on the UI, a smart toilet roll holder and the DIY smart mailbox"
|
||||||
|
date: 2020-01-31 00:00:00
|
||||||
|
date_formatted: "January 31, 2020"
|
||||||
|
author: Franck Nijhof
|
||||||
|
author_twitter: frenck
|
||||||
|
categories: Community
|
||||||
|
og_image: /images/blog/2020-01-31-community-highlights/social.png
|
||||||
|
---
|
||||||
|
|
||||||
|
Back in [2015][community-highlights-2015] and in [2016][community-highlights-2016], we tried starting a series of blog posts called "Community Highlight",
|
||||||
|
a few times, a blog post appeared about the amazingly awesome stuff our community does with Home Assistant.
|
||||||
|
|
||||||
|
Recently, that idea was picked up again by adding an "In Other News" section to the release notes on each Home Assistant release. However, the development pace of Home Assistant is high! As a result, that section is always hidden all the way down somewhere in those release notes. A bit unfortunate, since there is so much cool stuff to be found!
|
||||||
|
|
||||||
|
So, today, we present you: the Community Highlights, the first edition!
|
||||||
|
|
||||||
|
Technically, not the first, but we rebooted this series, right?
|
||||||
|
|
||||||
|
We hope you enjoy this, please let us know in the comments below!
|
||||||
|
Or join us for a little chat in our [#lounge at Discord][chat]
|
||||||
|
|
||||||
|
../Frenck
|
||||||
|
|
||||||
|
## A different take on designing your frontend
|
||||||
|
|
||||||
|
Mattias Persson showed an interesting alternative approach to the design of his Lovelace UI.
|
||||||
|
It looks fabulous; we don't even know where to start explaining, check the video below for an impression:
|
||||||
|
|
||||||
|
<div class='videoWrapper'>
|
||||||
|
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/727tFhqpFAE" frameborder="0" allowfullscreen></iframe>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
Mattias created [a post in the Community Forum][different-take] with all the details, including more screenshots, the things he used and links to his GitHub repository. Everything you'd need if you wanted to replicate this for your own use. Thanks Mattias!
|
||||||
|
|
||||||
|
## Smart toilet roll holder
|
||||||
|
|
||||||
|
Com'on, we all know what it is like to be in the restroom, taking a number two, discovering that you are out of paper.
|
||||||
|
|
||||||
|
For the-berik, on our [subreddit][reddit], it was reason enough to do something about it. He converted his toilet roll holder into a smart version using an ESP8266 chip, a load cell and [ESPHome][esphome], allowing Home Assistant to know how many rolls of toilet paper are left on the holder.
|
||||||
|
|
||||||
|
Click on the video below to see how it works.
|
||||||
|
|
||||||
|
<blockquote class="reddit-card"><a href="https://www.reddit.com/r/homeassistant/comments/elwvro/smart_toiletroll_holder_with_esphome_and/">Smart toiletroll holder with Esphome and Homeassistant</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>
|
||||||
|
|
||||||
|
## Smart mailbox sensor, the easy way
|
||||||
|
|
||||||
|
Another one from our [subreddit][reddit], where choketube shares his pride for the mailbox sensor he created.
|
||||||
|
He placed a Hue motion sensor inside his mailbox that will trigger if it is opened, really smart and simple!
|
||||||
|
|
||||||
|
He demonstrates his mailbox in the video below.
|
||||||
|
|
||||||
|
<blockquote class="reddit-card"><a href="https://www.reddit.com/r/homeassistant/comments/ejgzeb/proud_of_my_new_automation_hue_sensor_in_my/">Proud of my new Automation - Hue Sensor in my Mailbox</a> from <a href="http://www.reddit.com/r/homeassistant">r/homeassistant</a></blockquote>
|
||||||
|
|
||||||
|
## 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
|
||||||
|
[community-highlights-2015]: https://www.home-assistant.io/blog/2015/12/05/community-highlights/
|
||||||
|
[community-highlights-2016]: https://www.home-assistant.io/blog/2016/02/20/community-highlights/
|
||||||
|
[different-take]: https://community.home-assistant.io/t/a-different-take-on-designing-a-lovelace-ui/162594
|
||||||
|
[esphome]: https://www.esphome.io
|
||||||
|
[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
|
@ -1,6 +1,9 @@
|
|||||||
# These redirects are handled by Netlify
|
# These redirects are handled by Netlify
|
||||||
#
|
#
|
||||||
|
|
||||||
|
# General use redirects
|
||||||
|
/suggest-community-highlight https://docs.google.com/forms/d/e/1FAIpQLSd9VWPeVM0xg0swWL6kT3wkQUKt8vWsTL5WtPO95LAy-0cYZw/viewform
|
||||||
|
|
||||||
# Older development pages
|
# Older development pages
|
||||||
/developers https://developers.home-assistant.io
|
/developers https://developers.home-assistant.io
|
||||||
/developers/add_new_platform https://developers.home-assistant.io/docs/en/creating_platform_index.html
|
/developers/add_new_platform https://developers.home-assistant.io/docs/en/creating_platform_index.html
|
||||||
|
@ -44,8 +44,8 @@ Now let's make a change using the configurator: we are going to change the name,
|
|||||||
</div>
|
</div>
|
||||||
|
|
||||||
- Click the save icon in the top right to commit changes.
|
- Click the save icon in the top right to commit changes.
|
||||||
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a config check. Do this by clicking on Configuration in the sidebar, click on "Server Control" and click on the CHECK CONFIG button. When it's valid, it will show the text "Configuration valid!"
|
- Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a config check. Do this by clicking on Configuration in the sidebar, click on "Server Controls" and click on the "CHECK CONFIG" button. When it's valid, it will show the text "Configuration valid!". In order for the "CHECK CONFIG" button to be visible, you must enable "Advanced Mode" on your user profile.
|
||||||
- Now Restart Home Assistant using the RESTART button in the Server management section on the same page. In order for "Check Config" to be visible, you must enable "Advanced Mode" on your user profile.
|
- Now Restart Home Assistant using the "RESTART" button in the Server management section on the same page.
|
||||||
|
|
||||||
<p class='img'>
|
<p class='img'>
|
||||||
<img src='/images/screenshots/configuration-validation.png' />
|
<img src='/images/screenshots/configuration-validation.png' />
|
||||||
|
BIN
source/images/blog/2020-01-31-community-highlights/social.png
Normal file
BIN
source/images/blog/2020-01-31-community-highlights/social.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 304 KiB |
Binary file not shown.
Before Width: | Height: | Size: 1.6 KiB After Width: | Height: | Size: 19 KiB |
@ -1,7 +1,8 @@
|
|||||||
---
|
---
|
||||||
---
|
---
|
||||||
|
|
||||||
{% assign recent_release_post = site.categories['Release-Notes'].first %}
|
{% assign posts = site.categories['Release-Notes'] | where_exp: "post", "post.title contains site.current_minor_version" %}
|
||||||
|
{% assign recent_release_post = posts.first %}
|
||||||
|
|
||||||
<script>
|
<script>
|
||||||
document.location = '{{ recent_release_post.url }}{{ site.patch_version_notes }}';
|
document.location = '{{ recent_release_post.url }}{{ site.patch_version_notes }}';
|
||||||
|
@ -22,7 +22,7 @@ views:
|
|||||||
type: string
|
type: string
|
||||||
badges:
|
badges:
|
||||||
required: false
|
required: false
|
||||||
description: List of entities IDs or `badge` objects to display as badges.
|
description: List of entities IDs or `badge` objects to display as badges. Note that badges do not show when view is in panel mode.
|
||||||
type: list
|
type: list
|
||||||
cards:
|
cards:
|
||||||
required: false
|
required: false
|
||||||
@ -57,17 +57,6 @@ views:
|
|||||||
default: true
|
default: true
|
||||||
{% endconfiguration %}
|
{% endconfiguration %}
|
||||||
|
|
||||||
### Options For Visible
|
|
||||||
|
|
||||||
If you define `visible` as objects instead of a boolean to specify conditions for displaying the view tab:
|
|
||||||
|
|
||||||
{% configuration badges %}
|
|
||||||
user:
|
|
||||||
required: true
|
|
||||||
description: User id that can see the view tab (unique hex value found on the Users configuration page).
|
|
||||||
type: string
|
|
||||||
{% endconfiguration %}
|
|
||||||
|
|
||||||
#### Example
|
#### Example
|
||||||
|
|
||||||
View config:
|
View config:
|
||||||
@ -141,10 +130,20 @@ views:
|
|||||||
cards:
|
cards:
|
||||||
...
|
...
|
||||||
```
|
```
|
||||||
|
### Options For Visible
|
||||||
|
|
||||||
|
If you define `visible` as objects instead of a boolean to specify conditions for displaying the view tab:
|
||||||
|
|
||||||
|
{% configuration badges %}
|
||||||
|
user:
|
||||||
|
required: true
|
||||||
|
description: User id that can see the view tab (unique hex value found on the Users configuration page).
|
||||||
|
type: string
|
||||||
|
{% endconfiguration %}
|
||||||
|
|
||||||
## Panel
|
## Panel
|
||||||
|
|
||||||
Setting panel true sets the view to panel mode. In this mode the first card is rendered full-width, other cards in the view will not be rendered. This mode is good when using cards like `map`, `stack` or `picture-elements`.
|
Setting panel true sets the view to panel mode. In this mode the first card is rendered full-width, other cards in the view will not be rendered. This mode is good when using cards like `map`, `stack` or `picture-elements`. Note that badges will not appear in Panel Mode.
|
||||||
|
|
||||||
#### Example
|
#### Example
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user