Merge branch 'current' into next

2025-07-23 09:17:06 +00:00 · 2021-01-27 11:57:33 +01:00 · 2021-01-27 11:57:33 +01:00 · 72cb1e2267
commit 72cb1e2267
parent 814253e735 dfdb58a73f
8 changed files with 74 additions and 33 deletions
--- a/2
+++ b/2
@ -15,7 +15,7 @@ group :jekyll_plugins do
  gem 'jekyll-sitemap', '1.4.0'
  gem 'jekyll-time-to-read', '0.1.2'
  gem 'jekyll-commonmark', '1.3.1'
-  gem 'jekyll-toc', '0.16.1'
+  gem 'jekyll-toc', '0.17.0'
 end

 gem 'sinatra', '2.1.0'
--- a/Gemfile.lock
+++ b/Gemfile.lock
@ -56,8 +56,8 @@ GEM
      jekyll (>= 3.7, < 5.0)
    jekyll-time-to-read (0.1.2)
      jekyll
-    jekyll-toc (0.16.1)
-      jekyll (>= 3.8)
+    jekyll-toc (0.17.0)
+      jekyll (>= 3.9)
      nokogiri (~> 1.10)
    jekyll-watch (2.2.1)
      listen (~> 3.0)
@ -129,7 +129,7 @@ DEPENDENCIES
  jekyll-paginate (= 1.1.0)
  jekyll-sitemap (= 1.4.0)
  jekyll-time-to-read (= 0.1.2)
-  jekyll-toc (= 0.16.1)
+  jekyll-toc (= 0.17.0)
  nokogiri (= 1.11.1)
  rake (= 13.0.3)
  sass-globbing (= 1.1.5)
--- a/README.md
+++ b/README.md
@ -13,7 +13,7 @@ Setting up to contribute to documentation and the process for submitting pull re

 ## Site preview

