Homeassistant

Hotfix release to improve config validation errors. Some got a bit confusing due to 1975.
- Add location back to config validation errors that were not 'extra keys not allowed'.
- Automation deprecation warning will now list the deprecated option used.
- Show YAML line in validation error if available.

This release is big. Until now, our automations and scripts have been very static. Starting today it should all be way more dynamic.

**Scripts** are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including `from_state` !). Passing data to script entities is available by passing the data to the script services.

yaml
automation:
trigger:
platform: mqtt
topic: some/notify/topic
action:
service: notify.notify
data_template:
message: {{ trigger.payload }}

automation 2:
trigger:
platform: state
entity_id: light.hue
action:
service: notify.notify
data_template:
message: {{ trigger.to_state.name }} is now {{ trigger.to_state.state }}


**Entity Namespaces** allow you to influence the entity ids for a specific platform. For example you can turn `light.living_room` into `light.holiday_home_living_room` with the following config:

yaml
light:
platform: hue
entity_namespace: holiday_home

- Automation: allow script syntax for action (balloob)
- Automation: expose `trigger` variable to script templates (balloob)
- Script: allow passing variables for script templates in the script service calls (balloob)
- Alexa/Amazon Echo: allow script syntax for action (balloob)
- Alexa/Amazon Echo: expose intent variables to script templates (balloob)
- Script syntax: conditions now supported to interrupt execution (balloob)
- Automation: use new condition syntax (balloob)
- Script syntax: two new conditions `and` and `or` to combine conditions (balloob)
- Any platform: Allow setting entity namespace to prefix entity_ids. (balloob)
- Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (milaq)
- Z-Wave: use more sane defaults (danieljkemp)
- Media Player: Snapcast now supports picking a source (happyleavesaoc)
- MySensors major cleanup (MartinHjelmare)
- Binary Sensor: Command line sensor now supports classes (fabaff)
- MQTT: allow client key authentication (timharton)
- Sensor: Forecast.io now supports minutely, hourly and daily summaries (aceat64)
- Media Player: Pioneer AVR now supported (kylehendricks)
- Switch: Acer Projectors now supported (deisi)
- HVAC component added with Z-Wave support (turbokongen)
- OctoPrint now supported (w1ll1am23)
- Configuration.yaml can now refer to environment variables using `!env_var` (bah2830)
- Lock: Z-Wave now supported (devdelay)
- Dweet component added to export data (fabaff)
- Media Player now supports stop command + initial kodi support (hmronline)
- Zigbee: push updates now supported (flyte)
- Wink devices with battery level will now show these (w1ll1am23)
- Templates: new `as_timestamp` method now available (srcLurker)
- API: Add `/api/discovery_info` with basic instance info (robbiet480)
- Sensor: Google Maps travel time added (Danielhiversen)
- Allow settings CORS headers (robbiet480)
- Sensor: Fitbit support added (robbiet480)
- Bug fixes and tweaks by turbokongen, danieljkemp, Danielhiversen, TheRealLink, persandstrom, sander76, fabaff, ishults, Bart274, robbiet480, Cinntax, blackdog70, gwendalg, JshWright, kylehendricks, bradsk88, shaftoe, molobrakos, bah2830, nkgilley

Deprecations
- Conditions in automations should now specify which condition to use with `condition:` instead of `platform:`. For example `condition: state`.
- RFXtrx has a new config format.

Old RFXtrx config format:


devices:
123efab1:
name: My DI.0 light device
packetid: 1b2200000890efab1213f60


New RFXtrx config format:


devices:
1b2200000890efab1213f60:
name: My DI.0 light device

_This release has been published on PyPi as 0.18.2 because I messed up._

It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs in the next 2 weeks.

Since the last release we have moved all Home Assistant source code etc into it's own [organisation on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
- New component: Zeroconf for Home Assistant discovery (robbiet480)
- Garage door: MQTT now supported (joelash)
- Thermostat: Homematic platform now supports Max! devices (bimbar)
- New component: Thinkingcleaner to integrate your Roomba into Home Assistant (TheRealLink)
- New component: upnp to automatically open a upnp port on your router for Home Assistant (robbiet480)
- HTTP: Use constant time comparison for auth (JshWright)
- Config and service validations (jaharkes, Danielhiversen)
- MySensors: Entity IDs will more clearly differentiate between node ID and child ID (oeysteinhansen)
- Media player: Plex will now monitor the server and add clients as they pop up (infamy)
- Core: We now use iso8601 for datetimes (balloob).
- Media Player: MPD now supports service to play playlists (Cinntax)
- Z-Wave should be a little bit more stable (Turbokongen)
- Media Player: Sonos will now only add visible devices (jpmossin)
- Light: Wink will now allow controlling the colors (bradsk88)
- Thermostat: EQ3 Bluetooth Smart Thermostats now supported (bimbar)
- New component Feedreader will track RSS feeds (shaftoe)
- Device Tracker: Bluetooth tracking platform added (vmulpuru)
- Media Player: LG WebOS TVs now supported (TheRealLink)
- MySensors: Add support for ethernet gateway (MartinHjelmare)
- Media Player: redesign! (DesignFirst, balloob)


Breaking changes
- The location of the Docker image has changed. There was no possibility for us to keep maintaining the old image (as it was bound to the GitHub repo under my name) or to make a redirect. So if you are using the Home Assistant Docker image, change it to run `homeassistant/home-assistant:latest` for the latest release and `homeassistant/home-assistant:dev` for the latest dev version.
- We have migrated our datetime format to be iso8601. This will only impact you if you are consuming the date times from the API directly. You can ignore this if you are just using Home Assistant via configuration and the frontend.
- The constant `TEMP_CELCIUS` is now correctly called `TEMP_CELSIUS`. Old one is deprecated and will eventually be removed.
- MySensors received two big changes that will cause you to update your configs.
1. All MySensors entity IDs are different! There was an error in the naming that caused MySensors to append node ID and child ID instead of separating them with an underscore. This has been fixed but will cause all your MySensors entity IDs to change. This is a one time breaking change.
2. The second change is that we now support the TCP ethernet gateway. This is causing a slight change to the config format: you have to change `port:` under `gateways` to `device:`. See below for new example config.

yaml
mysensors:
gateways:
- device: '/dev/ttyUSB0'
persistence_file: 'path/mysensors.json'
baud_rate: 38400
- device: '/dev/ttyACM0'
persistence_file: 'path/mysensors2.json'
baud_rate: 115200
- device: '192.168.1.18'
persistence_file: 'path/mysensors3.json'
tcp_port: 5003
debug: true
persistence: true
version: '1.5'
optimistic: false

One more hot fix to help people with validation issues.

We allow people passing in the API password as a GET/POST parameter. If the REST API would be used to call a service, the password would be forwarded to the service. If the service contained validation, it would fail because of an unexpected key.

Thanks to jaharkes for squashing this bug.

Two more fixes to help handle duplicate keys in YAML:
- Better error reporting if a duplicate key found in YAML (jaharkes)
- Device Tracker will no longer write duplicate keys (balloob)

This will be a quick bug fix release for 0.17.1. Thanks to turbokongen and jaharkes for the quick bug fixes and thanks for all the people that reported them.
- RFXTRX no longer raises config validation errors when run combined with other components
- MQTT will validate the protocol field correctly
- Light will validate flash and effect fields correctly
- Groups will now allow again to be created without any entities