mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-22 00:36:49 +00:00
Replaces all internal full URL links (#9787)
This commit is contained in:
Franck Nijhof
Fabian Affolter
parent
56ec75238c
commit
4a1932b2a8
@ -160,7 +160,7 @@ The following are some examples showing how to correctly make service calls usin
|
||||
|
||||
### Snap Picture and Save Locally
|
||||
|
||||
This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](https://www.home-assistant.io/components/camera#service-snapshot)
|
||||
This example script shows how to take a picture with your camera, named `My Camera` in your Blink app (this is **not necessarily** the friendly name in home-assistant). After snapping a picture, the image will then be saved to a local directory called `/tmp/my_image.jpg`. Note that this example makes use of services found in the [camera integration](/components/camera#service-snapshot)
|
||||
|
||||
```yaml
|
||||
alias: Blink Snap Picture
|
||||
@ -178,9 +178,9 @@ sequence:
|
||||
|
||||
### Arm Blink When Away
|
||||
|
||||
This example automation will arm your blink sync module to detect motion on any of your blink cameras that have motion detection enabled. By default, Blink enables motion detection on all cameras so, unless you've changed anything in your app, you're all set. If you want to manually enable motion detection for individual cameras, you can utilize the [appropriate camera service](https://www.home-assistant.io/components/camera#service-enable_motion_detection) but pelase note that motion will only be captured if the sync module is armed.
|
||||
This example automation will arm your blink sync module to detect motion on any of your blink cameras that have motion detection enabled. By default, Blink enables motion detection on all cameras so, unless you've changed anything in your app, you're all set. If you want to manually enable motion detection for individual cameras, you can utilize the [appropriate camera service](/components/camera#service-enable_motion_detection) but pelase note that motion will only be captured if the sync module is armed.
|
||||
|
||||
Here, this example assumes your blink module is named `My Sync Module` and that you have [device trackers](https://www.home-assistant.io/components/device_tracker) set up for presence detection.
|
||||
Here, this example assumes your blink module is named `My Sync Module` and that you have [device trackers](/components/device_tracker) set up for presence detection.
|
||||
|
||||
```yaml
|
||||
- id: arm_blink_when_away
|
||||
@ -214,7 +214,7 @@ Similar to the previous example, this automation will disarm blink when arriving
|
||||
|
||||
When motion is detected, you can use the Blink Home-Assistant integration to save the last recorded video locally, rather than relying on Blink's servers to save your data.
|
||||
|
||||
Again, this example assumes your camera's name (in the blink app) is `My Camera` and your sync module name is `My Sync Module`. The file will be saved to `/tmp/videos/blink_video_{YYYMMDD_HHmmSS}.mp4` where `{YYYYMMDD_HHmmSS}` will be a timestamp create via the use of [templating](https://www.home-assistant.io/docs/configuration/templating/).
|
||||
Again, this example assumes your camera's name (in the blink app) is `My Camera` and your sync module name is `My Sync Module`. The file will be saved to `/tmp/videos/blink_video_{YYYMMDD_HHmmSS}.mp4` where `{YYYYMMDD_HHmmSS}` will be a timestamp create via the use of [templating](/docs/configuration/templating/).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@ -61,12 +61,12 @@ hosts:
|
||||
|
||||
The `daikin` climate platform integrates Daikin air conditioning systems into Home Assistant, enabling control of setting the following parameters:
|
||||
|
||||
- [**mode**](https://www.home-assistant.io/components/climate#service-climateset_operation_mode) (cool, heat, dry, fan only or auto)
|
||||
- [**target temperature**](https://www.home-assistant.io/components/climate#service-climateset_temperature)
|
||||
- [**fan mode**](https://www.home-assistant.io/components/climate#service-climateset_fan_mode) (speed)
|
||||
- [**swing mode**](https://www.home-assistant.io/components/climate#service-climateset_swing_mode)
|
||||
- [**turn on/off**](https://www.home-assistant.io/components/climate#service-climateturn_on)
|
||||
- [**away mode**](https://www.home-assistant.io/components/climate#service-climateset_away_mode)
|
||||
- [**mode**](/components/climate#service-climateset_operation_mode) (cool, heat, dry, fan only or auto)
|
||||
- [**target temperature**](/components/climate#service-climateset_temperature)
|
||||
- [**fan mode**](/components/climate#service-climateset_fan_mode) (speed)
|
||||
- [**swing mode**](/components/climate#service-climateset_swing_mode)
|
||||
- [**turn on/off**](/components/climate#service-climateturn_on)
|
||||
- [**away mode**](/components/climate#service-climateset_away_mode)
|
||||
|
||||
Current inside temperature is displayed.
|
||||
|
||||
|
||||
@ -56,7 +56,7 @@ ecobee:
|
||||
api_key: YOUR_API_KEY
|
||||
```
|
||||
|
||||
[Restart Home Assistant](https://www.home-assistant.io/docs/configuration/#reloading-changes) for the changes to take effect.
|
||||
[Restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect.
|
||||
|
||||
The first time you (re)run Home Assistant with this integration it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking **Add Application** in the **My Apps** section in the sidebar.
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ ha_qa_scale: internal
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant component](/components/google_assistant/) or [Nabu Casa cloud](https://www.home-assistant.io/components/cloud) component.
|
||||
Be aware that `emulated_hue` doesn't work for new users of **Google Home** with `emulated_hue`. If you've not previously set this up and had it working, use the [Google Assistant component](/components/google_assistant/) or [Nabu Casa cloud](/components/cloud) component.
|
||||
</p>
|
||||
|
||||
The `emulated_hue` integration provides a virtual Philips Hue bridge, written entirely in software, which allows services that work with the Hue API to interact with Home Assistant
|
||||
|
||||
@ -103,7 +103,7 @@ ssl_profile:
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note'>
|
||||
Configuring trusted_networks via the `http` integration will be deprecated and moved to `auth_providers` instead. For instructions, see <a href="https://www.home-assistant.io/docs/authentication/providers/#trusted-networks">trusted networks</a>. In Home Assistant 0.89.0 and 0.89.1, you need place the trusted network under both `http` and `auth_providers` if you still want to use trusted networks features. You can remove it from `http` section starting from 0.89.2.
|
||||
Configuring trusted_networks via the `http` integration will be deprecated and moved to `auth_providers` instead. For instructions, see <a href="/docs/authentication/providers/#trusted-networks">trusted networks</a>. In Home Assistant 0.89.0 and 0.89.1, you need place the trusted network under both `http` and `auth_providers` if you still want to use trusted networks features. You can remove it from `http` section starting from 0.89.2.
|
||||
</p>
|
||||
|
||||
The sample below shows a configuration entry with possible values:
|
||||
|
||||
@ -131,7 +131,7 @@ However, in some circumstances, it might be helpful to limit which Life360 Circl
|
||||
|
||||
For a particular Member to be tracked, they must be included (or at least not excluded), and must be in at least one of the included Circles. See [example configuration](#circle-and-member-filtering-example) below.
|
||||
|
||||
Note that Life360's app and website typically only show Members' first names. However, you must use their _full_ names here. If you're not sure what a Member's full name (i.e., first and last) is in Life360, ask them. Alternatively, you can set the [`logger`](https://www.home-assistant.io/components/logger/) to `debug` and look in `home-assistant.log`. The full names of all Life360 Circles & Members will be logged.
|
||||
Note that Life360's app and website typically only show Members' first names. However, you must use their _full_ names here. If you're not sure what a Member's full name (i.e., first and last) is in Life360, ask them. Alternatively, you can set the [`logger`](/components/logger/) to `debug` and look in `home-assistant.log`. The full names of all Life360 Circles & Members will be logged.
|
||||
|
||||
## Home - Home Assistant vs. Life360
|
||||
|
||||
@ -139,7 +139,7 @@ Normally Home Assistant device trackers are "Home" when they enter `zone.home`.
|
||||
|
||||
## Home Assistant Zones & Life360 Places
|
||||
|
||||
See [Zone documentation](https://www.home-assistant.io/components/zone/#home-zone) for details about how HA zones are defined. If you'd like to create HA zones from Life360 Places (e.g., to make HA's `zone.home` be identical to Life360's "Home Place"), make sure `logger` is set to `debug`. Then when HA starts the details of all the Places defined in the included Circles will be written to `home-assistant.log` in a format that can be copied into your configuration under `zone:`. E.g., you would see something like this:
|
||||
See [Zone documentation](/components/zone/#home-zone) for details about how HA zones are defined. If you'd like to create HA zones from Life360 Places (e.g., to make HA's `zone.home` be identical to Life360's "Home Place"), make sure `logger` is set to `debug`. Then when HA starts the details of all the Places defined in the included Circles will be written to `home-assistant.log` in a format that can be copied into your configuration under `zone:`. E.g., you would see something like this:
|
||||
|
||||
```text
|
||||
2019-05-31 12:16:58 DEBUG (SyncWorker_3) [homeassistant.components.life360.device_tracker] My Family Circle: will be included, id=xxxxx
|
||||
|
||||
@ -99,9 +99,9 @@ That's it. You can copy and paste your new `client id` and `client secret` in yo
|
||||
|
||||
### Webhooks
|
||||
|
||||
The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](https://www.home-assistant.io/components/camera.netatmo/) or by enabeling [discovery](https://www.home-assistant.io/components/netatmo/#discovery).
|
||||
The Welcome and Presence cameras can send instant events to Home Assistant by using webhooks. There are different types of events, each with slightly different data attached. To enable the webhooks add `webhooks: true` to your configuration. It is also required to have your camera enabled in Home Assistant. You can do this either by manually setting up the [platform](/components/camera.netatmo/) or by enabeling [discovery](/components/netatmo/#discovery).
|
||||
|
||||
To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](https://www.home-assistant.io/addons/duckdns/)) and you need to have the base_url configured for the HTTP integration ([docs](https://www.home-assistant.io/components/http/#base_url)).
|
||||
To be able to receive events from Netatmo, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the base_url configured for the HTTP integration ([docs](/components/http/#base_url)).
|
||||
|
||||
Events coming in from Netatmo will be available as events in Home Assistant and are fired as netatmo_*, along with their data. You can use this event to trigger automations.
|
||||
|
||||
@ -141,7 +141,7 @@ The Welcome camera additionally has these attributes for `netatmo_person` events
|
||||
| is_known | Boolean value if the person is known.
|
||||
| face_url | URL to a picture of the person.
|
||||
|
||||
The `netatmo_other` event passes all the webhook data through for all webhook events that don't match any of the above. Set the [level of logging](https://www.home-assistant.io/components/logger/) for the `netatmo` integration to `debug` to view the data in the Home Assistant logs.
|
||||
The `netatmo_other` event passes all the webhook data through for all webhook events that don't match any of the above. Set the [level of logging](/components/logger/) for the `netatmo` integration to `debug` to view the data in the Home Assistant logs.
|
||||
|
||||
### Services (only for webhooks)
|
||||
|
||||
@ -149,7 +149,7 @@ There are two services to manually add and drop the webhooks. This might be usef
|
||||
|
||||
| Service | Description |
|
||||
| ------- | ----------- |
|
||||
| addwebhook | Subscribe to webhooks. By default the automatically generated URL will be used. But you can pass `{"url": "https://yourdomain.com/yourwebhook/"}` as service data to the service call if you want to use a manually created [webhook trigger](https://www.home-assistant.io/docs/automation/trigger/#webhook-trigger). In this case you have to manually process the data that is sent by Netatmo.
|
||||
| addwebhook | Subscribe to webhooks. By default the automatically generated URL will be used. But you can pass `{"url": "https://yourdomain.com/yourwebhook/"}` as service data to the service call if you want to use a manually created [webhook trigger](/docs/automation/trigger/#webhook-trigger). In this case you have to manually process the data that is sent by Netatmo.
|
||||
| dropwebhook | Unsubscribe existing webhooks.
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
@ -66,7 +66,7 @@ The only thing that you can do out of the box is to track whether they are avail
|
||||
Also for sensors a list of raw values is exposed as `sensor_values` attribute, and you can use them
|
||||
in automations, if you know what particular values mean for your sensor.
|
||||
|
||||
It is suggested to make [scan_interval](https://www.home-assistant.io/docs/configuration/platform_options/#scan-interval)
|
||||
It is suggested to make [scan_interval](/docs/configuration/platform_options/#scan-interval)
|
||||
(30 seconds by default) less or equal to `interval_lightify_status`, oherwise the latter won't work
|
||||
as expected. Shorter `scan_interval` may improve synchronization speed between individual lights and
|
||||
groups. For example, if you turn on a group, all its lights may be updated to `on` immediately,
|
||||
|
||||
@ -14,7 +14,7 @@ ha_qa_scale: internal
|
||||
ha_release: 0.88
|
||||
---
|
||||
|
||||
The person integration allows connecting [device tracker](https://www.home-assistant.io/components/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
|
||||
The person integration allows connecting [device tracker](/components/device_tracker/) entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
|
||||
|
||||
1. If there are stationary trackers (non-GPS trackers, i.e., a router or Bluetooth 'device_trackers') presenting the status 'home', the tracker most recently updated will be used.
|
||||
2. If there are trackers of type 'gps', then the most recently updated tracker will be used.
|
||||
@ -23,7 +23,7 @@ The person integration allows connecting [device tracker](https://www.home-assis
|
||||
Let's say, for example, that you have 3 trackers: 'tracker_gps', 'tracker_router' and 'tracker_ble'.
|
||||
|
||||
1. You're at home, all 3 devices show status 'home' - status of your Person entity will be 'home' with source 'tracker_router' or 'tracker_ble', whichever was most recently updated.
|
||||
2. You just left home. 'tracker_gps' shows status 'not_home', but the other two trackers show status 'home' (they may not have yet updated due to their 'consider_home' setting see [device_tracker](https://www.home-assistant.io/components/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered 'home'.
|
||||
2. You just left home. 'tracker_gps' shows status 'not_home', but the other two trackers show status 'home' (they may not have yet updated due to their 'consider_home' setting see [device_tracker](/components/device_tracker/#configuring-a-device_tracker-platform)). Since the stationary trackers have priority, you are considered 'home'.
|
||||
3. After some time, both stationary trackers show status 'not_home'. Now your Person entity has status 'not_home' with source 'tracker_gps'.
|
||||
4. While you are away from home, your Home Assistant is restarted. Until 'tracker_gps' receives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be 'not_home'.
|
||||
5. Then you're going into a zone you have defined as 'zone1', 'tracker_gps' sends an update, and now your status is 'zone1' with source 'tracker_gps'.
|
||||
@ -32,7 +32,7 @@ Let's say, for example, that you have 3 trackers: 'tracker_gps', 'tracker_router
|
||||
|
||||
TL;DR: When you're at home, your position is determined first by stationary trackers (if any) and then by GPS. When you're outside your home, your position is determined firstly by GPS and then by stationary trackers.
|
||||
|
||||
**Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home` for stationary trackers as low as possible see [device_tracker](https://www.home-assistant.io/components/device_tracker/#configuring-a-device_tracker-platform)).
|
||||
**Hint**: When you use multiple device trackers together, especially stationary and GPS trackers, it's advisable to set `consider_home` for stationary trackers as low as possible see [device_tracker](/components/device_tracker/#configuring-a-device_tracker-platform)).
|
||||
|
||||
You can manage persons via the UI from the person page inside the configuration panel or via `YAML` in your `configuration.yaml` file.
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ The integration supports the following device types within Home Assistant:
|
||||
- [Sensor](#sensor)
|
||||
|
||||
<p class='note'>
|
||||
The Point is just active occasionally so the [Sensors](#sensor) are only updated every hour or so. The [Binary Sensors](#binary-sensor) are however updated via [Cloud Push](https://www.home-assistant.io/blog/2016/02/12/classifying-the-internet-of-things/#cloud-pushing-new-state), making the changes close to instant.
|
||||
The Point is just active occasionally so the [Sensors](#sensor) are only updated every hour or so. The [Binary Sensors](#binary-sensor) are however updated via [Cloud Push](/blog/2016/02/12/classifying-the-internet-of-things/#cloud-pushing-new-state), making the changes close to instant.
|
||||
</p>
|
||||
|
||||
## Alarm
|
||||
|
||||
@ -77,7 +77,7 @@ sudo setcap 'cap_net_bind_service=+ep' /usr/bin/python3.5
|
||||
|
||||
To find your system Python path:
|
||||
|
||||
- Add the [System Health](https://www.home-assistant.io/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http://<yourhomeassistanturl>/dev-info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run:
|
||||
- Add the [System Health](/components/system_health/) integration to your `configuration.yaml`. In a web browser access your frontend and navigate to the about/logs page "http://<yourhomeassistanturl>/dev-info). In the System Health box locate the item **python_version** and note the value that is displayed. Then in terminal run:
|
||||
|
||||
```bash
|
||||
whereis python<version>
|
||||
|
||||
@ -153,7 +153,7 @@ automation:
|
||||
|
||||
## Advanced Configuration for DSMR users
|
||||
|
||||
When using the [DSMR component](https://www.home-assistant.io/components/sensor.dsmr/) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
|
||||
When using the [DSMR component](/components/sensor.dsmr/) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component.
|
||||
|
||||
If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors:
|
||||
|
||||
|
||||
@ -95,7 +95,7 @@ Replace 443 with whatever port you chose to bind to in the config if different.
|
||||
|
||||
### Configure Home Assistant HTTP Component
|
||||
|
||||
In your `configuration.yaml` file, edit the [http component](https://www.home-assistant.io/components/http/).
|
||||
In your `configuration.yaml` file, edit the [http component](/components/http/).
|
||||
|
||||
```text
|
||||
http:
|
||||
|
||||
@ -149,4 +149,4 @@ tap_action:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
The filename needs to be a path that is writable by Home Assistant in your system. You may need to configure `whitelist_external_dirs` ([documentation](https://www.home-assistant.io/docs/configuration/basic/)).
|
||||
The filename needs to be a path that is writable by Home Assistant in your system. You may need to configure `whitelist_external_dirs` ([documentation](/docs/configuration/basic/)).
|
||||
|
||||
@ -16,40 +16,40 @@ A man in the middle attack is when an attacker is able to inject itself between
|
||||
|
||||
After research, the following integrations have been impacted. Although the odds are extremely small, we still suggest that if you use any of these integrations, to create new API keys or change your password.
|
||||
|
||||
- [alarm_control_panel.alarmdotcom](https://www.home-assistant.io/components/alarm_control_panel.alarmdotcom/)
|
||||
- [climate.sensibo](https://www.home-assistant.io/components/climate.sensibo/)
|
||||
- [cloud](https://www.home-assistant.io/components/cloud/) (only short lived tokens impacted)
|
||||
- [device_tracker.automatic](https://www.home-assistant.io/components/device_tracker.automatic/)
|
||||
- [duckdns](https://www.home-assistant.io/components/duckdns/)
|
||||
- [freedns](https://www.home-assistant.io/components/freedns/)
|
||||
- [google_assistant](https://www.home-assistant.io/components/google_assistant/) (manual setup)
|
||||
- [google_domains](https://www.home-assistant.io/components/google_domains/)
|
||||
- [homematicip_cloud](https://www.home-assistant.io/components/homematicip_cloud/)
|
||||
- [image_processing.openalpr_cloud](https://www.home-assistant.io/components/image_processing.openalpr_cloud/)
|
||||
- [microsoft_face](https://www.home-assistant.io/components/microsoft_face/)
|
||||
- [namecheapdns](https://www.home-assistant.io/components/namecheapdns/)
|
||||
- [no_ip](https://www.home-assistant.io/components/no_ip/)
|
||||
- [notify.flock](https://www.home-assistant.io/components/notify.flock/)
|
||||
- [notify.prowl](https://www.home-assistant.io/components/notify.prowl/)
|
||||
- [rest_command](https://www.home-assistant.io/components/rest_command/)
|
||||
- [scene.lifx_cloud](https://www.home-assistant.io/components/scene.lifx_cloud/)
|
||||
- [switch.hook](https://www.home-assistant.io/components/switch.hook/)
|
||||
- [switch.rest](https://www.home-assistant.io/components/switch.rest/)
|
||||
- [telegram_bot.polling](https://www.home-assistant.io/components/telegram_bot.polling/)
|
||||
- [tts.voicerss](https://www.home-assistant.io/components/tts.voicerss/)
|
||||
- [alarm_control_panel.alarmdotcom](/components/alarm_control_panel.alarmdotcom/)
|
||||
- [climate.sensibo](/components/climate.sensibo/)
|
||||
- [cloud](/components/cloud/) (only short lived tokens impacted)
|
||||
- [device_tracker.automatic](/components/device_tracker.automatic/)
|
||||
- [duckdns](/components/duckdns/)
|
||||
- [freedns](/components/freedns/)
|
||||
- [google_assistant](/components/google_assistant/) (manual setup)
|
||||
- [google_domains](/components/google_domains/)
|
||||
- [homematicip_cloud](/components/homematicip_cloud/)
|
||||
- [image_processing.openalpr_cloud](/components/image_processing.openalpr_cloud/)
|
||||
- [microsoft_face](/components/microsoft_face/)
|
||||
- [namecheapdns](/components/namecheapdns/)
|
||||
- [no_ip](/components/no_ip/)
|
||||
- [notify.flock](/components/notify.flock/)
|
||||
- [notify.prowl](/components/notify.prowl/)
|
||||
- [rest_command](/components/rest_command/)
|
||||
- [scene.lifx_cloud](/components/scene.lifx_cloud/)
|
||||
- [switch.hook](/components/switch.hook/)
|
||||
- [switch.rest](/components/switch.rest/)
|
||||
- [telegram_bot.polling](/components/telegram_bot.polling/)
|
||||
- [tts.voicerss](/components/tts.voicerss/)
|
||||
|
||||
Also impacted, but integrations are read only:
|
||||
|
||||
- [sensor.airvisual](https://www.home-assistant.io/components/sensor.airvisual/)
|
||||
- [sensor.ebox](https://www.home-assistant.io/components/sensor.ebox/)
|
||||
- [sensor.fido](https://www.home-assistant.io/components/sensor.fido/)
|
||||
- [sensor.foobot](https://www.home-assistant.io/components/sensor.foobot/)
|
||||
- [sensor.hydroquebec](https://www.home-assistant.io/components/sensor.hydroquebec/)
|
||||
- [sensor.startca](https://www.home-assistant.io/components/sensor.startca/)
|
||||
- [sensor.teksavvy](https://www.home-assistant.io/components/sensor.teksavvy/)
|
||||
- [sensor.thethingsnetwork](https://www.home-assistant.io/components/sensor.thethingsnetwork/)
|
||||
- [sensor.tibber](https://www.home-assistant.io/components/sensor.tibber/)
|
||||
- [sensor.waqi](https://www.home-assistant.io/components/sensor.waqi/)
|
||||
- [sensor.airvisual](/components/sensor.airvisual/)
|
||||
- [sensor.ebox](/components/sensor.ebox/)
|
||||
- [sensor.fido](/components/sensor.fido/)
|
||||
- [sensor.foobot](/components/sensor.foobot/)
|
||||
- [sensor.hydroquebec](/components/sensor.hydroquebec/)
|
||||
- [sensor.startca](/components/sensor.startca/)
|
||||
- [sensor.teksavvy](/components/sensor.teksavvy/)
|
||||
- [sensor.thethingsnetwork](/components/sensor.thethingsnetwork/)
|
||||
- [sensor.tibber](/components/sensor.tibber/)
|
||||
- [sensor.waqi](/components/sensor.waqi/)
|
||||
|
||||
If you are running Home Assistant on a system with Python 3.4, we've created a new release 0.64.4b0 with the patch applied. We have made it available as a beta. To install the pre-release run `python3 -m pip install homeassistant==0.64.4b0`.
|
||||
|
||||
@ -59,48 +59,48 @@ For complete transparency, the following two sets of integrations also used aioh
|
||||
|
||||
Affected, but not transmitting authentication:
|
||||
|
||||
- [sensor.buienradar](https://www.home-assistant.io/components/sensor.buienradar/)
|
||||
- [sensor.citybikes](https://www.home-assistant.io/components/sensor.citybikes/)
|
||||
- [sensor.comed_hourly_pricing](https://www.home-assistant.io/components/sensor.comed_hourly_pricing/)
|
||||
- [sensor.luftdaten](https://www.home-assistant.io/components/sensor.luftdaten/)
|
||||
- [sensor.pollen](https://www.home-assistant.io/components/sensor.pollen/)
|
||||
- [sensor.sochain](https://www.home-assistant.io/components/sensor.sochain/)
|
||||
- [sensor.swiss_public_transport](https://www.home-assistant.io/components/sensor.swiss_public_transport/)
|
||||
- [sensor.viaggiatreno](https://www.home-assistant.io/components/sensor.viaggiatreno/)
|
||||
- [sensor.wunderground](https://www.home-assistant.io/components/sensor.wunderground/)
|
||||
- [sensor.yr](https://www.home-assistant.io/components/sensor.yr/)
|
||||
- [weather.ipma](https://www.home-assistant.io/components/weather.ipma/)
|
||||
- [tts.google](https://www.home-assistant.io/components/tts.google/)
|
||||
- [tts.yandextts](https://www.home-assistant.io/components/tts.yandextts/)
|
||||
- [updater](https://www.home-assistant.io/components/updater/)
|
||||
- [sensor.buienradar](/components/sensor.buienradar/)
|
||||
- [sensor.citybikes](/components/sensor.citybikes/)
|
||||
- [sensor.comed_hourly_pricing](/components/sensor.comed_hourly_pricing/)
|
||||
- [sensor.luftdaten](/components/sensor.luftdaten/)
|
||||
- [sensor.pollen](/components/sensor.pollen/)
|
||||
- [sensor.sochain](/components/sensor.sochain/)
|
||||
- [sensor.swiss_public_transport](/components/sensor.swiss_public_transport/)
|
||||
- [sensor.viaggiatreno](/components/sensor.viaggiatreno/)
|
||||
- [sensor.wunderground](/components/sensor.wunderground/)
|
||||
- [sensor.yr](/components/sensor.yr/)
|
||||
- [weather.ipma](/components/weather.ipma/)
|
||||
- [tts.google](/components/tts.google/)
|
||||
- [tts.yandextts](/components/tts.yandextts/)
|
||||
- [updater](/components/updater/)
|
||||
|
||||
Local, so cannot be impacted:
|
||||
|
||||
- [android_ip_webcam](https://www.home-assistant.io/components/android_ip_webcam/)
|
||||
- [apple_tv](https://www.home-assistant.io/components/apple_tv/)
|
||||
- [camera.amcrest](https://www.home-assistant.io/components/camera.amcrest/)
|
||||
- [camera.doorbird](https://www.home-assistant.io/components/camera.doorbird/)
|
||||
- [camera.familyhub](https://www.home-assistant.io/components/camera.familyhub/)
|
||||
- [camera.generic](https://www.home-assistant.io/components/camera.generic/)
|
||||
- [camera.mjpeg](https://www.home-assistant.io/components/camera.mjpeg/)
|
||||
- [camera.proxy](https://www.home-assistant.io/components/camera.proxy/)
|
||||
- [camera.synology](https://www.home-assistant.io/components/camera.synology/)
|
||||
- [deconz](https://www.home-assistant.io/components/deconz/)
|
||||
- [device_tracker.upc_connect](https://www.home-assistant.io/components/device_tracker.upc_connect/)
|
||||
- [hassio](https://www.home-assistant.io/components/hassio/)
|
||||
- [hue](https://www.home-assistant.io/components/hue/)
|
||||
- [media_player.bluesound](https://www.home-assistant.io/components/media_player.bluesound/)
|
||||
- [media_player.epson](https://www.home-assistant.io/components/media_player.epson/)
|
||||
- [media_player.kodi](https://www.home-assistant.io/components/media_player.kodi/)
|
||||
- [media_player.squeezebox](https://www.home-assistant.io/components/media_player.squeezebox/)
|
||||
- [media_player.volumio](https://www.home-assistant.io/components/media_player.volumio/)
|
||||
- [notify.kodi](https://www.home-assistant.io/components/notify.kodi/)
|
||||
- [qwikswitch](https://www.home-assistant.io/components/qwikswitch/)
|
||||
- [rainmachine](https://www.home-assistant.io/components/rainmachine/)
|
||||
- [scene.hunterdouglas_powerview](https://www.home-assistant.io/components/scene.hunterdouglas_powerview/)
|
||||
- [sensor.netdata](https://www.home-assistant.io/components/sensor.netdata/)
|
||||
- [sensor.pi_hole](https://www.home-assistant.io/components/sensor.pi_hole/)
|
||||
- [sensor.sma](https://www.home-assistant.io/components/sensor.sma/)
|
||||
- [sensor.worxlandroid](https://www.home-assistant.io/components/sensor.worxlandroid/)
|
||||
- [spc](https://www.home-assistant.io/components/spc/)
|
||||
- [tts.marytts](https://www.home-assistant.io/components/tts.marytts/)
|
||||
- [android_ip_webcam](/components/android_ip_webcam/)
|
||||
- [apple_tv](/components/apple_tv/)
|
||||
- [camera.amcrest](/components/camera.amcrest/)
|
||||
- [camera.doorbird](/components/camera.doorbird/)
|
||||
- [camera.familyhub](/components/camera.familyhub/)
|
||||
- [camera.generic](/components/camera.generic/)
|
||||
- [camera.mjpeg](/components/camera.mjpeg/)
|
||||
- [camera.proxy](/components/camera.proxy/)
|
||||
- [camera.synology](/components/camera.synology/)
|
||||
- [deconz](/components/deconz/)
|
||||
- [device_tracker.upc_connect](/components/device_tracker.upc_connect/)
|
||||
- [hassio](/components/hassio/)
|
||||
- [hue](/components/hue/)
|
||||
- [media_player.bluesound](/components/media_player.bluesound/)
|
||||
- [media_player.epson](/components/media_player.epson/)
|
||||
- [media_player.kodi](/components/media_player.kodi/)
|
||||
- [media_player.squeezebox](/components/media_player.squeezebox/)
|
||||
- [media_player.volumio](/components/media_player.volumio/)
|
||||
- [notify.kodi](/components/notify.kodi/)
|
||||
- [qwikswitch](/components/qwikswitch/)
|
||||
- [rainmachine](/components/rainmachine/)
|
||||
- [scene.hunterdouglas_powerview](/components/scene.hunterdouglas_powerview/)
|
||||
- [sensor.netdata](/components/sensor.netdata/)
|
||||
- [sensor.pi_hole](/components/sensor.pi_hole/)
|
||||
- [sensor.sma](/components/sensor.sma/)
|
||||
- [sensor.worxlandroid](/components/sensor.worxlandroid/)
|
||||
- [spc](/components/spc/)
|
||||
- [tts.marytts](/components/tts.marytts/)
|
||||
|
||||
@ -80,7 +80,7 @@ Relying on donations makes budgeting for employees impossible without exposing t
|
||||
|
||||
### Is Home Assistant Cloud open source?
|
||||
|
||||
The majority of Home Assistant Cloud is open source. The Alexa skill source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/alexa/smart_home.py) (with manual setup instructions [here](https://github.com/mike-grant/haaska/)) and the Google Assistant source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/smart_home.py) (with manual setup instructions [here](https://www.home-assistant.io/components/google_assistant/)). Our account page and relayer are not open source.
|
||||
The majority of Home Assistant Cloud is open source. The Alexa skill source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/alexa/smart_home.py) (with manual setup instructions [here](https://github.com/mike-grant/haaska/)) and the Google Assistant source code is [here](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/smart_home.py) (with manual setup instructions [here](/components/google_assistant/)). Our account page and relayer are not open source.
|
||||
|
||||
### Will you offer a lifetime plan for a one time fee?
|
||||
|
||||
|
||||
@ -81,5 +81,5 @@ If you think that you are not enough qualified to do it, don’t worry, there ar
|
||||
|
||||
## Not a coder? Not a problem!
|
||||
|
||||
Also, feel free to [report bugs](https://github.com/home-assistant/home-assistant/issues/new/choose), give us feedback about your user experience, tell the community about your [super cool setup](https://community.home-assistant.io/c/projects), create a [super awesome frontend](https://community.home-assistant.io/c/projects/frontend) with [Lovelace](https://www.home-assistant.io/lovelace) or help other users in the [forum](https://community.home-assistant.io/).
|
||||
Also, feel free to [report bugs](https://github.com/home-assistant/home-assistant/issues/new/choose), give us feedback about your user experience, tell the community about your [super cool setup](https://community.home-assistant.io/c/projects), create a [super awesome frontend](https://community.home-assistant.io/c/projects/frontend) with [Lovelace](/lovelace) or help other users in the [forum](https://community.home-assistant.io/).
|
||||
|
||||
|
||||
@ -98,10 +98,10 @@ On the devices side, we got basic support for the new IKEA TRÅDFRI switches, Ho
|
||||
[@StevenLooman]: https://github.com/StevenLooman
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@hobbypunk90]: https://github.com/hobbypunk90
|
||||
[hangouts docs]: https://www.home-assistant.io/components/hangouts/
|
||||
[media_player.dlna_dmr docs]: https://www.home-assistant.io/components/media_player.dlna_dmr/
|
||||
[media_player.snapcast docs]: https://www.home-assistant.io/components/media_player.snapcast/
|
||||
[upnp docs]: https://www.home-assistant.io/components/upnp/
|
||||
[hangouts docs]: /components/hangouts/
|
||||
[media_player.dlna_dmr docs]: /components/media_player.dlna_dmr/
|
||||
[media_player.snapcast docs]: /components/media_player.snapcast/
|
||||
[upnp docs]: /components/upnp/
|
||||
|
||||
## New Features
|
||||
|
||||
|
||||
@ -866,4 +866,4 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[zha docs]: /components/zha/
|
||||
[zoneminder docs]: /components/zoneminder/
|
||||
[zwave docs]: /components/zwave/
|
||||
[platform_options]: https://www.home-assistant.io/docs/configuration/platform_options/#scan-interval
|
||||
[platform_options]: /docs/configuration/platform_options/#scan-interval
|
||||
|
||||
@ -52,7 +52,7 @@ We hope that this was an oversight on their end and that it will be reverted sho
|
||||
Thread by member of the Harmony Team.
|
||||
</p>
|
||||
|
||||
**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant developer [@ehendrix23] is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](https://www.home-assistant.io/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release.
|
||||
**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant developer [@ehendrix23] is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release.
|
||||
|
||||
[@ehendrix23]: https://github.com/ehendrix23
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ og_image: /images/blog/2019-01-lovelace/demo.png
|
||||
|
||||
Today we're happy to announce that our new Lovelace UI, which has been in beta for the last 8 months, is becoming the new default interface of [Home Assistant 0.86](/blog/2019/01/23/release-86/). With Lovelace we're taking a new approach to building user interfaces for Home Assistant. We're no longer storing the look and feel of your UI in your configuration.yaml, requiring restarts for changes. With Lovelace we're keeping the UI concerns in the UI<sup>1</sup>, unlocking a whole new set of features:
|
||||
|
||||
- [24 cards](https://www.home-assistant.io/lovelace/alarm-panel/) to place and configure as you like.
|
||||
- [24 cards](/lovelace/alarm-panel/) to place and configure as you like.
|
||||
- UI Editor. A configuration UI to manage your Lovelace UI including live preview when editing cards.
|
||||
- Fast. Using a static config allows us to build up the UI once.
|
||||
- Customizable.
|
||||
|
||||
@ -154,4 +154,4 @@ Have fun!
|
||||
|
||||
|
||||
[@maxandersen]: https://xam.dk/about
|
||||
[hass-087]: https://www.home-assistant.io/blog/2019/02/06/release-87/
|
||||
[hass-087]: /blog/2019/02/06/release-87/
|
||||
|
||||
@ -140,13 +140,13 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](https://www.home-assistant.io/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
|
||||
- __http.api_password__ - __Deprecated__ - Users who are still using api_password for authentication will need to move its configuration under auth_providers. Please see the [updated documentation](/docs/authentication/providers/#legacy-api-password) for further details. Those who don't make this change will see an INFO level reminder in the Home Assistant logs until the fix is made for a time, but please note, __api_password authentication will eventually be removed completely__ and we advise users to change to use one of the [other authentication methods](/docs/authentication/providers/#available-auth-providers). If you manually specify auth providers in your `configuration.yaml`, you will need to migrate your API Password from the http section to the auth provider section to continue using it. ([@awarecan] - [#21884]) ([api docs]) ([frontend docs]) ([hassio docs]) ([http docs]) ([mqtt docs]) ([websocket_api docs]) ([zeroconf docs]) ([camera.proxy docs])
|
||||
- __Default Config__ - Default config no longer contains the discovery component. That is now part of the initial written configuration.yaml. If you rely on default config and want to use discovery, add `discovery:` back to your configuration.yaml.
|
||||
- __Netatmo__
|
||||
* Added support for multiple Netatmo thermostats/valves allowing the user to specify different homes or rooms! Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for configuration details. ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs])
|
||||
* `current_operation` will no longer return the the boiler status, but the operation_mode. For example, heat, cool, or idle. Please check the [updated documentation](https://www.home-assistant.io/components/climate.netatmo/) for more details. ([@shanbs] - [#21633]) ([netatmo docs])
|
||||
* Added support for multiple Netatmo thermostats/valves allowing the user to specify different homes or rooms! Please check the [updated documentation](/components/climate.netatmo/) for configuration details. ([@shanbs] - [#19407]) ([netatmo docs]) ([climate.netatmo docs])
|
||||
* `current_operation` will no longer return the the boiler status, but the operation_mode. For example, heat, cool, or idle. Please check the [updated documentation](/components/climate.netatmo/) for more details. ([@shanbs] - [#21633]) ([netatmo docs])
|
||||
- __Utility Meter__ - Currently the offset configuration parameter is an integer that limits daily cycles to have offsets in days, monthly cycles to have offsets in months, etc.
|
||||
This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the [updated documentation](https://www.home-assistant.io/components/utility_meter/) for the new configuration options. ([@dgomes] - [#20926]) ([utility_meter docs])
|
||||
This change increases the flexibility of offset by making it a more flexible time period that can be described in a combination of hours, days, months, etc. This makes it possible for a yearly cycle to start at a given day of a given month. Please see the [updated documentation](/components/utility_meter/) for the new configuration options. ([@dgomes] - [#20926]) ([utility_meter docs])
|
||||
- __KNX__ - An update for xknx to version 0.10.0 requires users to update their configuration by changing `target_temperature_address` to `target_temperature_state_address`. Other fixes and features:
|
||||
* Connection config can now be configured in xknx.yml.
|
||||
* Introduce a configurable rate limit which limits the number of KNX telegrams sent to the bus per second.
|
||||
|
||||
@ -10,7 +10,7 @@ comments: true
|
||||
categories: Announcements
|
||||
---
|
||||
|
||||
1 year, 11 months and 17 days ago or 716 days ago, [I announced Home Assistant Companion for iOS on this blog](https://www.home-assistant.io/blog/2017/04/15/ios/).
|
||||
1 year, 11 months and 17 days ago or 716 days ago, [I announced Home Assistant Companion for iOS on this blog](/blog/2017/04/15/ios/).
|
||||
Ever since then, at least once a week, sometimes far more often, I am asked a question that I haven't been able to truly answer until today.
|
||||
It's a question that has gotten on my nerves almost every time I've seen it. I could understand why people were wanting an official Android app to mirror the functionality of the iOS app.
|
||||
But I never thought of myself as the person to best deliver on that idea.
|
||||
|
||||
@ -203,8 +203,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
|
||||
- __iOS__ - Improves the text description of ATTR_BATTERY_STATE_UNPLUGGED from Unplugged to Not Charging as many new iOS devices now use Wireless charging and there is no concept of "Plugging In". This is potentially a breaking change if you have automations making use of "unplugged". ([@FattusMannus] - [#22152]) ([ios docs])
|
||||
- __Iliad Italy__ - __Removed__ - This was removed because it uses webscraping. ([@eliseomartelli] - [#22175])
|
||||
- __Netgear lte__ - The previous three components (network, notify, and sensor) now fall under one netgear_lte component. Check the [updated documentation](https://www.home-assistant.io/components/netgear_lte/) for more information. ([@amelchio] - [#22105]) ([netgear_lte docs])
|
||||
- __API streams sensor__ - __Removed__ - This sensor component was designed to count connected front-end clients. However, it depended on the implementation details of other components, and has therefore been broken since 0.80, so it has been removed. The replacement sensor is now the [websocket_api sensor](https://www.home-assistant.io/components/websocket_api/), which does basically the same thing apart from the rename. ([@Swamp-Ig] - [#22200]) ([websocket_api docs])
|
||||
- __Netgear lte__ - The previous three components (network, notify, and sensor) now fall under one netgear_lte component. Check the [updated documentation](/components/netgear_lte/) for more information. ([@amelchio] - [#22105]) ([netgear_lte docs])
|
||||
- __API streams sensor__ - __Removed__ - This sensor component was designed to count connected front-end clients. However, it depended on the implementation details of other components, and has therefore been broken since 0.80, so it has been removed. The replacement sensor is now the [websocket_api sensor](/components/websocket_api/), which does basically the same thing apart from the rename. ([@Swamp-Ig] - [#22200]) ([websocket_api docs])
|
||||
- __Public Transit (GTFS)__
|
||||
* The state for this sensor component was a countdown in minutes. If the next departure was in a few hours, this number became quite large and a tad harder to rapidly calculate mentally (463 minutes anyone?). The sensor's state output has been changed from minutes to an ISO 8601 UTC timestamp, which allows the UI to interpret the state as needed. ([@renemarc] - [#21053]) ([gtfs docs])
|
||||
* Sensor updates were running many database queries to populate attributes, on top of the bus schedule queries themselves. This is doubled with two sensors. That led to a lot of slowdowns for everything else when using an SD card! Considering that some data never changes (agency, routes...) and that others like departure times are good until invalidated, now we fetch such metadata at first and then only when relevant changes do occur. GTFS sensor attributes are now named using the standard snake_case format. ([@renemarc] - [#20966]) ([gtfs docs])
|
||||
|
||||
@ -23,7 +23,7 @@ Demo with an add-on on Ingress.
|
||||
Some add-ons already have been upgraded to support the new Ingress feature. Here are a couple of add-ons that support Ingress and are available on the add-on store right now:
|
||||
|
||||
Core add-ons:
|
||||
* [Configurator](https://www.home-assistant.io/addons/configurator/)
|
||||
* [Configurator](/addons/configurator/)
|
||||
* [deCONZ](https://github.com/home-assistant/hassio-addons/tree/master/deconz#readme)
|
||||
|
||||
Community add-ons:
|
||||
@ -78,7 +78,7 @@ Please update your Home Assistant installation to 0.91.3 or higher.
|
||||
We found a last minute issue impacting Firefox based browsers (including the Tor Browser). There are some issues accessing add-ons that use WebSockets. We have identified the issue and expect it to be solved with the release of Home Assistant 0.91.4.
|
||||
|
||||
|
||||
[Configurator]: https://www.home-assistant.io/addons/configurator/
|
||||
[Configurator]: /addons/configurator/
|
||||
[deCONZ]: https://github.com/home-assistant/hassio-addons/tree/master/deconz#readme
|
||||
[Node-RED]: https://github.com/hassio-addons/addon-node-red#readme
|
||||
[Visual Studio Code]: https://github.com/hassio-addons/addon-vscode#readme
|
||||
|
||||
@ -143,19 +143,19 @@ Finally, if you are still receiving a message that your configuration contains e
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@robbiet480]: https://github.com/robbiet480
|
||||
[@zxdavb]: https://github.com/zxdavb
|
||||
[alexa docs]: https://www.home-assistant.io/components/alexa/
|
||||
[auth docs]: https://www.home-assistant.io/components/auth/
|
||||
[cast docs]: https://www.home-assistant.io/components/cast/
|
||||
[cloud docs]: https://www.home-assistant.io/components/cloud/
|
||||
[geniushub docs]: https://www.home-assistant.io/components/geniushub/
|
||||
[google_assistant docs]: https://www.home-assistant.io/components/google_assistant/
|
||||
[heos docs]: https://www.home-assistant.io/components/heos/
|
||||
[hue docs]: https://www.home-assistant.io/components/hue/
|
||||
[mobile_app docs]: https://www.home-assistant.io/components/mobile_app/
|
||||
[myq docs]: https://www.home-assistant.io/components/myq/
|
||||
[netatmo_public docs]: https://www.home-assistant.io/components/netatmo_public/
|
||||
[traccar docs]: https://www.home-assistant.io/components/traccar/
|
||||
[upnp docs]: https://www.home-assistant.io/components/upnp/
|
||||
[alexa docs]: /components/alexa/
|
||||
[auth docs]: /components/auth/
|
||||
[cast docs]: /components/cast/
|
||||
[cloud docs]: /components/cloud/
|
||||
[geniushub docs]: /components/geniushub/
|
||||
[google_assistant docs]: /components/google_assistant/
|
||||
[heos docs]: /components/heos/
|
||||
[hue docs]: /components/hue/
|
||||
[mobile_app docs]: /components/mobile_app/
|
||||
[myq docs]: /components/myq/
|
||||
[netatmo_public docs]: /components/netatmo_public/
|
||||
[traccar docs]: /components/traccar/
|
||||
[upnp docs]: /components/upnp/
|
||||
|
||||
## If you need help...
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ This month marked a year since Ubiquiti got involved, and also their last month,
|
||||
|
||||
For the last year, the Home Assistant community has been working on building a user-friendly version of Home Assistant, also known as Home Assistant 1.0.
|
||||
|
||||
We’re aiming to release Home Assistant 1.0 this year. With Home Assistant 1.0, installation and basic functionality can be done via a user interface. Advanced options will require entering an advanced mode or set up via `configuration.yaml`. Check out last year’s [state of the union](https://www.home-assistant.io/blog/2018/11/16/state-of-the-union/) for more details. We have started using [this project board](https://github.com/orgs/home-assistant/projects/1) to keep track of our progress.
|
||||
We’re aiming to release Home Assistant 1.0 this year. With Home Assistant 1.0, installation and basic functionality can be done via a user interface. Advanced options will require entering an advanced mode or set up via `configuration.yaml`. Check out last year’s [state of the union](/blog/2018/11/16/state-of-the-union/) for more details. We have started using [this project board](https://github.com/orgs/home-assistant/projects/1) to keep track of our progress.
|
||||
|
||||
While we’re working hard on Home Assistant 1.0, we have also started working on the next goal for post 1.0 launch: a better story for manufacturers and integrations.
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ If you are migrating from the custom integration, [please read the instructions]
|
||||
|
||||
One more thing… This release improves the Home Assistant Cloud Alexa integration. Just like Google Assistant, it is now possible to manage which entities are exposed to Amazon via the user interface. Alexa actually offers some cool features around this. Any change you make is instantly reflected inside Alexa. Add an entity? Control it instantly via Alexa.
|
||||
|
||||
However, we didn't stop there. The [manual installations of Alexa](https://www.home-assistant.io/components/alexa.smart_home/#alexa-component-configuration) has had optional proactive state reporting since earlier this year, and this is now available for Home Assistant Cloud users too. If you choose to opt-in to this, every state change of your exposed entities is sent to Amazon as soon as they happen. It allows Amazon Echos with displays, to instantly reflect the state and allows you to create routines inside Amazon powered by your Home Assistant entities.
|
||||
However, we didn't stop there. The [manual installations of Alexa](/components/alexa.smart_home/#alexa-component-configuration) has had optional proactive state reporting since earlier this year, and this is now available for Home Assistant Cloud users too. If you choose to opt-in to this, every state change of your exposed entities is sent to Amazon as soon as they happen. It allows Amazon Echos with displays, to instantly reflect the state and allows you to create routines inside Amazon powered by your Home Assistant entities.
|
||||
|
||||
<div class="videoWrapper">
|
||||
<iframe width="853" height="480" src="https://www.youtube-nocookie.com/embed/8NfDr5lBcmQ" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user