Merge branch 'current' into next

This commit is contained in:
Paulus Schoutsen 2019-03-27 22:11:06 -07:00
commit 0d441ddd90
3 changed files with 9 additions and 1 deletions

View File

@ -43,7 +43,9 @@ To get the webhook URL, go to the integrations page in the configuration screen
- Click on "Create Agent" - 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 - 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" - 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` - Enable Webhook and set your Dialogflow webhook url as the endpoint, e.g., `https://myhome.duckdns.org/api/webhook/800b4cb4d27d078a8871656a90854a292651b20635685f8ea23ddb7a09e8b417`
- Click "Save" - Click "Save"
- Create a new intent - Create a new intent

View File

@ -86,6 +86,8 @@ While you should hopefully be storing your passwords in a password manager, if y
* `auth` * `auth`
* `auth_provider.homeassistant` * `auth_provider.homeassistant`
* `onboarding` * `onboarding`
* `hassio` (for hassio users)
* `cloud` (for nabucasa users)
When you start Home Assistant next, you'll be required to set up authentication again. When you start Home Assistant next, you'll be required to set up authentication again.

View File

@ -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 $ 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 %} ### {% 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`: 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.
<!-- from https://products.z-wavealliance.org/products/2817 --> <!-- from https://products.z-wavealliance.org/products/2817 -->
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 ```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0"> <CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
<Instance index="1" /> <Instance index="1" />