diff --git a/.github/stale.yml b/.github/stale.yml
new file mode 100644
index 00000000000..e5b0f5e954c
--- /dev/null
+++ b/.github/stale.yml
@@ -0,0 +1,17 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 60
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+#exemptLabels:
+# - pinned
+# - security
+# Label to use when marking an issue as stale
+staleLabel: Stale
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+ This issue has been automatically marked as stale because it has not had
+ recent activity. It will be closed if no further activity occurs. Thank you
+ for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false
diff --git a/_config.yml b/_config.yml
index 9500187094b..69312dd7804 100644
--- a/_config.yml
+++ b/_config.yml
@@ -140,11 +140,11 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 57
-current_patch_version: 0
-date_released: 2017-11-04
+current_patch_version: 2
+date_released: 2017-11-05
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
# Major release:
-patch_version_notes: ""
+patch_version_notes: "#release-0572--november-5"
# Minor release (Example #release-0431---april-25):
diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss
index 16024b33bfe..2a9e1fb4ebc 100644
--- a/sass/custom/_paulus.scss
+++ b/sass/custom/_paulus.scss
@@ -394,15 +394,15 @@ p.note {
.aside-module {
.section {
- margin-bottom: 16px;
+ margin-bottom: 10px;
}
.brand-logo-container {
text-align: center;
- height: 97px;
+ height: 87px;
img {
- max-height: 97px;
+ max-height: 67px;
}
}
}
diff --git a/source/_components/arduino.markdown b/source/_components/arduino.markdown
index acfd091c727..5105f19c4cc 100644
--- a/source/_components/arduino.markdown
+++ b/source/_components/arduino.markdown
@@ -30,9 +30,12 @@ arduino:
port: /dev/ttyACM0
```
-Configuration variables:
-
-- **port** (*Required*): The port where your board is connected to your Home Assistant host. If you are using an original Arduino, the port will be named `ttyACM*` otherwise `ttyUSB*`.
+{% configuration %}
+port:
+ description: The port where your board is connected to your Home Assistant host. If you are using an original Arduino, the port will be named `ttyACM*` otherwise `ttyUSB*`.
+ required: true
+ type: string
+{% endconfiguration %}
The exact number can be determined with the command shown below.
diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown
index 62f2a50b1ba..009f4131ddd 100644
--- a/source/_components/binary_sensor.template.markdown
+++ b/source/_components/binary_sensor.template.markdown
@@ -39,31 +39,36 @@ binary_sensor:
required: true
type: map
keys:
- friendly_name:
- description: Name to use in the frontend.
- required: false
- type: string
- entity_id:
- description: Add a list of entity IDs so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update its state.
- required: false
- type: string, list
- device_class:
- description: The type/class of the sensor to set the icon in the frontend.
- required: false
- type: device_class
- default: None
- value_template:
- description: Defines a template to set the state of the sensor.
+ sensor_name:
+ description: The slug of the sensor.
required: true
- type: template
- delay_on:
- description: The amount of time the template state must be ***met*** before this sensor will switch to `on`.
- required: false
- type: time
- delay_off:
- description: The amount of time the template state must be ***not met*** before this sensor will switch to `off`.
- required: false
- type: time
+ type: map
+ keys:
+ friendly_name:
+ description: Name to use in the frontend.
+ required: false
+ type: string
+ entity_id:
+ description: Add a list of entity IDs so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update its state.
+ required: false
+ type: string, list
+ device_class:
+ description: The type/class of the sensor to set the icon in the frontend.
+ required: false
+ type: device_class
+ default: None
+ value_template:
+ description: Defines a template to set the state of the sensor.
+ required: true
+ type: template
+ delay_on:
+ description: The amount of time the template state must be ***met*** before this sensor will switch to `on`.
+ required: false
+ type: time
+ delay_off:
+ description: The amount of time the template state must be ***not met*** before this sensor will switch to `off`.
+ required: false
+ type: time
{% endconfiguration %}
## {% linkable_title Considerations %}
diff --git a/source/_components/camera.markdown b/source/_components/camera.markdown
index 48d1f58f5f0..e0dee527ad6 100644
--- a/source/_components/camera.markdown
+++ b/source/_components/camera.markdown
@@ -43,6 +43,8 @@ Take a snapshot from a camera.
| `entity_id` | no | Name(s) of entities to create a snopshot from, e.g., `camera.living_room_camera`. |
| `filename ` | no | Template of a file name. Variable is `entity_id`, e.g., {% raw %}`/tmp/snapshot_{{ entity_id }}`{% endraw %}. |
+The path part of `filename` must be an entry in the `whitelist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file.
+
### {% linkable_title Test if it works %}
A simple way to test if you have set up your `camera` platform correctly, is to use **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.
diff --git a/source/_components/camera.rpi_camera.markdown b/source/_components/camera.rpi_camera.markdown
index 7189dfd3d8a..6bfeb7696ea 100644
--- a/source/_components/camera.rpi_camera.markdown
+++ b/source/_components/camera.rpi_camera.markdown
@@ -24,17 +24,53 @@ camera:
- platform: rpi_camera
```
-Configuration variables:
-
- - **name** (*Optional*): Name of the camera
- - **image_width** (*Optional*): Set the image width (default: 640)
- - **image_height** (*Optional*): Set the image height (default: 480)
- - **image_quality** (*Optional*): Set the image quality (from 0 to 100, default: 7)
- - **image_rotation** (*Optional*): Set image rotation (0-359, default: 0)
- - **horizontal_flip** (*Optional*): Set horizontal flip (0 to disable, 1 to enable, default: 0)
- - **vertical_flip** (*Optional*): Set vertical flip (0 to disable, 1 to enable, default: 0)
- - **timelapse** (*Optional*): Takes a picture every ms (default: 1000)
- - **file_path** (*Optional*): Save the picture in a custom file path (default: camera components folder)
+{% configuration %}
+image_width:
+ description: Set the image width.
+ required: false
+ default: 640
+ type: int
+name:
+ description: Name of the camera.
+ required: false
+ default: Raspberry Pi Camera
+ type: string
+image_height:
+ description: Set the image height.
+ required: false
+ default: 480
+ type: int
+image_quality:
+ description: Set the image quality (from 0 to 100).
+ required: false
+ default: 7
+ type: int
+image_rotation:
+ description: Set image rotation (0-359).
+ required: false
+ default: 0
+ type: int
+horizontal_flip:
+ description: Set horizontal flip (0 to disable, 1 to enable).
+ required: false
+ default: 0
+ type: int
+vertical_flip:
+ description: Set vertical flip (0 to disable, 1 to enable).
+ required: false
+ default: 0
+ type: int
+timelapse:
+ description: Takes a picture every millisecond.
+ required: false
+ default: 1000
+ type: int
+file_path:
+ description: Save the picture in a custom file path.
+ required: false
+ default: The camera components folder.
+ type: string
+{% endconfiguration %}
The given **file_path** must be an existing file because the camera platform setup make a writeable check on it.
diff --git a/source/_components/climate.ephember.markdown b/source/_components/climate.ephember.markdown
index 962b34746e2..0b77e6a58b7 100644
--- a/source/_components/climate.ephember.markdown
+++ b/source/_components/climate.ephember.markdown
@@ -9,7 +9,7 @@ sharing: true
footer: true
logo: ephcontrolsember.png
ha_category: Climate
-ha_release: "0.55"
+ha_release: 0.57
ha_iot_class: "Local Polling"
---
diff --git a/source/_components/input_number.markdown b/source/_components/input_number.markdown
index e043b924696..9c041e1b7f3 100644
--- a/source/_components/input_number.markdown
+++ b/source/_components/input_number.markdown
@@ -145,13 +145,12 @@ input_number:
icon: mdi:target
# Automation.
- # This automation script runs when a value is received via MQTT on retained topic: setTemperature
- # It sets the value slider on the GUI. This slides also had its own automation when the value is changed.
+# This automation script runs when a value is received via MQTT on retained topic: setTemperature
+# It sets the value slider on the GUI. This slides also had its own automation when the value is changed.
- alias: Set temp slider
trigger:
platform: mqtt
topic: "setTemperature"
- # entity_id: input_number.target_temp
action:
service: input_number.set_value
data_template:
diff --git a/source/_components/media_player.vizio.markdown b/source/_components/media_player.vizio.markdown
index ae68385e13a..7c8cfa363ba 100644
--- a/source/_components/media_player.vizio.markdown
+++ b/source/_components/media_player.vizio.markdown
@@ -97,4 +97,7 @@ Vizio SmartCast service is accessible through HTTPS with self-signed certificate
`InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.`
You can adjust the log level for `media_player` components with the [logger](https://home-assistant.io/components/logger/) component, or if you need to keep a low log level for `media_player` you could proxy calls to your TV through an NGINX reverse proxy.
+
+If you want to only ignore only this specific [python urllib3 SSL warning](https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings), you will need to run Home Assistant with the python flag `-W` or the environment variable `PYTHONWARNINGS` set to:
+`ignore:Unverified HTTPS request is being made`
+ The Python version 3.4.4 or greater is required for this component. The component will not initialize without this and will report a `Could not install all requirements` error in the logs. +
+ You can add the following to your `configuration.yaml` file if you are not using the [`discovery:`](/components/discovery/) component: ```yaml @@ -33,7 +37,7 @@ tradfri: Configuration variables: - **host** (*Required*): The IP address or hostname of your Trådfri gateway. - - **allow_tradfri_groups** (*Optional*): Enable this to stop Home Assistant from importing the groups defined on the Trådfri bridge. Defaults to `true`. + - **allow_tradfri_groups** (*Optional*): Set this to `false` to stop Home Assistant from importing the groups defined on the Trådfri bridge. Defaults to `true`.
Do not use the `api_key` variable. The key is only needed once at initial setup.
diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown
index 9531f61520d..43f6885f334 100644
--- a/source/_docs/configuration/customizing-devices.markdown
+++ b/source/_docs/configuration/customizing-devices.markdown
@@ -49,7 +49,7 @@ homeassistant:
icon: mdi:description
"scene.month_*_colors":
hidden: true
- emulated_hue: false
+ emulated_hue_hidden: false
homebridge_hidden: true
```
diff --git a/source/_docs/ecosystem/tor.markdown b/source/_docs/ecosystem/tor.markdown
index 6d87b5f08b4..4c81451d576 100644
--- a/source/_docs/ecosystem/tor.markdown
+++ b/source/_docs/ecosystem/tor.markdown
@@ -10,20 +10,14 @@ footer: true
redirect_from: /cookbook/tor_configuration/
---
-This is an example about how you can configure Tor to provide secure remote access to your Home Assistant instance as an Onion site, through [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en) feature. With this enabled, you do not need to open your firewall ports or setup HTTPS to enable secure remote access.
+This article guides your through the configuration of Tor to provide a secure access to your Home Assistant instance as an Onion site, through [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en) feature, from remote. With this enabled, you do not need to open your firewall ports or setup HTTPS to enable secure remote access.
This is useful if you want to have:
- * Access your Home Assistant instance remotely without opening a firewall port or setting up a VPN
- * Don't want to or know how to get an SSL/TLS certificate and HTTPS configuration setup
- * Want to block attackers from even being able to access/scan your port and server at all
- * Want to block anyone from knowing your home IP address and seeing your traffic to your Home Assistant
-
-## {% linkable_title Background and Contact %}
-
-This configuration is part of an effort to apply strong cryptography technologies (like Onion Routing and End-to-End Encryption) to technology we increasingly depend on in our day to day lives. Just like when WhatsApp enabled end-to-end encryption messaging for everyone, every home automation and IoT platform should do the same, because A) the technology is all there, freely licensed and open-source and B) up to this point, all the commercial manufacturers have been doing a horrific job with security.
-
-You can learn more about how Tor can be used to secure home automation and IoT platforms through this short set of slides on the [Internet of Onion Things](https://github.com/n8fr8/talks/blob/master/onion_things/Internet%20of%20Onion%20Things.pdf)
+ * Access your Home Assistant instance remotely without opening a firewall port or setting up a VPN.
+ * Don't want to or know how to get an SSL/TLS certificate and HTTPS configuration setup.
+ * Want to block attackers from even being able to access/scan your port and server at all.
+ * Want to block anyone from knowing your home IP address and seeing your traffic to your Home Assistant.
## {% linkable_title Hidden Services and Onion Sites %}
@@ -61,7 +55,7 @@ The "stealth" entry above ensures traffic to and from your Home Assistant instan
Then, restart Tor:
```bash
-$ sudo /etc/init.d/tor restart
+$ sudo systemctl restart tor
```
Then read the new generated authentication cookie from the Tor-generated hostname file:
@@ -106,5 +100,3 @@ You could also use Tor as a means to connect your Home Assistant instance to a r
As mentioned, with Orbot on Android, you can enable a "full device" VPN mode, that allows any app you have to tunnel through Tor, even if it is not Tor or proxy aware. This means you should be able to enter your "dot onion" Onion site address into any app you want to access to your Home Assistant instance, and it should work.
-This configuration was provided by @n8fr8 ([github](https://github.com/n8fr8), [twitter](https://twitter.com/n8fr8)) of the [Guardian Project](https://guardianproject.info) and [Tor Project](https://torproject.org). You can send questions, feedback and ideas to [support@guardianproject.info](mailto:support@guardianproject.info).
-
diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown
index b7b6a12336f..40ef9739c62 100644
--- a/source/_docs/z-wave/installation.markdown
+++ b/source/_docs/z-wave/installation.markdown
@@ -153,6 +153,23 @@ On macOS you can find the USB stick with:
$ ls /dev/cu.usbmodem*
```
+### {% linkable_title Hass.io %}
+
+To enable Z-Wave, plug your Z-Wave USB stick into your Raspberry Pi 3 and add the following to your `configuration.yaml`:
+
+```yaml
+zwave:
+ usb_path: /dev/ttyACM0
+```
+
+For some devices the `/dev/ttyAMA0` device is not detected by udev and is therefore not mapped by Docker. To explicitly set this device for mapping to Home-Assistant, execute the following command using the ssh add-on:
+
+```bash
+$ curl -d '{"devices": ["ttyAMA0"]}' http://hassio/homeassistant/options
+```
+
+After that, you need to change `usb_path` to `/dev/ttyAMA0`.
+
### {% linkable_title Network Key %}
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the *network_key* configuration variable to use a network key before adding these devices.
@@ -167,3 +184,30 @@ Ensure you keep a backup of this key. If you have to rebuild your system and don
## {% linkable_title First Run %}
Upon first run, the `zwave` component will take time to initialize entities and entities may appear with incomplete names. Running a network heal may speed up this process.
+
+## {% linkable_title Troubleshooting %}
+
+### {% linkable_title Component could not be set up %}
+
+Sometimes the device may not be accessible and you'll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path:
+
+```bash
+ls -l /dev/ttyAMA0
+```
+
+You should then see something like this:
+
+```
+crw-rw---- 1 root dialout 204, 64 Apr 1 12:34 /dev/ttyAMA0
+```
+
+The important pieces are the first piece `crw-rw----` and the group `dialout`. If those are different then, for your device path, run:
+
+```bash
+sudo chgrp dialout /dev/ttyAMA0
+sudo chmod g+rw /dev/ttyAMA0
+```
+
+### {% linkable_title Device path changes %}
+
+If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it.
diff --git a/source/_faq/browser.markdown b/source/_faq/browser.markdown
new file mode 100644
index 00000000000..ee2dd204f7a
--- /dev/null
+++ b/source/_faq/browser.markdown
@@ -0,0 +1,13 @@
+---
+layout: page
+title: "Frontend is acting weird"
+description: "Frontend is acting weird"
+date: 2017-06-18 09:00
+comments: false
+sharing: true
+footer: true
+ha_category: Usage
+---
+
+
+Close the windows or tab and clear the cache. The frontend is aggressively caching and clearing the cache ensures that the frontend is reloaded when you access it the next time.
diff --git a/source/_includes/asides/component_navigation.html b/source/_includes/asides/component_navigation.html
index ac543147b60..56ba92ee777 100644
--- a/source/_includes/asides/component_navigation.html
+++ b/source/_includes/asides/component_navigation.html
@@ -1,4 +1,5 @@
{% assign components = site.components | sort: 'title' %}
+{% assign github_main_repo = 'https://github.com/home-assistant/home-assistant/blob/master/homeassistant' %}
+
+The translation of the Home Assistant frontend is still a work in progress. More phrases will be available for translation soon.
+
+Region specific translations (`en-US`, `fr-CA`) will only be included if translations for that region need to differ from the base language translation.
+
+The Home Assistant sidebar in 12 different languages.
+
button. For more information about the translation workflow, please see the [Lokalise translation workflow documents](https://docs.lokalise.co/category/iOzEuQPS53-for-team-leads-and-translators).
+
+