From 85185aec4cdef75e2dc206d494fd20e7ed71a8ba Mon Sep 17 00:00:00 2001 From: Smart Home Junkie <67226335+smarthomejunkie@users.noreply.github.com> Date: Thu, 28 Sep 2023 08:30:33 +0200 Subject: [PATCH 01/34] Added a video tutorial (#29052) * Added a video tutorial * Tiny tweak --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/google_mail.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/_integrations/google_mail.markdown b/source/_integrations/google_mail.markdown index 54bfa9b7ac0..68c47c637ad 100644 --- a/source/_integrations/google_mail.markdown +++ b/source/_integrations/google_mail.markdown @@ -122,3 +122,8 @@ data: - "example4@gmail.com" from: "example@gmail.com" ``` + +### Video Tutorial +This video tutorial explains how to set up Gmail in Home Assistant and how you can create a dashboard and automations to send e-mail and toggle your out-of-office notice. + + From 8d41522ae9048186c1c916b574cec601e9adc973 Mon Sep 17 00:00:00 2001 From: Jan Bouwhuis Date: Thu, 28 Sep 2023 08:31:50 +0200 Subject: [PATCH 02/34] Correct descriptions mqtt patload_reset options (#29045) --- source/_integrations/fan.mqtt.markdown | 4 ++-- source/_integrations/humidifier.mqtt.markdown | 4 ++-- source/_integrations/number.mqtt.markdown | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_integrations/fan.mqtt.markdown b/source/_integrations/fan.mqtt.markdown index 06e1fe14e61..9cc7d7a23cb 100644 --- a/source/_integrations/fan.mqtt.markdown +++ b/source/_integrations/fan.mqtt.markdown @@ -223,12 +223,12 @@ payload_oscillation_on: type: string default: oscillate_on payload_reset_percentage: - description: A special payload that resets the `percentage` state attribute to `None` when received at the `percentage_state_topic`. + description: A special payload that resets the `percentage` state attribute to `unknown` when received at the `percentage_state_topic`. required: false type: string default: 'None' payload_reset_preset_mode: - description: A special payload that resets the `preset_mode` state attribute to `None` when received at the `preset_mode_state_topic`. + description: A special payload that resets the `preset_mode` state attribute to `unknown` when received at the `preset_mode_state_topic`. required: false type: string default: 'None' diff --git a/source/_integrations/humidifier.mqtt.markdown b/source/_integrations/humidifier.mqtt.markdown index 835dfabf64c..77ceb813694 100644 --- a/source/_integrations/humidifier.mqtt.markdown +++ b/source/_integrations/humidifier.mqtt.markdown @@ -215,12 +215,12 @@ payload_on: type: string default: "ON" payload_reset_humidity: - description: A special payload that resets the `target_humidity` state attribute to `None` when received at the `target_humidity_state_topic`. + description: A special payload that resets the `target_humidity` state attribute to an `unknown` state when received at the `target_humidity_state_topic`. When received at `current_humidity_topic` it will reset the current humidity state. required: false type: string default: 'None' payload_reset_mode: - description: A special payload that resets the `mode` state attribute to `None` when received at the `mode_state_topic`. When received at `current_humidity_topic` it will reset the current humidity state. + description: A special payload that resets the `mode` state attribute to an `unknown` state when received at the `mode_state_topic`. required: false type: string default: 'None' diff --git a/source/_integrations/number.mqtt.markdown b/source/_integrations/number.mqtt.markdown index 65329a9337e..46ee2aed08b 100644 --- a/source/_integrations/number.mqtt.markdown +++ b/source/_integrations/number.mqtt.markdown @@ -167,7 +167,7 @@ optimistic: type: boolean default: "`true` if no `state_topic` defined, else `false`." payload_reset: - description: A special payload that resets the state to `None` when received on the `state_topic`. + description: A special payload that resets the state to `unknown` when received on the `state_topic`. required: false type: string default: '"None"' From ee965c1043b90b501a672819443a04291f9da225 Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Thu, 28 Sep 2023 17:32:58 +0200 Subject: [PATCH 03/34] Update green blogpost (#29060) --- ...me-assistant-green-your-entry-to-home-assistant.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown b/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown index dcfb7bf05d3..3e600692e68 100644 --- a/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown +++ b/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown @@ -43,11 +43,9 @@ For more information about Home Assistant Green, [visit our product page](/green
-To celebrate [the 10th anniversary of Home Assistant][10ha-blog], we are making an anniversary batch of 1000 Home Assistant Green hubs available for sale via our partner Seeed Studio. You can order your Home Assistant Green right now: +To celebrate [the 10th anniversary of Home Assistant][10ha-blog], we made an anniversary batch of 1000 Home Assistant Green hubs available. This batch has sold out, but Home Assistant Green will become widely available through our existing distributor network starting in November. You can pre-order your Home Assistant Green at our product page: -Order at Seeed Studio - -If this anniversary batch sells out before you can get one, don't worry! At the end of October, the Home Assistant Green will become widely available through our existing distributor network. Keep an eye on the Home Assistant Green website for availability! +Home Assistant Green [logo-blog]: /blog/2023/09/17/a-refreshed-logo-for-home-assistant/ [10ha-blog]: /blog/2023/09/17/10-years-home-assistant/ From 376f548c5fbb8b7212f04b94e3a7bdd1c0fb5bdd Mon Sep 17 00:00:00 2001 From: Sam Reed Date: Fri, 29 Sep 2023 19:15:19 +0100 Subject: [PATCH 04/34] flume.markdown: Improve leading link to flume website (#29070) Co-authored-by: Franck Nijhof --- source/_integrations/flume.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/flume.markdown b/source/_integrations/flume.markdown index a06342267d2..fc35df4ba57 100644 --- a/source/_integrations/flume.markdown +++ b/source/_integrations/flume.markdown @@ -19,7 +19,7 @@ ha_platforms: ha_integration_type: integration --- -The `flume` sensor will show you the current [flume](https://portal.flumewater.com) status for the given Device ID. +The Flume integration will show you the current [Flume](https://flumewater.com/) status for the given Device ID. Flume monitors the real-time status of your home water meter. Allowing the end-user to detect small leaks, gain real-time information on household water consumption, set water goals and budgets, and receive push notifications when suspicious water activities occur. From 80833aae0296a49b6f21e48f2bdf401eed6f1478 Mon Sep 17 00:00:00 2001 From: Jon Griffith <32052562+arretx@users.noreply.github.com> Date: Sat, 30 Sep 2023 22:45:30 -0700 Subject: [PATCH 05/34] Update imap.markdown (#29079) The steps were a bit out of date. I ran through this process and found some holes in the actual steps. Changes are reflected in my edit. --- source/_integrations/imap.markdown | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/source/_integrations/imap.markdown b/source/_integrations/imap.markdown index 6471c32ccec..2967737548d 100644 --- a/source/_integrations/imap.markdown +++ b/source/_integrations/imap.markdown @@ -20,17 +20,27 @@ The IMAP integration is observing your [IMAP server](https://en.wikipedia.org/wi ### Gmail with App Password -If you’re going to use Gmail, you need to create an [App Password](https://support.google.com/mail/answer/185833). +If you’re going to use Gmail, 2-step verification must be enabled on your Gmail account. Once it is enabled, you need to create an [App Password](https://support.google.com/mail/answer/185833). 1. Go to your [Google Account](https://myaccount.google.com/) 2. Select **Security** -3. Under “Signing in to Google” select **App Passwords** -4. Sign in to your Account, and create a new App Password for Gmail. -5. Then you can setup the intergation as below: +3. Under “How you sign into Google” select **2-Step Verification**. +4. Sign in to your Account. +5. At the bottom of the 2-Step Verification page, click **App Passwords**. +6. Give your app a name that makes sense to you (Home Assistant IMAP, for example). +7. Click **Create**, then make a note of your 16-character app password for safekeeping (remove the spaces when you save it). +8. Click **Done**. +9. Add the IMAP Integration to your Home Assistant instance using the My button above. Enter the following information as needed: + + - Username: Your Gmail email login + - Password: your 16-character app password (without the spaces) - Server: `imap.gmail.com` - Port: `993` - - Username: Your full email address - - Password: The new app password + +10. Click **Submit**. +11. Assign your integration to an "Area" if desired, then click **Finish**. + +Congratulations, you now how a sensor that counts the number of unread e-mails in your Gmail account. From here you can create additional sensors based upon the data that comes through the event bus when there's a new message detected. ### Configuring IMAP Searches From 013ddd5950c534c94407cc7d790dd760cd276aa5 Mon Sep 17 00:00:00 2001 From: R Huish <5207490+genestealer@users.noreply.github.com> Date: Sun, 1 Oct 2023 16:58:07 +0100 Subject: [PATCH 06/34] Nest Troubleshooting info for "No Access to Partner Information" Error Update nest.markdown (#29085) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Added requirement to migrate next account to google account "No Access To Partner” error - Update nest.markdown Added requirement to migrate next account to google account "No Access To Partner” error - Update nest.markdown * Update nest.markdown * Typo Information fixed * Added edit as per feedback As per https://github.com/home-assistant/home-assistant.io/pull/29085#discussion_r1342151285 * Update source/_integrations/nest.markdown --------- Co-authored-by: Allen Porter --- source/_integrations/nest.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index 1d43c7b5323..9bf568cb51c 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -466,6 +466,8 @@ Once you have completed the above steps, you can continue through the flow to re ## Troubleshooting +- *No access to partner information* "Information could not be retrieved" error message during the setup wizard means that the Google Account used is not able to access the Home. Please ensure that you have successfully migrated your Nest Account to a Google Account using the Google Nest App. Additionally, if your home has multiple members, please note that the individual who initially set up the home must complete the migration of their Nest Account to a Google Account before you can establish a connection with Home Assistant. + - You can manage devices and permissions granted to Home Assistant in the Nest [Partner Connections Manager](https://nestservices.google.com/partnerconnections). Restart Home Assistant to make new devices available. See the [SDM API Troubleshooting](https://developers.google.com/nest/device-access/authorize#modify_account_permissions) documentation for more details. - *Error 400: invalid_request* plus a message about not complying with *Google's OAuth Policy for keeping accounts secure* is shown when using *App Auth* or *Desktop Auth* or *OOB Auth* which has been [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) by Google. Follow the steps in the previous section to upgrade Home Assistant and restore access. From 3d8f64e930849a42e6b238f70303a30e9d9187e5 Mon Sep 17 00:00:00 2001 From: Jan Bouwhuis Date: Mon, 2 Oct 2023 08:02:08 +0200 Subject: [PATCH 07/34] Type in imap docs (#29090) --- source/_integrations/imap.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/imap.markdown b/source/_integrations/imap.markdown index 2967737548d..b9dda766a26 100644 --- a/source/_integrations/imap.markdown +++ b/source/_integrations/imap.markdown @@ -40,7 +40,7 @@ If you’re going to use Gmail, 2-step verification must be enabled on your Gmai 10. Click **Submit**. 11. Assign your integration to an "Area" if desired, then click **Finish**. -Congratulations, you now how a sensor that counts the number of unread e-mails in your Gmail account. From here you can create additional sensors based upon the data that comes through the event bus when there's a new message detected. +Congratulations, you now have a sensor that counts the number of unread e-mails in your Gmail account. From here you can create additional sensors based upon the data that comes through the event bus when there's a new message detected. ### Configuring IMAP Searches From 3851a7b50c5e9eba6c8667be24b63bf3ee6fff8c Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 2 Oct 2023 08:48:48 +0200 Subject: [PATCH 08/34] Bump unicode-display_width from 2.4.2 to 2.5.0 (#29093) 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 c367e36c513..edc7bc78e53 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -114,7 +114,7 @@ GEM concurrent-ruby (~> 1.0) tzinfo-data (1.2023.3) tzinfo (>= 1.0.0) - unicode-display_width (2.4.2) + unicode-display_width (2.5.0) webrick (1.8.1) PLATFORMS From ff3d3728d93f12548eb9db864ccd2b8d94953776 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Mon, 2 Oct 2023 08:54:03 +0200 Subject: [PATCH 09/34] resetting password via console: explain placeholders in command (#29094) --- source/_docs/locked_out.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_docs/locked_out.md b/source/_docs/locked_out.md index 610b4282290..683ddf854a6 100644 --- a/source/_docs/locked_out.md +++ b/source/_docs/locked_out.md @@ -1,12 +1,12 @@ --- -title: "I'm Locked Out!" +title: "I'm locked out!" description: "Options for regaining access" --- The sections below deal with recovering from a situation where you are not able to sign in, or need to recover your data. -## Forgot Password +## Forgot password ### Home Assistant (including Supervised) @@ -30,7 +30,9 @@ Use this procedure if you know the username, and you can access the [Home Assist - If you are using a Home Assistant Green, refer to the following procedure: - [Using the terminal](https://green.home-assistant.io/guides/use-terminal/) 2. Once you have opened the Home Assistant command line, enter the following command: - `auth reset --username existing_user --password new_password` + - Note: `existing_user` is a placeholder. Replace it with your user name. + - Note: `new_password` is a placeholder. Replace it with your new password. + - **Command**: `auth reset --username existing_user --password new_password` 3. You can now log in to Home Assistant using this new password. #### To reset a user's password, via the container command line From b24f1f2f409196fec7dfeabe1004ec683868107a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20L=C3=B6vdahl?= Date: Mon, 2 Oct 2023 10:00:25 +0300 Subject: [PATCH 10/34] Fix Vallox profile name (#29080) Fixes #29053. --- source/_integrations/vallox.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/vallox.markdown b/source/_integrations/vallox.markdown index 7cb5b68e82b..dfeae5ee1c7 100644 --- a/source/_integrations/vallox.markdown +++ b/source/_integrations/vallox.markdown @@ -40,7 +40,7 @@ For convenient switching of ventilation profiles in the GUI, just click on the ` The four standard Vallox profiles are supported: -- `At Home` +- `Home` - `Away` - `Boost` - `Fireplace` From badd4e9cb771bd03986adf32e2e8c35c5cc2f692 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20S=C3=B8rensen?= Date: Mon, 2 Oct 2023 09:01:37 +0200 Subject: [PATCH 11/34] Replace service for CLA authorize (#29064) --- source/developers/cla_sign.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/developers/cla_sign.html b/source/developers/cla_sign.html index fc300f3b973..2523ba90ee8 100644 --- a/source/developers/cla_sign.html +++ b/source/developers/cla_sign.html @@ -437,7 +437,7 @@ description: "The Home Assistant contributor license agreement (CLA) signature p if (codeCheck && codeCheck.length > 0) { $.ajax({ type: "POST", - url: "https://cla.home-assistant.io/github/exchange", + url: "https://service-hub-bots.home-assistant.io/cla-sign/authorize", data: JSON.stringify({"code": codeCheck}), contentType: "application/json", }).done(function(data){ @@ -446,7 +446,7 @@ description: "The Home Assistant contributor license agreement (CLA) signature p var clean_uri = uri.substring(0, uri.indexOf("?")); window.history.replaceState({}, document.title, clean_uri); } - localStorage.setItem("gh_token", data.token); + localStorage.setItem("gh_token", data.access_token); fill_fields(); }); } else if (localStorage.getItem("gh_token") != null) { From dd0d700de69ddf0b66553aa262818e1ce33b99cd Mon Sep 17 00:00:00 2001 From: Ketil Moland Olsen Date: Mon, 2 Oct 2023 09:03:30 +0200 Subject: [PATCH 12/34] Fixed dead link to yr.no documentation (#29084) The link to the Norwegian yr.no Meteogram SVG documentation returned a 404. This is likely due to a restructuring of the website. I have found the new page this documentation is on, and have linked to it accordingly. --- source/_integrations/generic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/generic.markdown b/source/_integrations/generic.markdown index 3348c79326a..699278fd0c7 100644 --- a/source/_integrations/generic.markdown +++ b/source/_integrations/generic.markdown @@ -63,7 +63,7 @@ In this section, you find some real-life examples of how to use this camera plat - Still Image URL: `https://www.yr.no/en/content/1-72837/meteogram.svg` -Instructions on how to locate the SVG for your location are available at [developer.yr.no](https://developer.yr.no/doc/guides/deprecating-old-widgets/) +Instructions on how to locate the SVG for your location are available at [developer.yr.no](https://developer.yr.no/doc/guides/available-widgets/) ### Local image From 7390f5903f8bf7b79abc880368c42255d59cd633 Mon Sep 17 00:00:00 2001 From: Glenn Waters Date: Mon, 2 Oct 2023 03:12:46 -0400 Subject: [PATCH 13/34] Update UPB docs to address feedback and to add Debugging section (#29086) * Update UPB docs to address feedback and to add Debugging section * tiny tweak --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/upb.markdown | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/source/_integrations/upb.markdown b/source/_integrations/upb.markdown index e0f4fc7ff18..3d03682d88e 100644 --- a/source/_integrations/upb.markdown +++ b/source/_integrations/upb.markdown @@ -230,3 +230,16 @@ kitchen_fade_on: ## Notes - A UPB device does not always report its current state. For example, if you call `upb.light_fade_start` and then, a few seconds later, call `upb.light_fade_stop`, the selected UPB device will not report its new brightness level. However, if you then call `homeassistant.update_entity` it will make the UPB device report its current state to Home Assistant. +- Alterations to your UPB configuration with UpStart must be re-exported. The exported UPE file must have the same filename in the Home Assistant `config` directory. + +## Debugging +Debug logs are often required to solve an issue. To enable UPB debug logs add the following to your `configuration.yaml` file in your Home Assistant `config` directory: + +```yaml +logger: + logs: + upb_lib: debug + homeassistant.components.upb: debug +``` + +After updating your configuration file, restart Home Assistant. The debug logs will be in the file `homeassistant.log` in the `config` directory. From 496d04b84d977a4a43aef313dc57c6ed34017315 Mon Sep 17 00:00:00 2001 From: Ketil Moland Olsen Date: Mon, 2 Oct 2023 09:14:42 +0200 Subject: [PATCH 14/34] Updated URL to HEOS website in docs (#29088) Denon has changed their site structure, resulting in a 404 error when clicking the referenced link. I have found the new corresponding link and corrected it. --- source/_integrations/heos.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/heos.markdown b/source/_integrations/heos.markdown index 58041dc0208..a31ba2a51cd 100644 --- a/source/_integrations/heos.markdown +++ b/source/_integrations/heos.markdown @@ -15,7 +15,7 @@ ha_platforms: ha_integration_type: integration --- -The HEOS integration adds support for [HEOS](https://www.denon.com/en-gb/shop/amplifiersmrs/heosavr) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include: +The HEOS integration adds support for [HEOS](https://www.denon.com/en-gb/category/heos/) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include: - Each device is represented as a media player entity - View the currently playing media From c7106739f466f98a210dbb528714465affe25d78 Mon Sep 17 00:00:00 2001 From: Maciej Bieniek Date: Mon, 2 Oct 2023 12:21:40 +0000 Subject: [PATCH 15/34] Update information about Shelly `update` platform (#29098) --- source/_integrations/shelly.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_integrations/shelly.markdown b/source/_integrations/shelly.markdown index 75076820b6d..5dcb16ae7b2 100644 --- a/source/_integrations/shelly.markdown +++ b/source/_integrations/shelly.markdown @@ -253,16 +253,16 @@ The firmware limits the transition time to 5 seconds. The integration offers device services which can be triggered by a configuration button. -### OTA update +### OTA firmware update Trigger device OTA firmware update. -#### Buttons +#### Update entities -- OTA Update - - triggers the OTA update process for latest stable version -- OTA Update Beta (_disabled by default_) - - triggers the OTA update process for latest beta version +- Firmware update + - triggers the OTA firmware update process to the latest stable version +- Beta firmware update (_disabled by default_) + - triggers the OTA firmware update process to the latest beta version ### Reboot @@ -315,5 +315,5 @@ Please check from the device Web UI that the configured server is reachable. - Only supports firmware 0.8 and later for generation 2 devices - Generation 1 "Shelly 4Pro" and "Shelly Sense" are not supported (devices based on old CoAP v1 protocol) - Before set up, battery-powered devices must be woken up by pressing the button on the device. -- OTA update service does not support battery-powered devices +- For battery-powered devices, the `update` platform entities only inform about the availability of firmware updates but are not able to trigger the update process. - Frequency sensors for generation 2 energy monitoring devices are supported by firmware 1.0.0 beta 6 or later. From 139c9fae6581ee8365498cc008413d1d8ba520f2 Mon Sep 17 00:00:00 2001 From: Ketil Moland Olsen Date: Mon, 2 Oct 2023 21:47:10 +0200 Subject: [PATCH 16/34] Fixed dead links to Bitron Video USB Stick (#29105) The URLs to the Bitron Video USB Stick web page were dead. I did some research and found the new URL in the new site structure. It is now updated and working again, --- source/_integrations/zha.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index dc6c49cffb9..8f16bd3695f 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -108,7 +108,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl - Silicon Labs EmberZNet based radios using legacy hardware using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) - [ITead Sonoff ZBBridge](https://itead.cc/product/sonoff-zbbridge/) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first has to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html)) - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/walthowd/husbzb-firmware)) - - [Bitron Video/Smabit BV AV2010/10 USB-Stick](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) with Silicon Labs Ember 3587 + - [Bitron Video/Smabit BV AV2010/10 USB-Stick](https://manuals.smabit.eu/len/av2010_10.html) with Silicon Labs Ember 3587 - Telegesis ETRX357USB/ETRX357USB-LR/ETRX357USB-LRS+8M (Note! These first have to be [flashed with other EmberZNet firmware](https://github.com/walthowd/husbzb-firmware)) - Texas Instruments based radios using legacy hardware (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy) - [CC2538 USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) (no longer recommended as only got deprecated old end-of-life firmware) @@ -195,7 +195,7 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------------------ | | [ITead SONOFF Zigbee 3.0 USB Dongle Plus V2 Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/) | USB | 1A86:55D4 | | [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-P" (CC2652P variant)](https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/) | USB | 10C4:EA60 | -| [Bitron Video/SMaBiT BV AV2010/10](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | USB | 10C4:8B34 | +| [Bitron Video/SMaBiT BV AV2010/10](https://manuals.smabit.eu/len/av2010_10.html) | USB | 10C4:8B34 | | [ConBee II](https://phoscon.de/conbee2) | USB | 1CF1:0030 | | [Nortek HUSBZB-1](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | USB | 10C4:8A2A | | [slae.sh CC2652RB development stick](https://slae.sh/projects/cc2652/) | USB | 10C4:EA60 | From bdab11984f1073d1aa59e57ee35d8a4568258104 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 2 Oct 2023 15:54:11 -0400 Subject: [PATCH 17/34] Hue update (#29106) * Hue update * remove accidentally reverted change * Update source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown Co-authored-by: Franck Nijhof --------- Co-authored-by: Franck Nijhof --- ...22-philips-hue-force-users-upload-data-to-cloud.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown b/source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown index bfabf42a402..8941c82756a 100644 --- a/source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown +++ b/source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown @@ -1,5 +1,5 @@ --- -title: "Philips Hue will force users to upload their data to Hue cloud" +title: "[Update Oct 2: data sharing to become optional] Philips Hue will force users to upload their data to Hue cloud" description: "To control your lights you soon need to create an account and share your data with the Hue cloud." date: 2023-09-22 0:0:00 date_formatted: "September 22, 2023" @@ -10,6 +10,10 @@ categories: Public-Service-Announcement og_image: /images/blog/2023-09-hue-upload-user-data-cloud/social.png --- +**Update Oct 2:** In a [conversation with The Verge](https://www.theverge.com/2023/9/28/23892761/philips-hue-app-account-changes), Philips Hue has announced that they will update their privacy policy to require users to consent to share their usage data with Philips Hue. + +_Original Post_ + Today’s story is about Philips Hue by Signify. They will soon start forcing accounts on all users and upload user data to their cloud. For now, Signify says you’ll still be able to control your Hue lights locally as you’re currently used to, but we don’t know if this may change in the future. The privacy policy allows them to store the data and share it with partners. Last week I wrote how toying with the first Philips Hue hub and their local API led me to [start Home Assistant back in 2013](/blog/2023/09/17/10-years-home-assistant/). They have played an important role in my smart home and they were a role model for [our Open Home vision](/blog/2021/12/23/the-open-home/). Sure, they are expensive but they work reliably, have a local API, can be used completely offline, and you don’t have to share your data with the cloud. From 782a678c194bbfac6a0b7e9a194fa8ebef8f74a8 Mon Sep 17 00:00:00 2001 From: Ketil Moland Olsen Date: Mon, 2 Oct 2023 22:11:34 +0200 Subject: [PATCH 18/34] Updated Volvo On Call URL and name (#29107) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Volvo has rebranded Volvo On Call to Volvo Cars App, and has changed the link structure in the process. The current link was dead, so I have updated it to match the new site structure. Since the Home Assistant Integration is still named Volvo On Call, I have left those instance names as is – except for the link to the service, where I have used the new naming convention and explained the name change as a side note. --- source/_integrations/volvooncall.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/volvooncall.markdown b/source/_integrations/volvooncall.markdown index 096115f8173..3f80ba1bd83 100644 --- a/source/_integrations/volvooncall.markdown +++ b/source/_integrations/volvooncall.markdown @@ -18,7 +18,7 @@ ha_integration_type: integration ha_config_flow: true --- -The `volvooncall` integration offers integration with the [Volvo On Call](https://www.volvocars.com/intl/why-volvo/human-innovation/future-of-driving/connectivity/volvo-on-call) cloud service and offers presence detection as well as sensors such as odometer and fuel level. +The `volvooncall` integration offers integration with the [Volvo Cars App](https://www.volvocars.com/intl/v/volvo-cars-app) (former Volvo On Call) cloud service and offers presence detection as well as sensors such as odometer and fuel level. {% include integrations/config_flow.md %} From 6fd5a6426857eca503ab14dd8bf9e07ffaab5231 Mon Sep 17 00:00:00 2001 From: olivervhansen <72828392+olivervhansen@users.noreply.github.com> Date: Mon, 2 Oct 2023 23:03:33 -0700 Subject: [PATCH 19/34] Update lyric.markdown instructions to add clarity (#29111) * Update lyric.markdown instructions to add clarity around account and secrets Using an email that does not match the one used in Resideo will not link the app with the thermostat. Clarifying where the Consumer key and secret are viewed after creating the app. * Tiny tweaks --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/lyric.markdown | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/_integrations/lyric.markdown b/source/_integrations/lyric.markdown index 3a6a85019c7..84534445cef 100644 --- a/source/_integrations/lyric.markdown +++ b/source/_integrations/lyric.markdown @@ -22,12 +22,13 @@ The Honeywell Lyric integration integrates the Lyric thermostat platform into Ho ## Setup -To set up this integration, you first **must** set up a developer account with Honeywell: +To set up this integration, you first **must** set up a developer account with Honeywell using the same email address as your Resideo account: 1. Go to the [developer site](https://developer.honeywellhome.com) and register with an account. 2. Next, create a [new app](https://developer.honeywellhome.com/user/me/apps/add) via the `My Apps` section. 1. App Name: You can use any name here, but it must not contain special characters. 2. Callback URL: `https://my.home-assistant.io/redirect/oauth` + 3. The app will be approved automatically. To view the **Consumer Key** and **Consumer Secret** values, select the name of the app. Copy the values, you will need them later. {% details "I have manually disabled My Home Assistant" %} @@ -46,7 +47,7 @@ You can then add the integration in the frontend via the steps below. {% include integrations/config_flow.md %} -The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details. +The integration configuration will ask for the **Client ID** and **Client Secret**, which correspond to the **Consumer** values in the app you created above. See [Application Credentials](/integrations/application_credentials) for more details. ## Sensors From 28a5b495798ee80fbc680acdc615b569250a2a08 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 08:24:29 +0200 Subject: [PATCH 20/34] Green page FAQ: update SkyConnect text (#29113) --- source/green/index.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/source/green/index.html b/source/green/index.html index 06e3fa57fc4..7052b7c18fe 100644 --- a/source/green/index.html +++ b/source/green/index.html @@ -2195,11 +2195,10 @@ frontpage_image: /images/frontpage/green-frontpage.png >

- No, Home Assistant Green works out of the box, but it does not - have a Zigbee radio.

If you want to use a Zigbee and/or - Matter-over-Thread network, Home Assistant SkyConnect can provide - that. + If you want to connect Home Assistant Green to the hub of your existing smart home system that uses Zigbee or Thread to communicate, you can do so out-of-the-box for most popular brands. This will be the easiest way to connect your existing Zigbee or Matter devices and does not require a Home Assistant SkyConnect.

+

You need a Home Assistant SkyConnect if you want to connect Zigbee or Thread* devices directly to Home Assistant Green.

+

* Thread support is currently under development.

From 98181c6d1bd529a38445d564e90fe51ecbd769eb Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 08:54:03 +0200 Subject: [PATCH 21/34] Green page: update SkyConnect marketing copy (#29114) --- source/green/index.html | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/green/index.html b/source/green/index.html index 7052b7c18fe..e0dadd17812 100644 --- a/source/green/index.html +++ b/source/green/index.html @@ -1008,10 +1008,8 @@ frontpage_image: /images/frontpage/green-frontpage.png Expand compatibility as your home expands.

- You can add Home Assistant SkyConnect* for Zigbee and - Matter-over-Thread, set up Home Assistant Cloud for voice - assistants, and integrate third-party USB accessories to support - other smart standards such as Z-Wave. + You can add Home Assistant SkyConnect to connect Zigbee and Thread* devices, set up Home Assistant Cloud for voice assistants, and integrate third-party USB accessories to support other smart standards, such as Z-Wave or Bluetooth. +
*Thread support is currently under development.

Date: Tue, 3 Oct 2023 08:55:04 +0200 Subject: [PATCH 22/34] Blog: update section on Green (#29115) --- ...-home-assistant-green-your-entry-to-home-assistant.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown b/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown index 3e600692e68..d545a689331 100644 --- a/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown +++ b/source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown @@ -25,11 +25,10 @@ Home Assistant Green contains everything you need for Home Assistant in one box. Home Assistant Green alongside Home Assistant Yellow and Home Assistant Blue

-On the inside, Home Assistant Green runs on a powerful 1.8 GHz quad-core CPU. Memory and storage are amply provided with 4 GB of RAM and 32 GB of eMMC, more than enough to keep you running Home Assistant on the device for a long time. When your smart home grows, you can use Home Assistant SkyConnect to add Zigbee and Matter support or one of many third-party USB devices available to expand Home Assistant Green with other smart standards like Z-Wave or Bluetooth. +On the inside, Home Assistant Green runs on a powerful 1.8 GHz quad-core CPU. Memory and storage are amply provided with 4 GB of RAM and 32 GB of eMMC, more than enough to keep you running Home Assistant on the device for a long time. Connecting to your existing smart home platforms lets you instantly use your devices that communicate over Zigbee, Matter, or other smart standards. And when your smart home grows, you can use Home Assistant SkyConnect to add Zigbee and Thread radios (Thread support under development) or one of many third-party USB devices available to expand Home Assistant Green with other smart standards like Z-Wave or Bluetooth. On the outside, Home Assistant Green has a stunning translucent enclosure design revealing the hub's inner hardware. Unlike some other smart home devices, it looks great in your home decor. The bottom of the case also functions as the hub's heat sink and is made of a solid piece of black, anodized aluminum. And, of course, this case features [the new Home Assistant logo][logo-blog] on top as a nice subtle mosaic pattern. -

Home Assistant Green has 1.8 GHz quad-code CPU, 4 GB of RAM and 32 GB of eMMC storage. Home Assistant Green specifications From 5aa25d212e7cdd60f88811e7081cd9542aba2a4a Mon Sep 17 00:00:00 2001 From: Bram Kragten Date: Tue, 3 Oct 2023 11:00:27 +0200 Subject: [PATCH 23/34] Update styling of my badges (#29119) --- sass/custom/_paulus.scss | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index 5b9c77c7c80..25dc5a0177a 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -934,6 +934,8 @@ code { a.my { img { border: 0px; + border-radius: 0; + box-shadow: none; } } From 40e2632f6ae2053fc0d3489bcf2df7ca59604594 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 3 Oct 2023 11:40:28 +0200 Subject: [PATCH 24/34] Restore from backup: emphasize required disk size (#29120) --- source/_includes/common-tasks/backups.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_includes/common-tasks/backups.md b/source/_includes/common-tasks/backups.md index 9ec7011535d..f6ed9efed9b 100644 --- a/source/_includes/common-tasks/backups.md +++ b/source/_includes/common-tasks/backups.md @@ -85,12 +85,13 @@ You can use a backup during the onboarding process to restore your configuration - This procedure assumes you have already completed the [installation](/installation/) procedure on your target device and are now viewing the welcome screen as part of the [onboarding](/getting-started/onboarding/). - The login credentials of the device from which you made the backup. -- If you migrate the installation to a new device, make sure the new device has more storage capacity than the existing device. +- **Required storage capacity**: If you migrate the installation to a new device, make sure the new device has more storage capacity than the existing device. - Before migrating, on the old system, check how much storage you used. - Go to **{% my system_health title="Settings > System > Repairs -> ... -> System Information" %}**, and under **Home Assistant Supervisor**, look at the **Disk used** value. - The target device must have more free space than the source device. - If your target device is a Home Assistant Yellow, note that it is the size of the eMMC that is relevant. - The restore process mainly uses the eMMC, not the NVMe. + - The size of the backup file is no indication of the size of your installation. To know the size of your installation, you need to check the **Disk used** value mentioned above. - If you are migrating to a new device: - You do not need to transfer the backup to a USB or SD card to bring it to your device. - You will be able to upload the backup file from the device you are accessing the onboarding from. From 024192d4f0dfd80086fbe289de09645d8338f634 Mon Sep 17 00:00:00 2001 From: EgonMarmol <56889319+EgonMarmol@users.noreply.github.com> Date: Tue, 3 Oct 2023 12:02:42 +0200 Subject: [PATCH 25/34] Fixed broken link pilight protocols doc (#29121) --- source/_integrations/pilight.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/pilight.markdown b/source/_integrations/pilight.markdown index 1ea9ac9a78e..73451081f02 100644 --- a/source/_integrations/pilight.markdown +++ b/source/_integrations/pilight.markdown @@ -152,7 +152,7 @@ binary_sensor: This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g., _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up. -To use your sensor via pilight, make sure it is [supported](https://wiki.pilight.org/protocols) and add the following to your `configuration.yaml` file: +To use your sensor via pilight, make sure it is [supported](https://manual.pilight.org/protocols/index.html) and add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry From 7ba343fcac14020579b9e1eade7f0402c5aa0985 Mon Sep 17 00:00:00 2001 From: Robert Date: Tue, 3 Oct 2023 12:38:00 +0200 Subject: [PATCH 26/34] Update select.markdown (#29122) --- source/_integrations/select.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/select.markdown b/source/_integrations/select.markdown index 05a9f43a8fc..ab9e125b9a0 100644 --- a/source/_integrations/select.markdown +++ b/source/_integrations/select.markdown @@ -17,8 +17,8 @@ a limited set of selectable options for the entity. ## Services -The select entity exposes additional to control the entity in, for example, -automation or scripts. These service can be created via the UI, but are +The select entity exposes additional services to control the entity in, for example, +automation or scripts. These services can be created via the UI, but are also available in YAML (for which examples are provided below). ### Service `select.select_first` From 25b009f35cb425d6b2baca426f7e322c6fc79949 Mon Sep 17 00:00:00 2001 From: EgonMarmol <56889319+EgonMarmol@users.noreply.github.com> Date: Tue, 3 Oct 2023 13:08:32 +0200 Subject: [PATCH 27/34] Corrected typo in URL to modbus specification doc (#29123) --- source/_integrations/modbus.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/modbus.markdown b/source/_integrations/modbus.markdown index d60075a741a..448cd3c2e1d 100644 --- a/source/_integrations/modbus.markdown +++ b/source/_integrations/modbus.markdown @@ -24,7 +24,7 @@ ha_integration_type: integration [modbus](http://www.modbus.org/) is a communication protocol to control PLCs (Programmable Logic Controller) and RTUs (Remote Terminal Unit). -The integration adheres strictly to the [protocol specification](https://modbus.org/docs/modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the actual protocol implmentation. +The integration adheres strictly to the [protocol specification](https://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the actual protocol implmentation. The modbus integration supports all devices adhering to the modbus standard. The communication to the device/devices can be serial (rs-485), TCP, or UDP connections. The modbus integration allows multiple communication channels e.g. a serial port connection combined with one or more TCP connections. From f81dd7b26b2d33e9d6080f8b9ee018c595ecda7d Mon Sep 17 00:00:00 2001 From: b-uwe <61052367+b-uwe@users.noreply.github.com> Date: Tue, 3 Oct 2023 13:59:42 +0200 Subject: [PATCH 28/34] Add Everything Smart, SmarterHome and Swiss Domotique to the Green distributors list (#29124) --- source/green/index.html | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/source/green/index.html b/source/green/index.html index e0dadd17812..79710d777dd 100644 --- a/source/green/index.html +++ b/source/green/index.html @@ -2324,6 +2324,24 @@ frontpage_image: /images/frontpage/green-frontpage.png

+ +
+
+
🇬🇧
+
Everything Smart Technology
+
Located in the United Kingdom
+
+ + + +
+ + + +
+
+
🇸🇰
+
SmarterHOME
+
Located in Slovakia
+
+ + + +
+ + + +
+
+
🇨🇭
+
Swiss-Domotique
+
Located in Switzerland
+
+ + + +
+ + From 76c26ff942cf69381faddaed226099c22b038ea2 Mon Sep 17 00:00:00 2001 From: EgonMarmol <56889319+EgonMarmol@users.noreply.github.com> Date: Tue, 3 Oct 2023 15:05:53 +0200 Subject: [PATCH 29/34] Updated MGV website link (#29127) The URL to the MGV website "meinhalt" section is dead. After a bit of researched, I've found the new corresponding site section and updated the URL accordingly. --- source/_integrations/mvglive.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/mvglive.markdown b/source/_integrations/mvglive.markdown index 614760c302b..433bb0268da 100644 --- a/source/_integrations/mvglive.markdown +++ b/source/_integrations/mvglive.markdown @@ -27,7 +27,7 @@ sensor: {% configuration %} station: - description: Name of the stop or station. Visit [the MVG live web site](https://www.mvg-live.de/ims/dfiStaticAuswahl.svc) to find valid names. Be aware, that not all data of interest might be available (i.e., bus departure-times in Haar). + description: Name of the stop or station. Visit [the MVG live web site](https://www.mvg.de/meinhalt.html) to find valid names. Be aware, that not all data of interest might be available (i.e., bus departure-times in Haar). required: true type: string destinations: From 82c44314a82fddfca1c2991c415c6bf09c814bf4 Mon Sep 17 00:00:00 2001 From: scheric <38077357+scheric@users.noreply.github.com> Date: Tue, 3 Oct 2023 15:07:05 +0200 Subject: [PATCH 30/34] Fix link in locative.md (#29128) --- source/_integrations/locative.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/locative.md b/source/_integrations/locative.md index 9e0299e35e3..f68023d902f 100644 --- a/source/_integrations/locative.md +++ b/source/_integrations/locative.md @@ -8,7 +8,7 @@ ha_iot_class: Cloud Push ha_domain: locative --- -This platform allows you to detect presence using [Locative](https://www.locative.io/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location. +This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location. Install on your smartphone: From 8bdc946fcc82824af5b58b4c4e6854d154411e92 Mon Sep 17 00:00:00 2001 From: EgonMarmol <56889319+EgonMarmol@users.noreply.github.com> Date: Tue, 3 Oct 2023 16:42:38 +0200 Subject: [PATCH 31/34] Removed dead URL to Plugwise Stretch (#29130) The Plugwise Strech-URL in the docs leads to a dead page. Plugwise has deprecated this product, so I think the right thing to do is remove the link and reference it in the text. I have added a short explanation to the text saying that the product is no longer for sale. --- source/_integrations/plugwise.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/plugwise.markdown b/source/_integrations/plugwise.markdown index 07c67d8fe99..5aa3a887801 100644 --- a/source/_integrations/plugwise.markdown +++ b/source/_integrations/plugwise.markdown @@ -29,7 +29,7 @@ ha_integration_type: hub --- This enables [Plugwise](https://www.plugwise.com) integrations with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address. -The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol), [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products and the [Stretch](https://www.plugwise.com/nl_NL/het-systeem) products. See below list for more details. +The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol), [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products and the Stretch products (not in sale). See below list for more details. Platforms available - depending on your Smile and setup include: From edbc2e85dfe8433dd65195080c9f203a11154c8c Mon Sep 17 00:00:00 2001 From: scheric <38077357+scheric@users.noreply.github.com> Date: Tue, 3 Oct 2023 19:27:58 +0200 Subject: [PATCH 32/34] Fix link to notify service in webostv (#29133) --- source/_integrations/webostv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 502833141fb..a91c59c1c6f 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -24,7 +24,7 @@ The `webostv` platform allows you to control a [LG](https://www.lg.com/) webOS S There is currently support for the following device types within Home Assistant: - [Media Player](/integrations/media_player/) -- [Notifications](/integrations/notification/) +- [Notifications](/integrations/notify/) To begin with enable *LG Connect Apps* feature in *Network* settings of the TV. From a4f76128df52b8aa01030a1daf53cd3a406a5043 Mon Sep 17 00:00:00 2001 From: erlendmoland <56839803+erlendmoland@users.noreply.github.com> Date: Tue, 3 Oct 2023 19:40:41 +0200 Subject: [PATCH 33/34] Fixed broken link to Keba manual (#29135) --- source/_integrations/keba.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/keba.markdown b/source/_integrations/keba.markdown index beef3a9e2ca..2cde4e5dad6 100644 --- a/source/_integrations/keba.markdown +++ b/source/_integrations/keba.markdown @@ -19,7 +19,7 @@ ha_platforms: ha_integration_type: integration --- -The `keba` integrates your Keba charging station/BMW Wallbox into your Home Assistant instance using the UDP Smart Home Interface ([manual](https://www.keba.com/web/downloads/e-mobility/KeContact_P20_P30_UDP_ProgrGuide_en.pdf)). The fetching interval to the charging station is set to 5 seconds, same as in the official mobile app. In order to use the integration, enable the UDP Smart Home Interface by adjusting the DIP switches within the charging station according to the [installation manual](https://www.keba.com/file/downloads/e-mobility/KeContact_KCP20_30_ih_en.pdf). +The `keba` integrates your Keba charging station/BMW Wallbox into your Home Assistant instance using the UDP Smart Home Interface ([manual](https://www.ifix-solar.shop/wp-content/uploads/shop/Dokumente/KEBA/KeContact_P20_P30_UDP_ProgrGuide_en.pdf)). The fetching interval to the charging station is set to 5 seconds, same as in the official mobile app. In order to use the integration, enable the UDP Smart Home Interface by adjusting the DIP switches within the charging station according to the [installation manual](https://www.keba.com/file/downloads/e-mobility/KeContact_KCP20_30_ih_en.pdf). This integration provides the following platforms: From 01a11412105e2fa9632967299a583eba4a1c8a60 Mon Sep 17 00:00:00 2001 From: Joakim Plate Date: Tue, 3 Oct 2023 19:47:52 +0200 Subject: [PATCH 34/34] Adjust documentation for knx (#29092) * Adjust documentation for knx * Switch to colon * Not allowed to use : in description --- source/_integrations/knx.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 4a894e82b9a..ff5d693127d 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -823,6 +823,8 @@ The KNX cover platform is used as an interface to KNX covers. Unlike most KNX devices, Home Assistant defines 0% as closed and 100% as fully open in regards to covers. The corresponding value inversion is done internally by the KNX integration. +Home Assistant will, by default, `close` a cover by moving it in the `DOWN` direction in the KNX nomenclature, and `open` a cover by moving it in the `UP` direction. + To use your KNX covers in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`: @@ -852,7 +854,7 @@ move_long_address: required: false type: [string, list] move_short_address: - description: KNX group address for moving the cover stepwise up or down. Used by some covers also as the means to stop the cover, if no dedicated `stop_address` exists on the actuator. *DPT 1* + description: KNX group address for moving the cover stepwise up or down. Used by some covers also as the means to stop the cover. Stepwise moves are only mapped to tilt angle functions in Home Assistant, as no stepwise move of cover position is generally supported by the architecture. If tilt angle is not supported, prefer the use of a `stop_address`. *DPT 1* required: false type: [string, list] stop_address: @@ -886,12 +888,12 @@ travelling_time_up: default: 25 type: integer invert_updown: - description: Set this to `true` to invert the binary up/down commands from/to your KNX actuator. Default is 0 for UP; 1 for DOWN. + description: Set this to `true` to invert the up/down commands from/to your KNX actuator. Default is to consider `UP` (0) as opening of a cover and `DOWN` (1) as closing of a cover. required: false default: false type: boolean invert_position: - description: Set this to `true` if your actuator reports fully closed position as 0% in KNX. + description: Set this to `true` if your actuator reports fully down position as 0% in KNX. required: false default: false type: boolean