diff --git a/source/_integrations/broadlink.markdown b/source/_integrations/broadlink.markdown index 541dcf93595..0ec2d74fc39 100644 --- a/source/_integrations/broadlink.markdown +++ b/source/_integrations/broadlink.markdown @@ -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. +#### 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 Use the `remote.send_command` service to send commands. diff --git a/source/_integrations/danfoss_air.markdown b/source/_integrations/danfoss_air.markdown index cfb49385e27..e7be8bfe54a 100644 --- a/source/_integrations/danfoss_air.markdown +++ b/source/_integrations/danfoss_air.markdown @@ -49,6 +49,11 @@ The following sensors are supported. - **Extract temperature:** Air temperature of the air extracted from the house. - **Exhaust temperature:** Exhausted air temperature. - **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 diff --git a/source/_integrations/fritzbox.markdown b/source/_integrations/fritzbox.markdown index b0a8578f463..7a1044a6523 100644 --- a/source/_integrations/fritzbox.markdown +++ b/source/_integrations/fritzbox.markdown @@ -66,7 +66,7 @@ To get AVM Fritzbox switch and thermostat follow the instructions above. ### 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 | | --------- | ----------- | @@ -88,7 +88,7 @@ To get AVM Fritzbox temperature sensor (e.g. FRITZ!DECT Repeater 100) follow the ### 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 | | --------- | ----------- | diff --git a/source/_integrations/hikvision.markdown b/source/_integrations/hikvision.markdown index 5fa2002b247..64bdc61950d 100644 --- a/source/_integrations/hikvision.markdown +++ b/source/_integrations/hikvision.markdown @@ -58,6 +58,7 @@ and has been confirmed to work with the following models: - DS-2CD2142FWD-I - DS-2CD2155FWD-IS - IPC-D140H(-M) +- DS-7616NI-K2 (NVR) ## Configuration diff --git a/source/_integrations/input_datetime.markdown b/source/_integrations/input_datetime.markdown index b3f663d7cf9..daa33d3108b 100644 --- a/source/_integrations/input_datetime.markdown +++ b/source/_integrations/input_datetime.markdown @@ -119,34 +119,39 @@ automation: 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.) 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 %} ```yaml # 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: trigger: platform: state entity_id: input_boolean.example to: 'on' action: + # Sets time to '05:30:00 - service: input_datetime.set_datetime entity_id: input_datetime.bedroom_alarm_clock_time data: time: '05:30:00' + # Sets time to time from datetime object (current time in this example) - service: input_datetime.set_datetime entity_id: input_datetime.another_time data_template: time: "{{ now().strftime('%H:%M:%S') }}" + # Sets date to date from timestamp (current date in this example) - service: input_datetime.set_datetime entity_id: input_datetime.another_date data_template: 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 entity_id: input_datetime.date_and_time data_template: 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 data_template: entity_id: input_datetime.date_and_time diff --git a/source/_integrations/nmap_tracker.markdown b/source/_integrations/nmap_tracker.markdown index eebd1789949..1eddbb7cacc 100644 --- a/source/_integrations/nmap_tracker.markdown +++ b/source/_integrations/nmap_tracker.markdown @@ -95,7 +95,7 @@ And you can set up the device tracker as ```yaml - platform: nmap_tracker 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. diff --git a/source/_integrations/tensorflow.markdown b/source/_integrations/tensorflow.markdown index 98aaa606a24..9c3db171f6c 100644 --- a/source/_integrations/tensorflow.markdown +++ b/source/_integrations/tensorflow.markdown @@ -19,7 +19,7 @@ The `tensorflow` image processing platform allows you to detect and recognize ob ## 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: diff --git a/source/_posts/2020-01-31-community-highlights.markdown b/source/_posts/2020-01-31-community-highlights.markdown new file mode 100644 index 00000000000..2c30d1f98d2 --- /dev/null +++ b/source/_posts/2020-01-31-community-highlights.markdown @@ -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: + +
+ +
+ +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. + +
Smart toiletroll holder with Esphome and Homeassistant from r/homeassistant
+ + +## 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. + +
Proud of my new Automation - Hue Sensor in my Mailbox from r/homeassistant
+ +## 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 diff --git a/source/_redirects b/source/_redirects index 5ce353649b3..f75f112d4d2 100644 --- a/source/_redirects +++ b/source/_redirects @@ -1,6 +1,9 @@ # 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 /developers https://developers.home-assistant.io /developers/add_new_platform https://developers.home-assistant.io/docs/en/creating_platform_index.html diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index a8133667aac..13c2a7f6cf7 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -44,8 +44,8 @@ Now let's make a change using the configurator: we are going to change the name, - 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!" - - 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. + - 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.

diff --git a/source/images/blog/2020-01-31-community-highlights/social.png b/source/images/blog/2020-01-31-community-highlights/social.png new file mode 100644 index 00000000000..475c3c083d1 Binary files /dev/null and b/source/images/blog/2020-01-31-community-highlights/social.png differ diff --git a/source/images/supported_brands/ecobee.png b/source/images/supported_brands/ecobee.png index f9621daaf68..64564fe04c0 100644 Binary files a/source/images/supported_brands/ecobee.png and b/source/images/supported_brands/ecobee.png differ diff --git a/source/latest-release-notes/index.html b/source/latest-release-notes/index.html index 743b5160158..ce27c6f0841 100644 --- a/source/latest-release-notes/index.html +++ b/source/latest-release-notes/index.html @@ -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 %}