Merge branch 'current' into next

Author: jesserockz

content/automations/actions.md

@@ -232,7 +232,7 @@ At least one of `condition`, `all` or `any` must be provided.
 
 ### `lambda` Action
 
-This action executes an arbitrary piece of C++ code (see [Lambda](#config-lambda)).
+This action executes an arbitrary piece of C++ code (see [Lambda](/automations/templates#config-lambda)).
 
 ```yaml
 on_...:
@@ -480,7 +480,7 @@ on_...:
 
 ### `lambda` Condition
 
-This condition performs an arbitrary piece of C++ code (see [Lambda](#config-lambda))
+This condition performs an arbitrary piece of C++ code (see [Lambda](/automations/templates#config-lambda))
 and can be used to create conditional flow in actions.
 
 ```yaml

content/automations/templates.md

@@ -98,14 +98,14 @@ using the lambda syntax as described/shown above.
 
 ## All Lambda Calls
 
-- [Sensor](#sensor-lambda_calls)
-- [Binary Sensor](#binary_sensor-lambda_calls)
-- [Switch](#switch-lambda_calls)
-- [Display](#display-engine)
-- [Cover](#cover-lambda_calls)
-- [Text Sensor](#text_sensor-lambda_calls)
-- [Stepper](#stepper-lambda_calls)
-- [Number](#number-lambda_calls)
+- [Sensor](/components/sensor#sensor-lambda_calls)
+- [Binary Sensor](/components/binary_sensor#binary_sensor-lambda_calls)
+- [Switch](/components/switch#switch-lambda_calls)
+- [Display](/components/display#display-engine)
+- [Cover](/components/cover#cover-lambda_calls)
+- [Text Sensor](/components/text_sensor#text_sensor-lambda_calls)
+- [Stepper](/components/stepper#stepper-lambda_calls)
+- [Number](/components/number#number-lambda_calls)
 
 ## See Also
 

content/changelog/2021.10.0.md

@@ -69,7 +69,7 @@ native component is still better and preferred if it exists.
 ## Text Sensor filters
 
 `text_sensors` now have `filters` that allow you to do string manipulation before the value is
-given to the frontend. Check out the [docs here](#text_sensor-filters).
+given to the frontend. Check out the [docs here](/components/text_sensor#text_sensor-filters).
 
 ## Lighting
 
@@ -80,7 +80,7 @@ could build a "fake" addressable light from regular rgb leds.
 
 ## Graphs
 
-There is new [Graph](#display-graphs) building functions for displays that will allow you to
+There is new [Graph](/components/graph#display-graphs) building functions for displays that will allow you to
 draw the history of sensors over time. See the docs for examples and images on what this looks like.
 
 ## `wait_until`

content/changelog/2021.9.0.md

@@ -37,7 +37,7 @@ devices with encryption. This is scheduled to be available in Home Assistant 202
 
 ## Git Packages
 
-[Packages](#config-git_packages) have been extended to allow loading (multiple) YAML file(s) from a git repo.
+[Packages](/components/packages#config-git_packages) have been extended to allow loading (multiple) YAML file(s) from a git repo.
 Take a look at the examples to see how to use them.
 
 ## Midea AC

content/changelog/2022.4.0.md

@@ -50,7 +50,7 @@ flashing custom firmware to the stm32 via ESPHome which is required to use the c
 
 {{< ghuser name="OttoWinter" >}} has given everyone a way to use Google Fonts in their YAML and displays without
 having to manually download TTF font files. The example below will automatically download and cache the Roboto
-TTF font file required so you can utilise it. See the [Font Renderer Component](#display-fonts) documentation
+TTF font file required so you can utilise it. See the [Font Renderer Component](/components/font#display-fonts) documentation
 for more details.
 
 ```yaml

content/changelog/2024.10.0.md

@@ -26,14 +26,14 @@ grouping feature that allows for custom/user defined groups of entities.
 This is also a breaking change as the previous `web_server_sorting_weight` has been moved into a new
 `web_server` -> `sorting_weight` configuration entry for the entity.
 
-Please see [Entity sorting](#config-webserver-sorting) for the latest documentation on these features.
+Please see [Entity sorting](/components/web_server#config-webserver-sorting) for the latest documentation on these features.
 
 ## ESP32 Advanced MAC Address Configuration
 
 ESPHome now supports reading a custom MAC address from the ESP32 eFuse blocks and will read and use it by default if
 there is data burned into the eFuses. If you would like to disable this, or the eFuse has data burned that is not a
 MAC address into those eFuses, then you can add `ignore_efuse_custom_mac: true` to your ESP32 `advanced`
-configuration. See [ESP32 Advanced Configuration](#esp32-advanced_configuration) for more details.
+configuration. See [ESP32 Advanced Configuration](/components/esp32#esp32-advanced_configuration) for more details.
 
 ## CSE7766 Breaking Changes
 

content/changelog/2024.2.0.md

@@ -42,7 +42,7 @@ See the {{< docref "/components/sensor/bme280" "component documentation" >}} for
 
 {{< ghuser name="ssieb" >}} has changed the CSE7766 sensor from appearing to be a polling component.
 It has a high update rate, so if you don't want to send a lot of data to HA, you can
-add the [throttle_average](#sensor-filters) filter
+add the [throttle_average](/components/sensor#sensor-filters) filter
 with the time period you were using for the update interval (the default is 60s) to each
 sensor. The example in the sensor doc page has been updated to show this.
 

content/changelog/2025.2.0.md

@@ -42,7 +42,7 @@ your microcontroller/board.
 In this release, we've removed support for the "old style" of configuring your microcontroller/board. If you're still
 using it, you'll need to update your configurations to use the new style. A brief explanation is
 [in this pull request](https://github.com/esphome/esphome/pull/8118), but for more detail, please see the
-[documentation for your microcontroller platform](#devices).
+[documentation for your microcontroller platform](/components#devices).
 
 ## Removal of Custom Components
 

content/changelog/v1.10.0.md

@@ -123,7 +123,7 @@ in it, so it will take time until the next release for this to be finished.
 
 - You can now configured multiple WiFi networks to connect to. The best one will be chosen automatically.
   This is along with a *complete* rewrite of the WiFi component which now interacts directly with the ESP SDK.
-  ([Connecting to Multiple Networks](#wifi-networks))
+  ([Connecting to Multiple Networks](/components/wifi#wifi-networks))
 
 - GPIO Switches have a new option `restore_mode` to configure how their values should be restored on boot.
   ({{< docref "/components/switch/gpio" >}})

content/changelog/v1.12.0.md

@@ -21,7 +21,7 @@ It's release day! 🎉 Today I'm happy to release ESPHome 1.12.0. What's new? A
 stuff got added! Let me walk you through it:
 
 Before 1.12, it was only possible to transfer data from ESPHome to Home Assistant (with the
-`homeassistant.service` call). With 1.12 you get [User-defined services](#api-device-actions),
+`homeassistant.service` call). With 1.12 you get [User-defined services](/components/api#api-device-actions),
 just define a service in your ESPHome file and call it like any other service from HA. All the
 rest (like variables, data validation, etc) are handled automatically!
 
@@ -50,9 +50,9 @@ suggestions for validation errors) and bug fixes to make your life easier.
 ## Other notable changes
 
 - Added `calibrate_linear` sensor filter for easier calibration of sensors
-  ([sensor-filter-calibrate_linear](#sensor-filter-calibrate_linear))
+  ([sensor-filter-calibrate_linear](/components/sensor/filter/multiply#sensor-filter-calibrate_linear))
 
-- Added `for` parameter to [binary_sensor.is_on](#binary_sensor-is_on_condition) condition.
+- Added `for` parameter to [binary_sensor.is_on](/components/binary_sensor#binary_sensor-is_on_condition) condition.
 - Added `streamer_mode`, `status_use_ping` and `relative_url` options to the Hass.io addon
   (see addon description).