You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release introduces a new [person component][person docs] thanks to [@MartinHjelmare]. With this component, Home Assistant can be set up to track the people in your home. Each person can be linked to a user and multiple device tracker entities. This release does basic device tracker state merging, which will be evolved in the future. Device trackers merging their own states will be phased out in favor of persons. You can configure persons via the config panel. To get started, add the person component to your configuration.yaml file: `person:`. If you want to automatically stay up to date with the latest default Home Assistant components, you can now also add `default_config:` to your config.
17
17
18
-
Person component
18
+
This release also extends the event dev tool to include an event debugger. It allows you to listen to core events and get them printend to the screen. This makes it easy to find the event data that your remote is sending out.
19
19
20
+
We also have a new command line auth provider. This will allow you to use a shell script to validate users logging in to the system. This gives a lot of flexibility. For example, you can now authenticate against LDAP. More info in [the documentation](/docs/authentication/providers/#command-line).
21
+
22
+
[@andrewsayre] has been working hard on extending the SmartThings support. This release brings sensors and climate devices into the mix. Awesome!
We have tightened config validation. Platform configuration will no longer allow to contain keys that are not supported. This should help with finding typos in your current and future YAML.
26
+
We have tightened config validation, so expect a couple of new warnings. Platform configuration will no longer allow to contain keys that are not supported. This should help with finding typos in your current and future YAML configs. This will currently fallback to a warning and will become a full error in the future.
24
27
25
-
Note for Lovelace custom card developers: if you relied on the availability of `<paper-button>` in your code, you will have to update it to `<mwc-button>` to work like before.
28
+
Note for Lovelace custom card developers: if you relied on the availability of `<paper-button>` in your code, you will have to update it to `<mwc-button>` to get a similar component.
26
29
27
-
Note for custom component developers: We are moving to a new file structure. Platforms now live embedded in components. Custom platforms will have to be updated to follow this pattern. This is a breaking change in case your custom platform overrides a built-in platform. Rename your custom platform from, ie `light/hue.py` to `hue/light.py`.
30
+
Note for custom component developers: We are moving to a new file structure. More information on [our dev blog](https://developers.home-assistant.io/blog/2019/02/19/the-great-migration.html).
28
31
29
32
## {% linkable_title New Platforms %}
30
33
@@ -37,16 +40,15 @@ Note for custom component developers: We are moving to a new file structure. Pla
0 commit comments