From f5b4dee474a5f08ca8899077a511c35470acfd6a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sat, 20 Jan 2018 22:54:09 -0800 Subject: [PATCH] Update 2018-01-21-clarification-emulated-hue.markdown --- source/_posts/2018-01-21-clarification-emulated-hue.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2018-01-21-clarification-emulated-hue.markdown b/source/_posts/2018-01-21-clarification-emulated-hue.markdown index 4af75e1128a..11d57e37c5e 100644 --- a/source/_posts/2018-01-21-clarification-emulated-hue.markdown +++ b/source/_posts/2018-01-21-clarification-emulated-hue.markdown @@ -10,7 +10,7 @@ comments: true categories: Public Service Announcement --- -There are some misconceptions floating about the future of the Emulated Hue component and I would like to set it straight. **The Emulated Hue component is not going to be removed nor will we ever remove any functionality from Home Assistant to push you to support the Home Assistant project by subscribing to the Community Support Package.** +There are some misconceptions floating around about the future of the Emulated Hue component and I would like to set the record straight. **The Emulated Hue component is not going to be removed nor will we ever remove any functionality from Home Assistant to push you to support the Home Assistant project by subscribing to the Community Support Package.** The reason people are concerned about the future of the Emulated Hue component is because of a poor choice of words in a deprecation message. This message was [introduced a year ago][pr2] when we deprecated the config option `type: alexa` for the Emulated Hue component: