From c56274472cdcb85996a190790b1d9565c850ec5c Mon Sep 17 00:00:00 2001 From: TheJulianJES Date: Wed, 26 Feb 2025 06:46:58 +0100 Subject: [PATCH 1/6] Update number device classes (#37709) --- source/_integrations/number.markdown | 36 +++++++++++++++------------- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/source/_integrations/number.markdown b/source/_integrations/number.markdown index ff81b2e2e646..35741f873536 100644 --- a/source/_integrations/number.markdown +++ b/source/_integrations/number.markdown @@ -42,37 +42,38 @@ The following device classes are supported for numbers: - **apparent_power**: Apparent power in VA. - **aqi**: Air Quality Index (unitless). - **area**: Area in m², cm², km², mm², in², ft², yd², mi², ac, ha -- **atmospheric_pressure**: Atmospheric pressure in cbar, bar, hPa, inHg, kPa, mbar, Pa, psi -- **battery**: Percentage of battery that is left -- **blood_glocose_concentration**: Blood glucose concentration in mg/dL, mmol/L -- **carbon_dioxide**: Carbon Dioxide in CO2 (Smoke) -- **carbon_monoxide**: Carbon Monoxide in CO (Gas CNG/LPG) +- **atmospheric_pressure**: Atmospheric pressure in cbar, bar, hPa, mmHg, inHg, kPa, mbar, Pa or psi +- **battery**: Percentage of battery that is left in % +- **blood_glucose_concentration**: Blood glucose concentration in mg/dL, mmol/L +- **carbon_dioxide**: Carbon Dioxide in CO2 (Smoke) in ppm +- **carbon_monoxide**: Carbon Monoxide in CO (Gas CNG/LPG) in ppm - **current**: Current in A, mA -- **data_rate**: Data rate in bit/s, kbit/s, Mbit/s, Gbit/s, B/s, kB/s, MB/s, GB/s, KiB/s, MiB/s, or GiB/s -- **data_size**: Data size in bit, kbit, Mbit, Gbit, B, kB, MB, GB, TB, PB, EB, ZB, YB, KiB, MiB, GiB, TiB, PiB, EiB, ZiB, or YiB -- **distance**: Generic distance in km, m, cm, mm, mi, yd, or in +- **data_rate**: Data rate in bit/s, kbit/s, Mbit/s, Gbit/s, B/s, kB/s, MB/s, GB/s, KiB/s, MiB/s or GiB/s +- **data_size**: Data size in bit, kbit, Mbit, Gbit, B, kB, MB, GB, TB, PB, EB, ZB, YB, KiB, MiB, GiB, TiB, PiB, EiB, ZiB or YiB +- **distance**: Generic distance in km, m, cm, mm, mi, nmi, yd, or in +- **duration**: Duration in d, h, min, s, or ms - **energy**: Energy in J, kJ, MJ, GJ, mWh, Wh, kWh, MWh, GWh, TWh, cal, kcal, Mcal, or Gcal - **energy_storage**: Stored energy in J, kJ, MJ, GJ, mWh, Wh, kWh, MWh, GWh, TWh, cal, kcal, Mcal, or Gcal - **frequency**: Frequency in Hz, kHz, MHz, or GHz -- **gas**: Gasvolume in m³, ft³, or CCF -- **humidity**: Percentage of humidity in the air +- **gas**: Gasvolume in m³, ft³ or CCF +- **humidity**: Percentage of humidity in the air in % - **illuminance**: The current light level in lx - **irradiance**: Irradiance in W/m² or BTU/(h⋅ft²) -- **moisture**: Percentage of water in a substance -- **monetary**: The monetary value +- **moisture**: Percentage of water in a substance in % +- **monetary**: The monetary value ([ISO 4217](https://en.wikipedia.org/wiki/ISO_4217#Active_codes)) - **nitrogen_dioxide**: Concentration of Nitrogen Dioxide in µg/m³ - **nitrogen_monoxide**: Concentration of Nitrogen Monoxide in µg/m³ - **nitrous_oxide**: Concentration of Nitrous Oxide in µg/m³ - **ozone**: Concentration of Ozone in µg/m³ - **ph**: Potential hydrogen (pH) value of a water solution - **pm1**: Concentration of particulate matter less than 1 micrometer in µg/m³ -- **pm10**: Concentration of particulate matter less than 10 micrometers in µg/m³ - **pm25**: Concentration of particulate matter less than 2.5 micrometers in µg/m³ -- **power_factor**: Power factor(unitless), unit may be `None` or % +- **pm10**: Concentration of particulate matter less than 10 micrometers in µg/m³ +- **power_factor**: Power factor (unitless), unit may be `None` or % - **power**: Power in mW, W, kW, MW, GW or TW - **precipitation**: Accumulated precipitation in cm, in or mm -- **precipitation_intensity**: Precipitation intensity in in/d, in/h, mm/d, or mm/h -- **pressure**: Pressure in Pa, kPa, hPa, bar, cbar, mbar, mmHg, inHg, or psi +- **precipitation_intensity**: Precipitation intensity in in/d, in/h, mm/d or mm/h +- **pressure**: Pressure in Pa, kPa, hPa, bar, cbar, mbar, mmHg, inHg or psi - **reactive_power**: Reactive power in var - **signal_strength**: Signal strength in dB or dBm - **sound_pressure**: Sound pressure in dB or dBA @@ -80,13 +81,14 @@ The following device classes are supported for numbers: - **sulphur_dioxide**: Concentration of sulphur dioxide in µg/m³ - **temperature**: Temperature in °C, °F or K - **volatile_organic_compounds**: Concentration of volatile organic compounds in µg/m³ +- **volatile_organic_compounds_parts**: Ratio of volatile organic compounds in ppm or ppb - **voltage**: Voltage in V, mV, µV, kV, MV - **volume**: Generic volume in L, mL, gal, fl. oz., m³, ft³, or CCF - **volume_flow_rate**: Volume flow rate in m³/h, ft³/min, L/min, gal/min, or mL/s - **volume_storage**: Generic stored volume in L, mL, gal, fl. oz., m³, ft³, or CCF - **water**: Water consumption in L, gal, m³, ft³, or CCF - **weight**: Generic mass in kg, g, mg, µg, oz, lb, or st -- **wind_speed**: Wind speed in ft/s, km/h, kn, m/s, or mph +- **wind_speed**: Wind speed in Beaufort, ft/s, km/h, kn, m/s, or mph ## Actions From bb7c3f43ca06260371ca757adb279394f0d56c72 Mon Sep 17 00:00:00 2001 From: kylehakala Date: Tue, 25 Feb 2025 23:52:15 -0600 Subject: [PATCH 2/6] Tuck the caution inside of the collapsed section (#37699) --- source/_integrations/zha.markdown | 26 +++++++++++--------------- 1 file changed, 11 insertions(+), 15 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index b20477ce374f..a5a8bb3a5133 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -108,13 +108,21 @@ Newer coordinators generally support Zigbee 3.0 firmware, but it is up to the ma ### Other supported but not recommended Zigbee radio adapters or modules +The following hardware is supported, but _not recommended_. Specific models and details are noted where available in each section. + {% details "List of hardware that is not recommended" %} -{% warning %} +{% caution %} -The following hardware is supported, but _not recommended_. Specific models and details are noted where available in each section. +- It is **not recommended** to run a coordinator via **Serial-Proxy-Server** _(also called Serial-to-IP bridge or Ser2Net remote adapter)_ over: + + - **Wi-Fi**, + - **WAN**, or + - **VPN** -{% endwarning %} +- The coordinator requires a stable, local connection to its serial port interface without drops in communication with the Zigbee gateway application running on the host computer. +- Serial protocols used by the coordinator do not have enough robustness, resilience, or fault tolerance to handle packet loss and latency delays that can occur over unstable connections. +{% endcaution %} **Silicon Labs EmberZNet based radios using legacy hardware using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)** @@ -165,18 +173,6 @@ The following hardware is supported, but _not recommended_. Specific models and If you find an opportunity to improve this information, refer to the section on how to [add support for new and unsupported devices](#how-to-add-support-for-new-and-unsupported-devices). -{% caution %} - -- It is **not recommended** to run a coordinator via **Serial-Proxy-Server** _(also called Serial-to-IP bridge or Ser2Net remote adapter)_ over: - - - **Wi-Fi**, - - **WAN**, or - - **VPN** - -- The coordinator requires a stable, local connection to its serial port interface without drops in communication with the Zigbee gateway application running on the host computer. -- Serial protocols used by the coordinator do not have enough robustness, resilience, or fault tolerance to handle packet loss and latency delays that can occur over unstable connections. -{% endcaution %} - ## Configuration requirements Be sure to connect a compatible radio module and restart Home Assistant before proceeding with configuration. From f84c1496f9a11cb65af69dffbad1c5d0e388fb5e Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 26 Feb 2025 08:01:19 +0100 Subject: [PATCH 3/6] build(deps-dev): bump sorbet-runtime from 0.5.11856 to 0.5.11862 (#37711) Bumps [sorbet-runtime](https://github.com/sorbet/sorbet) from 0.5.11856 to 0.5.11862. - [Release notes](https://github.com/sorbet/sorbet/releases) - [Commits](https://github.com/sorbet/sorbet/commits) --- updated-dependencies: - dependency-name: sorbet-runtime dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] 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 c713dafde37e..7eee5aea2767 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -158,7 +158,7 @@ GEM rack-protection (= 4.1.1) rack-session (>= 2.0.0, < 3) tilt (~> 2.0) - sorbet-runtime (0.5.11856) + sorbet-runtime (0.5.11862) stringex (2.8.6) terminal-table (3.0.2) unicode-display_width (>= 1.1.1, < 3) From 0ba72f821a87ef88d9bfb3fb131e579b3245509a Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 26 Feb 2025 08:01:43 +0100 Subject: [PATCH 4/6] build(deps-dev): bump rubocop-ast from 1.38.0 to 1.38.1 (#37712) Bumps [rubocop-ast](https://github.com/rubocop/rubocop-ast) from 1.38.0 to 1.38.1. - [Release notes](https://github.com/rubocop/rubocop-ast/releases) - [Changelog](https://github.com/rubocop/rubocop-ast/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-ast/compare/v1.38.0...v1.38.1) --- updated-dependencies: - dependency-name: rubocop-ast dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] 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 7eee5aea2767..09fd5b582775 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -130,7 +130,7 @@ GEM rubocop-ast (>= 1.38.0, < 2.0) ruby-progressbar (~> 1.7) unicode-display_width (>= 2.4.0, < 4.0) - rubocop-ast (1.38.0) + rubocop-ast (1.38.1) parser (>= 3.3.1.0) ruby-lsp (0.23.11) language_server-protocol (~> 3.17.0) From a9a7e0a9cb4ded37117b7c19df50afaab905805d Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Wed, 26 Feb 2025 09:52:41 +0100 Subject: [PATCH 5/6] update step to enable local wake word to reflect current SW (#37714) * update step to enable local wake word to reflect current SW - fixes #37593 * Fix typo --- source/voice_control/create_wake_word.markdown | 6 ++++-- source/voice_control/install_wake_word_add_on.markdown | 6 ++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/source/voice_control/create_wake_word.markdown b/source/voice_control/create_wake_word.markdown index ba44fb124d01..f7db21c5ce94 100644 --- a/source/voice_control/create_wake_word.markdown +++ b/source/voice_control/create_wake_word.markdown @@ -56,8 +56,10 @@ Enabling a wake word consists of 2 steps: - If the **Text-to-speech** and **Speech-to-text** sections do not provide language selectors, this means you do not have an Assist pipeline set up. - Set up [Home Assistant Cloud](https://www.nabucasa.com) or a manually configured [Assist pipeline](/voice_control/voice_remote_local_assistant). 5. Under **Text-to-speech**, select the language and voice you want Home Assistant to use when speaking to you. -6. To define the wake word engine, under **Wake word**, select **openwakeword**. - - Then, select **ok nabu**. +6. To define the wake word engine, in the top-right corner of the dialog, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Add streaming wake word**. + - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** integration is added. + - **Result**: on the bottom of the page, you now see a new section **Streaming wake word engine**. + - Select **openwakeword**, then select **ok nabu**. - If you created a new assistant, select **Create**. - If you edited an existing assistant, select **Update**. - **Result**: You now have a voice assistant that listens to a wake word. diff --git a/source/voice_control/install_wake_word_add_on.markdown b/source/voice_control/install_wake_word_add_on.markdown index fe8b3a327c73..e899d53e45f6 100644 --- a/source/voice_control/install_wake_word_add_on.markdown +++ b/source/voice_control/install_wake_word_add_on.markdown @@ -38,8 +38,10 @@ Enabling a wake word consists of 2 steps: - If the **Text-to-speech** and **Speech-to-text** sections do not provide language selectors, this means you do not have an Assist pipeline set up. - Set up [Home Assistant Cloud](https://www.nabucasa.com) or a manually configured [Assist pipeline](/voice_control/voice_remote_local_assistant). 5. Under **Text-to-speech**, select the language and voice you want Home Assistant to use when speaking to you. -6. To define the wake word engine, under **Wake word**, select **openwakeword**. - - Then, select **ok nabu**. +6. To define the wake word engine, in the top-right corner of the dialog, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Add streaming wake word**. + - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** integration is added. + - **Result**: on the bottom of the page, you now see a new section **Streaming wake word engine**. + - Select **openwakeword**, then select **ok nabu**. - If you created a new assistant, select **Create**. - If you edited an existing assistant, select **Update**. - **Result**: You now have a voice assistant that listens to a wake word. From e88ab4b674579a05182724727a6aab3dcab47802 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Wed, 26 Feb 2025 10:00:41 +0100 Subject: [PATCH 6/6] point out that openwakeword is part of Wyoming (#37716) --- source/voice_control/create_wake_word.markdown | 6 +++--- source/voice_control/install_wake_word_add_on.markdown | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/source/voice_control/create_wake_word.markdown b/source/voice_control/create_wake_word.markdown index f7db21c5ce94..326ab52201ee 100644 --- a/source/voice_control/create_wake_word.markdown +++ b/source/voice_control/create_wake_word.markdown @@ -41,9 +41,9 @@ Enabling a wake word consists of 2 steps: 1. Go to {% my supervisor_addon addon="core_openwakeword" title="**Settings** > **Add-ons** > **openWakeWord**" %} and select **Install**. 2. **Start** the add-on. 3. Go to {% my integrations title="**Settings** > **Devices & Services**" %}. - - Under **Discovered**, you should now see the **openWakeWord** integration. + - Under **Discovered**, you should now see the **openWakeWord** component of the **Wyoming** integration. - Select **Configure** and **Submit**. - - **Result**: You have successfully installed the **openWakeWord** add-on and Wyoming integration. + - **Result**: You have successfully installed the **openWakeWord** add-on and **Wyoming** integration. ### To enable wake word for your voice assistant @@ -57,7 +57,7 @@ Enabling a wake word consists of 2 steps: - Set up [Home Assistant Cloud](https://www.nabucasa.com) or a manually configured [Assist pipeline](/voice_control/voice_remote_local_assistant). 5. Under **Text-to-speech**, select the language and voice you want Home Assistant to use when speaking to you. 6. To define the wake word engine, in the top-right corner of the dialog, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Add streaming wake word**. - - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** integration is added. + - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** component of the **Wyoming** integration is added. - **Result**: on the bottom of the page, you now see a new section **Streaming wake word engine**. - Select **openwakeword**, then select **ok nabu**. - If you created a new assistant, select **Create**. diff --git a/source/voice_control/install_wake_word_add_on.markdown b/source/voice_control/install_wake_word_add_on.markdown index e899d53e45f6..593e0a083c92 100644 --- a/source/voice_control/install_wake_word_add_on.markdown +++ b/source/voice_control/install_wake_word_add_on.markdown @@ -23,7 +23,7 @@ Enabling a wake word consists of 2 steps: 1. Go to {% my supervisor_addon addon="core_openwakeword" title="**Settings** > **Add-ons** > **openWakeWord**" %} and select **Install**. 2. **Start** the add-on. 3. Go to {% my integrations title="**Settings** > **Devices & Services**" %}. - - Under **Discovered**, you should now see the **openWakeWord** integration. + - Under **Discovered**, you should now see the **openWakeWord** component of the **Wyoming** integration. - Select **Configure** and **Submit**. - **Result**: You have successfully installed the openWakeWord add-on and Wyoming integration. @@ -39,7 +39,7 @@ Enabling a wake word consists of 2 steps: - Set up [Home Assistant Cloud](https://www.nabucasa.com) or a manually configured [Assist pipeline](/voice_control/voice_remote_local_assistant). 5. Under **Text-to-speech**, select the language and voice you want Home Assistant to use when speaking to you. 6. To define the wake word engine, in the top-right corner of the dialog, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Add streaming wake word**. - - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** integration is added. + - **Troubleshooting**: If you don't see the three dots {% icon "mdi:dots-vertical" %} menu, go to {% my integrations title="**Settings** > **Devices & Services**" %} and make sure the **openWakeWord** component of the **Wyoming** integration is added. - **Result**: on the bottom of the page, you now see a new section **Streaming wake word engine**. - Select **openwakeword**, then select **ok nabu**. - If you created a new assistant, select **Create**.