mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-24 01:37:23 +00:00
Add 0.7.4 release blog post
This commit is contained in:
parent
966416644d
commit
f4deb41e4c
2
_deploy
2
_deploy
@ -1 +1 @@
|
||||
Subproject commit 65ede4184b03f7aeeca7fb149351501dc52d6de1
|
||||
Subproject commit 0cd346e67621d1f676d6873e94fc289317ecf2f0
|
@ -0,0 +1,47 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant goes geo with OwnTracks"
|
||||
description: "Home Assistant 0.7.4 has been released with support for OwnTracks and geofencing."
|
||||
date: 2015-10-05 21:49:00 +0700
|
||||
date_formatted: "October 5, 2015"
|
||||
author: Paulus Schoutsen
|
||||
comments: true
|
||||
categories: release-notes
|
||||
og_image: /images/screenshots/map.png
|
||||
---
|
||||
|
||||
A few weeks have past and it is time again for another release: version 0.7.4. This time we're very
|
||||
glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map.
|
||||
The geo support consists of three different parts:
|
||||
|
||||
- [OwnTracks platform for the device tracker][platform-owntracks] to get locations for devices
|
||||
- Brand new [zone component][component-zone] to define zones to identify locations and [trigger automation][zone-automation]
|
||||
- A map in the UI to see all this ([see it in action in the demo](/demo/))
|
||||
|
||||
We have added a new [getting started section][start-presence] to get up and running.
|
||||
|
||||
[platform-owntracks]: /components/device_tracker.owntracks.html
|
||||
[component-zone]: /components/zone.html
|
||||
[zone-automation]: /components/automation.html#zone-trigger
|
||||
[start-presence]: /getting-started/presence-detection.html
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/map.png' />
|
||||
Map in Home Assistant showing two people and three zones (home, school, work)
|
||||
</p>
|
||||
|
||||
Ofcourse more things happened in the last three weeks. I'm moving away from my usual long post to a
|
||||
short summary of highlights:
|
||||
|
||||
<a href='/components/media_player.plex.html'>
|
||||
<img src='/images/supported_brands/plex.png' style='border:none; box-shadow: none; float: right;' height='50' />
|
||||
</a>
|
||||
|
||||
- Sensor: [rest platform](/components/sensor.rest.html) added ([@fabaff](https://github.com/fabaff))
|
||||
- Alarm Control Panel: [MQTT platform](/components/alarm_control_panel.mqtt.html) added ([@sfam](https://github.com/sfam))
|
||||
- Media Player: [Plex platform](/components/media_player.plex.html) added ([@miniconfig](https://github.com/miniconfig, [@adrienbrault](https://github.com/adrienbrault))
|
||||
- Dev Tools: services can now show description of fields ([@balloob](https://github.com/balloob))
|
||||
- MQTT: Support for certificates and improved error reporting ([@balloob](https://github.com/balloob))
|
||||
- Light: [limitlessled platform](/components/light.limitlessled.html) extended with white light support ([@auchter](https://github.com/auchter))
|
||||
- Fuzzy matching for scenes ([@pavoni](https://github.com/pavoni))
|
||||
- Scene support for media player ([@maddox](https://github.com/maddox))
|
@ -10,10 +10,10 @@ footer: true
|
||||
---
|
||||
|
||||
<img src='/images/supported_brands/mqtt.png' class='brand pull-right' />
|
||||
This platform enables the possibility to control an MQTT alarm. The alarm will only change state after receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT alarm will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state will
|
||||
be `unknown`.
|
||||
|
||||
To enable this alarm, add the following lines to your `configuration.yaml` for a GET request:
|
||||
This platform enables the possibility to control an MQTT alarm. The alarm will only change state after
|
||||
receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT
|
||||
alarm will receive an instant state update after subscription and will start with correct state. Otherwise,
|
||||
the initial state will be `unknown`.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
@ -30,16 +30,16 @@ automation:
|
||||
offset: '-01:00:00'
|
||||
- platform: state
|
||||
entity_id: group.all_devices
|
||||
state: home
|
||||
state: 'home'
|
||||
condition:
|
||||
# Prefix the first line of each condition configuration
|
||||
# with a '-'' to enter multiple
|
||||
- platform: state
|
||||
entity_id: group.all_devices
|
||||
state: home
|
||||
state: 'home'
|
||||
- platform: time
|
||||
after: "16:00:00"
|
||||
before: "23:00:00"
|
||||
after: '16:00:00'
|
||||
before: '23:00:00'
|
||||
action:
|
||||
service: homeassistant.turn_on
|
||||
entity_id: group.living_room
|
||||
@ -70,10 +70,6 @@ automation:
|
||||
message: 'Paulus left the house'
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
With the updated automation layout, you are now able to list all rules under on a single `automation:` entry. Use `-alias` to define the start of each rule.
|
||||
</p>
|
||||
|
||||
- [Jump to conditions](#conditions)
|
||||
- [Jump to actions](#actions)
|
||||
- [Jump to troubleshooting](#troubleshooting)
|
||||
@ -134,11 +130,11 @@ automation:
|
||||
platform: state
|
||||
entity_id: device_tracker.paulus
|
||||
# Optional
|
||||
from: "not_home"
|
||||
to: "home"
|
||||
from: 'not_home'
|
||||
to: 'home'
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
<p class='note warning'>
|
||||
Use quotes around your values for <code>from</code> and <code>to</code> to avoid the YAML parser
|
||||
interpreting some values as booleans.
|
||||
</p>
|
||||
@ -170,7 +166,7 @@ automation:
|
||||
# All following are optional.
|
||||
# When 'after' is used, you cannot also match on hour, minute, seconds.
|
||||
# Military time format.
|
||||
# after: "15:32:00"
|
||||
# after: '15:32:00'
|
||||
hours: 0
|
||||
minutes: 5
|
||||
seconds: 0
|
||||
@ -258,8 +254,8 @@ automation:
|
||||
condition:
|
||||
platform: time
|
||||
# At least one of the following is required.
|
||||
after: "15:00:00"
|
||||
before: "23:00:00"
|
||||
after: '15:00:00'
|
||||
before: '23:00:00'
|
||||
weekday:
|
||||
- mon
|
||||
- wed
|
||||
|
@ -114,7 +114,8 @@ of CloudMQTT (port range 20 000 - 30 000).
|
||||
- [MQTT Switch](/components/switch.mqtt.html)
|
||||
- [MQTT Device Tracker](/components/device_tracker.mqtt.html)
|
||||
- [OwnTracks Device Tracker](/components/device_tracker.owntracks.html)
|
||||
- [MQTT-automation rule](/components/automation.html#mqtt-based-automation)
|
||||
- [MQTT automation rule](/components/automation.html#mqtt-based-automation)
|
||||
- [MQTT alarm](/components/alarm_control_panel.mqtt.html)
|
||||
- Integrating it into a component. See the [MQTT example component](https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py) how to do this.
|
||||
|
||||
## {% linkable_title Testing your setup %}
|
||||
|
@ -9,6 +9,11 @@ sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
Z-Wave support is currently broken as we're unable to compile
|
||||
<a href='https://github.com/OpenZWave/python-openzwave/tree/python3'>Python Open Z-Wave</a>.
|
||||
</p>
|
||||
|
||||
<img src='/images/supported_brands/z-wave.png' class='brand pull-right' />
|
||||
|
||||
[Z-Wave](http://www.z-wave.com/) support for Home Assistant is very new. We have started now by integrating only the sensors.
|
||||
|
@ -170,3 +170,8 @@ go automate!
|
||||
- Learn about [scripts](/components/script.html) to help you trigger multiple actions and delays
|
||||
- Learn about [scenes](/components/scene.html) to help you set many entities at once to your liking
|
||||
- Setup the [notification component](/components/#notify-service) to sent yourself messages
|
||||
|
||||
<p class='note warning'>
|
||||
Whenever you write the value <code>on</code> or <code>off</code>, surround it with quotes to avoid
|
||||
the YAML parser interpreting the values as booleans.
|
||||
</p>
|
||||
|
@ -48,13 +48,13 @@ of these parameters. This can be done by adding the following config to the `hom
|
||||
# Example configuration.yaml entry
|
||||
homeassistant:
|
||||
|
||||
# Add this to your existing configuration
|
||||
# Only the `entity_id` is required. All other options are optional.
|
||||
customize:
|
||||
some.entity_id:
|
||||
hidden: true
|
||||
entity_picture: http://placehold.it/200x200
|
||||
friendly_name: My better name
|
||||
# Add this to your existing configuration
|
||||
# Only the `entity_id` is required. All other options are optional.
|
||||
customize:
|
||||
some.entity_id:
|
||||
hidden: true
|
||||
entity_picture: http://placehold.it/200x200
|
||||
friendly_name: My better name
|
||||
```
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user