Home Assistant

0.52: Scripts editor, Nello.io locks, HipChat and Abode Home Security

Paulus Schoutsen 11 minutes reading time
  • Release-Notes
 Comments

Although the summer is in full progress, the development hasn’t stalled. This release brings bug fixes, clean ups and another 8 new integrations. On top of that we are also introducing a new script editor!

To use the scripts editor, create a new file in your config directory named scripts.yaml and copy your existing scripts over:

# scripts.yaml
turn_on_some_lights:
  alias: Turn on the lights
  sequence:
  - data: {}
    service: light.turn_on

Than update your configuration.yaml to look like this:

# Configuration.yaml example
script: !include scripts.yaml

New Platforms

Release 0.52.1 - August 28

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.

Breaking Changes

  • Remove spaces from Xiami switch attributes (@syssi - #8952) (switch.xiaomi docs) (breaking change)
  • MQTT Switch: command and availability payload are now no longer linked. Command and availability payload default to ON/OFF and must be configured individually if custom values are required. (@timstanley1985 - #8934) (switch.mqtt docs) (breaking change)
 -  platform: mqtt
    name: "Kitchen"
    state_topic: "stat/sonoff_1/POWER"
    command_topic: "cmnd/sonoff_1/POWER"
    availability_topic: "tele/sonoff_1/LWT"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

usps:
  username: user
  password: pass
  name: optional
  • eliqonline: The optional channel_id configuration variable of the Eliqonline sensor needs to be a positive integer. (@molobrakos - #9072) (sensor.eliqonline docs) (breaking change)
  • MySensors: Not a breaking change per se but users that have not been following the mysensors serial API could face dropped messages after this change. Messages are now validated according to the API before being passed along from/to devices. See 0.11 release notes for more info. (@MartinHjelmare - #9069) (mysensors docs) (binary_sensor.mysensors docs) (climate.mysensors docs) (cover.mysensors docs) (device_tracker.mysensors docs) (light.mysensors docs) (notify.mysensors docs) (sensor.mysensors docs) (switch.mysensors docs) (breaking change)
  • Automatic has disabled password authentication on their API. Home Assistant will now use OAuth2 to authenticate accounts. The following steps must be taken to transition your setup: 1) Log in to your Automatic developer account. In the Automatic Developer Apps Manager, specify the OAuth Redirect URL in the developer page. This should be configured to <home-assistant-url>/api/automatic/callback. (Example: http://hassio.local:8123/api/automatic/callback) Note that this URL only needs to be accessible from the browser you use to perform the authentication. 2) Remove username/password from your automatic device tracker configuration in configuration.yaml. 3) If you have authorized your account for scope:current_location, add current_location: true to your automatic device tracker configuration in configuration.yaml. 4) When you restart Home Assistant, click on the Automatic Configure link in the Configurator card, and follow the instructions to authorize Home Assistant.

    NOTE: Automatic’s API is currently not correctly authorizing with refresh tokens, so Step 4 currently needs to be performed after every restart. (@armills - #8962) (configurator docs) (device_tracker.automatic docs) (breaking change)

All changes