jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 17:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 105.1

Browse Source
This commit is contained in:
Paulus Schoutsen 2020-02-05 23:35:51 -08:00
parent c178a7c13d
commit 9499d1fcae
2 changed files with 33 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_config.yml
View File

@ -101,7 +101,7 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 105
current_patch_version: 0
current_patch_version: 1
date_released: 2020-02-05
# Either # or the anchor link to latest release notes in the blog post.

41
source/_posts/2020-02-05-release-105.markdown
View File

@ -195,7 +195,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __Hass.io/Supervisor__ - The "Hass.io" menu item in the side bar has been renamed to Supervisor. This was done to match the announced re-branding. While not really a breaking change, it still is a change that might cause confusion at first. - ([@frenck] - [#31480])
- __Spotify__ - Spotify is now available to be added from the integrations UI! Removing the current Spotify platform and setting up the integration from scratch is recommended.
The device aliases and the `spotify.play_playlist` service, have been removed. Be sure to remove calls to that service from your automations.
If you use the Spotify platform at this moment:
@ -203,7 +203,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Remove the current configuration from your `configuration.yaml` file.
- Remove the `.spotify-token-cache` file from your configuration directory. It is no longer used, however, it does contain security credentials.
- Follow the documentation on how to set up the new Spotify integration from scratch.
Please note, if you have an existing Spotify Developer Application, you need to edit it. The URL's have changed. Consult the integration documentation for the new URL's to use.
([@frenck] - [#30717]) ([spotify docs])
@ -267,7 +267,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- Services to toggle the light/set it to auto have been removed until implemented in `pyatmo`.
If you have an existing configuration, you will need to remove/update that and run the configuration flow dialogue to get their sensors/etc, back using the `configuration.yaml` option.
([@cgtobi] - [#29851]) ([netatmo docs]) (new-platform)
Example configuration YAML:
@ -305,13 +305,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __Simplisafe__ - Many changes here!
Simplisafe's cloud API anticipates receiving updates all at once, which our method did not do, which and could result in failed updates. This change consolidates all of the service calls into a single admin service, and makes `set_pin` and `remove_pin` require admin rights.
It is no longer possible to configure `scan_interval` for the integration and a code-defined interval has been set, as there was potential for users setting this too low and possibly ruin the integration for everyone.
Also, the integration now makes us of `triggered` and `arming` states. Control panel entities no longer have an `alarm_active` attribute.
([@bachya] - [#30567], [#30909], [#31060]) ([simplisafe docs])
Example configuration YAML:
```yaml
@ -393,7 +393,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- __LG webOS Smart TV__ - After the discovery of some additional commands, the client library now has much better tracking of TV power state. As a result of the client library changes, the standby_connection parameter is no longer needed/present (since the relevant behavior can be steered automatically by the client library now) - ([@bendavid] - [#31042]) ([webostv docs])
- __Zone__ - If you're using YAML to configure zones, specifying a name is now required. - ([@balloob] - [#30774]) ([zone docs])
Example configuration YAML:
```yaml
@ -456,7 +456,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
```
- __ZHA remotes__ - `binary_sensor` and `switch` entities are not going to be available for some Zigbee "remotes", but they were not supposed to be available to begin with. - ([@Adminiuga] - [#31146]) ([zha docs])
Affected devices:
- Centralite 3130 remote dimmer, DeviceType: 0x0001, removes binary_sensor entity
@ -483,6 +483,29 @@ Hats over your heart for these shuttered integrations. Pour one out for:
- __Hook__ *Removed* - The `hook` integration has been removed due to the shutdown of the connected service. All servers that have been providing this service will be turned off on 31 Jan 2020. - ([@springstan] - [#31046])
## Release 0.105.1 - February 5
- Check for known Hue vulnerability ([@balloob] - [#31494]) ([hue docs])
- Move program_mode check ([@aneisch] - [#31501]) ([radiotherm docs])
- Updated frontend to 20200130.2 ([@balloob] - [#31502]) ([frontend docs])
- Sonos services to work without admin access ([@balloob] - [#31506]) ([sonos docs])
[#31489]: https://github.com/home-assistant/home-assistant/pull/31489
[#31494]: https://github.com/home-assistant/home-assistant/pull/31494
[#31501]: https://github.com/home-assistant/home-assistant/pull/31501
[#31502]: https://github.com/home-assistant/home-assistant/pull/31502
[#31506]: https://github.com/home-assistant/home-assistant/pull/31506
[@aneisch]: https://github.com/aneisch
[@balloob]: https://github.com/balloob
[@frenck]: https://github.com/frenck
[abode docs]: /integrations/abode/
[adguard docs]: /integrations/adguard/
[airly docs]: /integrations/airly/
[frontend docs]: /integrations/frontend/
[hue docs]: /integrations/hue/
[radiotherm docs]: /integrations/radiotherm/
[sonos docs]: /integrations/sonos/
## Beta Fixes
- ZHA dependencies bump ([@Adminiuga] - [#31295]) ([zha docs]) (beta fix)