mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-13 12:26:50 +00:00
Merge branch 'current' into next
This commit is contained in:
Fabian Affolter
commit
94a68b65bf
@ -28,7 +28,7 @@ Set up [Mosquitto](https://mosquitto.org/) as MQTT broker.
|
||||
```
|
||||
|
||||
<p class='warning note'>
|
||||
Make sure you use logins and disable anonymous access if you want to secure the system.
|
||||
Since version 4.1 of the addon, an explicit ACL definition is now required, [see these instructions](https://www.home-assistant.io/addons/mosquitto/#access-control-lists-acls).
|
||||
</p>
|
||||
|
||||
{% configuration %}
|
||||
@ -63,7 +63,7 @@ To use the Mosquitto as [broker](/docs/mqtt/broker/#run-your-own), go to the int
|
||||
|
||||
3. Once back on-line, return to `Configuration > Integrations` and select configure next to `MQTT`.
|
||||
|
||||
```
|
||||
```text
|
||||
Broker: YOUR_HASSIO_IP_ADDRESS
|
||||
Port: 1883
|
||||
Username: MQTT_USERNAME
|
||||
@ -86,13 +86,24 @@ See the following links for more information:
|
||||
* [Mosquitto topic restrictions](http://www.steves-internet-guide.com/topic-restriction-mosquitto-configuration/)
|
||||
* [Mosquitto.conf man page](https://mosquitto.org/man/mosquitto-conf-5.html)
|
||||
|
||||
Add the following configuration to enable ACLs:
|
||||
Add the following configuration to enable **unrestricted** access to all topics.
|
||||
|
||||
1. Set the `active` flag within the `customize` section to `true` in your configuration.
|
||||
2. Create a file in `/share/mosquitto` named `acl.conf` with the following contents:
|
||||
1. Enable the customize flag
|
||||
```json
|
||||
"customize": {
|
||||
"active": true,
|
||||
"folder": "mosquitto"
|
||||
},
|
||||
```
|
||||
|
||||
2. Create `/share/mosquitto/acl.conf` with the contents:
|
||||
```text
|
||||
acl_file /share/mosquitto/accesscontrollist
|
||||
```
|
||||
3. Create a file in `/share/mosquitto` named `accesscontrollist` and add contents according to your requirements.
|
||||
|
||||
The `/share` folder can be found on the host filesystem under `/usr/share/hassio/share`, or via the `Share` folder through SMB (Samba).
|
||||
3. Create `/share/mosquitto/accesscontrollist` with the contents:
|
||||
```text
|
||||
topic readwrite #
|
||||
```
|
||||
|
||||
The `/share` folder can be accessed via SMB, or on the host filesystem under `/usr/share/hassio/share`.
|
||||
|
||||
@ -11,23 +11,25 @@ ha_category:
|
||||
- Climate
|
||||
- Binary Sensor
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: 0.87
|
||||
logo: danfoss_air.png
|
||||
ha_iot_class: Local Polling
|
||||
redirect_from:
|
||||
- /components/binary_sensor.danfoss_air/
|
||||
- /components/sensor.danfoss_air/
|
||||
- /components/switch.danfoss_air/
|
||||
---
|
||||
|
||||
The `danfoss_air` component allows you to access information from your Danfoss Air HRV unit.
|
||||
|
||||
*Note*: Danfoss Air CCM only accepts one TCP connection at a time. Due to this the component
|
||||
will not work while you have the HRV PC-Tool open.
|
||||
*Note*: Danfoss Air CCM only accepts one TCP connection at a time. Due to this the component will not work while you have the HRV PC-Tool open.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Binary Sensor](#binary-sensor)
|
||||
- [Binary sensor](#binary-sensor)
|
||||
- [Sensor](#sensor)
|
||||
- [Switch](#switch)
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -57,3 +59,9 @@ The following sensors are supported.
|
||||
- **Extract temperature:** Air temperature of the air extracted from the house.
|
||||
- **Exhaust temperature:** Exhausted air temperature.
|
||||
- **Remaining filter lifetime:** Reamining filter lifetime measured in percent.
|
||||
|
||||
## {% linkable_title Switch %}
|
||||
|
||||
The following switches are supported.
|
||||
|
||||
- **Boost:** Switch to manually activate boost.
|
||||
|
||||
@ -96,7 +96,7 @@ If everything is working fine you can disable the pure `api` service in RouterOS
|
||||
To use this device tracker you need restricted privileges only. To enhance the security of your MikroTik device create a "read only" user who is able to connect to API only:
|
||||
|
||||
```bash
|
||||
/user group add name=homeassistant policy=read,api,!local,!telnet,!ssh,!ftp,!reboot,!write,!policy,!test,!winbox,!password,!web,!sniff,!sensitive on,!dude,!tikapp
|
||||
/user group add name=homeassistant policy=read,api,!local,!telnet,!ssh,!ftp,!reboot,!write,!policy,!test,!winbox,!password,!web,!sniff,!sensitive,!romon,!dude,!tikapp
|
||||
/user add group=homeassistant name=homeassistant
|
||||
/user set password="YOUR_PASSWORD" homeassistant
|
||||
```
|
||||
|
||||
@ -111,7 +111,6 @@ google_assistant:
|
||||
exposed_domains:
|
||||
- switch
|
||||
- light
|
||||
- group
|
||||
entity_config:
|
||||
switch.kitchen:
|
||||
name: CUSTOM_NAME_FOR_GOOGLE_ASSISTANT
|
||||
@ -193,6 +192,10 @@ Currently, the following domains are available to be used with Google Assistant,
|
||||
- climate (temperature setting, operation_mode)
|
||||
- vacuum (dock/start/stop/pause)
|
||||
|
||||
<p class='note warning'>
|
||||
The domain groups contains groups containing all items, by example group.all_automations. When telling Google Assistant to shut down everything, this will lead in this example to disabling all automations
|
||||
</p>
|
||||
|
||||
### {% linkable_title Media Player Sources %}
|
||||
|
||||
Media Player sources are sent via the Modes trait in Google Assistant.
|
||||
|
||||
@ -40,8 +40,8 @@ Most lights do not support all attributes. You can check the platform documentat
|
||||
| `color_temp` | yes | An integer in mireds representing the color temperature you want the light to be.
|
||||
| `kelvin` | yes | Alternatively, you can specify the color temperature in Kelvin.
|
||||
| `color_name` | yes | A human-readable string of a color name, such as `blue` or `goldenrod`. All [CSS3 color names](https://www.w3.org/TR/css-color-3/#svg-color) are supported.
|
||||
| `brightness` | yes | Integer between 0 and 255 for how bright the light should be.
|
||||
| `brightness_pct`| yes | Alternatively, you can specify brightness in percent (a number between 0 and 100).
|
||||
| `brightness` | yes | Integer between 0 and 255 for how bright the light should be, where 0 means the light is off, 1 is the minimum brightness and 255 is the maximum brightness supported by the light.
|
||||
| `brightness_pct`| yes | Alternatively, you can specify brightness in percent (a number between 0 and 100), where 0 means the light is off, 1 is the minimum brightness and 100 is the maximum brightness supported by the light.
|
||||
| `flash` | yes | Tell light to flash, can be either value `short` or `long`.
|
||||
| `effect`| yes | Applies an effect such as `colorloop` or `random`.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ The `plex` platform allows you to connect to a [Plex Media Server](https://plex.
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
The preferred way to setup the Plex platform is by enabling the [discovery component](/components/discovery/) which requires GDM enabled on your Plex server.
|
||||
The preferred way to setup the Plex platform is by enabling the [discovery component](/components/discovery/) which requires GDM enabled on your Plex server. This can be found on your Plex Web App under Settings > (server Name) > settings > Network and choose "Enable local network discovery (GDM)".
|
||||
|
||||
If your Plex server has local authentication enabled or multiple users defined, Home Assistant requires an authentication token to be entered in the frontend. Press "CONFIGURE" to do it.
|
||||
|
||||
@ -43,7 +43,7 @@ media_player:
|
||||
- platform: plex
|
||||
```
|
||||
|
||||
In case [discovery](/components/discovery/) does not work (GDM disabled or non-local Plex server), you can create the `plex.conf` manually and placed it in your [configuration directory ](/docs/configuration/) or `/config/` if you are running Hass.io.
|
||||
In the event that [discovery](/components/discovery/) does not work (GDM disabled or non-local Plex server), you can manually create a `plex.conf` file manually and place it in your [configuration directory ](/docs/configuration/) or `/config/` if you are running Hass.io. The following is an example of `plex.conf`:
|
||||
|
||||
```json
|
||||
{"IP_ADDRESS:PORT": {"token": "TOKEN", "ssl": false, "verify": true}}
|
||||
@ -174,5 +174,5 @@ Plays a song, playlist, TV episode, or video on a connected client.
|
||||
INFO:homeassistant.components.media_player.plex:No server found at: http://192.168.1.10:32400
|
||||
```
|
||||
|
||||
If this occurs, check the setting `Server`>`Network`>`Secure connections` in your Plex Media Server: if it is set to `Preferred` or `Required`, you may need to manually set the `ssl` and `verify` booleans in the `plex.conf` file to, respectively, `true` and `false`. See the **"Setup"** section above for details.
|
||||
If this occurs, check the setting `Server`>`Network`>`Secure connections` on your Plex Media Server: if it is set to `Preferred` or `Required`, you may need to manually set the `ssl` and `verify` booleans in the `plex.conf` file to, respectively, `true` and `false`. See the **"Setup"** section above for details.
|
||||
* Movies must be located under 'Movies' section in the Plex library to properly get 'playing' state.
|
||||
|
||||
@ -1,22 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Danfoss Air Switch"
|
||||
description: "Instructions for how to setup Danfoss Air switches within Home Assistant."
|
||||
date: 2019-02-13 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: danfoss_air.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.89
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
To get your Danfoss Air sensors working with Home Assistant, follow the instructions for the general [Danfoss Air component](/components/danfoss_air/).
|
||||
</p>
|
||||
|
||||
The following switches.
|
||||
|
||||
* **Boost:** Switch to manually activate boost.
|
||||
@ -379,3 +379,13 @@ Software Required:
|
||||
6. Go to \apps\com.xiaomi.smarthome\db
|
||||
7. Open miio2.db with SQLite Browser
|
||||
8. You can find your device tokens in "devicerecord" table
|
||||
|
||||
## {% linkable_title Retrieving the Zone Coordinates %}
|
||||
|
||||
### {% linkable_title Using FloleVac (Android) %}
|
||||
|
||||
1. Download [FloleVac](https://play.google.com/store/apps/details?id=de.flole.xiaomi)
|
||||
2. Login with your Xiaomi credentials
|
||||
3. Open Map (make sure you're on the same network as your vacuum cleaner)
|
||||
4. Select "Zone cleanup" and draw a box around the zone you'd like to clean
|
||||
5. Long press "Cleanup" and the zone coordinates will be copied to your clipboard
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -53,6 +53,8 @@ Looking for [talking points](/help/talking-points/) or [trivia](/help/trivia)?
|
||||
|
||||
Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
|
||||
|
||||
- [Thomas-Krenn-Award 2019 – The winners](https://www.thomas-krenn.com/de/tkmag/tk-insights/thomas-krenn-award-2019-gewinner/) - March 2019
|
||||
- [How to set up and use Home Assistant: For Dummies edition](https://www.the-ambient.com/how-to/set-up-use-home-assistant-644) - October 2018
|
||||
- [DINAcon begeistert 200 Teilnehmende und die Award-Gewinner 2018](https://dinacon.ch/wp-content/uploads/sites/4/2018/10/2018-10-19_DINAcon2018_Medienmitteilung.pdf) - October 2018
|
||||
- [Build a wireless MQTT weather sensor for your Home Assistant](https://www.smartlab.at/build-a-wireless-mqtt-temperature-and-humidity-sensor-for-your-home-assistant/) - October 2018
|
||||
- [Nominations for the DINACon award 2018](https://www.netzwoche.ch/news/2018-09-04/das-sind-die-nominierten-fuer-die-dinacon-awards-2018) - September 2018
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user