From bfa903b5a53d255793f9fb62c358c5b3a65f1e42 Mon Sep 17 00:00:00 2001 From: Paolo <1306977+vernazza@users.noreply.github.com> Date: Tue, 3 Oct 2023 20:45:00 +0200 Subject: [PATCH 1/9] Update reolink.markdown with extra troubleshooting (#29131) Co-authored-by: Franck Nijhof --- source/_integrations/reolink.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown index a02410874a7..c33679a5e90 100644 --- a/source/_integrations/reolink.markdown +++ b/source/_integrations/reolink.markdown @@ -273,6 +273,7 @@ Then power up the camera while pointing it at the QR code. It takes about a minu - Setting a static IP address for Reolink cameras/NVRs in your router is advisable to prevent (temporal) connectivity issues when the IP address changes. - Do not set a static IP in the Reolink device itself, but leave the **Connection Type** on **DHCP** under **Settings** > **Network** > **Network Information** > **Set Up**. If you set it to **static** on the Reolink device itself, this is known to cause incorrect DHCP requests on the network. The incorrect DHCP request causes Home Assistant to use the wrong IP address for the camera, resulting in connection issues. The issue originates from the Reolink firmware, which keeps sending DCHP requests even when you set a static IP address in the Reolink device. - Reolink cameras can support a limited amount of simultaneous connections. Therefore using third-party software like Frigate, Blue Iris, or Scrypted, or using the ONVIF integration at the same time can cause the camera to drop connections. This results in short unavailabilities of the Reolink entities in Home Assistant. Especially when the connections are coming from the same device (IP) where Home Assistant is running, the Reolink cameras can get confused, dropping one connection in favor of the other originating from the same host IP. If you experience disconnections/unavailabilities of the entities, please first temporarily shut down the other connections (like Frigate) to diagnose if that is the problem. If that is indeed the problem, you could try moving the third-party software to a different host (IP address) since that is known to solve the problem most of the time. You could also try switching the protocol to FLV on Home Assistant and/or the third-party software, as that is known to be less resource-intensive on the camera. +- If the integration and the browser can't connect to the camera even after you enable the HTTP/HTTPS ports, try to create a new user on the camera; that fixes the problem in some cases. ### Reducing latency of motion events From e404d1c4e531d6941cea8977914ca052eb38fa45 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 20:46:26 +0200 Subject: [PATCH 2/9] RFLink: remove logo from header (#29102) --- source/_integrations/binary_sensor.rflink.markdown | 1 - source/_integrations/cover.rflink.markdown | 1 - source/_integrations/light.rflink.markdown | 1 - source/_integrations/sensor.rflink.markdown | 1 - source/_integrations/switch.rflink.markdown | 1 - 5 files changed, 5 deletions(-) diff --git a/source/_integrations/binary_sensor.rflink.markdown b/source/_integrations/binary_sensor.rflink.markdown index a8aba0991cc..9861e92944a 100644 --- a/source/_integrations/binary_sensor.rflink.markdown +++ b/source/_integrations/binary_sensor.rflink.markdown @@ -1,7 +1,6 @@ --- title: "RFLink Binary Sensor" description: "Instructions on how to integrate RFLink binary sensors into Home Assistant." -logo: rflink.png ha_category: - Binary Sensor ha_iot_class: Local Push diff --git a/source/_integrations/cover.rflink.markdown b/source/_integrations/cover.rflink.markdown index c4a9e3cac45..0e9fbe14803 100644 --- a/source/_integrations/cover.rflink.markdown +++ b/source/_integrations/cover.rflink.markdown @@ -1,7 +1,6 @@ --- title: "RFLink Cover" description: "Instructions on how to integrate RFLink Somfy RTS and KAKU ASUN-650 covers into Home Assistant." -logo: rflink.png ha_category: - Cover ha_iot_class: Assumed State diff --git a/source/_integrations/light.rflink.markdown b/source/_integrations/light.rflink.markdown index 1e8b5e0e032..f73430a268b 100644 --- a/source/_integrations/light.rflink.markdown +++ b/source/_integrations/light.rflink.markdown @@ -1,7 +1,6 @@ --- title: "RFLink Light" description: "Instructions on how to integrate RFLink lights into Home Assistant." -logo: rflink.png ha_category: - Light ha_iot_class: Assumed State diff --git a/source/_integrations/sensor.rflink.markdown b/source/_integrations/sensor.rflink.markdown index fb4dbc91cfd..f35003e244d 100644 --- a/source/_integrations/sensor.rflink.markdown +++ b/source/_integrations/sensor.rflink.markdown @@ -1,7 +1,6 @@ --- title: "RFLink Sensor" description: "Instructions on how to integrate RFLink sensors into Home Assistant." -logo: rflink.png ha_category: - Sensor ha_iot_class: Local Push diff --git a/source/_integrations/switch.rflink.markdown b/source/_integrations/switch.rflink.markdown index 7316083e596..3494cf7af1c 100644 --- a/source/_integrations/switch.rflink.markdown +++ b/source/_integrations/switch.rflink.markdown @@ -1,7 +1,6 @@ --- title: "RFLink Switch" description: "Instructions on how to integrate RFLink switches into Home Assistant." -logo: rflink.png ha_category: - Switch ha_iot_class: Assumed State From 87c7d61eac2b255f73639123b491157ef9ddce23 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 20:47:37 +0200 Subject: [PATCH 3/9] Integrations pages: remove logo from header (#29103) --- source/_integrations/bsblan.markdown | 1 - source/_integrations/dsmr.markdown | 1 - source/_integrations/enocean.markdown | 1 - source/_integrations/numato.markdown | 1 - source/_integrations/wiffi.markdown | 1 - 5 files changed, 5 deletions(-) diff --git a/source/_integrations/bsblan.markdown b/source/_integrations/bsblan.markdown index 550be726637..aa425834b42 100644 --- a/source/_integrations/bsblan.markdown +++ b/source/_integrations/bsblan.markdown @@ -1,7 +1,6 @@ --- title: BSB-Lan description: Instructions on how to integrate BSBLan device into Home Assistant. -logo: bsblan.png ha_category: - Climate ha_release: '0.110' diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown index 40b97c4c449..fce170641eb 100644 --- a/source/_integrations/dsmr.markdown +++ b/source/_integrations/dsmr.markdown @@ -1,7 +1,6 @@ --- title: DSMR Slimme Meter description: Instructions on how to integrate DSMR Smartmeter within Home Assistant. -logo: netbeheernederland.jpg ha_category: - Energy ha_release: 0.34 diff --git a/source/_integrations/enocean.markdown b/source/_integrations/enocean.markdown index 6e830948eef..ea70d9b8e4d 100644 --- a/source/_integrations/enocean.markdown +++ b/source/_integrations/enocean.markdown @@ -1,7 +1,6 @@ --- title: EnOcean description: Connect EnOcean devices to Home Assistant -logo: enocean.png ha_category: - Binary Sensor - Hub diff --git a/source/_integrations/numato.markdown b/source/_integrations/numato.markdown index 32eabe37682..5613fc79edc 100644 --- a/source/_integrations/numato.markdown +++ b/source/_integrations/numato.markdown @@ -6,7 +6,6 @@ ha_category: - DIY - Sensor - Switch -logo: numato.png ha_release: '0.110' ha_iot_class: Local Push ha_domain: numato diff --git a/source/_integrations/wiffi.markdown b/source/_integrations/wiffi.markdown index 0ae3ac7526a..50f91440b19 100644 --- a/source/_integrations/wiffi.markdown +++ b/source/_integrations/wiffi.markdown @@ -1,6 +1,5 @@ --- title: Wiffi -logo: wiffi.png description: Support for WIFFI devices from stall.biz, e.g., Weatherman, Rainyman, ... ha_category: - DIY From f851b307878fb0bcd0efa68e4180d6b119ff9b4b Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 21:08:22 +0200 Subject: [PATCH 4/9] Building block integration: add text fragment source (#29129) * Building block integration: add text fragment source * Apply suggestions from code review Co-authored-by: Franck Nijhof --------- Co-authored-by: Franck Nijhof --- source/_includes/integrations/building_block_integration.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 source/_includes/integrations/building_block_integration.md diff --git a/source/_includes/integrations/building_block_integration.md b/source/_includes/integrations/building_block_integration.md new file mode 100644 index 00000000000..d4e710f384b --- /dev/null +++ b/source/_includes/integrations/building_block_integration.md @@ -0,0 +1,4 @@ +{% capture name %}{{ include.name | default: page.title }}{% endcapture %} +{% capture domain %}{{ include.domain | default: page.ha_domain }}{% endcapture %} + +**Building block integration**: The {{ name | downcase }} integration cannot be directly used. You cannot create your own {{ domain }} entities using this integration. This integration is a building block for other integrations to use, enabling them to create {{ domain }} entities for you. From c1baa34398dcff8da951a0e57bbb2d8dd474e2c2 Mon Sep 17 00:00:00 2001 From: b-uwe <61052367+b-uwe@users.noreply.github.com> Date: Tue, 3 Oct 2023 22:06:17 +0200 Subject: [PATCH 5/9] Fix wrong URL (#29136) --- source/green/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/green/index.html b/source/green/index.html index 79710d777dd..ab7fb69fc42 100644 --- a/source/green/index.html +++ b/source/green/index.html @@ -2325,7 +2325,7 @@ frontpage_image: /images/frontpage/green-frontpage.png
From 780e40e7141a82927ea20c3de37763c2acc28539 Mon Sep 17 00:00:00 2001 From: OzGav Date: Wed, 4 Oct 2023 16:45:03 +1000 Subject: [PATCH 6/9] Update sidebar.markdown (#29140) --- source/_dashboards/sidebar.markdown | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/source/_dashboards/sidebar.markdown b/source/_dashboards/sidebar.markdown index d5774b5cd4b..14ff2ab1205 100644 --- a/source/_dashboards/sidebar.markdown +++ b/source/_dashboards/sidebar.markdown @@ -25,18 +25,6 @@ type: type: string {% endconfiguration %} -### Example - -Alternatively, the position of the card can be configured using YAML with the `view_layout` option: - -```yaml -type: entities -entities: - - media_player.lounge_room -view_layout: - position: sidebar -``` - ## Cards config: {% configuration %} @@ -45,3 +33,17 @@ view_layout.position: description: "The position of the card, `main` or `sidebar`" type: string {% endconfiguration %} + +### Example + +The position of the card is configured using YAML with the `view_layout` option: + +```yaml +type: sidebar +cards: + - type: entities + entities: + - media_player.lounge_room + view_layout: + position: sidebar +``` From 9b14f28600a0d24b106d4592a0ffd45a74a97eff Mon Sep 17 00:00:00 2001 From: Jan Bouwhuis Date: Wed, 4 Oct 2023 09:28:16 +0200 Subject: [PATCH 7/9] Remove custom port limit for alexa account linking (#29137) * Remove custom port limit for alexa account linking * tiny tweaks --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/alexa.smart_home.markdown | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown index 15203bb7e24..28ec8bb685b 100644 --- a/source/_integrations/alexa.smart_home.markdown +++ b/source/_integrations/alexa.smart_home.markdown @@ -229,10 +229,18 @@ Alexa needs to link your Amazon account to your Home Assistant account. Therefor - Find the skill you just created, click `Edit` link in the `Actions` column. - Click `ACCOUNT LINKING` in the left navigation bar of build page - Do not turn on the "Allow users to link their account to your skill from within your application or website" switch. This will require a Redirect URI, which won't work. -- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`. Alexa account linking does not work with a non-standard port. You must use port 443. Use your firewall to forward, if needed. Using a `:1234` or a similar port number will not work. +- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`. For Alexa account linking, by default, the standard port 443 is used. Use your firewall to forward this, if needed: - `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]/auth/authorize` - `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]/auth/token` - - Note: you must use a valid/trusted SSL Certificate for account linking to work + + It is also possible to use a different port by appending `:1443` or a similar port number, make sure your firewall is forwarding the correct port: + - `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]:1443/auth/authorize` + - `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]:1433/auth/token` + +
+ Note: you must use a valid/trusted SSL certificate for account linking to work. Self signed certificates will not work, but you can use a free Let's Encrypt certificate. +
+ - `Client ID`: - `https://pitangui.amazon.com/` if you are in US - `https://layla.amazon.com/` if you are in EU From 27191fcdbbf7951b223e4aef6c3a2903c524d433 Mon Sep 17 00:00:00 2001 From: erlendmoland <56839803+erlendmoland@users.noreply.github.com> Date: Wed, 4 Oct 2023 09:33:33 +0200 Subject: [PATCH 8/9] Updated broken product links on Eufy page (#29138) All the links to the various Eufy smart scale models were outdated and did not resolve. I have found the correct products on Eufy's updated website and have updated the links accordingly. --- source/_integrations/eufylife_ble.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_integrations/eufylife_ble.markdown b/source/_integrations/eufylife_ble.markdown index 42304630353..39a99de70ee 100644 --- a/source/_integrations/eufylife_ble.markdown +++ b/source/_integrations/eufylife_ble.markdown @@ -18,11 +18,11 @@ The EufyLife integration allows you to integrate Eufy smart scales with Home Ass ## Supported devices -- [Smart Scale (T9140)](https://www.eufy.com/products/t9140) -- [Smart Scale C1 (T9146)](https://www.eufy.com/products/t9146) -- [Smart Scale P1 (T9147)](https://www.eufy.com/products/t9147) -- [Smart Scale P2 (T9148)](https://www.eufy.com/products/t9148) -- [Smart Scale P2 Pro (T9149)](https://www.eufy.com/products/t9149111) +- [Smart Scale (T9140)](https://support.eufy.com/s/product/a085g000000Nm5FAAS/smart-scale(t9140)) +- [Smart Scale C1 (T9146)](https://us.eufy.com/products/t9146) +- [Smart Scale P1 (T9147)](https://us.eufy.com/products/t9147) +- [Smart Scale P2 (T9148)](https://us.eufy.com/products/t9148) +- [Smart Scale P2 Pro (T9149)](https://us.eufy.com/products/t9149111)
From 06a91a5e1384414c98443476b7ed927b18f99b13 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 4 Oct 2023 10:07:22 +0200 Subject: [PATCH 9/9] Bump google-protobuf from 3.24.3 to 3.24.4 (#29142) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile.lock b/Gemfile.lock index edc7bc78e53..add00f36439 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -26,7 +26,7 @@ GEM eventmachine (1.2.7-x64-mingw32) ffi (1.16.2) forwardable-extended (2.6.0) - google-protobuf (3.24.3) + google-protobuf (3.24.4) http_parser.rb (0.8.0) i18n (1.14.1) concurrent-ruby (~> 1.0)