0.71: Lagute LW-12, Iperf3, Hydrawise, Ryobi Garage Doors

Blog
1

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

0.71 has arrived. My favorite feature in this release is the conversion of the Nest component from cloud poll to cloud push. Sure, it’s still through the cloud but changes are now made available in Home Assistnat as soon as they happen. Thanks @awarecan!

We’ve continued the frontend tweaks after the major overhaul in the last release. We’ve had some issues with the Hass.io panel on both Firefox and Safari. They have been addressed and all browsers should hopefully work again.

On the frontend side, custom panels have gotten some new tricks, including support for building panels using React. So if you’re a developer, check it out. And thanks to @c727 a lot more strings can now be translated. More info on how to help with translating the frontend can be found here.

HomeKit support also keeps growing. This release includes support for media players, automations and outlets thanks to @schmittx.

And in case you missed it, @OttoWinter has created esphomeyaml, which allows you to program and deploy ESP chips throughout your house by using a Home Assistant inspired configuration.yaml. Check it out.

Have a good weekend everyone!

New Platforms

New Features

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

  • BOM sensor: 'Wind Direction kt' to 'Wind Speed kt' (fixes #14535) (@fabaff - #14541) (sensor.bom docs) (breaking change)
  • Removed attribute current_time from Raincloudy sensors to avoid being triggered by recorder component (@tchellomello - #14584) (raincloud docs) (switch.raincloud docs) (breaking change)
  • Remove Notify My Android component as it shut down on May 24 (@cgarwood - #14594) (notify docs) (breaking change)
  • CoinMarketCap sensor: It is no longer possible to query a ticker by the name of the currency (i.e. bitcoin). The API instead uses IDs (integers) for these tickers (i.e. bitcoin -> 1). Rounding of decimals is now configurable, because it made no sense to round to 2 decimals if display_currency was set to BTC, some values showed up as 0.00. (#14437) (@kotlarz - #14604) (sensor.coinmarketcap docs) (breaking change)
  • Give unknown zwave nodes a better name and don’t add them to entity registry (@andrey-git - #14353) (zwave docs) (breaking change)
  • The netdata sensor was re-worked to support all available details from Netdata. This requires you to adjust the your existing configuration if you use the netdata sensor. (@fabaff - #14613) (sensor.netdata docs) (breaking change)
  • Disallow automation.trigger without entity_id. Triggering all automations at once is most likely a user mistake but if it is really needed, one can use entity_id: group.all_automations. (@amelchio - #14724) (automation docs) (breaking change)

Beta Fixes

All changes

This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2018/06/08/release-71/
2 Likes
2

Still getting many pages of requirement notices… Is the Docker image still on the wrong OS?

1 Like
3

Do we have to do anything to upgrade to the new Nest cloud push?

4

No: there are no configuration changes.

5

Sonos players no longer loading for me on 0.71. (Nothing in the notes about sonos that I can see)

Edit: after a couple of restarts it appears that Sonos has loaded now - odd

6

6 posts were split to a new topic: Configuring outlets in HomeKit

7

Also included in this release:

8

For zha users this release adds illuminance, metering and electrical measurement. My Iris smart plugs now report how much power is being used :slight_smile:

If you have a zigbee bulb that reports power you will see that as well.

9

Thanks for this new release.

Special thanks to @cdce8p and @schmittx for all their great work on the Homekit component! It really works awesome :+1:

When using Homekit and having a lot of automations make sure you exclude these in the Homekit settings before upgrading to 0.71. That avoids that Homekit won’t startup because it reached the maximum of devices which happened for me :blush: .

homekit:
  filter:
    exclude_domains:
      - automation
3 Likes
10

Perhaps you should add this tip to the official component documentation? Your fellow users will thank you for it.

11

PR submitted to update the HomeKit docs here.

Thanks @gerard33 for catching this!

1 Like