0.76: Auth almost done, FleetGo, PJLink, RMV public transport

    Note

    This 发布 has a migration, initial startup can take ~20 minutes (depends on size DB)

    This 发布 includes a database migration to allow us to store context in the database. This will make it possible in the future to introduce attribution. For example, we'll be able to say which 用户 opened the garage door or which 自动化 triggered the party mode at 3am.

    The auth system is entering 发布 candidate status 🎉. If nothing major is found, it will be enabled by default starting the next 发布 (0.77) with backwards compatibility modus turned on. If you want to get ahead of the pack, you can already easily enable it now:

    homeassistant:
  # add this part
  auth_providers:
   - type: homeassistant
   # uncomment this to enable backwards compatible API password support
   # - type: legacy_api_password

    For iOS 用户, your 前端 should be a lot faster. We had an issue that forced us to serve the 前端 in compatibility mode, which is slower. We haven't been able to solve the issue, but found a workaround. Race on 🏎.

    警告. If you are using the internal MQTT broker, we've had to make a change how the 密码 is set. In the past it would automatically start the broker with the 用户 homeassistant and a 密码 equal to the API 密码. This is no longer the case and you need to 配置 it yourself now:

    mqtt:
  password: mypass

    New Platforms

    New Features

    • Add and 恢复 context in recorder (@balloob - #15859) (new-feature)

    发布 0.76.1 - August 19

    发布 0.76.2 - August 21

    If you need help...

    ...don't hesitate to use our very active forums or join us for a little chat. The 发布 notes have comments enabled but it's preferred if you use the former communication channels. Thanks.

    Reporting Issues

    Experiencing issues introduced by this 发布? Please report them in our issue tracker. Make sure to fill in all fields of the issue 模板.

    Backward-incompatible changes

    • Keenetic NDMS: 用户 needs to have access to the TelNet interface (@foxel - #15511) (device_tracker docs) (breaking change)
    • openweathermap: wind speed is now correctly in km/h (fixes #15710) (@fabaff - #15740) (天气.openweathermap docs) (breaking change)
    • Remove Telstra notifiy component: This API has been decommissioned on the 31st of May 2018 by Telstra (@dgomes - #15757) (通知 docs) (breaking change)
    • deCONZ - support for power plugs. Power plugs that are of type "On/Off plug-in unit" and "Smart plug" (Osram and Innr among others) will now be 开关 instead of 灯光. 实体 will be found as 开关.entity_id instead of 灯光.entity_id. (@Kane610 - #15752) (deconz docs) (灯光.deconz docs) (开关.deconz docs) (breaking change) (new-platform)
    • HTTP: Make sure use_x_forward_for and trusted_proxies must be configured together (@awarecan - #15804) (http docs) (breaking change)
    • Velbus: Backward-incompatible changes include auto-discovery support so that you don't need to specify modules manually anymore in the 配置 file, but just load the velbus component which will automatically load the 开关 and binary_sensor platforms. In addition, the 风扇 and 灯光 platforms are removed since these should be modeled with 模板 platform based on velbus 开关. (@thomasdelaet - #13742) (velbus docs) (binary_sensor.velbus docs) (开关.velbus docs) (breaking change)
    • Facebox: Events are no longer fired when a face is taught, as these are unnecessary and the info they convey is already in the 日志. (@robmarkcole - #15439) (image_processing.facebox docs) (breaking change)
    • AMCrest 开关: Fix for multiple 摄像头 开关 naming of 实体. May change 开关 entity_id. Please check your 自动化 and 更新 the identity-id if you have previously assigned a name to your 摄像头 as it appends the name of the 摄像头 to the 开关 id. (@rafale77 - #14028) (开关.amcrest docs) (breaking change)
    • MQTT embedded broker will no longer rely on HTTP API 密码 to automatically 配置 itself. You need to set own 密码. (@awarecan - #15929) (MQTT docs) (breaking change) (beta fix)
    • Remove 遥控器.API from 核心.Config. Might break custom components if they rely on hass.config.api (@awarecan - #15951) (http docs) (breaking change) (beta fix)

    Beta Fixes

    All changes