title: '0.97: Apache Kafka, Fortigate, Twente Milieu' description: '<a href=''/home-assistant/integrations/版本/0.97''<img src=''/home-assistant/images/blog/2019-08-0.97/components.png'' style=''border: 0;box-shadow: none;''</a。' 重新加载 场景 服务 has been introduced.

    0.97: Apache Kafka, Fortigate, Twente Milieu

    It's time for Home Assistant 0.97! It has been a very busy 发布 cycle as we have been fine-tuning our development process, which makes it easier to maintain and contribute to Home Assistant in the future.

    已移除 Python 3.5 支持

    As per previous announcements, this is the first 发布 that requires at least Python 3.6. If you are on Hassbian and are planning to 升级 Python, please take note of the 已知问题 with the default wheel server.

    Docker

    This is the last 发布 that bases our Home Assistant Docker 图像 (homeassistant/home-assistant) on Debian. As decided in Architecture Decision Record 0006: Docker Images, the 图像 will be based on Alpine Linux starting with the 0.98 发布. These new Docker 图像 will be running same the Home Assistant Docker 图像 that powers Hass.io. You don't need to change anything unless you have 已安装 Debian packages manually or made any other changes to the running 容器. However, if that is the case, you'll need to find the Alpine equivalent of whatever you were doing.

    The main driver behind this change is that by re-using 图像, maintenance becomes easier, and 用户 of the homeassistant/home-assistant 图像 can benefit from the many optimizations that went into the Hass.io 图像.

    重载 场景 from configuration.yaml

    Thanks to @balloob it is now possible to 重载 场景 from configuration.yaml without restarting Home Assistant. This is part of an effort for Home Assistant 1.0 to make 场景 a first-class citizen of Home Assistant, including creating/restoring 场景 on the fly in the future. To track this effort, follow this page.

    Home Assistant Cast

    In case you missed the announcement, we released Home Assistant Cast yesterday. It allows you to transform any Cast interface into a display for Home Assistant. Read the announcement 更多信息..

    Picture of a Google Nest Hub with the Home Assistant UI on it.

    Home Assistant Cast opens a whole new world of possibilities for using Lovelace, and we are really excited to learn what cool things you will do with it! If you 创建 something, feel free to share it on social media using the #homeassistantcast hash-tag. We are looking forward to your pictures!

    UI 变化

    This 发布 contains a couple of notable UI changes:

    • New Cast row available in the Lovelace 实体 卡片 to start Home Assistant Cast.
    • Improved accessibility for visually impaired 用户. This is an ongoing effort on making the 前端 accessible.
    • Split out configuration.yaml 动作 from the 核心 配置 into a new server control config 面板. Thanks @IcyPalm
    • Markdown 卡片 now has a size + 1, if it has a header defined. Some layouts might be moved around due to this.

    其他消息

    Frenck wrote an excellent 博客 post on how to make a $2 smart doorbell using Home Assistant and ESPHome, which doesn't require soldering.

    Aaron 创建 a great and detailed 教程 explaining how to add an interactive 3D floorplan to Home Assistant.

    We wrote about how we use Azure DevOps to automate the development of Home Assistant. Interested to see how Home Assistant is automatically build? Check the developer 博客.

    @jimz011 has updated his amazing, HomeKit inspired, Lovelace config and shared it on the forums. Sneak preview on how it looks:

    New 集成

    发布 0.97.1 - August 9

    A new breaking change was introduced with 0.97.1 to accommodate for the HaveIBeenPwned shutting down v2 of their API on August 18. The 集成 has been migrated to using v3.

    发布 0.97.2 - August 11

    如果你需要帮助……

    ……欢迎随时使用我们非常活跃的论坛，或者加入我们的 聊天频道。

    反馈问题

    如果这次发布引入了问题，请前往我们的 issue tracker 提交反馈。请务必填写 issue 模板中的所有字段。

    Backward-incompatible changes

    • Python - Bump Python support to min Python 3.6.0 (@balloob - #25582)

    • Z-Wave - Improve handling of Z-Wave config entry vs yaml config. If a Z-Wave network_key is specified in 配置.yaml it will override a network_key specified in the Z-Wave config entry. (@cgarwood - #25112) (zwave docs)

    • Unifi - Unifi 设备 tracker is now part of config entry. After initial import the unifi 设备 tracker 配置 is no longer needed. If configuring SSID filter or detection time you will need to use the new 配置 from UniFi. See UniFi component 文档 for details. (@Kane610 - #24367) (unifi docs)

    • Ecobee - Ecobee presets now represent the different Ecobee comfort 设置. Selectable by name instead of unknown ID. (@balloob - PR link todo)

    • 日历 - Rewrite 日历 component - The 日历 集成 has been rewritten to follow our current standards and is mostly non breaking. The reset (clean up) of 状态 属性 upon an event time passing has been removed, though. 属性 are no longer set to an arbitrary default value, and will now keep the 属性 representing the last event. With this change, 自动化 that rely on 状态 属性 getting reset will need to be updated. All platforms have been converted. - (@MartinHjelmare - #24950) (caldav docs) (日历 docs) (demo docs) (google cal docs) (todoist docs)

    • SyncThru - The monitored_conditions 配置 option has been removed. All available monitored 条件 will be used by default. 用户 that have been using the monitored_conditions option need to remove it from the syncthru section in 配置.yaml. (@nielstron - #25052) (syncthru docs)

    • KNX - Updates the knx component to use xknx 0.11.1 . This introduces several new features and bugfixes. For a complete list see: https://github.com/XKNX/xknx/releases/tag/0.11.0 (@farmio - #24738) (knx docs)

      • scene: scene_number is now 1 indexed according to KNX standards. Previously it was 0 based. Please add 1 to your already configured 场景 numbers (scene_number: 5 becomes scene_number: 6).
      • sensor: state_address replaces address in 配置
      • binary_sensor: state_address replace address in 配置 when using xknx config file (knx: config_file = ...): Replace group_address in BinarySensor and 传感器 with group_address_state.

    • RitAssist - The company has been renamed from RitAssist to FleetGO, so this component needed to get renamed. 用户 of 此integrations will need to 更新 their device_tracker config section to use the new name. (@depl0y - #25093) (fleetgo docs) (ritassist docs)

    • N26 - Adds support for multiple N26 accounts. The generation of unique ids for spaces has been changed. 用户 may need to remove the stale old id 实体, representing spaces, from the 实体 registry. (@gorynychzmey - #25086) (n26 docs)

    • Environment Canada - This change removes the monitored_conditions and name options and adds an optional language option. 传感器 are now 创建 for all provided data. (@michaeldavie - #24884) (environment_canada docs)

      sensor:
  - platform: environment_canada
    language: french

    • TotalConnect - Total Connect Client was upgraded to support more than one 报警 面板 and allow future support for additional 传感器. Previous alarm_control_panel entries must be removed, and a new totalconnect entry must be added to 配置.yaml. See </integrations/totalconnect/> for 配置 details. (@austinmroczek - #24427) (totalconnect docs)

    • Nuki - The lock.nuki_unlatch 服务 has been removed. It has been replaced by the lock.open 服务. The lock.nuki_lock_n_go 服务 has been renamed to nuki.lock_n_go. 用户 that are using the removed or renamed 服务 in 自动化 need to replace them with the new 服务. (@franfos - #22888) (nuki docs)

    • Snapcast - This changes adds multiroom support for the snapcast component. It adds 2 服务 media_player.snapcast_join and media_player.snapcast_unjoin to group/ungroup a client with another client. Also added source selection support in the snapcast clients as the groups are unusable due to their dynamic nature. (@lyghtnox - #24061) (snapcast docs)

    • Ambient 天气 Station - The unique_id for Ambient 传感器 uses a new formula, meaning that even though they have the same friendly names, new 传感器 will be 创建. The 集成 will automatically perform this migration under the hood, but if you've altered the 实体 IDs of any Ambient PWS 实体, you'll need do the same to the new 实体 upon creation. Additionally, the monitored_keys 配置 option is no longer supported in configuration.yaml. The 集成 will now create 传感器 for all 条件 supported by the particular 设备. (@bachya - #25284) (ambient_station docs)

    • Google Maps - Google Passwords are no longer required to be provided in your config. An external program is now required to obtain the necessary cookie file to place in your Home Assistant config directory. This is due to the 认证 process being removed from the underlying package. Existing 用户 should remove the password: entry from their config file (username is still required). The cookie file previously generated should still be valid and will allow the tracker to continue functioning normally until the cookie is invalidated. New 用户 will need to follow the instructions on the Google Maps Location Sharing page to create their cookie file.(@shbatm - #25316) (google_maps docs)

    • BuienRadar - Updates to the new 版本 of python-buienrader (1.0.1); this 版本 now leverages the new json buienradar-api. (@mjj4791 - #24463) (buienradar docs)

      The following 传感器 types (monitored_conditions) are no longer supported, since they are no longer provided by the json api of buienradar:

      • snow_1d .. snow_5d

      The following monitored 条件 will change units:

      • windgust (now km/h, was m/s)
      • windspeed (now km/h, was m/s)
      • windspeed_?d (now km/h, was m/s)
      • visibility (now km, was m)

    • Rejseplanen - Improve and align Rejseplanen with other transport components. (@DarkFox - #25375) (rejseplanen docs)

      • All 属性 changed to snake_case.
      • Later departure 属性 has been removed.
      • Added next_departures which contains a list of all later departures returned from the search, as dictionaries with the same fields as the next departure.

      Any existing 模板 using the 传感器's 属性 will need to be updated as follows:

      • Stop ID -> stop_id
      • Stop -> stop
      • Route -> route
      • Type -> type
      • Direction -> direction
      • Due in -> due_in
      • Due at -> due_at

    • haveibeenpwned - the v2 API is now replaced with the v3 API, which requires an API key. v2 of the API will stop working on August 18.

    Beta Fixes

    All changes