2021.2:Z-Wave... JS!

亲爱的读者:

通常我会写一小段开场,回顾这个月的发布,也顺便加入一点自己的感受。但这一次,我一时之间真的不知道该怎么开口……

当然,这次加入了非常棒的 DHCP 发现功能!还有一些超实用的新蓝图选择器,以及大量 UI 微调!但说真的……

你听说 Z-Wave JS 了吗?!

这个月,一大群开发者突然集结,硬是在短时间内做出了一个全新的、完整的、快速的、流畅的、漂亮的 Z-Wave 集成!🤯

所以,真的非常感谢大家!这份成就几乎难以用语言形容;你们太强了 ❤️

祝你享受这次发布!

../Frenck

Erik Montnemery 加入 Nabu Casa

今天,我们很自豪地宣布 Erik Montnemery 已加入 Nabu Casa,开始全职参与 Home Assistant 项目。

你可能更熟悉他的 GitHub 名字 @emontnemery,或者他参与维护的一些集成,比如 CastTasmotaMQTT

很高兴你加入我们,Erik,欢迎!

停止支持 Python 3.7,支持 Python 3.9

我们已经移除了对 Python 3.7 的支持,因此运行 Home Assistant Core 所需的最低 Python 版本现在提升到了 Python 3.8。自 Home Assistant Core 0.116.0 起,Python 3.7 就已经被标记为弃用。

只有在你直接在 Python 环境中运行 Home Assistant Core 时,这件事才需要你关心。如果你使用的是 Home Assistant OS、Supervised 或容器安装方式,就不用担心,因为 Home Assistant 项目会为你处理这些细节。

与此同时,也欢迎 Python 3.9!从这次发布开始,Python 3.9 已经获得完整支持并通过测试。

Z-Wave JS

这次发布带来了 Z-Wave JS 集成

这是 Home Assistant 中一个全新的 Z-Wave 集成,由一群超棒的人在短短一个月内打造出来,而且完成度非常高!

越来越多的人开始担心 Home Assistant 中 Z-Wave 的未来;与此同时,Z-Wave JS 项目正在迅速成长,并围绕它聚集起了一个庞大的社区。长话短说:Home Assistant 和 Z-Wave JS 携手合作了!而且还有大量贡献者一同加入!

这个新集成基于与 OpenZWave 集成相同的核心原则:它与 Home Assistant 解耦。 Z-Wave JS 集成不再使用 MQTT,而是通过 WebSocket 连接到一个 Z-Wave JS 服务器。

这意味着,要使用这个新集成,你需要运行一个位于 Z-Wave USB 棒与 Home Assistant 之间的 Z-Wave JS 服务器。运行 Z-Wave JS 服务器有多种方式,可以通过 Docker、 手动部署,也可以直接使用 Home Assistant 插件。

如果你使用的是带 Supervisor 的安装方式,这个插件甚至会自动为你完成设置。

Z-Wave JS 当前状态

新的 Z-Wave JS 集成已经相当完整。从一开始,它就支持以下平台:二元传感器、 温控、遮盖、风扇、灯光、门锁、传感器和开关,连场景也支持!

除此之外,它还快得惊人!⚡️

虽然它发展得非常快,但毕竟还是一个新集成,仍有不少内容正在持续完善中。 当然,毫无疑问也会存在一些 Bug。不过这些问题都会被逐步修复与处理。 如果你遇到问题,请务必在我们的问题追踪器中反馈。

还有哪些内容待完成?可以查看我们的 Z-Wave JS 集成路线图 了解详情。

感谢所有人

多亏了下面这些人的努力,Z-Wave JS 集成才能在短短一个月内正式问世!

没错,这真的是一大群人!能在这么短时间内凝聚起来并完成这一切,实在太惊人了!

旧版 Z-Wave 集成怎么办?

旧的 zwave 集成基于 OpenZWave 1.4,而这个版本已经非常老旧, 上游也早已不再更新。这也意味着,我们很难在未来继续维持它的正常可用状态。

因此,从今天开始,旧版 Z-Wave 已被标记为 弃用

如果你刚开始使用 Home Assistant 和 Z-Wave,我们已经不再推荐使用 zwave 集成。 对于现有用户,我们建议迁移到 Z-Wave JS 集成。 不过也别慌,zwave 目前只是弃用,并没有被移除。我们暂时也没有计划移除它, 除非它未来已经无法继续适配最新版本的 Python。

