diff --git a/_config.yml b/_config.yml index ae52f220238..348d7464ba4 100644 --- a/_config.yml +++ b/_config.yml @@ -140,11 +140,14 @@ social: # Home Assistant release details current_major_version: 0 -current_minor_version: 44 -current_patch_version: 2 -date_released: 2017-05-08 +current_minor_version: 45 +current_patch_version: 0 +date_released: 2017-05-20 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. -# Example #release-0431---april-25 -patch_version_notes: "#release-0442---may-8" +# Major release: +patch_version_notes: "#" +# Minor release (Example #release-0431---april-25): +#patch_version_notes: "#release-0451---may-X" + diff --git a/source/_components/cover.lutron_caseta.markdown b/source/_components/cover.lutron_caseta.markdown new file mode 100644 index 00000000000..3064c7377cb --- /dev/null +++ b/source/_components/cover.lutron_caseta.markdown @@ -0,0 +1,14 @@ +--- +layout: page +title: "Lutron Caseta Cover" +description: "Instructions how to setup the Lutron Caseta covers within Home Assistant." +date: 2017-05-20 09:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: lutron.png +ha_category: Cover +--- + +To get your Lutron Caseta covers working with Home Assistant, follow the instructions for the general [Lutron Caseta component](/components/lutron_caseta/). diff --git a/source/_components/datadog.markdown b/source/_components/datadog.markdown index 5ad53d9e96a..511d51608a5 100644 --- a/source/_components/datadog.markdown +++ b/source/_components/datadog.markdown @@ -8,8 +8,8 @@ comments: false sharing: true logo: datadog.png footer: true -ha_category: "History" -ha_release: 0.43 +ha_category: History +ha_release: 0.45 --- The `datadog` component sends all state changes to [Datadog](https://www.datadoghq.com/) using a [Datadog Agent](http://docs.datadoghq.com/guides/basic_agent_usage/). diff --git a/source/_components/image_processing.openalpr_local.markdown b/source/_components/image_processing.openalpr_local.markdown index b41a691f434..76e00486710 100644 --- a/source/_components/image_processing.openalpr_local.markdown +++ b/source/_components/image_processing.openalpr_local.markdown @@ -22,17 +22,20 @@ For using inside automation look on [component](/components/image_processing) pa If you want process all data locally, you need version 2.3.1 or higher of the `alpr` commandline tool. -If you don't find binaries for your distribution you can compile from source. Documention of how to build openalpr is found [here](https://github.com/openalpr/openalpr/wiki). +If you don't find binaries for your distribution you can compile from source. Documention of how to build OpenALPR is found [here](https://github.com/openalpr/openalpr/wiki). On a Debian system you can use this `cmake` command to build only the command line tool: ```bash -$ cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr .. +$ cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE \ + --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr .. ``` +For other operating system please refer to the [OpenALPR wiki](https://github.com/openalpr/openalpr/wiki). + Verify your `alpr` installation with: -``` +```bash $ wget -O- -q http://plates.openalpr.com/h786poj.jpg | alpr - ``` diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown index b34b849927a..bd8054caa3d 100644 --- a/source/_components/media_player.markdown +++ b/source/_components/media_player.markdown @@ -71,4 +71,4 @@ Currently only supports Spotify. | Service data attribute | Optional | Description | | ---------------------- | -------- | ---------------------------------------------------- | | `entity_id` | no | Target a specific media player. For example `media_player.spotify`| -| `source` | no | `true`/`false` for enabling/disabling shuffle | +| `shuffle` | no | `true`/`false` for enabling/disabling shuffle | diff --git a/source/_components/notify.file.markdown b/source/_components/notify.file.markdown index b2c3a07d051..0061b31f003 100644 --- a/source/_components/notify.file.markdown +++ b/source/_components/notify.file.markdown @@ -28,7 +28,7 @@ notify: Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. -- **filename** (*Required*): Name of the file to use. The file will be created if it doesn't exist and saved in your `config/` folder. +- **filename** (*Required*): Name of the file to use. The file will be created if it doesn't exist and saved in your [configuration](/docs/configuration/) folder. - **timestamp** (*Optional*): Setting `timestamp` to `True` adds a timestamp to every entry. To use notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/_components/notify.nfandroidtv.markdown b/source/_components/notify.nfandroidtv.markdown index b620f23a169..90b204dcfd0 100644 --- a/source/_components/notify.nfandroidtv.markdown +++ b/source/_components/notify.nfandroidtv.markdown @@ -13,7 +13,7 @@ ha_release: 0.32 --- -Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google&hl=de) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). +Notification platform for [Notifications for Android TV](https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google&hl=en) and [Notifications for FireTV](https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google). The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running. The In-App purchases only apply to the client for Android smartphones, so there isn't any limit when pushing notifications from Home Assistant. diff --git a/source/_components/opencv.markdown b/source/_components/opencv.markdown index ab98fadc783..0ea2dcc9f81 100644 --- a/source/_components/opencv.markdown +++ b/source/_components/opencv.markdown @@ -23,7 +23,6 @@ To setup OpenCV with Home Assistant, add the following section to your `configur ```yaml # Example configuration.yaml entry - opencv: classifier_group: - name: Family diff --git a/source/_components/raspihats.markdown b/source/_components/raspihats.markdown index b392712675b..5e298c83be1 100644 --- a/source/_components/raspihats.markdown +++ b/source/_components/raspihats.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: raspihats.png ha_category: DIY -ha_release: 0.44 +ha_release: 0.45 --- The `raspihats` component is the base for all related Raspihats platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages. diff --git a/source/_docs/configuration/secrets.markdown b/source/_docs/configuration/secrets.markdown index db62c0159f4..14170759340 100644 --- a/source/_docs/configuration/secrets.markdown +++ b/source/_docs/configuration/secrets.markdown @@ -59,7 +59,7 @@ This will print all your secrets ### {% linkable_title Storing passwords in a keyring managed by your OS %} -Using [Keyring](http://pythonhosted.org/keyring/) is an alternative way to `secrets.yaml`. They can be managed from the command line via the keyring script. +Using [Keyring](https://github.com/jaraco/keyring) is an alternative way to `secrets.yaml`. They can be managed from the command line via the keyring script. ```bash $ hass --script keyring --help diff --git a/source/_docs/installation/archlinux.markdown b/source/_docs/installation/archlinux.markdown index 32961b7dc4c..8c2b8b38024 100644 --- a/source/_docs/installation/archlinux.markdown +++ b/source/_docs/installation/archlinux.markdown @@ -27,5 +27,5 @@ $ pip3 install homeassistant Home Assistant is part of the [AUR](https://aur.archlinux.org/packages/home-assistant/). This means that it can be installed with `pacaur`: ```bash -$ sudo pacaur -S home-assistant +$ pacaur -S home-assistant ``` diff --git a/source/_docs/installation/raspberry-pi-all-in-one.markdown b/source/_docs/installation/raspberry-pi-all-in-one.markdown index 4a6d02173a5..97da2ba5a98 100644 --- a/source/_docs/installation/raspberry-pi-all-in-one.markdown +++ b/source/_docs/installation/raspberry-pi-all-in-one.markdown @@ -8,15 +8,15 @@ footer: true redirect_from: /getting-started/installation-raspberry-pi-all-in-one/ --- -The [Raspberry Pi All-In-One Installer](https://github.com/home-assistant/fabric-home-assistant) deploys a complete Home Assistant server including support for MQTT with websockets, Z-Wave, and the Open-Zwave Control Panel. +The [Raspberry Pi All-In-One Installer](https://github.com/home-assistant/fabric-home-assistant) deploys a complete Home Assistant server including support for MQTT with websockets, Z-Wave, and the OpenZWave Control Panel. The only requirement is that you have a Raspberry Pi with a fresh installation of [Raspbian](https://www.raspberrypi.org/downloads/raspbian/) connected to your network.

