0.90:远程 UI、流媒体与用户分组

Home Assistant 0.90 来了,只能说:太强了。这次发布塞满了各种酷炫内容,多到都不知道该从哪里开始,那我们就直接进入正题吧。

第一个重磅功能是,Home Assistant Cloud 现在支持远程控制了。这让你即使不在家,也能查看家里的情况。收到“检测到移动”的通知?现在你可以立刻查看发生了什么,并在外出时直接采取行动。它采用端到端加密。想开始使用?只需要启用它,就这么简单。

想了解它的工作方式,请查看文档,或收听 Home Assistant Podcast 最新一期

Screenshot of the 遥控器 UI preference. Screenshot of the 遥控器 UI preference.

人人可用的摄像头流媒体

在这个版本里,我们开始认真打磨摄像头能力。 @hunterjm 为此投入了数月时间,现在终于可以首次公开展示了。借助 stream 集成,我们可以转发家中摄像头的视频流,并重新封装成你的显示设备能够理解的格式。此前,摄像头流媒体仅限前端使用,而且只有每秒 2 帧。第一版我们重点支持的是 HLS 格式,现代浏览器和 Chromecast 都支持它。每个摄像头集成都需要单独适配,而在首个版本中,我们目前只为 generic 摄像头集成加入了支持。

那现在能做到什么?比如门铃响起时,你可以立刻把前门摄像头画面投到电视上;又或者在婴儿房安装一个摄像头,把 Google Home Hub 变成婴儿监视器。

要开始使用,请在 configuration.yaml 中加入 stream:,配置 generic 摄像头,然后开始使用新的 camera.play_stream 服务。

用户分组

这是一个酝酿和开发了很久的功能:你现在可以把用户加入分组,从而阻止他们通过 UI 修改配置。被放入新“用户”组的用户将不会看到配置面板或开发者工具的入口。当前这还只是一个 UI 层面的功能,并不是安全特性。我们正在努力把它扩展为真正的安全能力,也就是在 API 层面限制访问。

更聪明的 SmartThings

如果你使用 Home Assistant Cloud,设置 SmartThings 时现在会自动利用 Cloudhooks。这意味着你无需把实例暴露到互联网就能开始使用 SmartThings。设置更简单了,感谢 @andrewsayre!SmartThings 现在还新增了对三轴传感器和空调设备的支持。

区域增强

这个版本也进一步增强了区域功能。感谢 @Swamp-Ig,当你把 Home Assistant 同步到 Google Assistant 时,区域现在会作为房间提示一并带过去,这会让设置变得更加轻松。

区域 can now also be used as targets in 服务. Just specify area_id instead of entity_id in your 脚本 or 自动化.

我们还把区域整合进了集成的设置流程。添加集成时,我们会检查新增了哪些设备,并立即提示你进行配置,这样你就不会忘记了。

VSCode 扩展

如果你错过了这个消息,本周早些时候 Kees Schollaart 发布了他的 VSCode Home Assistant 扩展首个版本。它可以连接到你的实例,并在你编辑配置时提供实体 ID 自动补全!

新平台

发布 0.90.1 - March 21

发布 0.90.2 - March 26

如果你需要帮助……

欢迎使用我们非常活跃的论坛,或者加入我们的聊天频道。虽然发布说明开放评论,但我们更希望你使用前面这些沟通渠道。谢谢。

反馈问题

如果你遇到了这个版本引入的问题,请在我们的 issue tracker 中报告。请务必填写 issue 模板中的所有字段。

向后不兼容的变更

  • http.api_password - Deprecated - 用户 who are still using api_password for 认证 will need to move its 配置 under auth_providers. Please see the updated 文档 for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant 日志 until the fix is made for a time, but please note, api_password 认证 will eventually be removed completely and we advise 用户 to change to use one of the other authentication methods. If you manually specify auth providers in your configuration.yaml, you will need to migrate your API 密码 from the http section to the auth provider section to continue using it. (@awarecan - #21884) (api docs) (前端 docs) (hassio docs) (http docs) (MQTT docs) (websocket_api docs) (zeroconf docs) (摄像头.proxy docs)
  • Default Config - Default config no longer contains the discovery component. That is now part of the initial written 配置.yaml. If you rely on default config and want to use discovery, add discovery: back to your 配置.yaml.
  • Netatmo
  • Utility Meter - Currently the offset 配置 parameter is an integer that limits daily cycles to have offsets in days, monthly cycles to have offsets in months, etc. This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the updated 文档 for the new 配置 options. (@dgomes - #20926) (utility_meter docs)
  • KNX - An 更新 for xknx to 版本 0.10.0 requires 用户 to 更新 their 配置 by changing target_temperature_address to target_temperature_state_address. Other fixes and features:
    • Connection config can now be configured in xknx.yml.
    • Introduce a configurable rate limit which limits the number of KNX telegrams sent to the bus per second.
    • 用户 who configured their 灯光 via xknx.yml no longer need to manually set min_kelvin and max_kelvin (fixes #21251) (@marvin-w - #21541) (knx docs)
  • Nanoleaf - The Nanoleaf component now supports both nanoleaf 灯光, Aurora and Canvas. As a result of this change the 用户 needs to change the platform from nanoleaf_aurora to nanoleaf (@Oro - #21913) (灯光.nanoleaf docs)
  • FireTV- is now androidtv. Instead of having near-duplicate 集成 for androidtv and firetv, the decision was made to combine them into one. 用户 will need to change - platform: firetv to - platform: androidtv in their 配置. (@JeffLIrion - #21944)
  • Tellstick - Some 配置 cleanup. The way Tellsick 传感器 配置 was set up using dynamic values for named 传感器 will not be supported in future versions of Home Assistant. 用户 that have configured the optional named 传感器 initiated with only_named will have to 更新 their 配置. Make sure to check the updated 文档 for further details. (@endor-force - #21402) (tellstick docs)
  • MQTT - Pass Message object to MQTT message callbacks instead of topic, message and qos. 用户 of custom components please take note, these values are now available on the passed in message object: msg.topic, msg.message, msg.qos. The old method will continue to work for now but will print 警告. (@emontnemery - #21959) (MQTT docs)

Beta 修复

所有变更