0.66: VeSync switches, HomematicIP, and a group cover.

17 minutes reading time
  • Release-Notes

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 should be the most stable release yet!

It’s also a release that is full of goodies. 80 people contributed over 223 fixes, improvements and new integrations during the last 2 weeks of this release 😎 I want to highlight the work of two people who are doing an amazing job: @NovapaX has been doing a great job triaging and fixing 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 a bunch of things that did not have translations yet, will now soon be translatable. We’re planning some cool things with this!

A quick note if you are using Philips Hue and a Hue custom component: it will no longer work due to the internal changes to the Hue platform. Remove the custom component to ensure that your Hue lights keep working.

New Platforms

Release 0.66.1 - April 1

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

  • Refactor Hue: If you specify a bridge in your config, the host key is now required and needs to be 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 how the Hue integration works, any Hue custom component will no longer work. (@balloob - #13043) (hue docs) (light.hue docs) (breaking change)
  • Z-Wave: In version 0.47, the opt-in new_entity_ids configuration was added to Z-Wave to smooth the transition through the 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 already be stored in the Entity Registry and no changes are required. If not, entity IDs can now be manually configured using the Entity Registry if necessary. (@armills - #12652) (zwave docs) (breaking change)
  • Spotcrime sensor: This update changes the sensor to require a user supplied 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 supplied API key.(@jcconnell - #12926) (sensor.spotcrime docs) (breaking change)
  • Smappee sensor: Fixed SI units for current consumption. Total consumption should be in kWh. not kW. (@vandenberghev - #13190) (sensor.smappee docs) (breaking change)
  • System monitor sensor: Used and available swap space reported by the system monitor component is now measured in MiB instead of GiB. (@DanNixon - #13148) (sensor.systemmonitor docs) (breaking change)
  • 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 accessory ids are generated. This means that in turn all previous accessory settings will need to be repeated. To avoid future conflicts, it is highly recommended to remove the Home Assistant Bridge from the Home app and repeat the setup process. (HomeKit Setup) (@cdce8p - #12997) (homekit docs) (breaking change) (new-platform)
  • Tibber: The name and the entity id for the Tibber sensor will now be the same as the nickname from the app. Default nick name is the address. So if you have not changed the nickname in the app, everything should be as before. (@clementhk - #13231) (sensor.tibber docs) (breaking change)
  • 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.(@cgtobi - #13415) (sensor.darksky docs) (breaking change)
  • HomeMatic: Locks are now under the lock component (@PH89 - #11980) (homematic docs) (lock docs) (lock.homematic docs) (breaking change) (new-platform)

All changes