Download Home Assistant 0.66.1

Release 0.66.1

• Update frontend to fix climate and chart issues
• Fix mqtt_json color commands
• Add pincode fallback
• Fix mysensors sensor type lookup

0.66: VeSync switches, HomematicIP, and a group cover.
This is the first release with our new release schedule. During the extra week we had a total of 4 beta releases with a total of 26 fixes. So this is the most stable release yet!
It is also a release that is full of goodies. 80 people contributed over 223 fixes, improvements and new integrations during the last two weeks of this release ? I want to highlight the work of two people who are doing an amazing job: @NovapaX has a great job and weird quirks and bugs in the frontend. And I want to give a shout out to @armills who has enabled backend translations. This means that you can translate. We’re planning some cool things with this!
A quick note if you are using Philips Hue and Hue custom component: it will no longer be the Hue platform. Remove the custom component to ensure that your Hue lights keep working.
New Platforms

• Add new platform for VeSync switches
• HomeKit Restructure
• Added cover.group platform (replaces # 12303)
• Add additional sensors for BMW ConnectedDrive
• Homekit: New supported devices
• Adding Foobot device sensor
• Added Stride notification component
• Xiaomi MiIO Sensor: Xiaomi Air Quality Monitor (PM2.5) integration
• Add initial support fo HomematicIP components
• Support for security systems controlled by IFTTT
• Zigbee fan [19659004] Adding a discoverable Samsung Syncthru Printer sensor platform
• Add trafikverket_weatherstation sensor platform
• Security fix & lock for HomeMatic

Breaking Changes

• Refactor Hue: If you specify a bridge in your config, the host key is now required and needs a valid ip address. Option allow_in_emulated_hue has been removed. Exclude the lights via the emulated hue config. Due to the internal changes of the Hue integration works, any Hue custom component will no longer work.
• Z-Wave: In version 0.47, the opt-in new_entity_ids configuration was added to Z-Wave change. Support for old entity IDs is now removed, and the configuration is no longer necessary. If you are migrating from 0.63 or higher, your entity IDs will be stored in the Entity Registry and no changes are required. If not, entity IDs can now be configured using the Entity Registry if necessary
• Spotcrime sensor: This update changes the sensor to require a user’s command API key as a configuration entry. The default key has been removed from the Spotcrime package and has also been modified to accept a user’s supplied API key.
• Smappee sensor: Fixed SI units for current consumption. Total consumption should be in kWh. not kW
• System monitor sensor: used and available swap space reported by the system monitor component is now measured in MiB instead of GiB
• HomeKit: The pincode parameter is deprecated, since the HomeKit component will now generate one for you and display it as a persistence notification during setup. Additionally the default port changed to 51827 to avoid potential conflicts with homebridge. Lastly to fix a major bug, we needed to change the way ids are generated. This means that in turn all previous settings settings will need to be repeated. To avoid future conflicts, it is highly recommended to remove the Home Assistant.
• Tibber: The name and the origin of the Tibber sensor will be the same as the nickname. app. Default nick name is the address. If you have not changed the nickname in the app, everything should be before
• Darsky sensor: Fix the incorrect unit of measurement for the ‘Precip Intensity’ and ‘Daily Max Precip Intensity’ for IS units according to the dark sky api documentation.
• HomeMatic: Locks are now under the lock component.