Merge branch 'current' into next

2025-07-19 15:26:59 +00:00 · 2024-06-25 14:58:44 +02:00 · 2024-06-25 14:58:44 +02:00 · 2a75ea93a0
commit 2a75ea93a0
parent d5ddced1ce d664bb9d80
9 changed files with 53 additions and 34 deletions
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@ -21,7 +21,6 @@
        "editorconfig.editorconfig",
        "GitHub.vscode-pull-request-github",
        "mrmlnc.vscode-scss",
-        "Shopify.ruby-lsp",
        "streetsidesoftware.code-spell-checker",
        "taichi.vscode-textlint",
        "yzhang.markdown-all-in-one"
--- a/Gemfile.lock
+++ b/Gemfile.lock
@ -1,8 +1,8 @@
 GEM
  remote: https://rubygems.org/
  specs:
-    addressable (2.8.6)
-      public_suffix (>= 2.0.2, < 6.0)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
    ast (2.4.2)
    base64 (0.2.0)
    bigdecimal (3.1.8)
@ -86,9 +86,9 @@ GEM
    pathutil (0.16.2)
      forwardable-extended (~> 2.6)
    prism (0.30.0)
-    public_suffix (5.1.1)
+    public_suffix (6.0.0)
    racc (1.8.0)
-    rack (3.1.3)
+    rack (3.1.4)
    rack-protection (4.0.0)
      base64 (>= 0.1.0)
      rack (>= 3.0.0, < 4)
@ -105,7 +105,7 @@ GEM
    rbs (3.5.1)
      logger
    regexp_parser (2.9.2)
-    rexml (3.3.0)
+    rexml (3.3.1)
      strscan
    rouge (4.3.0)
    rubocop (1.64.1)
@ -142,7 +142,7 @@ GEM
      rack-protection (= 4.0.0)
      rack-session (>= 2.0.0, < 3)
      tilt (~> 2.0)
-    sorbet-runtime (0.5.11439)
+    sorbet-runtime (0.5.11444)
    stringex (2.8.6)
    strscan (3.1.0)
    terminal-table (3.0.2)
--- a/source/_integrations/http.markdown
+++ b/source/_integrations/http.markdown
@ -86,11 +86,6 @@ ssl_profile:
  required: false
  type: string
  default: modern
