diff --git a/Gemfile.lock b/Gemfile.lock index 3400e1f00ae..75755dbe683 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -109,7 +109,7 @@ GEM tilt (2.0.11) tzinfo (2.0.5) concurrent-ruby (~> 1.0) - tzinfo-data (1.2022.6) + tzinfo-data (1.2022.7) tzinfo (>= 1.0.0) unicode-display_width (2.3.0) webrick (1.7.0) diff --git a/source/_docs/automation/action.markdown b/source/_docs/automation/action.markdown index 74ccbe6f9e7..d1ca5057684 100644 --- a/source/_docs/automation/action.markdown +++ b/source/_docs/automation/action.markdown @@ -7,6 +7,8 @@ The action of an automation rule is what is being executed when a rule fires. Th You can also call the service to activate [a scene](/integrations/scene/) which will allow you to define how you want your devices to be and have Home Assistant call the right services. +{% raw %} + ```yaml automation: # Change the light in the kitchen and living room to 150 brightness and color red. @@ -42,6 +44,8 @@ automation 2: message: "Oh wow you really missed something great." ``` +{% endraw %} + Conditions can also be part of an action. You can combine multiple service calls and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any service calls after that condition will not be executed. ```yaml diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html index fcdf3f5da32..2bd4e9ff98c 100644 --- a/source/_includes/asides/component_navigation.html +++ b/source/_includes/asides/component_navigation.html @@ -35,7 +35,7 @@ The {{ page.title | default: page.name }} brand was introduced in Home Assistant {{ page.ha_release | default: "unknown" }}. {%- else -%} The {{ page.title | default: page.name }} {{ page.ha_integration_type | default: "integration" }} was introduced in Home Assistant {{ page.ha_release | default: "unknown" }}, - and it's used by + and it's used by {% if percentage < 1 %} {{ active_installations }} active installations. diff --git a/source/_integrations/frontier_silicon.markdown b/source/_integrations/frontier_silicon.markdown index d510f891e0a..eed3d21811d 100644 --- a/source/_integrations/frontier_silicon.markdown +++ b/source/_integrations/frontier_silicon.markdown @@ -16,7 +16,7 @@ ha_codeowners: This integration provides support for Internet Radios based on the [Frontier Silicon chipset]. Some of the manufacturers which offer products based on these chips include: Hama, Medion, Slivercrest, Auna, Technisat, Revo, Pinnel, etc. These devices will be usually controlled by the [UNDOK] app. ## Supported Models -* Hama: [IR110], [DIR3110] +* Hama: [IR50], [IR110], [DIR3110] * Medion: [Medion Radios] * Silvercrest: [SIRD 14 C2 (archived website)] * Teufel: [Radio 3sixty (2019)] @@ -107,6 +107,7 @@ The Frontier Silicon API does not provide a multi-user environment. There is alw [Frontier Silicon chipset]: https://www.frontiersmart.com/solution/solutions-for-digital-radio/ [Medion Radios]: https://www.medion.com/de/shop/internetradios +[IR50]: https://support.hama.com/00054840/hama-internetradio-ir50-wifi [IR110]: https://www.hama.com/00054823/hama-ir110ms-internet-radio-multiroom-app-control-black [DIR3110]: https://www.hama.com/00054824/hama-dir3110ms-digital-radio-fm-dab-dab+-internet-radio-app-multiroom-white [MD 87466]: https://www.conrad.com/p/medion-p83302-md-87466-internet-kitchen-radio-dab-fm-aux-internet-radio-dlna-compatible-white-1434428 diff --git a/source/_integrations/intellifire.markdown b/source/_integrations/intellifire.markdown index 4cc15c34a69..005fb57eaea 100644 --- a/source/_integrations/intellifire.markdown +++ b/source/_integrations/intellifire.markdown @@ -45,7 +45,13 @@ The following controllable entities are available: ### Fan -- **Fan** - If your unit is equipped with a fan - this entry will be present. There are 4 fan speeds (1-4), with 0 being off. +If your unit is equipped with a fan - this entry will be present. There are 5 possible fan control values: + +- `0%` - Off +- `25%` - Quiet +- `50%` - Low +- `75%` - Medium +- `100%` - High ### Climate diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 60d4b67b361..21ea29784ce 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -589,7 +589,7 @@ knx: `setpoint_shift_mode` allows the two following DPTs to be used: -- DPT6002 (for 1 byte signed integer) +- DPT6010 (for 1 byte signed integer with scale factor) - DPT9002 (for 2 byte float) Example: @@ -644,7 +644,7 @@ temperature_address: required: true type: [string, list] temperature_step: - description: Defines the step size in Kelvin for each step of setpoint_shift. + description: Defines the step size in Kelvin for each step of setpoint_shift (scale factor). For non setpoint-shift configurations this is used to set the step of temperature sliders in UI. required: false type: float default: 0.1 diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown index a659fd9e421..b0bc113b640 100644 --- a/source/_integrations/mqtt.markdown +++ b/source/_integrations/mqtt.markdown @@ -637,10 +637,13 @@ For most platforms it is also possible to manual set up MQTT items in `configura - [Siren](/integrations/siren.mqtt/) - [Switch](/integrations/switch.mqtt/) - [Text](/integrations/text.mqtt/) +- [Update](/integrations/update.mqtt/) - [Vacuum](/integrations/vacuum.mqtt/) {% enddetails %} +If you have a lot of manual configured items you might want to consider [splitting up the configuration](/docs/configuration/splitting_configuration/). + ## Using Templates The MQTT platform support templating. Read more [about using templates with the MQTT integration](/docs/configuration/templating/#using-templates-with-the-mqtt-integration). diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown index d5655509e6e..c1b13634a2f 100644 --- a/source/_integrations/nest.markdown +++ b/source/_integrations/nest.markdown @@ -289,7 +289,7 @@ All cameras have motion and person triggers, however only some support capturing | Nest Cam with floodlight | WebRTC | Motion
Person | N/A | | Nest Doorbell (battery) | WebRTC | Motion
Person
Chime | Clip Preview (mp4, gif) | | Nest Doorbell (wired) | RTSP
Recording | Motion
Person
Sound
Chime | Snapshot (jpg) | -| Nest Hub Max | RTSP
Recording | Motion
Person
Sound
* [SDM API known issue](https://github.com/home-assistant/core/issues/58482) | Snapshot (jpg) | +| Nest Hub Max | RTSP
Recording | Motion
Person
Sound
| Snapshot (jpg) | Given a camera named `Front Yard` then the camera is created with a name such as `camera.front_yard`. diff --git a/source/_integrations/sql.markdown b/source/_integrations/sql.markdown index 02d301b42ad..59e453c34fd 100644 --- a/source/_integrations/sql.markdown +++ b/source/_integrations/sql.markdown @@ -95,6 +95,12 @@ Use the same Database URL as for the `recorder` integration. Change `DB_NAME` to Example Database URL: `"mssql+pyodbc://username:password@SERVER_IP:1433/DB_NAME?charset=utf8&driver=FreeTDS"` +
+Connecting with MSSQL requires "pyodbc" to be installed on your system, which can only be done on systems using the Home Assistant Core installation type to be able to install the necessary dependencies. + +"pyodbc" has special requirements which need to be pre-installed before installation, see the ["pyodbc" wiki](https://github.com/mkleehammer/pyodbc/wiki/Install) for installation instructions +
+ ```sql SELECT TOP 1 SUM(m.size) * 8 / 1024 as size FROM sys.master_files m INNER JOIN sys.databases d ON d.database_id=m.database_id WHERE d.name='DB_NAME'; ```