From c4e7c03587ea4c0353a64bb15191208a6cb66d64 Mon Sep 17 00:00:00 2001 From: Daniel Shokouhi Date: Sat, 18 Jan 2020 04:40:54 -0800 Subject: [PATCH] Add breaking change for google assistant (#11777) * Add breaking change for google assistant * Move the links * Review comments --- source/_posts/2020-01-15-release-104.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2020-01-15-release-104.markdown b/source/_posts/2020-01-15-release-104.markdown index b91f402957f..efdb991faac 100644 --- a/source/_posts/2020-01-15-release-104.markdown +++ b/source/_posts/2020-01-15-release-104.markdown @@ -373,6 +373,8 @@ Make sure to fill in all fields of the issue template, that is helping us a lot! One possible scenario is if you have set an automation using the state of one lock to trigger an action on other lock(s). This change would cause the action to trigger on `locking` if it was previously triggering on `unlocking`. - ([@davet2001] - [#30663]) ([binary_sensor docs]) +- __Google Assistant__ - The `api_key` for manual installs is now deprecated and will be removed in 0.105. To correct this you will need to remove `api_key` from the `configuration.yaml` and switch to using `service_account` instead. - ([@elupus] - [#30402]) ([google_assistant docs]) + ## Beta Fixes - Fix upnp raw sensor state formatting when None ([@pnbruckner] - [#30444]) ([upnp docs]) (beta fix)