From 84c95bd409f6f454f3057fc5a74d2d3a271244f4 Mon Sep 17 00:00:00 2001 From: cogneato Date: Tue, 26 Mar 2019 16:33:59 -0600 Subject: [PATCH 1/3] Update lost owner password files (#9041) Added hassio and cloud files which need to be removed when resetting auth accounts --- source/_docs/authentication.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index 655e4002d57..c466826a196 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -86,6 +86,8 @@ While you should hopefully be storing your passwords in a password manager, if y * `auth` * `auth_provider.homeassistant` * `onboarding` +* `hassio` (for hassio users) +* `cloud` (for nabucasa users) When you start Home Assistant next, you'll be required to set up authentication again. From 2720713e9ee162f9bbed771cf935f7693d941490 Mon Sep 17 00:00:00 2001 From: mastakebob <47671816+mastakebob@users.noreply.github.com> Date: Tue, 26 Mar 2019 18:34:48 -0400 Subject: [PATCH 2/3] Update device-specific.markdown (#9042) Updates include an alternate way of turning off the aeotec z wave 'disco lights' that is known to work on the latest Hass.io and Pi configuration (using ttyACM0 instead of the the by serial id method). Also provides additional guidance on how to properly insert the aeotec nanomote xml code into the zwcfg*.xml file. --- source/_docs/z-wave/device-specific.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown index 1ebb5083945..288eb1d57e0 100644 --- a/source/_docs/z-wave/device-specific.markdown +++ b/source/_docs/z-wave/device-specific.markdown @@ -45,6 +45,8 @@ Turn on "Disco lights": $ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00 ``` +If the above two commands give errors about not having that device, you should try replacing the `/dev/serial/by-id/usb-0658_0200-if00` with `/dev/ttyACM0` or `/dev/ttyACM1` (depending on which tty your aeotec stick is addressed to). + ### {% linkable_title Razberry Board %} You need to disable the on-board Bluetooth since the board requires the use of the hardware UART (and there's only one on the Pi3). You do this by adding the following to the end of `/boot/config.txt`: @@ -298,6 +300,8 @@ Press circle and plus simultaneously to wake up the device. +Once you've added the NanoMote to your z-wave network, you'll need to update your zwcfg*.xml file with the below xml data. Stop Home Assistant and open your zwcfg*.xml file (located in your config folder). Find the NanoMote device section and then its corresponding `CommandClass` section with id="91". Replace the entire CommandClass section with the below xml data. Save the file and restart Home Assistant. + ```xml From c2ff81aa3af4d209db7a3003b3977f20f1173bd7 Mon Sep 17 00:00:00 2001 From: Aalian Khan <39784853+AalianKhan@users.noreply.github.com> Date: Wed, 27 Mar 2019 03:38:51 -0400 Subject: [PATCH 3/3] Need to switch API version to make component work (#9052) --- source/_components/dialogflow.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_components/dialogflow.markdown b/source/_components/dialogflow.markdown index efef285aa7b..c1f384b73cd 100644 --- a/source/_components/dialogflow.markdown +++ b/source/_components/dialogflow.markdown @@ -43,7 +43,9 @@ To get the webhook URL, go to the integrations page in the configuration screen - Click on "Create Agent" - Select name, language (if you are planning to use Google Actions check their [supported languages](https://support.google.com/assistant/answer/7108196?hl=en)) and time zone - Click "Save" -- Go to "Fulfillment" (in the left menu) +- Go to project settings (cog symbol in left menu) +- under "API VERSION" click on "V1 API" +- Now go to "Fulfillment" (in the left menu) - Enable Webhook and set your Dialogflow webhook url as the endpoint, e.g., `https://myhome.duckdns.org/api/webhook/800b4cb4d27d078a8871656a90854a292651b20635685f8ea23ddb7a09e8b417` - Click "Save" - Create a new intent