From 2c2343bb3edfd7c64fb9842f7bf1164204f74365 Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Fri, 25 Nov 2022 13:40:21 +0100 Subject: [PATCH 1/8] Add Motion Blinds troubleshooting for range (#25046) Co-authored-by: Franck Nijhof --- source/_integrations/motion_blinds.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_integrations/motion_blinds.markdown b/source/_integrations/motion_blinds.markdown index 9e3538489c0..f89c78d77c6 100644 --- a/source/_integrations/motion_blinds.markdown +++ b/source/_integrations/motion_blinds.markdown @@ -142,6 +142,14 @@ For tilt capable blinds a new position and tilt can be specified and the blind w ## Troubleshooting +### Range of the gateway + +When the gateway is placed too far from the blinds, sometimes the blinds do react to commands from the gateway, but the gateway is not able to receive messages from the blinds. In those cases, the position of the blinds will not be reported correctly (both in Home Assistant and in the mobile app of the blinds). This can cause problems with specifically Top Down Bottom Up (TDBU) blinds since, for TDBUs, the requested position is checked to guard for collisions between the top and bottom motor; therefore, not all positions are allowed based on the current position of both motors. If the gateway does not receive the current position correctly, some commands may be wrongfully rejected to prevent collisions. + +Please try placing the gateway closer to the blinds if you experience issues. + +### Allowing UDP multicast communication + Home Assistant uses the following UDP multicast addresses/ports for communication with the gateway: - Motion hub receive UDP multicast `238.0.0.18:32100` From 003b42cece8d646775c82094ef511eec07d51dba Mon Sep 17 00:00:00 2001 From: starkillerOG Date: Fri, 25 Nov 2022 13:46:08 +0100 Subject: [PATCH 2/8] Add xiaomi miio troubleshooting (#24802) Co-authored-by: Franck Nijhof --- source/_integrations/xiaomi_miio.markdown | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown index eb097afbfe6..8be081b4ede 100644 --- a/source/_integrations/xiaomi_miio.markdown +++ b/source/_integrations/xiaomi_miio.markdown @@ -72,6 +72,13 @@ you used in the Xiaomi Home App (where you initially setup the device). There ar [this page](https://www.openhab.org/addons/bindings/miio/#country-servers) for the server to use for each country. +## Troubleshooting + +The most common problems are: +- Xiaomi Miio devices do not communicate across subnets/VLANs due to the source address of the UDP packet not belonging to the subnet of the device itself, [more information and solutions](https://python-miio.readthedocs.io/en/latest/troubleshooting.html#discover-devices-across-subnets). +- Roborock vacuums need to be connected to the Xiaomi Home app, not the Roborock app, [more information](https://python-miio.readthedocs.io/en/latest/troubleshooting.html#roborock-vacuum-not-detected). +- Blocking the network access to the device is known to cause intermittent connection issues due to the device's internal software hanging and a watchdog restarting the internal software, [more information](https://python-miio.readthedocs.io/en/latest/troubleshooting.html#intermittent-connection-issues-timeouts-xiaomi-vacuum). + ## Xiaomi Gateway The `xiaomi_miio` gateway integration allows you to control the gateway and its connected subdevices. @@ -1125,12 +1132,6 @@ Set the extra features. | `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. | | `features` | no | Integer, known values are 0 and 1. | -### Troubleshooting `Unable to find device` error messages - -Check if the device is in the same subnet as the Home Assistant instance. Otherwise, you should configure your router/firewall to put this device in the same VLAN as the Home Assistant instance. - -If it's not possible to use VLANs for some reason, your last resort may be using NAT translation, between the IPs. - ## Xiaomi Air Quality Monitor The `xiaomi_miio` Air Quality Monitor is observing your Xiaomi Mi Air Quality Monitor (PM2.5) and reporting the air quality index and other values. From cbf3658a31e8bec55ffd901c0f8bcb5d399f52b0 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 28 Nov 2022 08:28:17 +0100 Subject: [PATCH 3/8] Bump sinatra from 3.0.3 to 3.0.4 (#25070) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile | 2 +- Gemfile.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Gemfile b/Gemfile index d2c0e995271..78f8f915f05 100644 --- a/Gemfile +++ b/Gemfile @@ -19,7 +19,7 @@ group :jekyll_plugins do gem 'jekyll-toc', '0.17.1' end -gem 'sinatra', '3.0.3' +gem 'sinatra', '3.0.4' gem 'nokogiri', '1.13.9' # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem diff --git a/Gemfile.lock b/Gemfile.lock index 6e5ef91124a..3400e1f00ae 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -81,7 +81,7 @@ GEM public_suffix (5.0.0) racc (1.6.0) rack (2.2.4) - rack-protection (3.0.3) + rack-protection (3.0.4) rack rake (13.0.6) rb-fsevent (0.11.2) @@ -98,10 +98,10 @@ GEM ffi (~> 1.9) sassc (2.1.0-x64-mingw32) ffi (~> 1.9) - sinatra (3.0.3) + sinatra (3.0.4) mustermann (~> 3.0) rack (~> 2.2, >= 2.2.4) - rack-protection (= 3.0.3) + rack-protection (= 3.0.4) tilt (~> 2.0) stringex (2.8.5) terminal-table (3.0.2) @@ -129,7 +129,7 @@ DEPENDENCIES rake (= 13.0.6) sass-globbing (= 1.1.5) sassc (= 2.1.0) - sinatra (= 3.0.3) + sinatra (= 3.0.4) stringex (= 2.8.5) tzinfo (~> 2.0) tzinfo-data From 648a083ace4a646a663a8b420e55f1f1e61d4fa9 Mon Sep 17 00:00:00 2001 From: jiriappl Date: Sun, 27 Nov 2022 23:58:51 -0800 Subject: [PATCH 4/8] Add template for the still image URL for Blue Iris (#25068) --- source/_integrations/mjpeg.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/mjpeg.markdown b/source/_integrations/mjpeg.markdown index db117a61646..72f4ec5447b 100644 --- a/source/_integrations/mjpeg.markdown +++ b/source/_integrations/mjpeg.markdown @@ -43,7 +43,7 @@ use is automatically detected when using a username and password. - Blue Iris Cameras / Blue Iris Server: - MJPEG URL: `http://IP:PORT/mjpg/CAMERASHORTNAME/video.mjpeg` - - Still Image URL: n/a + - Still Image URL: `http://IP:PORT/image/CAMERASHORTNAME` - DCS-930L Wireless N Network Camera from D-Link: - MJPEG URL: `http://IP/video/mjpg.cgi` From 3be41149d89a9b1e9c6d5fc26cd5cfe97b2ab97a Mon Sep 17 00:00:00 2001 From: Hmmbob <33529490+hmmbob@users.noreply.github.com> Date: Mon, 28 Nov 2022 09:03:00 +0100 Subject: [PATCH 5/8] Darksky extended API access until 31 Mar 2023 (#25066) --- source/_integrations/darksky.markdown | 2 +- source/_integrations/weather.darksky.markdown | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/darksky.markdown b/source/_integrations/darksky.markdown index b26b889cb7d..563129422c6 100644 --- a/source/_integrations/darksky.markdown +++ b/source/_integrations/darksky.markdown @@ -20,7 +20,7 @@ The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as
-On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users through the [end of 2022](https://blog.darksky.net/), but it is no longer possible to obtain an API key for new users. Home Assistant supports many alternative [weather integrations](/integrations/#weather). +On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users [until March 31st, 2023](https://blog.darksky.net/), but it is no longer possible to obtain an API key for new users. Home Assistant supports many alternative [weather integrations](/integrations/#weather).
diff --git a/source/_integrations/weather.darksky.markdown b/source/_integrations/weather.darksky.markdown index 731484e6cb1..9fe40c223ec 100644 --- a/source/_integrations/weather.darksky.markdown +++ b/source/_integrations/weather.darksky.markdown @@ -16,7 +16,7 @@ The `darksky` platform uses the [Dark Sky](https://darksky.net/) web service as
-On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users through the [end of 2022](https://blog.darksky.net/), but it is no longer possible to obtain an API key for new users. Home Assistant supports many alternative [weather integrations](/integrations/#weather). +On March 31, 2020 Dark Sky was [acquired by Apple](https://blog.darksky.net/dark-sky-has-a-new-home/) and is no longer allowing new API registrations. The Dark Sky API will continue to function for existing users [until March 31st, 2023](https://blog.darksky.net/), but it is no longer possible to obtain an API key for new users. Home Assistant supports many alternative [weather integrations](/integrations/#weather).
From 4d460d9e5e810a1824ae5b1ab355914d8181d453 Mon Sep 17 00:00:00 2001 From: Jefe2 <47016097+Jefe2@users.noreply.github.com> Date: Mon, 28 Nov 2022 07:51:38 -0500 Subject: [PATCH 6/8] Update tile.markdown (#25074) --- source/_dashboards/tile.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_dashboards/tile.markdown b/source/_dashboards/tile.markdown index b9ca80a6afb..16aa7a632b9 100644 --- a/source/_dashboards/tile.markdown +++ b/source/_dashboards/tile.markdown @@ -2,7 +2,7 @@ type: card title: "Tile Card" sidebar_label: Tile -description: "The tile card gives you a quick overview of your entity. The card allows you to toggle the entity, show the more info dialog, or custom actions." +description: "The tile card gives you a quick overview of your entity. The card allows you to toggle the entity, show the more-info dialog, or custom actions." --- The tile card gives you a quick overview of your entity. The card allows you to toggle the entity and show the more info dialog. A badge is shown for some entities like the [climate](/integrations/climate) or [person](/integrations/person) entities. @@ -33,7 +33,7 @@ icon: type: string color: required: false - description: Set the color when the entity is active. By default, the color is based on `state`, `domain`, and `device_class` of your entity. It accept [color token](/dashboards/tile/#available-color-tokens) or hex color code. + description: Set the color when the entity is active. By default, the color is based on `state`, `domain`, and `device_class` of your entity. It accepts [color token](/dashboards/tile/#available-color-tokens) or hex color code. type: string default: state show_entity_picture: @@ -47,7 +47,7 @@ tap_action: type: map icon_tap_action: required: false - description: Action taken on icon card tap. See [action documentation](/dashboards/actions/#tap-action). By default, it will `toggle` the entity (if possible), otherwise, show the more-info" dialog. + description: Action taken on icon card tap. See [action documentation](/dashboards/actions/#tap-action). By default, it will `toggle` the entity (if possible), otherwise, show the "more-info" dialog. type: map {% endconfiguration %} From a925b912b136fcd53806e706454d4700d6cac8e5 Mon Sep 17 00:00:00 2001 From: RonnyAL Date: Mon, 28 Nov 2022 14:28:34 +0100 Subject: [PATCH 7/8] Fixed typo in docs (#25076) --- source/_integrations/yamaha_musiccast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown index 6ab154fc491..ef5c542ace0 100644 --- a/source/_integrations/yamaha_musiccast.markdown +++ b/source/_integrations/yamaha_musiccast.markdown @@ -34,7 +34,7 @@ The Yamaha MusicCast integration implements the grouping services. There are som ## Play Media functionality -The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text to text services. +The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text to speech services. It is also possible to recall NetUSB presets using the play media service. To do so "presets:" has to be used as `media_content_id` in the service call. From a2c37441c6c9c08d165920c640d3ae1b2e3c2e64 Mon Sep 17 00:00:00 2001 From: Adrian Walker Date: Mon, 28 Nov 2022 13:29:16 +0000 Subject: [PATCH 8/8] Clarity over supported devices (#25073) Co-authored-by: Franck Nijhof --- source/_integrations/nest.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index b329958513f..d5655509e6e 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -35,7 +35,7 @@ ha_integration_type: integration -The `nest` integration allows you to integrate your [Google Nest](https://store.google.com/us/category/connected_home?) devices in Home Assistant. This integration uses the [Smart Device Management](https://developers.google.com/nest/device-access/api) API and Google's Cloud Pubsub to efficiently listen for changes in device state or other events. See [Supported Devices](https://developers.google.com/nest/device-access/supported-devices) for all devices supported by the SDM API. +The `nest` integration allows you to integrate a few [supported](https://developers.google.com/nest/device-access/supported-devices) Google [Nest](https://store.google.com/us/category/connected_home?) devices in Home Assistant. This integration uses the [Smart Device Management](https://developers.google.com/nest/device-access/api) API and Google's Cloud Pubsub to efficiently listen for changes in device state or other events. See [Supported Devices](https://developers.google.com/nest/device-access/supported-devices) for all devices supported by the SDM API. There is currently support for the following device types within Home Assistant: @@ -49,7 +49,7 @@ You are in control of the information and capabilities exposed to Home Assistant
-The Nest Smart Device Management (SDM) API **requires a US$5 fee**. +The Nest Smart Device Management (SDM) API **requires a US$5 fee**. Before buying, make sure your device is [supported](https://developers.google.com/nest/device-access/supported-devices).