From 371803bc24ebce5f85601f99115d46a237b7b5bd Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Fri, 21 Dec 2018 21:56:40 +0100 Subject: [PATCH] Add paragraph --- .../2018-12-17-logitech-harmony-removes-local-api.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown index c565237c44c..a5642041149 100644 --- a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown +++ b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown @@ -23,6 +23,8 @@ Tenable, the cyber security firm that discovered the security vulnerabilities, h **Update 7 (21 dec):** Even better news! Someone from Harmony posted [in our forums](https://community.home-assistant.io/t/logitechs-stance-on-local-apis/85842/18?u=balloob) and stated that they are now committed to maintaining their local XMPP API. +We will verify with Logitech if this post is official, and if so, we will revert the Home Assistant implementation back to using the XMPP API. Until then, we don't expect the websocket API that we are using since 0.84.3 to go away or change until we migrate back, so if your Harmony setup works today, don't change anything. +

Screenshot of someone from Harmony stating that they are going to keep the local XMPP API around. Forum post by Harmony employee on the Home Assistant forums.