Homeassistant

_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

Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we've been hard at work to introduce config validation! Especially huge thanks to jaharkes for his hard work on this. Config validation is still in it's early stages. More common platforms and components have been added but we didn't do everything yet.

When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We're looking into options to make it more clear - it is a work in progress.

Another big thing is the addition of GTFS support. You probably don't know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.
- Config validation (balloob, jaharkes)
- Sensor: GTFS support (public transit open standard) (robbiet480)
- Camera: Raspberry PI support added (LucaSoldi)
- Z-Wave: improved startup reliability (srcLurker)
- Media Player: Onkyo receiver now supported (danieljkemp)
- Sensor: Loop Energy now supported (pavoni)
- Thermostat: Z-Wave now supported (coteyr, turbokongen, luxus)
- Sensor: NZBGet now supported (justyns)
- Media Player: Panasonic Viera TV now supported (florianholzapfel)
- Thermostats: Use whole degrees if user uses Fahrenheit (JshWright)
- Frontend: more material love (balloob)

Breaking changes

As of now we are not aware of any breaking changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to `execute_service` in their script configs. This should be `service`.

- Device Tracker - iCloud: Revert upgrade of pyICloud because it was breaking for users.