0.100: Better Plex, Bye JSON, HERE Travel time.

    欢迎来到又一个精彩版本的发布说明！没错，我们这次不是 1.0，而是 0.100！我们觉得距离 1.0 的目标还没完全准备好，但每天都在持续推进。想提前看看我们的思路，可以阅读开发者博客中的 Home Assistant 1.0 简易模式。

    Hacktoberfest

    It is Hacktoberfest. This means that we're spending the month celebrating contributing to 开源. If you make 4 pull requests this month, you get a free Hacktoberfest t-shirt! More info and what to work on, check our Hacktoberfest 博客 post.

    Average contributions per day have doubled for the month of October. There are now on average 40 contributions coming in each day. Breakdown is ~50% Home Assistant 后端, ~37% 文档 and ~13% the 前端. Most of these contributions you'll see in the next 发布!

    Graph of 420 PRs that got opened and merged in the last 14 days. Last 14 days of pull pequest throughput in the Home Assistant organization. (source)

    2019 年年度状况更新

    We're going to have another 状态 of the Union! It will be held at November 13, in Amsterdam. Like last year, it will be hosted by our friends at ING. I'm looking forward to talk about all the great things that are happening in Home Assistant land. We had 150 tickets available when we announced it on social media, and they were all gone in less than 24 hours!

    We're going to make sure that there will be a live stream available. We'll announce that in time via the 博客 and social media. Some people are talking about hosting viewing parties across the globe. Keep an eye out on the social category on the forums for announcements. This would also be the place to announce if you are planning on hosting one.

    Plex

    @jjlawren has been on fire with the Plex 集成. You will now be able to link your account via the official Plex account link feature.

    Screenshot of the Plex 用户 interface asking the 用户 if they want to link with Home Assistant. Screenshot of the Plex 用户 interface asking the 用户 if they want to link with Home Assistant.

    Lovelace

    @iantrich fire has not been put out yet. This 版本 he has also added many new functions to Lovelace! Check the Lovelace changelog for all changes. Some hightlights:

    • There are a lot more option for 状态 filtering
    • We have a bunch of new UI editors
    • A new 动作 url to link to external sites
    • Config 面板: Disabled 实体 are now hidden by default.

    设备 自动化

    @emontnemery has been hard at work at further expanding 设备 自动化 aided by @dmulcahey and @Kane610. This 发布 includes improved support for Zigbee (ZHA) 设备, 传感器, 二元sensor, 开关 and Deconz. One neat new improvement is the addition of a "for" option. This allows you to specify 触发器 for when a certain 设备 has been on for a period of time.

    Screenshot of a 设备 触发器 for a temperature 传感器. Screenshot of a 设备 触发器 for a temperature 传感器.

    自动化 editor

    @emontnemery has added a bunch of functions to the 自动化 editor, you can now use and and or 条件, and give your 自动化 a description so you know why you did what you did.

    Screenshot of an and-条件 in the 自动化 editor. Screenshot of an and-条件 in the 自动化 editor.

    设备

    设备 自动化 are now available on the experimental 设备 page that we introduced in the last 发布. You can now see all the 触发器, 条件 and 动作 the 设备 supports. Clicking on it will open the 自动化 editor with the 自动化 filled in, ready to edit.

    Screenshot of a 卡片 showing 设备 触发器 to create 自动化 from.

    We also added the 实体 registry, so you can change all the 设置 of the 设备 实体 in one place.

    And, bonus, when you rename a 设备 on the 设备 page, it will now also rename the 实体 of that 设备 if they contain the 设备 name. When you are in advanced mode, it can also rename the 实体 id's for you.

    告别 JSON 👋

    On the 后端 we have been using YAML for a long time, but on the 前端, we still used JSON for a lot of things. JSON is harder to write than YAML so we have aligned that. All data inputs on the 前端 now accept YAML. You can still use JSON, as JSON is valid YAML.

    This includes:

    • The 自动化 editor
    • The 脚本 editor
    • 服务 data in dev tools
    • 状态 in dev tools
    • Events in dev tools

    Screenshot of a 服务 动作 in the 自动化 editor using YAML. Screenshot of a 服务 动作 in the 自动化 editor using YAML.

    Thank You, @Amelchio

    核心 developer @amelchio is taking a break from working on Home Assistant. Amelchio has been a contributing member of the Home Assistant community for 2.5 years in which he made a grand total of 275 pull requests! Amelchio has worked on improving database performance and under his wing the Sonos, LIFX and Netgear LTE 集成 flourished. He is an example community member, always available in the chat to help other people contribute to Home Assistant.

    Thanks Anders, we're going to miss you! ❤️

    In other news

    Hans Oischinger showcased how he can steer his 吸尘器 cleaner to specific 房间 in his house via his floorplan. Besides this tweet, he also wrote a great 博客 about it.

    To improve discovery, we're collecting discovery info of 设备 and 服务. Please help us gather zeroconf discovery info and HomeKit discovery info.

    As always, this 发布 of Home Assistant is accompanied with a new 发布 of the Home Assistant Podcast:

    New 集成

    New Platforms

    发布 0.100.1 - October 10

    发布 0.100.2 - October 12

    发布 0.100.3 - October 21

    如果你需要帮助……

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

    反馈问题

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

    Backward-incompatible changes

    • Removed - The following 集成 which were marked in .98 for pending removal have now been removed (ADR-0004):

    • NZBGet - The 集成 has been changed to support multiple platforms and future events, and common code has been centralized to the component. The 配置 has moved from the 传感器 platform to the nzbget key in 配置.yaml, and the monitored_variables option has been removed. 用户 need to 更新 their 配置. - (@chriscla - #26462) (nzbget docs)

      New example 配置 entry:

      nzbget:
  host: 192.168.1.1
  ssl: false

    • SpaceAPI - Values that were not compliant with the SpaceAPI specification were changed.

      • contact / mailing_list has changed to contact / ml, to migrate change the mailing_list key to ml
      • location / address is no longer required but is optional as the latitude and longitude properties of the location are added automatically from the HA config). There is no need to change anything. - (@Bouni - #26453) (spaceapi docs)

    • Linky - Linky 传感器 have been grouped to one Linky 设备. 用户 will need to remove and re-add the Linky 集成 to clear the 设备 registry. - (@piitaya - #26738)

    • Elv - ELV/PCA is now its own 集成. Existing 配置 should be removed and replaced. Optionally the port for the serial interface can be specified (default is: /dev/ttyUSB0). - (@majuss - #26552) (elv docs)

      Example 配置 entry:

      elv:
  device: "/dev/ttyUSB0"

    • 自动化 - Custom component 开发者 who started playing with 设备 自动化 only: we have restructured how 集成 can expose their 设备 触发器/条件/动作. Instead of 1 platform device_automation.py it's now device_action.py, device_trigger.py, device_condition.py. The method to attach a 设备 触发器 has been updated from async_trigger to async_attach_trigger to better reflect what is going on. - (@balloob - #26880) (自动化 docs) (binary_sensor docs) (deconz docs) (device_automation docs) (灯光 docs) (开关 docs) (zha docs)

    • Ecobee - Ecobee will now be set up via config flow. Existing 用户 will have their config imported from ecobee.conf via an import flow so it shouldn't break their experience. 用户 configuring via 配置.yaml will have their api key and options imported into the flow but will still need to finish authorization via the flow (instead of the configurator component as previously). The 配置 parameter hold_temp has been removed, as it was not being used in the 温控 platform and had no effect on whether the temperature was held indefinitely or not. 用户 will need to remove the parameter hold_temp from 配置.yaml. Ecobee-specific 服务 will now be registered under the ecobee domain rather than the 温控 domain, and 服务 names will not include the prefix "ecobee_" (e.g., the 服务 "温控.ecobee_resume_program" will become "ecobee.resume_program"). - (@marthoc - #26634) (ecobee docs)

    • Transmission - The Transmission 集成 can now be configured through a config flow via 集成 in the GUI. Once configured all 传感器 and 开关 will be 创建 and available for the 用户. monitored_conditions has been removed so existing 用户 need to 更新 their 配置 in 配置.yaml and remove monitored 条件. The existing 配置 will be imported as an entry under 集成. - (@engrbm87 - #26434) (transmission docs)

      Example 配置 entry:

      transmission:
  host: 192.168.1.1

    • Rainbird - Rainbird is now its own platform. The 配置 of rainbird 开关 has been moved under zones: as part of the rainbird: 集成. - (@konikvranik - #26393) (rainbird docs)

      Example 配置 entry:

      rainbird:
  host: IP_ADDRESS_OF_MODULE
  password: YOUR_PASSWORD
  trigger_time: 6
  zones:
    1:
      trigger_time: 6

    • Incomfort - 设备 状态 属性 that were causing pointless 状态 changes have been removed:

      • "rf_message_rssi signal strength (between gateway & boiler), changes almost every scan_interval
      • nodenr unknown, is static
      • rfstatus_cntr unknown, changes

      This is not likely to be considered a breaking change by 用户. - (@zxdavb - #26802) (incomfort docs)

    • Evohome - 设备 状态 属性 keys have been changed to snake_case and, since this a breaking change, the opportunity was taken to revise/simplify the entire 设备 状态 属性 schema. Evohome is a complicated 集成, has had major changes in recent times, and is not yet mature - these changes address some bugs and related architectural issues:

      • Modify behavior of set_temperature to mirror that of the vendor's UI (e.g., any target temp changes until next setpoint, unless explicitly set otherwise)
      • Setpoint datetimes are now correctly converted to local/aware isoformat (internally, and for logging/状态 属性)
      • Use snake_case for 设备 状态 属性
      • Add a unique_id for each 实体 (systemId, zoneID, dhwId)
      • Refactoring - remove API wrappers (no longer using private methods)
      • Add away mode for DHW (set to permanent off or Auto, depending)(@zxdavb - #26810) (evohome docs)

    • OpenTherm - Move 温控 实体 状态 to hvac_action 属性 to comply with 温控 1.0. May break e.g., 自动化. - (@mvn23 - #25931) (opentherm_gw docs)

    • Genius Hub - 用户 connecting to a Hub via the v1 API will need to specify a valid MAC address for the hub (see example YAML, below). Those using the v3 API will be unaffected. This change is in preparation for for further changes, so the geniushub 实体 can be given more appropriate entity_ids.

      Some 传感器 实体 fro GeniusHub Issues have been renamed, and so will get a new 实体 ID:

      • 传感器.错误 to 传感器.geniushub_errors
      • 传感器.警告 to 传感器.geniushub_warnings
      • 传感器.information to 传感器.geniushub_informationeniushub and bump client to v0.6.26 - (@zxdavb - #26640) (geniushub docs)

      Example 配置 entry:

      geniushub:
  token: JqVFd0UUEi...
  mac: 18:CC:23:12:34:56

    Beta Fixes

    All changes