diff --git a/Gemfile.lock b/Gemfile.lock index d692e942dcac..d53ceec1dc15 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -135,7 +135,7 @@ GEM rack-protection (= 4.0.0) rack-session (>= 2.0.0, < 3) tilt (~> 2.0) - sorbet-runtime (0.5.11367) + sorbet-runtime (0.5.11368) stringex (2.8.6) terminal-table (3.0.2) unicode-display_width (>= 1.1.1, < 3) diff --git a/source/_includes/common-tasks/filters.md b/source/_includes/common-tasks/filters.md index 9533bbc03cf4..aed41f62775e 100644 --- a/source/_includes/common-tasks/filters.md +++ b/source/_includes/common-tasks/filters.md @@ -32,4 +32,4 @@ Filters are applied as follows: The following characters can be used in entity globs: `*` - The asterisk represents zero, one, or multiple characters -`?` - The question mark represents a single character +`?` - The question mark represents zero or one character diff --git a/source/_includes/common-tasks/flashing_n2_otg.md b/source/_includes/common-tasks/flashing_n2_otg.md index d6f46f80d003..8a53895d93ea 100644 --- a/source/_includes/common-tasks/flashing_n2_otg.md +++ b/source/_includes/common-tasks/flashing_n2_otg.md @@ -72,9 +72,9 @@ This will configure the ODROID-N2+ and OTG to act as a memory card reader: - Make sure to toggle the boot mode switch back to MMC. 4. Put the ODROID back in its case. -5. Connect your ODROID-N2+ to your network with an Ethernet cable and plug in power. +5. Connect your ODROID-N2+ to your network with an Ethernet cable, make sure there is internet access, and plug in power. 6. If your router supports mDNS, you can reach your installation at `http://homeassistant.local:8123`. - - If your network doesn’t support mDNS, you’ll have to use the IP address of your ODROID-N2+ instead of `homeassistant.local`. For example, `http://192.168.0.9:8123`. + - If your network doesn’t support mDNS, you’ll have to use the IP address of your ODROID-N2+ instead of `homeassistant.local`. For example, `http://192.168.0.9:8123`. - You should be able to find the IP address of your ODROID-N2+ from the admin interface of your router. 7. Continue with [onboarding](/getting-started/onboarding/). \ No newline at end of file diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md index 53503a6e9c02..e9af36c2a5c5 100644 --- a/source/_includes/installation/operating_system.md +++ b/source/_includes/installation/operating_system.md @@ -227,7 +227,8 @@ Use this method only if Method 1 does not work for you. - If you used method 2 for the installation, install the boot medium into your x86-64 hardware. -1. Plug in an Ethernet cable that is connected to the network. +1. Plug in an Ethernet cable that is connected to the network and to the internet. + - Note: Internet is required because the newly installed Home Assistant OS does not contain all Home Assistant components yet. It downloads the latest version of Home Assistant Core on first start. 2. Power the system on. If you have a screen connected to the {{site.installation.types[page.installation_type].board}} system, after a minute or so the Home Assistant welcome banner will appear in the console.
@@ -254,7 +255,8 @@ Or else, the BIOS might provide you with a tool to add boot options, there you c {% else %} 1. Insert the boot medium ({{ site.installation.types[page.installation_type].installation_media }}) you just created. -2. Plug in an Ethernet cable that is connected to the network and power the system on. +2. Plug in an Ethernet cable that is connected to the network and to the internet and power the system on. + - Note: Internet is required because the newly installed Home Assistant OS does not contain all Home Assistant components yet. It downloads the latest version of Home Assistant Core on first start. {% endif %} diff --git a/source/_integrations/binary_sensor.rest.markdown b/source/_integrations/binary_sensor.rest.markdown index 10e9f358dd31..7be75ced4ac0 100644 --- a/source/_integrations/binary_sensor.rest.markdown +++ b/source/_integrations/binary_sensor.rest.markdown @@ -19,6 +19,9 @@ _Tip:_ If you want to create multiple `sensors` using the same endpoint, use the The JSON messages can contain different values like `1`, `"1"`, `TRUE`, `true`, `on`, or `open`. If the value is nested then use a [template](/docs/configuration/templating/#processing-incoming-data). +If the endpoint returns XML with the `text/xml`, `application/xml` or +`application/xhtml+xml` content type, it will automatically be converted +to JSON according to this [specification](https://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html). ```json { diff --git a/source/_integrations/husqvarna_automower.markdown b/source/_integrations/husqvarna_automower.markdown index 8e51bd69b23a..03b01a9cd832 100644 --- a/source/_integrations/husqvarna_automower.markdown +++ b/source/_integrations/husqvarna_automower.markdown @@ -113,7 +113,14 @@ The integration will create a lawn mower entity to control the mower. This entit ### Number (if available) -The integration will create a number entity for changing the cutting height of the mower. This entity is disabled by default. You have to enable it manually because it can't be detected with the API if the mower has the capability to change the cutting height remotely. Before enabling this function, consult the handbook of the mower. It's possible that you can use this entity only as sensor but cannot actively change the cutting height. +#### Cutting height + +The integration will create a number entity for changing the cutting height of the mower. This entity is disabled by default. You have to enable it manually. It can't be detected with the API if the mower has the capability to change the cutting height remotely. Before enabling this function, refer to the mower documentation. Depending on the mower, it is possible that you can use this entity only passively as a sensor and not actively to change the cutting height. +Possible values are 1 (grass stays short) to 9 (grass stays high). + +#### Cutting height for work areas + +The integration will create a number entity for changing the cutting height for each work area of the mower if your mower supports work areas. Possible values for the cutting heights are 0% (grass stays short) to 100% (grass stays high) of the default cutting height. Note: It's not yet possible to change the default cutting height with Home Assistant. ### Select (if available) diff --git a/source/_integrations/nina.markdown b/source/_integrations/nina.markdown index c2664f491135..988edfd8c706 100644 --- a/source/_integrations/nina.markdown +++ b/source/_integrations/nina.markdown @@ -20,7 +20,7 @@ For each county/city it creates warning slots that change to Unsafe when warning
-This integration may only works with an Internet connection that supports IPv4. +This integration may only work with an Internet connection that supports IPv4.
diff --git a/source/_integrations/python_script.markdown b/source/_integrations/python_script.markdown index 49069c5f9876..0bb9c2ff22df 100644 --- a/source/_integrations/python_script.markdown +++ b/source/_integrations/python_script.markdown @@ -129,7 +129,7 @@ The above `python_script` can be called using the following YAML as an input. rgb_color: [255, 0, 0] ``` -Services can also respond with data. Retrieving this data in your Python script can be done by setting the `blocking` and `return_response` arguments of the `hass.services.call` function to `True`. This is shown in the example below, in this case, retrieving the weather forecast and putting it into a variable: +Services can also respond with data. Retrieve this data in your Python script by setting the `blocking` and `return_response` arguments of the `hass.services.call` function to `True`. The example below retrieves the weather forecast and assigns it to the `current_forecast` variable: ```python # get_forecast.py diff --git a/source/_posts/2024-05-01-release-20245.markdown b/source/_posts/2024-05-01-release-20245.markdown index e274a17497ad..d566db2331f9 100644 --- a/source/_posts/2024-05-01-release-20245.markdown +++ b/source/_posts/2024-05-01-release-20245.markdown @@ -255,7 +255,7 @@ We welcome the following new {% term integrations %} in this release: - **[Arve]**, added by [@ikalnyi]
Monitor real-life air quality data from your Arve devices. - **[Energenie Power-Sockets]**, added by [@gnumpi]
- Control your Energie Power-Strips over USB. + Control your Energenie Power-Strips over USB. - **[Epic Games Store]**, added by [@Quentame]
Provides a calendar for the Epic Games Store to monitor discounts and free games. - **[eQ-3 Bluetooth Smart Thermostats]**, added by [@EuleMitKeule]
@@ -271,7 +271,7 @@ We welcome the following new {% term integrations %} in this release: [@tomaszsluszniak]: https://github.com/tomaszsluszniak [Ambient Weather Network]: /integrations/ambient_network [Arve]: /integrations/arve -[Energenie Power-Sockets]: /integratoins/egps +[Energenie Power-Sockets]: /integrations/energenie_power_sockets [Epic Games Store]: /integrations/epic_games_store [eQ-3 Bluetooth Smart Thermostats]: /integrations/eq3btsmart [Sanix]: /integrations/sanix