From fddce93b9c679a79029faf8a0f7687dfd9a81cf8 Mon Sep 17 00:00:00 2001 From: Jeremy Pack Date: Thu, 22 Dec 2022 19:14:22 +0000 Subject: [PATCH 1/9] Correct typos and gramma (#25308) Co-authored-by: Franck Nijhof --- source/_integrations/python_script.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_integrations/python_script.markdown b/source/_integrations/python_script.markdown index fef340fd7fa..5ba43f72de0 100644 --- a/source/_integrations/python_script.markdown +++ b/source/_integrations/python_script.markdown @@ -37,15 +37,15 @@ It is not possible to use Python imports with this integration. If you want to d This is a simplified example that does no real work. It is created as a first step, to help with: -- Demonstrate how to setup the script +- Demonstrating how to setup the script - How to process the input data - How to log the script activity - How to troubleshoot / manually call the script. -Start by enabling the Python script and create the first script. +Start by enabling the Python Scripts integration and create the first script. - Add to `configuration.yaml`: `python_script:` -- Create folder `/python_scripts` +- Create the folder `/python_scripts` - Create a file `/python_scripts/hello_world.py` in the folder and give it this content: ```python @@ -82,7 +82,7 @@ logger: The following example shows how to trigger a custom event over the `hass.bus`. This example uses the `hello_world.py` from the previous example. -Edit the file and the code listed below to the end of the file. +Edit the file adding the code listed below to the end of the file. There is no need to reload the configuration or restart Home Assistant. ```python From 0f71c73de916660f90250ff382292c9e94de1904 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Thu, 22 Dec 2022 21:32:37 +0100 Subject: [PATCH 2/9] Various improvements to Calendar integration page (#25382) --- source/_integrations/calendar.markdown | 127 +++++++++++++++---------- 1 file changed, 79 insertions(+), 48 deletions(-) diff --git a/source/_integrations/calendar.markdown b/source/_integrations/calendar.markdown index d84a0089ba9..ecafdee3080 100644 --- a/source/_integrations/calendar.markdown +++ b/source/_integrations/calendar.markdown @@ -10,23 +10,50 @@ ha_codeowners: ha_integration_type: entity --- -The calendar integration allows you to integrate your calendars into Home Assistant. Calendars are shown on the calendar dashboard, and can be used with automations. +The calendar integration provides calendar entities, allowing other integrations +to integrate calendars into Home Assistant. Calendars are shown on the calendar +dashboard and can be used with automations. -A calendar entity has state and attributes represent the next upcoming event (only). A calendar trigger is much more flexible, has fewer limitations, and is recommended for automations, instead of using the entity state. +A calendar entity has a state and attributes representing the next event (only). +A calendar trigger is much more flexible, has fewer limitations, and is +recommended for automations instead of using the entity state. + +
+ +Calendar entities are here to be consumed and provided by other integrations. + +This page, therefore, does not provide instructions on how to create calendar +entities. Please see the ["Calendar" category](/integrations/#calendar) on the +integrations page to find integration offering calendar entities. + +
+ +## Viewing and managing calendars + +Each calendar is represented as its own entity in Home Assistant and can be +viewed and managed on a calendar dashboard. You can find the calendar dashboard +in the main sidebar of your Home Assistant instance. + +Some calendar integrations allow Home Assistant to manage your calendars +directly from Home Assistant. In this case, you can add new events by clicking +the “Add event” button in the lower right corner of the calendar dashboard. ## Automation -Calendar [Triggers](/docs/automation/trigger) enable automation based on an event start or end. Review the [Automating Home Assistant](/getting-started/automation/) getting started guide on automations or the [Automation](/docs/automation/) documentation for full details. +Calendar [Triggers](/docs/automation/trigger) enable automation based on an +event's start or end. Review the [Automating Home Assistant](/getting-started/automation/) +getting started guide on automations or the [Automation](/docs/automation/) +documentation for full details. {% my automations badge %} ![Screenshot Trigger](/images/integrations/calendar/trigger.png) -An example of a calendar trigger in yaml: +An example of a calendar trigger in YAML: ```yaml automation: - trigger: + - trigger: - platform: calendar # Possible values: start, end event: start @@ -36,10 +63,14 @@ automation: offset: -00:15:00 ``` -Calendar triggers should not generally use automation mode `single` to ensure the trigger -can fire when multiple events start at the same time (e.g., use `queued` or `parallel` instead). Note that calendars are read once every 15 minutes. When testing, make sure you do not plan events less than 15 minutes away from the current time, or your trigger might not fire. +Calendar triggers should not generally use automation mode `single` to ensure +the trigger can fire when multiple events start at the same time (e.g., use +`queued` or `parallel` instead). Note that calendars are read once every 15 +minutes. When testing, make sure you do not plan events less than 15 minutes +away from the current time, or your trigger might not fire. -See [Automation Trigger Variables: Calendar](/docs/automation/templating/#calendar) for additional trigger data available for conditions or actions. +See [Automation Trigger Variables: Calendar](/docs/automation/templating/#calendar) +for additional trigger data available for conditions or actions. ### Automation Recipes @@ -48,26 +79,26 @@ Below are a few example ways you can use Calendar triggers. {% details "Example: Calendar Event Notification " %} This example automation consists of: -- For the calendar entity `calendar.personal` -- At the start of any calendar event -- Send a notification with the title and start time of the event -- Allowing multiple events starting at the same time + +- For the calendar entity `calendar.personal`. +- At the start of any calendar event. +- Send a notification with the title and start time of the event. +- Allowing multiple events starting at the same time. {% raw %} ```yaml automation: - alias: Calendar notification - trigger: - - platform: calendar - event: start - entity_id: calendar.personal - action: - - service: persistent_notification.create - data: - message: >- - Event {{ trigger.calendar_event.summary }} @ - {{ trigger.calendar_event.start }} - mode: queued + - alias: Calendar notification + trigger: + - platform: calendar + event: start + entity_id: calendar.personal + action: + - service: persistent_notification.create + data: + message: >- + Event {{ trigger.calendar_event.summary }} @ + {{ trigger.calendar_event.start }} ``` {% endraw %} @@ -76,34 +107,34 @@ automation: {% details "Example: Calendar Event Light Schedule " %} This example consists of: -- For the calendar entity ` calendar.device_automation` -- When event summary contains `Front Lights` -- Turn on and off light named `light.front` when the event starts and ends + +- For the calendar entity ` calendar.device_automation`. +- When event summary contains `Front Lights`. +- Turn on and off light named `light.front` when the event starts and ends. {% raw %} ```yaml automation: - alias: Front Light Schedule - trigger: - - platform: calendar - event: start - entity_id: calendar.device_automation - - platform: calendar - event: end - entity_id: calendar.device_automation - condition: - - condition: template - value_template: "{{ 'Front Lights' in trigger.calendar_event.summary }}" - action: - - if: - - "{{ trigger.event == 'start' }}" - then: - - service: light.turn_on - entity_id: light.front - else: - - service: light.turn_off - entity_id: light.front - mode: queued + - alias: Front Light Schedule + trigger: + - platform: calendar + event: start + entity_id: calendar.device_automation + - platform: calendar + event: end + entity_id: calendar.device_automation + condition: + - condition: template + value_template: "{{ 'Front Lights' in trigger.calendar_event.summary }}" + action: + - if: + - "{{ trigger.event == 'start' }}" + then: + - service: light.turn_on + entity_id: light.front + else: + - service: light.turn_off + entity_id: light.front ``` {% endraw %} From 511bdd63bcff9f276fa1fa5e83a3db6897e8211d Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Fri, 23 Dec 2022 12:52:25 +0100 Subject: [PATCH 3/9] Bump racc from 1.6.1 to 1.6.2 (#25392) 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 585a9dd12cc..026ab82d4b9 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -81,7 +81,7 @@ GEM pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (5.0.1) - racc (1.6.1) + racc (1.6.2) rack (2.2.4) rack-protection (3.0.5) rack From d4e59d3ca4892f6af30dcda728e6d3377b498e7b Mon Sep 17 00:00:00 2001 From: Matrix Date: Tue, 27 Dec 2022 15:25:24 +0800 Subject: [PATCH 4/9] Update support devices list (#25406) --- source/_integrations/yolink.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/yolink.markdown b/source/_integrations/yolink.markdown index 88caec2f5ad..fd6f8328f67 100644 --- a/source/_integrations/yolink.markdown +++ b/source/_integrations/yolink.markdown @@ -41,7 +41,7 @@ The integration is tested and verified for the following devices from YoLink: * YS6602/4 YS6704 (outlet | plug) * YS7103/4/5 (siren) -* YS7704 (door sensor) +* YS7704/7705/7706 (door sensor) * YS7707 (Contact Sensor) * YS7804/5 (motion sensor) * YS7903/4 (leak sensor) @@ -52,6 +52,6 @@ The integration is tested and verified for the following devices from YoLink: * YS5705/6 (switch) * YS7A01/2 (CO & Smoke Sensor) * YS4002/3 (Thermostat) -* YS4906/8 YS7706 (Garage Door Sensor/ Garage Door Controller) +* YS4906/8 (Garage Door Sensor/ Garage Door Controller) * YS5707 (Dimmer) * YS6801/2 (MultiOutlet) From 184add960c825e7b7196a9d50b1c9848dbed07ff Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 27 Dec 2022 08:27:23 +0100 Subject: [PATCH 5/9] Bump mini_portile2 from 2.8.0 to 2.8.1 (#25407) 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 026ab82d4b9..eeed5096307 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -69,7 +69,7 @@ GEM rb-fsevent (~> 0.10, >= 0.10.3) rb-inotify (~> 0.9, >= 0.9.10) mercenary (0.4.0) - mini_portile2 (2.8.0) + mini_portile2 (2.8.1) multi_json (1.15.0) mustermann (3.0.0) ruby2_keywords (~> 0.0.1) From b956e682708f0c881a3be7436e70b23a006ded91 Mon Sep 17 00:00:00 2001 From: pvmil Date: Tue, 27 Dec 2022 08:40:03 +0100 Subject: [PATCH 6/9] Add Home Assistant SkyConnect as compatible device (#25395) Co-authored-by: Franck Nijhof --- source/_integrations/zha.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 4b10ffe2c06..d973f9e9cf4 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -83,6 +83,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl - [RaspBee II (a.k.a. RaspBee 2) Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee2) - [RaspBee Raspberry Pi Shield from dresden elektronik](https://phoscon.de/raspbee) - Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy) + - [Home Assistant SkyConnect](/skyconnect/) - [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/) - [ITead Sonoff ZBBridge](https://itead.cc/product/sonoff-zbbridge/) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first have to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html)) - [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/walthowd/husbzb-firmware)) From 1f5af06d81fe8bb79deeae11c5fd7426bd5258e8 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 26 Dec 2022 21:58:00 -1000 Subject: [PATCH 7/9] Add Yale Conexis L2 to august (#25400) --- source/_integrations/august.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/august.markdown b/source/_integrations/august.markdown index 1e8db269dc9..90efcdb2ca6 100644 --- a/source/_integrations/august.markdown +++ b/source/_integrations/august.markdown @@ -42,6 +42,7 @@ The `august` integration allows you to integrate your [August](https://august.co | Yale Assure Lock | yes | | Yale Assure Lock 2 | yes | | Yale Conexis L1 | yes | +| Yale Conexis L2 | yes | | Yale Linus | yes | There is currently support for the following device types within Home Assistant: From f0c5b857a8e1459408c5843803684869d185aa1e Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 26 Dec 2022 21:58:22 -1000 Subject: [PATCH 8/9] Add Yale Conexis L2 to Yale Access Bluetooth (#25399) --- source/_integrations/yalexs_ble.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/yalexs_ble.markdown b/source/_integrations/yalexs_ble.markdown index 5c5d5796bcf..3234199e14a 100644 --- a/source/_integrations/yalexs_ble.markdown +++ b/source/_integrations/yalexs_ble.markdown @@ -44,7 +44,7 @@ Devices must have a Yale Access module installed to function with this integrati These devices do not send updates, but can be locked and unlocked. -- MD-04I (Yale Conexis L1) +- MD-04I (Yale Conexis L1, Yale Conexis L2) - YRCB-490 (Yale Smart Cabinet Lock) ## Push updates From 7256ce0f52ed39c5985a3a6cb658cebaacdb6a3e Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 27 Dec 2022 09:06:30 +0100 Subject: [PATCH 9/9] Bump rack from 2.2.4 to 2.2.5 (#25414) 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 eeed5096307..fe932d6e589 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -82,7 +82,7 @@ GEM forwardable-extended (~> 2.6) public_suffix (5.0.1) racc (1.6.2) - rack (2.2.4) + rack (2.2.5) rack-protection (3.0.5) rack rake (13.0.6)