-In order to make the preview available on [http://127.0.0.1:4000](http://127.0.0.1:4000), use the following [bundler](
+In order to make the preview available on `http://127.0.0.1:4000`, use the following [bundler](
 https://bundler.io/
 ) command:

@ -21,6 +21,12 @@ https://bundler.io/
 bundle exec rake preview
 ```

+If the preview is not running on your local machine, pass the IP of the target machine from where it should be served as a parameter, i.e. to access on `http://192.168.0.123:4000`:
+
+```bash
+bundle exec rake preview[192.168.0.123]
+```
+
 ## Speeding up site generation

 Every release we post long changelogs to the website. This slows down generation of the website significantly! We include some tools to temporarily exclude the blog posts that you're not working on out of the way.
--- a/source/_docs/installation/troubleshooting.markdown
+++ b/source/_docs/installation/troubleshooting.markdown
@ -43,3 +43,22 @@ For `iptables` systems (was the default for older distributions):
 iptables -I INPUT -p tcp --dport 8123 -j ACCEPT
 iptables-save > /etc/network/iptables.rules  # your rules may be saved elsewhere
 ```
+
+### System freezes
+
+On small systems (such as a Pi2), not directly sypported by binaries (Python Wheels) you may run out of memory.
+Upon the first run or after an upgrade, Home Assistant uses a lot of resources to (re)compile all the integrations. 
+If you run out of memory and/or swap memory, your system will freeze.
+Increasing swap memory can help:
+
+```bash
+sudo dphys-swapfile swapoff
+sudo nano /etc/dphys-swapfile
+```
+
+Modify the line the sets the swapfile size. Set it equal to your memory or double your current setting: `CONF_SWAPSIZE = 925` then:
+
+```bash
+sudo dphys-swapfile swapon
+sudo systemctl restart dphys-swapfile.service
+```
--- a/source/_docs/z-wave/device-specific.markdown
+++ b/source/_docs/z-wave/device-specific.markdown
@ -67,32 +67,35 @@ Reboot your Pi 4 without the Razberry Z-Wave hat first. Then shutdown, add the h

 #### Raspberry Pi 3 procedure

+Add the following parameters to the bottom of the `/boot/config.txt` file.
+
 ```text
-dtoverlay=pi3-disable-bt
+dtoverlay=disable-bt
 ```

-Then disable the Bluetooth modem service:
+Reboot your Pi 3.
+
+For Home Assistant OS this should be everything you need to do. You should now be able to use Razberry Z-Wave from `/dev/ttyAMA0`.
+
+For other operating systems such as Raspberry Pi OS you will also have to run the following command:

 ```bash
 sudo systemctl disable hciuart
 ```

-Once Bluetooth is off, enable the serial interface via the `raspi-config` tool. After reboot run:
+You should also check the README for details on the overlays. You might find it in `/boot/overlays/README` on your SD-card. If it is not there you can find [the official version here](https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README).

-```bash
-sudo systemctl mask serial-getty@ttyAMA0.service
-```
+<div class='note'>

-so that your serial interface looks like:
+  It is possible to keep a limited Bluetooth functionality while using Razberry Z-Wave. Check `boot/overlays/README` on `miniuart-bt`.

-```text
-crw-rw---- 1 root dialout 204, 64 Sep  2 14:38 /dev/ttyAMA0
-```
-at this point simply add your user (homeassistant) to the dialout group:
+</div>

-```bash
-sudo usermod -a -G dialout homeassistant
-```
+<div class='note'>
+
+  `disable-bt` was previously known as `pi3-disable-bt`. If your OS is old, you might need to use this instead.
+
+</div>

 <div class='note'>

--- a/source/_integrations/home_connect.markdown
+++ b/source/_integrations/home_connect.markdown
@ -33,19 +33,20 @@ Note that it depends on the appliance and on API permissions which of the featur
 ### Installation using a developer account

 1. Visit [https://developer.home-connect.com](https://developer.home-connect.com) and sign up for a developer account.
-2. Under [Applications](https://developer.home-connect.com/applications), register a new App:
+2. Enter the email of your login for the original Home Connect App from Bosch/Siemens under "Default Home Connect User Account for Testing" in the sign up process.
+3. Under [Applications](https://developer.home-connect.com/applications), register a new App:

 - Application ID: Home Assistant (or whatever name makes sense to you)
 - OAuth Flow: Authorization Code Grant Flow
 - Redirect URI: "`<INTERNAL_HOME_ASSISTANT_URL>/auth/external/callback`
  Use your internal Home Assistant URL, if you didn't configure one manually, use your local IP address. Examples: `http://192.168.0.2:8123/auth/external/callback`, `http://homeassistant.local:8123/auth/external/callback`."

-3. Add the client ID and client secret to your `configuration.yaml` (see below).
-4. Once Home Assistant has restarted, go to Configuration > Integrations.
-5. Select the Home Connect integration.
-6. You will be prompted to open a web page and authenticate your app with Home Connect.
-7. Use your Home Connect account details associated with your developer app (this may not be your developer account details you created but will be the account you use to login to the original Home Connect App from Bosch/Siemens).
-8. You will know it works when you are prompted to allow Home Assistant to access your Home Connect data, including the list of devices accessible to the original Home Connect app.
+4. Add the client ID and client secret to your `configuration.yaml` (see below).
+5. Once Home Assistant has restarted, go to Configuration > Integrations.
+6. Select the Home Connect integration.
+7. You will be prompted to open a web page and authenticate your app with Home Connect.
+8. Use your Home Connect account details associated with your developer app. It must be the login for the Home Connect account you entered in Step 2.
+9. You will know it works when you are prompted to allow Home Assistant to access your Home Connect data, including the list of devices accessible to the original Home Connect app.

 ### Configuration

--- a/source/_integrations/input_datetime.markdown
+++ b/source/_integrations/input_datetime.markdown
@ -133,40 +133,47 @@ If you have a `datetime` object you can use its `timestamp` method. Of if you ha
 ```yaml
 # Sets time to 05:30:00
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    time: '05:30:00'
 # Sets time to time from datetime object
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    time: "{{ now().strftime('%H:%M:%S') }}"
 # Sets date to 2020-08-24
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    date: '2020-08-24'
 # Sets date to date from datetime object
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    date: "{{ now().strftime('%Y-%m-%d') }}"
 # Sets date and time to 2020-08-25 05:30:00
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    datetime: '2020-08-25 05:30:00'
 # Sets date and time from datetime object
 - service: input_datetime.set_datetime
-  entity_id: input_datetime.XXX
+  target:
+    entity_id: input_datetime.XXX
  data:
    datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
 # Sets date and/or time from UNIX timestamp
 # This can be used whether the input_datetime has just a date,
 # or just a time, or has both
 - service: input_datetime.set_datetime
-  data:
+  target:
    entity_id: input_datetime.XXX
+  data:
    timestamp: "{{ now().timestamp() }}"
 ```

--- a/source/_integrations/yeelight.markdown
+++ b/source/_integrations/yeelight.markdown
@ -131,6 +131,11 @@ custom_effects:
           required: false
           type: integer
           default: 0
+         action:
+            description: The action to take after the flow stops. Can be 'recover', 'stay', 'off'.
+            required: false
+            type: string
+            default: recover
         transitions:
           description: List of transitions, for that effect, check [example](#custom-effects).
           required: true