Carlo joins Rohan and Phil to discuss 0.66, and the new Home Assistant release schedule
- New Home Assistant Release Schedule
- 1 Week beta before official release
- 0.66 Release on March 31st
- 0.67 Beta release on April 7th
- 0.67 Release on April 14th
- 0.68 Beta release on April 21st
- Running the beta available for the following platforms
- Docker, using the rc tag
- HASS.IO users can enable the development channel from the system settings
- Pypi, the Python Package Manager service will also have access to the beta, but will require users to specify they want to install the beta version.
- Release notes are available on rc.home-assistant.io
- No change to the Podcast release schedule, we’ll try release episodes on the same weekend Home Assistant releases are made available (not the weekend the betas come out).
- 1 Week beta before official release
- 0.66
- New Platforms
- New Vesync Switch Platform (Etekcity Smart Switches) https://home-assistant.io/components/switch.vesync/
- New cover group platform, similar to the light group https://home-assistant.io/components/cover.group/
- New sensors for the BMW connected drive platform, including binary sensors for doors, windows and door lock status.
- Foobot Air Quality Monitor https://home-assistant.io/components/sensor.foobot/
- Xiaomi MiIO Sensor: Xiaomi Air Quality Monitor
- Stride Notification Platform (Atlassian’s new HipChat)
- Initial support for HomematicIP components
- IFTTT Controlled Security Systems/Alarm Panels https://home-assistant.io/components/alarm_control_panel.ifttt/
- Control Zigbee Fans
- Breaking Changes
- HomeKit gets support for scripts, lights and % sensors. However there are some breaking changes, including a new Homekit start service, and a new default port of 51827 to not conflict with HomeBridge. https://github.com/home-assistant/home-assistant/pull/12997
- Philips Hue: Hue gets an async update by replacing the library used. Existing setups should work with the new library, however if you have manually specified a Hue Bridge in your configuration file, the host key is now required to be set, and point to a valid IP address. The allow_in_emulated_hue setting has also been removed.
- Darksky sensor had an error with the precip_intensity attribute, which has been fixed.
- Z-wave entity IDs are now moved over to the Entity Registry. The old entity_ids will no longer be provided as an attribute of the device in Home Assistant.
- Spotcrime sensor will now require an API key https://home-assistant.io/components/sensor.spotcrime/
- System monitor will now report swap in MiB instead of GiB
- Other Changes
- Glances sensor can now measure running docker containers, CPU use, and memory use.
- Sensibo devices can now be controlled via the Entity Registry
- Downloader component can now send an event to Home Assistant to trigger things like Notifications or flashing lights when a download is complete
- Darksky sensor can now specify the language for weather data
- u/joshmaxd on Reddit noticed a PR from Paulus for the Google Assistant integration with Home Assistant Cloud. Expect to hear more about that in a future release. However setup should be the same as the Amazon Echo.
- New Platforms
- Today’s Guest – Carlo
- Previous Episode with Carlo, episode 4: https://staging.hasspodcast.io/ha004
- BearStoneHA