OpenZWave Beta 集成怎么办?

一年多以前,Home Assistant 开始投入开发 OpenZWave 集成。 它基于 OpenZWave 1.6 与 OZW 守护进程,并使用 MQTT 作为传输方式。 这个项目原本很有前景,我们也为它投入了大量时间与精力。

但遗憾的是,OpenZWave 项目本身逐渐陷入停滞,因为上游的大部分开发工作都由同一个人承担: Justin Hammond(Fishwaldo)。

不少人都对 OpenZWave 活跃度下降表示担忧。 Justin 也曾在我们的论坛上回应过他生活中的近况,而读完后会让人很难过, 因为有太多人在个人层面上对他造成了负面影响。

Is OZW Dead - No. I’ll tinker with it, I’ll make changes as time allows, but it will be at my own pace, to scratch my own itches now.

坦白说,OpenZWave 是一个已经走过 11 年的项目,在这个世界上被大量系统所使用 (不只是 Home Assistant),而且拥有极其出色的历史积累。所以:

Thank you Justin for all you have done in all those years!

原本在开发 OZW 集成的团队,如今已经把重心转向新的 Z-Wave JS 集成。 我们认为 OpenZWave 集成大概率不会结束 Beta 阶段,因此建议 Home Assistant 用户迁移到 Z-Wave JS 集成。

自动生成的仪表板不再显示徽章

If you are using an auto generated Lovelace 仪表盘, you probably always had a ton of badges on the top of your 仪表盘. If there are just a few it works, but as more start to appear, it soon becomes cluttered.

Screenshot of the old badges clutter Screenshot of the old badges clutter that is now gone!

We decided to no longer use badges in the auto generated Lovelace 仪表盘. Instead, every 实体 is neatly grouped by 区域 or domain in an 实体 卡片.

If you liked the badges, you can always take control of your 仪表盘 and add them.

DHCP 发现

Home Assistant now listens on your network for 设备 that request a IP address. Based on those intercepted messages, Home Assistant can now discover 集成 for you to use with the discovered 设备.

This really powerful addition has been made by @bdraco, and many 集成 have quickly enriched their 集成 to use this new discovery method.

So as of this 发布, your Home Assistant might actually find some new 设备 it can use! Thanks @bdraco!

新的蓝图选择器

For our 蓝图 fanatics, some new goodies to the 蓝图 has been added this 发布. Thanks to @thomasloven, we now have two new selectors:

Screenshot of the new text selector Screenshot of the text selectors.

  • An object selector: Shows an YAML editor in the UI.
  • An text selector: Show a single line text input or text 区域 for longer messages in the UI.
  • 蓝图 descriptions now support Markdown.

Screenshot of new object selector Screenshot of the object selector, giving a YAML input field.

Cloud 文本转语音设置

Nabu Casa has been offering an amazing text-to-speech 服务 for a while now, yet it was hard to find, and even harder to 设置 and use.

To fix this, a new 设置 UI has been added where you can select the default language and gender to use for the text-to-speech 服务, so you no longer have to attach that to every 服务 call. You can find it in the Home Assistant Cloud 面板.

Screenshot of Cloud TTS options Screenshot of Cloud TTS options.

We also added the ability to try the chosen 设置 right in your browser. Click the try 按钮, enter some text and click play to hear the text being spoken.

其他值得注意的变化

这次发布虽然没有特别重磅的新功能,但依然包含了不少值得一提的调整与优化。

  • We now give you a clearer reason why your Lovelace 卡片 配置 is not supported in the UI editor thanks to @spacegaier.
  • Shelly RGB 设备 are now fully supported!! Nice @chemelli74!
  • @dmulcahey Added filtering and zoom to node to the ZHA network visualization. Very useful to find you Zigbee network issues.
  • The deCONZ 集成 added support for logging basic event in the logbook. Nicely done @Kane610.
  • The Tasmota 集成 is out of beta! Awesome @emontnemery!
  • @spacegaier Added support for themes on the media 卡片.
  • The items in the shopping list 卡片 can be ordered using drag & drop! Thanks @ShaneQi!
  • Newly ignored discovered 集成 now show a name of the item ignored. This makes it easier to undo that later.
  • @balloob made a new framework that can detect significant changes in 实体, allowing to reduce the amount of 更新 we need to send to both Google Assistant and Alexa!
  • Setting up Lutron Caseta was quite a pain, but not anymore! @bdraco added one-touch pairing to the 集成 set up!
  • If you use 灯光 profiles, @Adminiuga is your man. All parameters of a 灯光 profile can now be optional and default profiles are always applied.
  • Dropdown 助手 (input_select) got some new 服务 capabilities added by @l-mb. They can now cycle through the options, and 服务 calls to jump to the first or last item have been added as well.
  • If you have a Foscam 摄像头, @joe248 added a 服务 to move to PTZ presets.

