Downloading and Preparing haaska

There are two ways to download and prepare haaska. There is the Simple Method (recommended), and there is the Advanced Method.

Simple Method - Recommended

Follow these steps:

1. Get haaska's Latest Release. This is usually named like haaska_1.1.0.zip, not the Source code files.

2. Add the following to your configuration.yaml file:

api:

alexa:
  smart_home:

3. Get a Long Lived Token. You can create one inside Home Assistant with these steps:

   • Log in to your Home Assistant install
   • Click on the letter inside the blue circle at the top left. This will take you to "Profile".
   • Scroll down to "Long-Lived Access Tokens". Click CREATE TOKEN.
   • For Name? enter haaska, and click OK.
   • A token will appear. Please copy it to somewhere safe, like a text file in Notepad. We will need it later.

4. That's it! Move on to the next section, Setup.

---

Advanced Method - Building from Source

Getting haaska

If you would like to, you can clone the repo, or download the packaged ZIP.

Pre-requisites to Building

In order to move forward, you will need to have a local build environment using Python 3.6 or newer, and Pip. Installing these is beyond the scope of this guide, but you can locate most downloads here: https://www.python.org/downloads/.

You will still require a Long Lived Token, which you can get with the instructions in Step 3 above.

Edit config.json and Build

In the config/ directory, open config.json and update it, using a text editor of your choice. Then, in a terminal shell, use make to build a haaska.zip for use. Below is a full list of properties for the config:

Key	Example Value	Required?	Notes
url	https://homeassistant.example.com:8123	Yes	A valid URL for your Home Assistant/Hass.io instance.
bearer_token	eyJ0eXA...	Yes	A Long Lived Token from your Home Assistant.
debug	false	No	When enabled, the haaska log level will be set to debug. If not provided, this defaults to false.
ssl_verify	true or false	Yes	Use to decide whether or not your SSL certificate will be checked. Defaults to true.
ssl_client	my-cert.crt	No	This will be passed as the verify parameter for all requests; see here for options. If used, this cert must be placed in the config directory before building.

Complete Setup

That's it for now! In the next section, you can skip the part where we edit the config file, because you've already done this. Move on to Setup.