mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
2c344a0d73
@ -142,13 +142,13 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 75
|
||||
current_patch_version: 1
|
||||
date_released: 2018-08-04
|
||||
current_patch_version: 2
|
||||
date_released: 2018-08-06
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
# Major release:
|
||||
patch_version_notes: "#release-0751---august-4"
|
||||
patch_version_notes: "#release-0752---august-6"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
# Date we moved to Discourse for comments
|
||||
|
||||
@ -96,7 +96,7 @@ Variables:
|
||||
- **search**: (*Optional*): If set will only trigger for matched events.
|
||||
- **offset**: (*Optional*): A set of characters that precede a number in the event title for designating a pre-trigger state change on the sensor. (Default: `!!`)
|
||||
- **ignore_availability**: (*Optional*): Should we respect `free`/`busy` flags? (Defaults to `true`)
|
||||
|
||||
|
||||
From this we will end up with the binary sensors `calendar.test_unimportant` and `calendar.test_important` which will toggle themselves on/off based on events on the same calendar that match the search value set for each. You'll also have a sensor `calendar.test_everything` that will not filter events out and always show the next event available.
|
||||
|
||||
But what if you only wanted it to toggle based on all events? Just leave out the *search* parameter.
|
||||
|
||||
@ -13,7 +13,14 @@ ha_release: pre 0.7
|
||||
---
|
||||
|
||||
|
||||
The `tplink` platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device. This includes the ArcherC9 line.
|
||||
The `tplink` platform allows you to detect presence by looking at connected devices to a [TP-Link](https://www.tp-link.com) device.
|
||||
|
||||
Currently supported devices includes the following:
|
||||
|
||||
- Archer C7 firmware version 150427
|
||||
- Archer C9 firmware version 150811
|
||||
- EAP-225 AP with latest firmware version
|
||||
- Archer D9 firmware version 0.9.1 0.1 v0041.0 Build 160224 Rel.59129n
|
||||
|
||||
<p class='note'>
|
||||
TP-Link devices typically only allow one login at a time to the admin console. This component will count towards your one allowed login. Depending on how aggressively you configure device_tracker you may not be able to access the admin console of your TP-Link device without first stopping Home Assistant. Home Assistant takes a few seconds to login, collect data, and log out. If you log into the admin console manually, remember to log out so that Home Assistant can log in again.
|
||||
@ -32,7 +39,7 @@ device_tracker:
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address of your router, e.g., 192.168.1.1.
|
||||
- **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
|
||||
- **username** (*Required*): The username of a user with administrative privileges, usually *admin*. The Archer D9 last firmware does not require a username.
|
||||
- **password** (*Required*): The password for your given admin account.
|
||||
|
||||
For Archer C9 models running firmware version 150811 or later please use the encrypted password you can retrieve like this:
|
||||
@ -45,3 +52,8 @@ For Archer C9 models running firmware version 150811 or later please use the enc
|
||||
6. Copy the returned value to your Home Assistant configuration as password.
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
||||
For Archer D9 model the default ip is 192.168.1.1, the username is not necessary and you can leave that field blank.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -70,6 +70,7 @@ Currently known supported models:
|
||||
- UE65KS8005 (port must be set to 8001, On/Off, Forward/Backward, Volume are OK, but no Play button)
|
||||
- UE6199UXZG (port must be set to 8001, On/Off, Forward/Backward, Volume control, but no Play button)
|
||||
- Q7F (port must be set to 8001, MAC must be specified for Power On)
|
||||
- UE40KU6400U (port must be set to 8001, and `pip3 install websocket-client` must be executed)
|
||||
|
||||
Currently tested but not working models:
|
||||
|
||||
|
||||
@ -16,3 +16,7 @@ ha_iot_class: "Local Push"
|
||||
The `rpi_pfio` component is the base for all related [PiFace Digital I/O (PFIO)](http://www.piface.org.uk/) platforms in Home Assistant. There is no setup needed for the component itself; for the platforms, please check their corresponding pages.
|
||||
|
||||
Set the jumpers on the PiFace board for address 0 (JP1: 1-2, JP2: 1-2).
|
||||
|
||||
## {% linkable_title Use with HassOS %}
|
||||
|
||||
Note that the PiFace Digital 2 uses the Raspberry Pi SPI port, which is disabled by default when using [HassOS](https://github.com/home-assistant/hassos). When using HassOS, you must mount the SD card on another computer and access the boot partition on the card. Edit the `config.txt` file and add the line `dtparam=spi=on` to the end. This should enable SPI when HassOS is booted and allow Home Assistant to access the PiFace Digital 2 board.
|
||||
|
||||
@ -27,7 +27,8 @@ To isolate the Home Assistant installation a [venv](https://docs.python.org/3/li
|
||||
|
||||
```bash
|
||||
$ sudo mkdir -p /opt/homeassistant
|
||||
$ sudo chown -R user:group /opt/homeassistant
|
||||
$ sudo useradd -rm homeassistant -G dialout,gpio
|
||||
$ sudo chown -R homeassistant:homeassistant /opt/homeassistant
|
||||
```
|
||||
Now switch to the new directory, setup the venv, and activate it.
|
||||
|
||||
|
||||
@ -94,7 +94,7 @@ You can now reach your installation on your Raspberry Pi over the web interface
|
||||
When you run the `hass` command for the first time, it will download, install and cache the necessary libraries/dependencies. This procedure may take anywhere between 5 to 10 minutes. During that time, you may get "site cannot be reached" error when accessing the web interface. This will only happen for the first time, and subsequent restarts will be much faster.
|
||||
</p>
|
||||
|
||||
If you want setup `hass` as a daemon and autostart it on boot please refer to [Autostart Home Assistant](/docs/autostart/).
|
||||
If you want to setup `hass` as a daemon and autostart it on boot please refer to [Autostart Home Assistant](/docs/autostart/).
|
||||
|
||||
### {% linkable_title Updating %}
|
||||
|
||||
|
||||
@ -44,6 +44,12 @@ This release also includes a bunch more Tuya integrations thanks to [@huangyupen
|
||||
- Fix rfxtrx device id matching ([@Danielhiversen] - [#15819]) ([rfxtrx docs])
|
||||
- Fix custom panel and Hass.io panel ([@balloob])
|
||||
|
||||
## {% linkable_title Release 0.75.2 - August 6 %}
|
||||
|
||||
- Upgrade voluptuous to 0.11.5 ([@fabaff] - [#15830])
|
||||
- Fix envisalink reconnect ([@Cinntax] - [#15832]) ([envisalink docs])
|
||||
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
@ -406,3 +412,8 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[@superpuffin]: https://github.com/superpuffin
|
||||
[rfxtrx docs]: /components/rfxtrx/
|
||||
[sensor.dht docs]: /components/sensor.dht/
|
||||
[#15830]: https://github.com/home-assistant/home-assistant/pull/15830
|
||||
[#15832]: https://github.com/home-assistant/home-assistant/pull/15832
|
||||
[@Cinntax]: https://github.com/Cinntax
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[envisalink docs]: /components/envisalink/
|
||||
|
||||
@ -16,6 +16,7 @@ There are various ways to get in touch with the Home Assistant community. It doe
|
||||
- [Forum][forum]
|
||||
- [Discord Chat Server][discord] for general Home Assistant discussions and questions.
|
||||
- Follow us on [Twitter][twitter], use [@home_assistant][twitter]
|
||||
- Join the [Facebook community][facebook]
|
||||
- Join the [Google+ community][google-plus]
|
||||
- Join the Reddit in [/r/homeassistant][reddit]
|
||||
|
||||
@ -85,6 +86,7 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
|
||||
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[twitter]: https://twitter.com/home_assistant
|
||||
[facebook]: https://www.facebook.com/homeassistantio
|
||||
[google-plus]: https://plus.google.com/u/0/b/110560654828510104551/communities/106562234893511202708
|
||||
[reddit]: https://reddit.com/r/homeassistant
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user