-strict_connection:
-  description: Specifies the strict connection mode. Please read the section ["Strict connection mode"](#strict-connection-mode) before changing this value. Can be one of `disabled`, `guard_page` or `drop_connection`.
-  required: false
-  type: string
-  default: disabled
 {% endconfiguration %}

 The sample below shows a configuration entry with possible values:
--- a/source/_integrations/jewish_calendar.markdown
+++ b/source/_integrations/jewish_calendar.markdown
@ -47,9 +47,9 @@ Allows you to override the default location information provided by Home Assista
 ### Data sensors

 - `date`: Shows the hebrew date for today.
- `weekly_portion`: Shows the weekly portion (parshat hashavu'a - פרשת השבוע)
+- `parshat_hashavua`: Shows the weekly portion (parshat hashavu'a - פרשת השבוע)
 - `holiday`: If it is a holiday, shows the name of the holiday _(see below for more info)_.
- `omer_count`: An integer sensor indicating the day of the Omer (1-49) or 0 if it is not currently the Omer.
+- `day_of_the_omer`: An integer sensor indicating the day of the Omer (1-49) or 0 if it is not currently the Omer.
 - `daf_yomi`: Shows the date's daf yomi page.

 ### Time sensors
@ -58,20 +58,19 @@ Allows you to override the default location information provided by Home Assista

 Time sensor states are represented as ISO8601 formatted *UTC time*.

- `first_light`: First light of dawn (Alot Hashachar - עלות השחר)
- `talit`: Earliest time for tallit and tefillin (Misheyakir - משיכיר)
- `sunrise`: Earliest time for Shacharit (Hanetz Hachama - הנץ החמה)
- `gra_end_shma`: Last time for the reading of the Shma according to the Gr"a.
- `mga_end_shma`: Last time for the reading of the Shma according to the MG"A.
- `gra_end_tefilla`: Last time for full shacharit according to the Gr"a.
- `mga_end_tefilla`: Last time for full shacharit according to the MG"A.
- `midday`: Half way through the day (Chatzot Hayom - חצות היום)
- `big_mincha`: Earliest time for Mincha (Mincha Gedola - מנחה גדולה)
- `little_mincha`: Preferable earliest time for Mincha (Mincha Ketana - מנחה קטנה)
- `plag_mincha`: Time of the Plag Hamincha (פלג המנחה)
- `sunset`: Sunset (Shkiya - שקיעה)
- `first_stars`: Time at which the first stars are visible (Tseit Hakochavim - צאת הכוכבים)
- `t_set_hakochavim_three_stars`: Time at which the first three stars are visible (Tseit Hakochavim - צאת הכוכבים - for Shabbat and Yom Tov) 
+- `alot_hashachar`: First light of dawn (Alot Hashachar - עלות השחר)
+- `talit_and_tefillin`: Earliest time for tallit and tefillin (Misheyakir - משיכיר)
+- `hanetz_hachama`: Earliest time for Shacharit (Hanetz Hachama - הנץ החמה)
+- `latest_time_for_shma_gr_a`: Last time for the reading of the Shma according to the Gr"a.
+- `latest_time_for_shma_mg_a`: Last time for the reading of the Shma according to the MG"A.
+- `latest_time_for_tefilla_gr_a`: Last time for full shacharit according to the Gr"a.
+- `latest_time_for_tefilla_mg_a`: Last time for full shacharit according to the MG"A.
+- `chatzot_hayom`: Half way through the day (Chatzot Hayom - חצות היום)
+- `mincha_gedola`: Earliest time for Mincha (Mincha Gedola - מנחה גדולה)
+- `mincha_ketana`: Preferable earliest time for Mincha (Mincha Ketana - מנחה קטנה)
+- `plag_hamincha`: Time of the Plag Hamincha (פלג המנחה)
+- `shkia`: Sunset (Shkiya - שקיעה)
+- `t_set_hakochavim`: Time at which the first stars are visible (Tseit Hakochavim - צאת הכוכבים)
 - `upcoming_shabbat_candle_lighting`: The time of candle lighting for either the current Shabbat (if it is currently Shabbat) or the immediately upcoming Shabbat.
 - `upcoming_shabbat_havdalah`: The time of havdalah for either the current Shabbat (if it is currently Shabbat) or the immediately upcoming Shabbat. If it is currently a three-day holiday, this value *could* be None (i.e., if a holiday is Sat./Sun./Mon. and it's Saturday, there will be no `shabbat_havdalah` value. See comments in hdate library for details.)
 - `upcoming_candle_lighting`: The time of candle lighting for either the current Shabbat OR Yom Tov, or the immediately upcoming Shabbat OR Yom Tov. If, for example, today is Sunday, and Rosh Hashana is Monday night through Wednesday night, this reports the candle lighting for Rosh Hashana on Monday night. This avoids a situation of triggering pre-candle-lighting automations while it is currently Yom Tov. To always get the Shabbat times, use the `upcoming_shabbat_candle_lighting` sensor.
--- a/source/_integrations/prometheus.markdown
+++ b/source/_integrations/prometheus.markdown
@ -204,3 +204,9 @@ For example:
 - record: "known_temperature_c"
  expr: "temperature_c unless entity_available == 0"
 ```
+
+## Supported metrics
+
+Metrics are exported only for the following domains:
+
+`automation`, `binary_sensor`, `climate`, `cover`, `counter`, `device_tracker`, `fan`, `humidifier`, `input_boolean`, `input_number`, `light`, `lock`, `number`, `person`, `sensor`, `update`, `switch`
--- a/source/_integrations/roborock.markdown
+++ b/source/_integrations/roborock.markdown
@ -15,7 +15,6 @@ ha_iot_class: Local Polling
 ha_release: 2023.5
 ha_config_flow: true
 ha_codeowners:
-  - '@humbertogontijo'
  - '@Lash-L'
 ha_domain: roborock
 ha_platforms:
--- a/source/_integrations/unifiprotect.markdown
+++ b/source/_integrations/unifiprotect.markdown
@ -299,5 +299,5 @@ If you get errors while authenticating or fetching data for `NvrError... 404 - R
 Similarly, a `502 Bad Gateway` also means that your UniFi Protect application may not be running.

 ```log
-pyunifiprotect.NvrError: Fetching Camera List failed: 404 - Reason: Not Found
+uiprotect.NvrError: Fetching Camera List failed: 404 - Reason: Not Found
 ```
--- a/source/_integrations/verisure.markdown
+++ b/source/_integrations/verisure.markdown
@ -38,6 +38,8 @@ There is currently support for the following device types within Home Assistant:

 {% include integrations/config_flow.md %}

+{% include integrations/option_flow.md %}
+
 ## Alarm control panel

 The Verisure alarm control panel platform allows you to control your [Verisure](https://www.verisure.com/) Alarms.
@ -73,6 +75,10 @@ automation:
 | enable_autolock | Enables autolock function for a specific lock. |
 | smartcam_capture | Capture a new image from a specific smartcam. |

+## Binary sensor
+
+- Ethernet status
+
 ## Lock

 | method state attribute | Description |
@ -91,3 +97,7 @@ Some users have reported that this integration currently doesn't work in the fol
 - Ireland
 - Italy
 - Sweden
+
+## Troubleshooting
+
+If you get an error message stating something like *"The code for lock.XXX doesn't match pattern `^\d{0}$`."*, make sure the number of digits for your code matches the number defined in the [configuration options](#options).
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@ -133,12 +133,15 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
  - [ZiGate-Ethernet (Ethernet gateway board for PiZiGate)](https://zigate.fr/produit/zigate-ethernet/)
  - [ZiGate + WiFi Pack](https://zigate.fr/produit/zigatev2-pack-wifi/)

-#### Warning about Wi-Fi-based Zigbee-to-Serial bridges/gateways
+#### Warning about using Zigbee Coordinator over Wi-Fi/WAN/VPN

 <div class="note warning">

-The **EZSP** protocol requires a stable connection to the serial port. With _ITEAD Sonoff ZBBridge_ connecting over the WiFi network
-it is expected to see `NCP entered failed state. Requesting APP controller restart` in the logs. This is a normal part of the operation and indicates there was a drop in communication between ZHA and Sonoff bridge.
+Be aware that using a Zigbee Coordinator via a Serial-Proxy-Server (also known as Serial-to-IP bridge or Ser2Net remote adapter) over a Wi-Fi, WAN, or VPN connection is not recommended.
+
+Serial protocols used by the Zigbee Coordinator do not have enough robustness, resilience, or fault tolerance to handle packet loss and latency delays that can occur over unstable connections.
+
+A Zigbee Coordinator requires a stable local connection to its serial port interface with no drops in communication between it and the Zigbee gateway application running on the host computer.

 </div>

@ -724,3 +727,11 @@ services:
    restart: always
    network_mode: host
 ```
+
+### EZSP error and other log messages
+
+#### NCP entered failed state
+
+When you see `NCP entered failed state. Requesting APP controller restart` in logs during normal operation, it indicates a drop in communication between ZHA and the serial interface of the Silabs EmberZNet Zigbee Coordinator.
+
+The EZSP (EmberZNet Serial Protocol) interface used by Silicon Labs EmberZNet Zigbee Coordinator adapters requires a stable connection to the serial port; therefore, it is not recommended to use a connection over Wi-Fi, WAN, VPN, etc.