Home Assistant 0.42: Eddystone Beacons, Lockitron locks and Total Connect alarm systems

Comments

It’s time for Home Assistant 0.42. This release has been focused on refining the system and fixing a lot of bugs. We have also upgraded to the latest version of our HTTP library which should give us a significant boost serving files and API.

On our social media front, we have crossed the 1000 likes on our Facebook page! Also on the social media front, the YouTube channel diyAutomate has been putting out a lot of great getting started videos about Home Assistant, go check them out!

Also want to take a moment to thank Austin Andrews aka Templarian for his Material Design Icons. He is part of what makes Home Assistant so beautiful 🤗.

New integrations

Backward-incompatible changes

  • We were incorrectly treating groups named default_view as default views. Make sure you set view: true in the config for these groups. #251 (frontend)
  • The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as lifx_legacy.
  • We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. #6688
  • Z-Wave cover workaround has been removed. Use device config instead. #6832
zwave:
  device_config:
    cover.my_cover:
      invert_openclose_buttons: true
  • If you set an initial state for an automation, input_boolean, input_slider or input_select it will overrule over the previous state. #6911 #6924
  • Z-Wave rename node service parameter entity_id has been replaced with node_id to align parameters #6938
  • Automations are now initialized when Home Assistant finishes starting up. This means that it is deprecated to listen for event homeassistant_start. Instead, use the new homeassistant automation platform. #6936
automation:
  trigger:
    platform: homeassistant
    event: start
  action:
    service: light.turn_on
  • The Ring component has moved the authentication to a dedicated ring component. #6520
ring:
    username: !secret ring_username
    password: !secret ring_password

binary_sensor:
  - platform: ring
    monitored_conditions:
      - ding
      - motion

sensor:
  - platform: ring
    monitored_conditions:
      - battery
      - last_activity
      - last_ding
      - last_motion
      - volume

If you need help…

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

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Release 0.42.1 - April 9

  • Upgrade aiohttp to 2.0.6
  • Make discovery not cause startup warning

Release 0.42.1 - April 9

  • Revert upgrade to aiothttp 2.0.6

Release 0.42.3 - April 11

Release 0.42.4 - April 17

All changes