-Note that as of 2016-11-30 SSH is disabled by default in the official Raspbian images. Adding an empty file called `ssh` to `/boot/` or the FAT32 partition will enable it. More information is on the Raspberry Pi Foundation [Blog](https://www.raspberrypi.org/blog/page/2/?fish#a-security-update-for-raspbian-pixel) +Note that as of 2016-11-30 SSH is disabled by default in the official Raspbian images. Adding an empty file called `ssh` to `/boot/` or the FAT32 partition will enable it. More information is on the Raspberry Pi Foundation [Blog](https://www.raspberrypi.org/blog/page/2/?fish#a-security-update-for-raspbian-pixel).

-Irrespective of whether you use SSH to connect to the Pi from another computer or not, you need SSH to install Home Assistant. So go ahead and enable SSH. +Irrespective of whether you use SSH to connect to the Pi from another computer or not, you need SSH to install Home Assistant. So go ahead and enable SSH. * Login to Raspberry Pi. For example with `ssh pi@your_raspberry_pi_ip` * Run the following command @@ -28,7 +28,7 @@ $ curl -O https://raw.githubusercontent.com/home-assistant/fabric-home-assistant Note this command is one-line and not run as sudo.

-Installation will take approx. 1-2 hours depending on the Raspberry Pi model the installer is being run against. The installer will identitfy what Raspberry PI hardware revision you are using and adjust commands accordingly. A complete log of the install is located at: `/home/pi/fabric-home-assistant/installation_report.txt` The installer has been updated to simply log any errors encountered, but resume installing. Please consult the "installation report" if your install encountered issues. +Installation will take approx. 1-2 hours depending on the Raspberry Pi model the installer is being run against. The installer will identitfy what Raspberry Pi hardware revision you are using and adjust commands accordingly. A complete log of the install is located at: `/home/pi/fabric-home-assistant/installation_report.txt` The installer has been updated to simply log any errors encountered, but resume installing. Please consult the "installation report" if your install encountered issues. [BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=VGl3KTrYo6s) explaining how to install Raspbian on your Raspberry Pi and install Home Assistant using the All-In-One Installer. @@ -52,7 +52,7 @@ The All-In-One Installer script will do the following automatically: * Install Home Assistant in a virtualenv * Install Mosquitto with websocket support running on ports 1883 and 9001 * Build and Install Python-openzwave in the Home Assistant virtualenv -* Build openzwave-control-panel in `/srv/homeassistant/src/open-zwave-control-panel` +* Build OpenZWave Control Panel in `/srv/homeassistant/src/open-zwave-control-panel` * Add Home Assistant to systemd services to start at boot ### {% linkable_title Upgrading %} @@ -62,7 +62,7 @@ To upgrade the All-In-One setup manually: * Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip` * Change to homeassistant user `sudo su -s /bin/bash homeassistant` * Change to virtual enviroment `source /srv/homeassistant/homeassistant_venv/bin/activate` -* Update HA `pip3 install --upgrade homeassistant` +* Update Home Assistant `pip3 install --upgrade homeassistant` * Type `exit` to logout the hass user and return to the `pi` user.
@@ -70,7 +70,7 @@ To upgrade the All-In-One setup manually: * Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip` * Change to homeassistant user `sudo su -s /bin/bash hass` * Change to virtual enviroment `source /srv/hass/hass_venv/bin/activate` -* Update HA `pip3 install --upgrade homeassistant` +* Update Home Assistant `pip3 install --upgrade homeassistant` * Type `exit` to logout the hass user and return to the `pi` user.
@@ -88,23 +88,27 @@ After upgrading, you can restart Home Assistant a few different ways: ### {% linkable_title Using the OZWCP web application %} -To launch the OZWCP web application: +To launch the OpenZWave Control Panel (OZWCP) web application: * Make sure Home Assistant is not running! So stop that first * Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip` -* Change to the ozwcp directory `cd /srv/homeassistant/src/open-zwave-control-panel/` +* Change to the OZWCP directory `cd /srv/homeassistant/src/open-zwave-control-panel/` * Launch the control panel `sudo ./ozwcp -p 8888` * Open a web browser to `http://your_pi_ip:8888` -* Specify your zwave controller, for example `/dev/ttyACM0` and hit initialize +* Specify your Z-Wave controller, for example `/dev/ttyACM0` and hit initialize + +

+ If OZWCP is running really slow verify that your not running Home Assistant or have another page running OZWCP open or strange errors might occur. +

**If you deployed Home Assistant via the AiO installer prior to December 2016** * Make sure Home Assistant is not running! So stop that first * Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip` -* Change to the ozwcp directory `cd /srv/hass/src/open-zwave-control-panel/` +* Change to the OZWCP directory `cd /srv/hass/src/open-zwave-control-panel/` * Launch the control panel `sudo ./ozwcp -p 8888` * Open a web browser to `http://your_pi_ip:8888` -* Specify your zwave controller, for example `/dev/ttyACM0` and hit initialize +* Specify your Z-Wave controller, for example `/dev/ttyACM0` and hit initialize

diff --git a/source/_includes/asides/developers_navigation.html b/source/_includes/asides/developers_navigation.html index d7cfb876d3e..1f7c6f02f23 100644 --- a/source/_includes/asides/developers_navigation.html +++ b/source/_includes/asides/developers_navigation.html @@ -47,7 +47,6 @@

  • {% active_link /developers/code_review_component/ Checklist creating a component %}
  • {% active_link /developers/component_loading/ Loading components %}
  • {% active_link /developers/component_deps_and_reqs/ Requirements & Dependencies %}
    • -
  • {% active_link /developers/component_initialization/ Initialization %}
  • {% active_link /developers/component_events/ Handling events %}
  • {% active_link /developers/component_states/ States %}
  • {% active_link /developers/component_visibility/ Visibility %}
    • @@ -87,6 +86,7 @@
  • {% active_link /developers/multiple_instances/ Multiple Instances %}
  • {% active_link /developers/website/ Home-Assistant.io %}
  • {% active_link /developers/releasing/ Releasing %}
    • +
  • {% active_link /developers/maintenance/ Maintenance %}
  • Governance