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 its 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)
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