From 4556da86b0aaa5905008ade7aa85465297df6bd2 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 16 Jun 2020 14:53:30 +0200 Subject: [PATCH 01/16] Fix warning note on KNX page (#13776) --- source/_integrations/knx.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index 85bf1ac0aab..95d3beb9a07 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -15,7 +15,9 @@ The [KNX](https://www.knx.org) integration for Home Assistant allows you to conn The integration requires a local KNX/IP interface or router. Through this, it will establish a connection between Home Assistant and your KNX bus.
+ Please note, the `knx` platform does not support KNX Secure. +
There is currently support for the following device types within Home Assistant: From 6ef398044133d2cb29a9b0d86cbbb3c6c3149246 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 16 Jun 2020 10:18:13 -0700 Subject: [PATCH 02/16] Release 111.3 --- _config.yml | 4 +-- source/_posts/2020-06-10-release-111.markdown | 26 +++++++++++++++++++ 2 files changed, 28 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index 6d527adc531..a271a7361bb 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 111 -current_patch_version: 2 -date_released: 2020-06-13 +current_patch_version: 3 +date_released: 2020-06-15 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index cb5403f26bb..d066321d397 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -398,6 +398,32 @@ The integrations below have been removed: [powerwall docs]: /integrations/powerwall/ [xiaomi_miio docs]: /integrations/xiaomi_miio/ +## Release 0.111.3 - June 16 + +- Upgrade wled 0.4.3 ([@frenck] - [#36760]) +- Fix history graphs with mysql/mariadb ([@bdraco] - [#36769]) +- Fix nanoleaf attribute when running an effect ([@N1c093] - [#36794]) +- Bump ZHA quirks to 0.0.40 ([@dmulcahey] - [#36797]) +- Fix X10 devices and adding default links ([@teharris1] - [#36807]) +- Fire config changed event during start ([@balloob] - [#36812]) +- Bump aioasuswrt to 1.2.6 ([@kennedyshead] - [#36820]) +- Fix cloudhooks coming in for non existing webhooks ([@balloob] - [#36836]) + +[@bdraco]: https://github.com/bdraco +[@N1c093]: https://github.com/N1c093 +[@dmulcahey]: https://github.com/dmulcahey +[@teharris1]: https://github.com/teharris1 +[@balloob]: https://github.com/balloob +[@kennedyshead]: https://github.com/kennedyshead +[#36760]: https://github.com/home-assistant/pull/36760 +[#36769]: https://github.com/home-assistant/pull/36769 +[#36794]: https://github.com/home-assistant/pull/36794 +[#36797]: https://github.com/home-assistant/pull/36797 +[#36807]: https://github.com/home-assistant/pull/36807 +[#36812]: https://github.com/home-assistant/pull/36812 +[#36820]: https://github.com/home-assistant/pull/36820 +[#36836]: https://github.com/home-assistant/pull/36836 + ## All changes
From 76c976a1c00b781f9a7302f5cb131625357802db Mon Sep 17 00:00:00 2001 From: Alex van den Hoogen Date: Wed, 17 Jun 2020 16:32:05 +0200 Subject: [PATCH 03/16] Fix links to merge requests in release 0.111.3 (#13780) --- source/_posts/2020-06-10-release-111.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index d066321d397..779b84f8512 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -415,14 +415,14 @@ The integrations below have been removed: [@teharris1]: https://github.com/teharris1 [@balloob]: https://github.com/balloob [@kennedyshead]: https://github.com/kennedyshead -[#36760]: https://github.com/home-assistant/pull/36760 -[#36769]: https://github.com/home-assistant/pull/36769 -[#36794]: https://github.com/home-assistant/pull/36794 -[#36797]: https://github.com/home-assistant/pull/36797 -[#36807]: https://github.com/home-assistant/pull/36807 -[#36812]: https://github.com/home-assistant/pull/36812 -[#36820]: https://github.com/home-assistant/pull/36820 -[#36836]: https://github.com/home-assistant/pull/36836 +[#36760]: https://github.com/home-assistant/core/pull/36760 +[#36769]: https://github.com/home-assistant/core/pull/36769 +[#36794]: https://github.com/home-assistant/core/pull/36794 +[#36797]: https://github.com/home-assistant/core/pull/36797 +[#36807]: https://github.com/home-assistant/core/pull/36807 +[#36812]: https://github.com/home-assistant/core/pull/36812 +[#36820]: https://github.com/home-assistant/core/pull/36820 +[#36836]: https://github.com/home-assistant/core/pull/36836 ## All changes From 386acb0f6edbf68fda95579f5490c88b57160849 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 17 Jun 2020 13:42:43 -0700 Subject: [PATCH 04/16] Release 111.4 --- _config.yml | 4 +-- source/_posts/2020-06-10-release-111.markdown | 25 +++++++++++++++++++ 2 files changed, 27 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index a271a7361bb..d037ec86bbe 100644 --- a/_config.yml +++ b/_config.yml @@ -101,8 +101,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 111 -current_patch_version: 3 -date_released: 2020-06-15 +current_patch_version: 4 +date_released: 2020-06-17 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index 779b84f8512..6364bdcd0e9 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -424,6 +424,31 @@ The integrations below have been removed: [#36820]: https://github.com/home-assistant/core/pull/36820 [#36836]: https://github.com/home-assistant/core/pull/36836 +## Release 0.111.4 - June 17 + +- Fix llamalab_automate notify priority ([@fb22] - [#36845]) ([llamalab_automate docs]) +- Bump Axis dependency to fix issue where ports dont initialize ([@Kane610] - [#36860]) ([axis docs]) +- Fix Daikin zeroconf discovery flow error ([@fredrike] - [#36868]) ([daikin docs]) +- Upgrade pymetno ([@Danielhiversen], [@balloob] - [#36880]) ([met docs]) ([norway_air docs]) +- Fix yr HTTP error handling ([@pnbruckner] - [#36889]) + +[#36889]: https://github.com/home-assistant/core/pull/36889 +[#36845]: https://github.com/home-assistant/core/pull/36845 +[#36860]: https://github.com/home-assistant/core/pull/36860 +[#36868]: https://github.com/home-assistant/core/pull/36868 +[#36880]: https://github.com/home-assistant/core/pull/36880 +[@Kane610]: https://github.com/Kane610 +[@pnbruckner]: https://github.com/pnbruckner +[@Danielhiversen]: https://github.com/Danielhiversen +[@balloob]: https://github.com/balloob +[@fb22]: https://github.com/fb22 +[@fredrike]: https://github.com/fredrike +[axis docs]: /integrations/axis/ +[daikin docs]: /integrations/daikin/ +[llamalab_automate docs]: /integrations/llamalab_automate/ +[met docs]: /integrations/met/ +[norway_air docs]: /integrations/norway_air/ + ## All changes
From c483e6e4d8d9e060264714b857576e4f4060357b Mon Sep 17 00:00:00 2001 From: Daniel <44697375+azrael783@users.noreply.github.com> Date: Thu, 18 Jun 2020 15:59:37 +0200 Subject: [PATCH 05/16] Update utility_meter.markdown (#13782) Deleted unnecessary second "for" in line 166 --- source/_integrations/utility_meter.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown index 7673775e0e0..78358f48fd6 100644 --- a/source/_integrations/utility_meter.markdown +++ b/source/_integrations/utility_meter.markdown @@ -163,7 +163,7 @@ When using the [DSMR component](/integrations/dsmr) to get data from the utility If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors: - `sensor.energy_consumption_tarif_1` for tarif 1 power (for example off-peak) -- `sensor.energy_consumption_tarif_2` for for tarif 2 power (for example peak) +- `sensor.energy_consumption_tarif_2` for tarif 2 power (for example peak) - `sensor.gas_consumption` for gas consumption So, tracking daily and monthly consumption for each sensor, will require setting up 6 entries under the `utility_meter` component. From fa9e0bb5ddb392780df75fd95a0061ae5ee33540 Mon Sep 17 00:00:00 2001 From: Matthew Grimes <7375220+cybergrimes@users.noreply.github.com> Date: Thu, 18 Jun 2020 12:29:48 -0500 Subject: [PATCH 06/16] Correct ZEN21 version# (#13781) ZEN21 v2 hardware is not capable of same advanced configurations as v3 hardware. It also can not be updated to v3 firmware. I've also submitted change on OZW configs to reference the correct hardware. Manufacturer reference: https://www.support.getzooz.com/kb/article/300-zen21-on-off-switch-change-log/ --- source/_docs/z-wave/device-specific.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index 98be85125cf..dc0ac20212d 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -191,13 +191,13 @@ Triple tap on|2|4 5x tap off|1|6 5x tap on|2|6 -### Zooz Scene Capable On/Off and Dimmer Wall Switches (Zen21v2 & Zen22v2 - Firmware 3.0+, Zen26 & Zen27 - Firmware 2.0+, Zen30 Double Switch) +### Zooz Scene Capable On/Off and Dimmer Wall Switches (Zen21v3 & Zen22v2 - Firmware 3.0+, Zen26 & Zen27 - Firmware 2.0+, Zen30 Double Switch) Many Zooz switches that have been sold do not have the latest firmwares. Contact Zooz to obtain the over the air firmware update instructions and new user manual for the switches. Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch): -Zen21v2 (On/Off Switch): +Zen21v3 (On/Off Switch): ```xml From 0cfbd3665042d3d2b3e916f067ea691855e695c2 Mon Sep 17 00:00:00 2001 From: Thomas Dulle Date: Fri, 19 Jun 2020 01:04:36 +0200 Subject: [PATCH 07/16] Fixed link to recorder (#13790) --- source/_integrations/history.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/history.markdown b/source/_integrations/history.markdown index caf48cc0949..650c421c768 100644 --- a/source/_integrations/history.markdown +++ b/source/_integrations/history.markdown @@ -11,7 +11,7 @@ ha_domain: history --- The `history` integration will track everything that is going on within Home -Assistant and allows the user to browse through it. It depends on the [`recorder`](integrations/recorder/) +Assistant and allows the user to browse through it. It depends on the [`recorder`](/integrations/recorder/) integration for storing the data and uses the same database setting. If any entities are excluded from being recorded, no history will be available for these entities. From 4e66a59d82e06e2a54971a7fecdea60a639fc78c Mon Sep 17 00:00:00 2001 From: tiagofreire-pt <41837236+tiagofreire-pt@users.noreply.github.com> Date: Fri, 19 Jun 2020 00:05:18 +0100 Subject: [PATCH 08/16] EA8300 is supported by integration Linksys (#13788) * EA8300 is supported by this integration * :pencil2: Tweak Co-authored-by: Franck Nijhof --- source/_integrations/linksys_smart.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/linksys_smart.markdown b/source/_integrations/linksys_smart.markdown index 8f6835d4bb0..ad8d3a5aaa1 100644 --- a/source/_integrations/linksys_smart.markdown +++ b/source/_integrations/linksys_smart.markdown @@ -13,6 +13,7 @@ Tested routers: - Linksys WRT3200ACM MU-MIMO Gigabit Wi-Fi Wireless Router - Linksys WRT1900ACS Dual-band Wi-Fi Router +- Linksys EA8300 Max-Stream AC2200 Tri-Band Wi-Fi Router ## Setup From 3af4ca7e5d0d21c6da5ea403532ce8fb25c6c6f2 Mon Sep 17 00:00:00 2001 From: rccoleman Date: Fri, 19 Jun 2020 05:42:01 -0700 Subject: [PATCH 09/16] Sensors with units are excluded (#13789) Co-authored-by: Franck Nijhof --- source/_integrations/logbook.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/logbook.markdown b/source/_integrations/logbook.markdown index 69c0dafe39d..30fb4655693 100644 --- a/source/_integrations/logbook.markdown +++ b/source/_integrations/logbook.markdown @@ -131,3 +131,9 @@ script: entity_id: light.kitchen domain: light ``` + +
+ +Sensor entities that have been assigned units (i.e., have a `unit_of_measurement` attribute) are assumed to change frequently and those sensors are automatically excluded from the logbook. + +
From 91f4fde48df90396467c72d184da0cafcb8ed96b Mon Sep 17 00:00:00 2001 From: xorbital <53773184+xorbital@users.noreply.github.com> Date: Fri, 19 Jun 2020 19:25:39 +0200 Subject: [PATCH 10/16] "Https:" to "https:" on Nextcloud Integration (#13792) Every other site uses "https:" instead of "Https:", I guess it's just a typo --- source/_integrations/nextcloud.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/nextcloud.markdown b/source/_integrations/nextcloud.markdown index 00aef931424..c079b31b476 100644 --- a/source/_integrations/nextcloud.markdown +++ b/source/_integrations/nextcloud.markdown @@ -27,7 +27,7 @@ To enable the Nextcloud integration, add the following lines to your `configurat ```yaml # Example configuration.yaml entry nextcloud: - url: Https://YOUR_NEXTCLOUD_URL + url: https://YOUR_NEXTCLOUD_URL username: YOUR_USERNAME password: YOUR_APP_PASSWORD From 4b3653016bd796e1de632fe90a43aed1eef92d8c Mon Sep 17 00:00:00 2001 From: Villhellm Date: Fri, 19 Jun 2020 11:21:32 -0700 Subject: [PATCH 11/16] fixed example formatting for Blink (#13796) --- source/_integrations/blink.markdown | 59 ++++++++++++++--------------- 1 file changed, 29 insertions(+), 30 deletions(-) diff --git a/source/_integrations/blink.markdown b/source/_integrations/blink.markdown index f737973099b..0ae9e9fff13 100644 --- a/source/_integrations/blink.markdown +++ b/source/_integrations/blink.markdown @@ -105,10 +105,9 @@ Save the last recorded video of a camera to a local file. Note that in most case ```yaml homeassistant: - ... - whitelist_external_dirs: - - '/tmp' - - '/path/to/whitelist' + whitelist_external_dirs: + - '/tmp' + - '/path/to/whitelist' ``` ### `blink.send_pin` @@ -135,15 +134,15 @@ This example script shows how to take a picture with your camera, named `My Came ```yaml alias: Blink Snap Picture sequence: - - service: blink.trigger_camera - data: - entity_id: camera.blink_my_camera - - delay: 00:00:05 - - service: blink.blink_update - - service: camera.snapshot - data: - entity_id: camera.blink_my_camera - filename: /tmp/my_image.jpg + - service: blink.trigger_camera + data: + entity_id: camera.blink_my_camera + - delay: 00:00:05 + - service: blink.blink_update + - service: camera.snapshot + data: + entity_id: camera.blink_my_camera + filename: /tmp/my_image.jpg ``` ### Arm Blink When Away @@ -156,12 +155,12 @@ Here, this example assumes your blink module is named `My Sync Module` and that - id: arm_blink_when_away alias: Arm Blink When Away trigger: - platform: state - entity_id: all - to: 'not_home' + platform: state + entity_id: all + to: 'not_home' action: - service: alarm_control_panel.alarm_arm_away - entity_id: alarm_control_panel.blink_my_sync_module + service: alarm_control_panel.alarm_arm_away + entity_id: alarm_control_panel.blink_my_sync_module ``` ### Disarm Blink When Home @@ -172,12 +171,12 @@ Similar to the previous example, this automation will disarm blink when arriving - id: disarm_blink_when_home alias: Disarm Blink When Home trigger: - platform: state - entity_id: all - to: 'home' + platform: state + entity_id: all + to: 'home' action: - service: alarm_control_panel.alarm_disarm - entity_id: alarm_control_panel.blink_my_sync_module + service: alarm_control_panel.alarm_disarm + entity_id: alarm_control_panel.blink_my_sync_module ``` ### Save Video Locally When Motion Detected @@ -191,14 +190,14 @@ Again, this example assumes your camera's name (in the blink app) is `My Camera` - id: save_blink_video_on_motion alias: Save Blink Video on Motion trigger: - platform: state - entity_id: binary_sensor.blink_my_camera_motion_detected - to: 'on' + platform: state + entity_id: binary_sensor.blink_my_camera_motion_detected + to: 'on' action: - service: blink.save_video - data_template: - name: "My Camera" - filename: "/tmp/videos/blink_video_{{ now().strftime('%Y%m%d_%H%M%S') }}.mp4" + service: blink.save_video + data_template: + name: "My Camera" + filename: "/tmp/videos/blink_video_{{ now().strftime('%Y%m%d_%H%M%S') }}.mp4" ``` {% endraw %} From 2cd47064f3b74fd8546869edf34d66244cdb96b9 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Fri, 19 Jun 2020 19:22:55 +0100 Subject: [PATCH 12/16] Fixing indenting and trap (#13795) There's four spaces per level, rather than the two we use everywhere else. Also `...` has tripped up _so many_ people. From e8aa6c406d7b9a277dc4efb029fddc78c783f7ce Mon Sep 17 00:00:00 2001 From: Anton Averkiev Date: Sun, 21 Jun 2020 23:38:43 +0300 Subject: [PATCH 13/16] Update weather-forecast.markdown (#13803) --- source/_lovelace/weather-forecast.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_lovelace/weather-forecast.markdown b/source/_lovelace/weather-forecast.markdown index 6091f5b2e8b..7209fa454e5 100644 --- a/source/_lovelace/weather-forecast.markdown +++ b/source/_lovelace/weather-forecast.markdown @@ -109,5 +109,5 @@ Weather icons can be overwritten with your own personal images via a [Theme](htt Example theme configuration: ```yaml ---weather-icon-sunny: url("local/sunny.png") +--weather-icon-sunny: url("/local/sunny.png") ``` From 8f0b2f9ac0c915ee069aad215fc6c6ccd14769e3 Mon Sep 17 00:00:00 2001 From: libots <989623+libots@users.noreply.github.com> Date: Sun, 21 Jun 2020 17:12:51 -0400 Subject: [PATCH 14/16] Typo fix (#13801) --- source/_integrations/proxmoxve.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/proxmoxve.markdown b/source/_integrations/proxmoxve.markdown index abb2f953c61..37c20743028 100644 --- a/source/_integrations/proxmoxve.markdown +++ b/source/_integrations/proxmoxve.markdown @@ -142,4 +142,4 @@ To apply the user and role just created, we need to give it permissions 4. Select "/" for the path 5. Select your Home Assistant user (`hass`) 6. Select the Home Assistant role (`home-assistant`) -7. Make sure `Propigate` is checked +7. Make sure `Propagate` is checked From a99f542fcd6faaf0c27822fa05090fb40e4af0d6 Mon Sep 17 00:00:00 2001 From: Jon Date: Mon, 22 Jun 2020 13:44:29 +0100 Subject: [PATCH 15/16] Added info re command line sensors being a breaking change (#13754) The fix for command line sensor was promoted as just a bugfix, whereas it is a breaking change. The workaround for the bug was to escape the quote with a backslash, and now the backslash is treated as a character and passed through. --- source/_posts/2020-06-10-release-111.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_posts/2020-06-10-release-111.markdown b/source/_posts/2020-06-10-release-111.markdown index 6364bdcd0e9..3e52fb5a0df 100644 --- a/source/_posts/2020-06-10-release-111.markdown +++ b/source/_posts/2020-06-10-release-111.markdown @@ -322,6 +322,13 @@ Experiencing issues introduced by this release? Please report them in our [issue Previously it was set after the action that was part of the trigger was done. ([@basnijholt] - [#35671]) ([automation docs]) + + **Command Line Sensors** + + The fix for command line sensors removing quotes with template breaks any sensors where the quote has been escaped using a backslash. + E.g. to work around the previous bug a quote could be added using \" and this must now be replaced with simply " + + (@shenxn - #35559) (command_line docs) ## Farewell to the following From 3a0a511e22fefea0971af1d729657d1e2efd6881 Mon Sep 17 00:00:00 2001 From: pakwan Date: Mon, 22 Jun 2020 14:59:06 +0200 Subject: [PATCH 16/16] Yeelight: Minimum brightness incorrect (#13216) The minimum brightness when using yeelight transitions is 1 and not 0. This can be seen in the python-yeelight docs (https://yeelight.readthedocs.io/en/stable/yeelight.html#flow-objects) on which this seems to be based. Entering 0 as brightness results in the following error on my machine: Unable to set scene: {'code': -5000, 'message': 'general error'} --- source/_integrations/yeelight.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/yeelight.markdown b/source/_integrations/yeelight.markdown index 105c300ae1e..91e93ffc265 100644 --- a/source/_integrations/yeelight.markdown +++ b/source/_integrations/yeelight.markdown @@ -266,9 +266,9 @@ Possible transitions are `RGBTransition`, `HSVTransition`, `TemperatureTransitio Where the array values are as per the following: -- RGBTransition: [red, green, blue, duration, brightness] with red / green / blue being an integer between 0 and 255, duration being in milliseconds (minimum of 50) and final brightness to transition to 0-100 (%). -- HSVTransition: [hue, saturation, duration, brightness] with hue being an integer between 0 and 359, saturation 0 -100, duration in milliseconds (minimum 50) and final brightness 0-100 (%). -- TemperatureTransition: [temp, duration, brightness] with temp being the final color temperature between 1700 and 6500, duration in milliseconds (minimum 50) and final brightness to transition to 0-100 (%). +- RGBTransition: [red, green, blue, duration, brightness] with red / green / blue being an integer between 0 and 255, duration being in milliseconds (minimum of 50) and final brightness to transition to 1-100 (%). +- HSVTransition: [hue, saturation, duration, brightness] with hue being an integer between 0 and 359, saturation 0 -100, duration in milliseconds (minimum 50) and final brightness 1-100 (%). +- TemperatureTransition: [temp, duration, brightness] with temp being the final color temperature between 1700 and 6500, duration in milliseconds (minimum 50) and final brightness to transition to 1-100 (%). - SleepTransition: [duration] with duration being in integer for effect time in milliseconds (minimum 50). More info about transitions and their expected parameters can be found in [python-yeelight documentation](https://yeelight.readthedocs.io/en/stable/flow.html).