0.64: Over 1000 integrations! New: HomeKit, BMW, August.

Blog
1

![](upload://gDN6Jw4aYHPqsttcvgdBNze2tJ5.png)

🎉 1000 integrations, 1000 integrations, 1000 integrations! 🎉

That’s right, Home Assistant 0.64 is here! In case you have missed our latest Cloud update, the Home Assistant Alexa skill is now live in all regions and we’re working with Google in getting the Smart Home skill for Google Assistant approved. Exciting times!

In the meanwhile, some great new integrations have landed, including yet another car 🚗 This time it’s BMW.

This is going to be the last release that supports Python 3.4. Starting with the next release, the minimum version required will be Python 3.5.3. Learn more here.

HomeKit

Native HomeKit support has arrived! Thanks to @cdce8p It is now possible to expose some devices over HomeKit to allow control via Siri and other things speaking the HomeKit protocol. Initial support has been added for temperature sensors and cover devices. Expect more devices to be added soon.

Check the HomeKit docs

Hass.io UI update

Some of you already noticed that your Hass.io panel looks a bit different since this morning: @pvizeli pressed the red green button and the new UI got live. The Hass.io team (@frenck @ryanm101) is doing a great job in adding new features (like partial or encrypted snapshots) to the Hass.io backend and fixing bugs. However, those features where only added to the command line tools but not to the frontend.

That’s where @c727 and @ciotlosm jumped in. They made new features accessible via the frontend and improved the overall navigation.

We know that some features are still missing or broken, we are fixing this right now! Check this issue first before you report any issues related to the Hass.io panel, please.

Chart.js

The frontend is now rendering the graphs and charts using Chart.js thanks to the hard work by @fanthos. This means that you can now render all the charts without being connected to the internet!

August integration

Major new integration by @snjoetw: August locks and door bells! Lock and unlock from Home Assistant and detect when your doorbell is rung or senses motion. Awesome!

Cast bug fixes

@OttoWinter has crushed a bunch of bugs for our ChromeCast integration. Including that nasy Cast group discovery issue! He is working on some more improvements that should arrive soon, stay tuned. Awesome work Otto!

New Platforms

Release 0.64.1 - February 27

Release 0.64.2 - March 1

Release 0.64.3 - March 2

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Breaking Changes

  • Home Assistant now defaults to purge recorded history that is older than 10 days. If you want to keep your recorded data for longer than that, you must configure the number of days to retain before starting 0.64 for the first time, for example: 
      recorder:
    purge_keep_days: 30

    If you want to keep the previous default of never deleting history, use this configuration:

      recorder:
    purge_interval: 0

    (@amelchio - #12271) (breaking change)

  • Show a persistent_notification if no symbols and no currencies are configured (@ChristianKuehnel - #12252) (sensor.alpha_vantage docs) (breaking change)
  • Updated RainMachine unique IDs to play better with the entity registry. If RainMachine had been configured previously, new entries will be placed into the entity registry, causing there to be two of each program/zone defined. To address, simply alter the entity_registry.yaml as desired. (@bachya - #12315) (switch.rainmachine docs) (breaking change)
  • Updated AirVisual unique IDs to play better with the entity registry. If AirVisual had been configured previously, new entries will be placed into the entity registry, causing there to be two of each sensor type defined. To address, simply alter the entity_registry.yaml as desired. (@bachya - #12319) (sensor.airvisual docs) (breaking change)
  • Custom component devs only: voluptuous now requires default values for config keys to be valid values. (@balloob - #12463) (breaking change)
  • Fixes usps platform. Dependency myusps now leverages Selenium webdriver to overcome login issues. This is a breaking change since the user must now have additional dependencies installed - either google-chrome and chromedriver, or phantomjs. There is a new config option driver that allows the user to specify their preference, though phantomjs is the default. Doc PR forthcoming that will outline choices and make suggestions based on user’s OS. (@happyleavesaoc - #12465) (usps docs) (breaking change)
  • LimitlessLED has been converted to assumed state. Will no longer turn the lights off when restarting Home Assistant. Will no longer revert changes made by other controllers. (@amelchio - #12475) (light.limitlessled docs) (breaking change)

All changes

This is a companion discussion topic for the original entry at https://home-assistant.io/blog/2018/02/26/release-64/
1 Like