新集成

我们欢迎以下新集成加入这次发布:

新平台

以下集成新增了平台支持:

现已支持通过 UI 设置的集成

以下集成现已可通过 Home Assistant UI 进行设置:

发布 2021.2.1 - February 5

发布 2021.2.2 - February 9

发布 2021.2.3 - February 11

如果你需要帮助……

如果你需要帮助,欢迎前往我们非常活跃的 论坛,或加入我们的 Discord 聊天

如果这次发布带来了问题,请到我们的 问题追踪器 提交反馈,并确保完整填写 issue 模板中的所有字段。

向后不兼容的变更

下面列出了本次发布中的破坏性变更,并按主题或集成分类。 点击其中任一项,即可阅读该项目对应的破坏性变更详情。

Python 3.7 支持

Support for Python 3.7 has been dropped, after being deprecated since Home Assistant 0.116.

This is only a concern if you are running Home Assistant 核心 directly on Python. You can check the Python 版本 Home Assistant uses by going to the information screen in 配置 -> Info.

If you run Home Assistant OS, 受监管模式 or 容器, you don’t have to worry about this, as the Home Assistant project takes care of this for you. As a Matter of fact, if you use one of those methods, you are already running Python 3.8.

(@frenck - #43805)

Z-Wave 集成

The old zwave 集成 is now considered legacy and deprecated. This 集成 is still based on OpenZwave 1.4, which has been out of active maintenance for quite some time now.

Alternatively, you can move to one of the other Z-Wave solutions Home Assistant offers:

  • OpenZWave (currently not maintained)

  • Z-Wave JS (introduced in this 发布, recommended)

PTVSD 调试器

The PTVSD extension has deprecated a couple of releases back and is now removed. The debugpy 集成 is a full replacement for 此integrations.

(@frenck - #44748)

Tado 集成

Tado's primary functionality has fully transitioned to 配置 via UI. YAML 配置 has been removed except for device_tracker. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

The device_tracker platform continues to use YAML, and will be updated at a later date when the 设备 tracker platform is modernized.

Tado 区域 传感器 have been replaced by their corresponding binary_sensors. Therefore, you'll have to 更新 Lovelace 面板, 脚本 and 自动化 referring to the following 传感器 by their corresponding 二元sensor (replace sensor with binary_sensor):

  • sensor.ZONE_early_start is replaced by binary_sensor.ZONE_early_start
  • sensor.ZONE_link is replaced by binary_sensor.ZONE_link
  • sensor.ZONE_open_window is replaced by binary_sensor.ZONE_open_window
  • sensor.ZONE_overlay is replaced by binary_sensor.ZONE_overlay
  • sensor.ZONE_power is replaced by binary_sensor.ZONE_power

The following 状态 属性 have been removed:

  • sensor.ZONE_overlay: termination
  • sensor.ZONE_open_window: open_window_attr

(@Noltari - #44576) (@bdraco - #45384) (tado docs)

KNX 集成

Some knx_events changed the name of event_data fields:

  • address renamed to destination
  • Added source
  • Added direction
  • Added telegramtype

Additionally:

  • fire_event in the knx 配置 is deprecated.
  • fire_event_filter in the knx 配置 is renamed to event_filter.

(@farmio - #44749 #45248) (knx docs)

RainMachine 集成

RainMachine 服务 now require an entity_id, an area_id, or a device_id parameter to be provided. You need to check your 自动化 to make sure all RainMachine 服务 calls have those.

(@bachya - #44139) (rainmachine docs)

ecobee 集成

The current 状态 of the ecobee 集成 always behaves as if the selected hold duration is Until next scheduled activity.

With this change the following 设置 are now respected:

  • 2 hours
  • 4 hours
  • Until I change it

If you rely on the previous behavior may need to 更新 your 自动化 to account for the support for the new 设置.

(@jamincollins - #40520) (ecobee docs)

August 集成

August has fully transitioned to 配置 via UI. YAML 配置 will be removed in an upcoming 版本. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45039) (august docs)

Roomba 集成

Roomba has fully transitioned to 配置 via UI. YAML 配置 is no longer supported. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45037) (roomba docs)

Plex 集成

The plex.play_on_sonos 服务 has been removed and functionality moved to the built-in media_player.play_media 服务.

Existing 服务 payloads can be used as-is after prepending the media_content_id with plex://.

(@jjlawren - #45066) (plex docs)

Lutron 集成

The Lutron Integration ID 属性 changed to lutron_integration_id, so any 自动化, 模板 传感器, etc. using that 属性 will need to be updated accordingly.

(@TimothyLeeAdams - #45114) (lutron docs)

DoorBird 集成

DoorBird has fully transitioned to 配置 via UI. YAML 配置 will be removed in an upcoming 版本. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45139) (doorbird docs)

Logitech Harmony Hub 集成

Harmony has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45140) (harmony docs)

Mikrotik 集成

Mikrotik now uses the device_tracker standard 属性 for ip and mac. The mac_address and ip_address 属性 have been removed.

(@bdraco - #45255) (mikrotik docs)

RoonLabs 音乐播放器

This PR changes how the play_media call works for roon players. The previous implementation was very limited - but anyone using it in 自动化 will need to change their calls to the new structure.

Please refer to the 集成 文档 更多信息.

(@pavoni - #45221) (roon docs)

Network UPS Tools(NUT)

Network UPS Tools (NUT) has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45276) (nut docs)

Dyson 集成

The speed of the Dyson Pure Cool Link 风扇 is now one of low, medium, and high instead of the original auto and integer 1 to 10.

In order to set the 风扇 speed more precisely and 开关 auto mode, you should use the 服务 dyson.set_speed and dyson.set_auto_mode.

(@shenxn - #45331) (dyson docs)

Viessmann ViCare 集成

The current power 传感器 has been removed since it was not provided by the Viessmann API anymore.

(@oischinger - #45301) (vicare docs)

MyQ 集成

MyQ has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45375) (myq docs)

Nexia 集成

Nexia has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45379) (nexia docs)

Hunter Douglas PowerView 集成

Hunter Douglas PowerView has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45376) (hunterdouglas_powerview docs)

Rachio 集成

Rachio has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45383) (rachio docs)

Tesla Powerwall 集成

Tesla Powerwall has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45381) (powerwall docs)

灯光配置文件

Nominally a breaking change. A default profile for the 灯光, now is always applied, so controlling a 灯光 from UI would set all the parameters defined in the profile.

For example, if the default profile for a particular 灯光 is set to:

  • Color: Green
  • Brightness: 255
  • Transition: 5

And the current 灯光 status is: Color - red, brightness - 20 and in UI you change the brightness to 100 with the intention to only change the brightness, then the default profile would also apply the color and transition.

(@Adminiuga - #45450) (灯光 docs)

MQTT 集成

MQTT allowed passing an arbitrary speed that was not in the speed_list.

With the conversion to percentages in upcoming releases, this aberration from the spec could not be converted to a percentage. Since it does not conform to the 实体 model, it is not possible to preserve this exception.

(@bdraco - #45445) (MQTT docs)

NuHeat 集成

NuHeat has fully transitioned to 配置 via UI. YAML 配置 has been removed. Existing YAML 配置 has already been imported automatically in the previous releases and can now safely be removed from your 配置 files.

(@bdraco - #45380) (nuheat docs)

Rheem EcoNET 热水设备

EcoNET has swirtched over to EcoNET's new API.

热水器 will no longer report current tank temperature. The add/remove vacation 服务 are also removed, alternatively, you can use away mode now.

(@w1ll1am23 - #44427) (econet docs)

意图

The method for matching 实体 in intents has changed slightly to prefer shorter matches before ordering.

This means some intents and/or 实体 names may need to be adjusted to maintain consistency in some edge cases. For most uses, this should only improve the quality of matches.

(@CtrlZvi - #43672)

Obihai 集成

The last_caller_info 传感器 now has the leading '' (quotes and space) removed as those were not needed and were randomly provided by the Obihai 设备.

So previously the 状态 would be '' 8185551212 now it is 8185551212

(@dshokouhi - #44768)

告别以下内容

以下集成已被移除:

所有变更

点击查看所有变更!