mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-24 17:57:14 +00:00
Merge branch 'current' into rc
This commit is contained in:
Paulus Schoutsen
commit
bd9e7179e6
@ -80,7 +80,7 @@ The Unifi controller allows you to create multiple users on it besides the main
|
||||
|
||||
The Unifi controller can either be a dedicated hardware device (Unifi's cloud key), or as software any Linux system. If you run the the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well.
|
||||
|
||||
It is recommended that you run the Unifi controller in a dedicate virtual machine to avoid that situation.
|
||||
It is recommended that you run the Unifi controller in a dedicated virtual machine to avoid that situation.
|
||||
|
||||
### {% linkable_title Troubleshooting and Time Synchronization %}
|
||||
|
||||
|
||||
@ -90,7 +90,7 @@ Please note, that sources from `trusted_networks` won't be banned automatically.
|
||||
|
||||
## {% linkable_title Hosting files %}
|
||||
|
||||
If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config` on Hass.io, `.homeassistant` elswhere). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`.
|
||||
If you want to use Home Assistant to host or serve static files then create a directory called `www` under the configuration path (`/config` on Hass.io, `.homeassistant` elsewhere). The static files in `www/` can be accessed by the following URL `http://your.domain:8123/local/`, for example `audio.mp3` would be accessed as `http://your.domain:8123/local/audio.mp3`.
|
||||
|
||||
<p class='note'>
|
||||
If you've had to create the `www/` folder for the first time, you'll need to restart Home Assistant.
|
||||
|
||||
17
source/_components/ios.markdown
Normal file
17
source/_components/ios.markdown
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
layout: page
|
||||
title: "iOS"
|
||||
description: "Instructions on how to use the iOS companion app with Home Assistant."
|
||||
date: 2018-04-06 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: apple.png
|
||||
ha_category: Hub
|
||||
featured: false
|
||||
ha_release: 0.31
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `ios` component is the Home Assistant part for using the iOS companion app. For further details please check the [iOS section](/docs/ecosystem/ios/) in the documentation for further details.
|
||||
@ -33,6 +33,10 @@ mqtt:
|
||||
broker: IP_ADDRESS_BROKER
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
The minimal setup uses the embedded MQTT broker, however a separate broker is advised for more stability.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Additional features %}
|
||||
|
||||
- [Certificate](/docs/mqtt/certificate/)
|
||||
|
||||
@ -167,7 +167,12 @@ sensor:
|
||||
|
||||
### {% linkable_title Get sensor value from a device with ESPEasy %}
|
||||
|
||||
Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/ESPEasy). Under "Config" set a name ("Unit Name:") for your device (here it's "bathroom"). A "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example the topics are prefixed with "home". Also, add a sensor in the "Devices" tap with the name "analog" and "brightness" as value.
|
||||
Assuming that you have flashed your ESP8266 unit with [ESPEasy](https://github.com/letscontrolit/ESPEasy). Under "Config" set a name ("Unit Name:") for your device (here it's "bathroom"). A "Controller" for MQTT with the protocol "OpenHAB MQTT" is present and the entries ("Controller Subscribe:" and "Controller Publish:") are adjusted to match your needs. In this example the topics are prefixed with "home". Please keep in mind that the ESPEasy default topics start with a `/` and only contain the name when writing your entry for the `configuration.yaml` file.
|
||||
|
||||
- **Controller Subscribe**: `home/%sysname%/#` (instead of `/%sysname%/#`)
|
||||
- **Controller Publish**: `home/%sysname%/%tskname%/%valname%` (instead of `/%sysname%/%tskname%/%valname%`)
|
||||
|
||||
Also, add a sensor in the "Devices" tap with the name "analog" and "brightness" as value.
|
||||
|
||||
As soon as the unit is online, you will get the state of the sensor.
|
||||
|
||||
@ -188,5 +193,3 @@ sensor:
|
||||
name: Brightness
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
|
||||
@ -12,41 +12,42 @@ ha_release: "0.64"
|
||||
ha_category: Hub
|
||||
---
|
||||
|
||||
[Smappee](https://www.smappee.com/) controller for energy monitoring and Comport plug switches.
|
||||
The `smappee` component adds support for the [Smappee](https://www.smappee.com/) controller for energy monitoring and Comport plug switches.
|
||||
|
||||
Switches and Sensors are supported - and will be automatically added when you connect to the Smappee controller.
|
||||
|
||||
The smappee component gets information from [Smappee API](https://smappee.atlassian.net/wiki/display/DEVAPI/API+Methods) using the [smappy](https://github.com/EnergieID/smappy) pypy module
|
||||
The smappee component gets information from [Smappee API](https://smappee.atlassian.net/wiki/display/DEVAPI/API+Methods).
|
||||
|
||||
<p class='note'>
|
||||
Info on how to get api access is described in the [smappy wiki](https://github.com/EnergieID/smappy/wiki)
|
||||
</p>
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
Info on how to get API access is described in the [smappy wiki](https://github.com/EnergieID/smappy/wiki).
|
||||
|
||||
To use the `smappee` component in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
# Configuration
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
smappee:
|
||||
host: 10.0.0.5
|
||||
client_id: YOUR_CLIENT_ID
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
username: YOUR_MYSMAPPEE_USERNAME
|
||||
password: YOUR_MYSMAPPEE_PASSWORD
|
||||
host: 10.0.0.5
|
||||
client_id: YOUR_CLIENT_ID
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
username: YOUR_MYSMAPPEE_USERNAME
|
||||
password: YOUR_MYSMAPPEE_PASSWORD
|
||||
```
|
||||
|
||||
```yaml
|
||||
# Minimal example configuration.yaml entry
|
||||
smappee:
|
||||
host: 10.0.0.5
|
||||
host: 10.0.0.5
|
||||
```
|
||||
|
||||
```yaml
|
||||
# Cloud only example configuration.yaml entry
|
||||
smappee:
|
||||
client_id: YOUR_CLIENT_ID
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
username: YOUR_MYSMAPPEE_USERNAME
|
||||
password: YOUR_MYSMAPPEE_PASSWORD
|
||||
client_id: YOUR_CLIENT_ID
|
||||
client_secret: YOUR_CLIENT_SECRET
|
||||
username: YOUR_MYSMAPPEE_USERNAME
|
||||
password: YOUR_MYSMAPPEE_PASSWORD
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
@ -12,7 +12,9 @@ ha_category: Switch
|
||||
ha_release: 0.66
|
||||
---
|
||||
|
||||
The `vesync` switch platform enabled integration with Etekcity VeSync smart switches.
|
||||
The `vesync` switch platform enables integration with Etekcity VeSync smart switches.
|
||||
|
||||
VeSync switches are low-cost wifi smart plugs that offer energy monitoring and work with popular voice assistants.
|
||||
|
||||
To use your VeSync switches, you must first register your switches with the VeSync app. Once registration is complete you must add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -20,8 +22,8 @@ To use your VeSync switches, you must first register your switches with the VeSy
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: vesync
|
||||
username: username
|
||||
password: password
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -34,3 +36,16 @@ password:
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### {% linkable_title Exposed Attributes %}
|
||||
|
||||
VeSync switches will expose the following details.
|
||||
|
||||
| Attribute | Description | Example |
|
||||
| ------------------- | ------------------------------------------------------------------- | --------------- |
|
||||
| `current_power_w` | The present power consumption of the switch in watts. | 100 |
|
||||
| `today_energy_kwh` | The kilowatt hours used by the switch during the previous 24 hours. | 0.12 |
|
||||
| `connection_status` | The connection status of the switch. | online |
|
||||
| `connection_type` | The connection type of the switch. | wifi |
|
||||
| `device_type` | The device type of the switch. | wifi-switch-1.3 |
|
||||
| `model` | The model of the switch. | wifi-switch |
|
||||
|
||||
@ -27,7 +27,7 @@ Available services: `turn_on`, `turn_off`, `start_pause`, `stop`, `return_to_hom
|
||||
|
||||
Before calling one of these services, make sure your botvac platform supports it.
|
||||
|
||||
#### {% linkable_title Service `vacuum/turn_on` %}
|
||||
#### {% linkable_title Service `vacuum.turn_on` %}
|
||||
|
||||
Start a new cleaning task.
|
||||
|
||||
@ -35,7 +35,7 @@ Start a new cleaning task.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/turn_off` %}
|
||||
#### {% linkable_title Service `vacuum.turn_off` %}
|
||||
|
||||
Stop the current cleaning task and return to the dock.
|
||||
|
||||
@ -43,7 +43,7 @@ Stop the current cleaning task and return to the dock.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/start_pause` %}
|
||||
#### {% linkable_title Service `vacuum.start_pause` %}
|
||||
|
||||
Start, pause or resume a cleaning task.
|
||||
|
||||
@ -51,7 +51,7 @@ Start, pause or resume a cleaning task.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/stop` %}
|
||||
#### {% linkable_title Service `vacuum.stop` %}
|
||||
|
||||
Stop the current activity of the botvac.
|
||||
|
||||
@ -59,7 +59,7 @@ Stop the current activity of the botvac.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/return_to_home` %}
|
||||
#### {% linkable_title Service `vacuum.return_to_home` %}
|
||||
|
||||
Tell the botvac to return home.
|
||||
|
||||
@ -67,7 +67,7 @@ Tell the botvac to return home.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/locate` %}
|
||||
#### {% linkable_title Service `vacuum.locate` %}
|
||||
|
||||
Locate the vacuum cleaner robot.
|
||||
|
||||
@ -75,7 +75,7 @@ Locate the vacuum cleaner robot.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/clean_spot` %}
|
||||
#### {% linkable_title Service `vacuum.clean_spot` %}
|
||||
|
||||
Tell the vacuum cleaner to do a spot clean-up.
|
||||
|
||||
@ -83,7 +83,7 @@ Tell the vacuum cleaner to do a spot clean-up.
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/set_fanspeed` %}
|
||||
#### {% linkable_title Service `vacuum.set_fanspeed` %}
|
||||
|
||||
Set the fan speed of the botvac. The `fanspeed` can be a label, as `balanced` or `turbo`, or be a number; it depends on the `vacuum` platform.
|
||||
|
||||
@ -92,7 +92,7 @@ Set the fan speed of the botvac. The `fanspeed` can be a label, as `balanced` or
|
||||
| `entity_id` | yes | Only act on specific botvac. Else targets all. |
|
||||
| `fanspeed` | no | Platform dependent vacuum cleaner fan speed, with speed steps, like 'medium', or by percentage, between 0 and 100. |
|
||||
|
||||
#### {% linkable_title Service `vacuum/send_command` %}
|
||||
#### {% linkable_title Service `vacuum.send_command` %}
|
||||
|
||||
Send a platform-specific command to the vacuum cleaner.
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@ Remote control the robot. Please ensure you first set it in remote control mode
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
| `velocity` | no | Speed: between -0.29 and 0.29 |
|
||||
| `rotation` | no | Rotation: between -179 degrees and 179 degrees |
|
||||
| `duration` | no | The number of seconds that the robot should move for |
|
||||
| `duration` | no | The number of milliseconds that the robot should move for |
|
||||
|
||||
### {% linkable_title Service `vacuum.xiaomi_remote_control_move_step` %}
|
||||
|
||||
@ -92,7 +92,7 @@ Enter remote control mode, make one move, stop, and exit remote control mode.
|
||||
| `entity_id` | yes | Only act on specific robot; default targets all |
|
||||
| `velocity` | no | Speed: between -0.29 and 0.29. |
|
||||
| `rotation` | no | Rotation: between -179 degrees and 179 degrees. |
|
||||
| `duration` | no | The number of seconds that the robot should move for |
|
||||
| `duration` | no | The number of milliseconds that the robot should move for |
|
||||
|
||||
## {% linkable_title Attributes %}
|
||||
|
||||
|
||||
@ -22,13 +22,12 @@ automation:
|
||||
event: sunset
|
||||
action:
|
||||
service: light.turn_on
|
||||
entity_id:
|
||||
- light.kitchen
|
||||
- light.living_room
|
||||
data:
|
||||
brightness: 150
|
||||
rgb_color: [255, 0, 0]
|
||||
|
||||
entity_id:
|
||||
- light.kitchen
|
||||
- light.living_room
|
||||
automation 2:
|
||||
# Notify me on my mobile phone of an event
|
||||
trigger:
|
||||
|
||||
@ -8,7 +8,6 @@ comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
redirect_from: /ecosystem/ios/
|
||||
redirect_from: /components/ios/
|
||||
---
|
||||
|
||||
The Home Assistant for iOS app offers a companion app for iOS which is deeply integrated into both Home Assistant and iOS. Its basic features include:
|
||||
@ -22,7 +21,7 @@ The app is available on the iOS App Store in every country that Apple supports.
|
||||
|
||||
<p style="text-align: center;"><a target="_blank" href="https://itunes.apple.com/us/app/home-assistant-open-source-home-automation/id1099568401?mt=8" style="display:inline-block;overflow:hidden;background:url(//linkmaker.itunes.apple.com/assets/shared/badges/en-us/appstore-lrg.svg) no-repeat;width:135px;height:40px;background-size:contain;"></a></p>
|
||||
|
||||
## Basic requirements
|
||||
## {% linkable_title Basic requirements %}
|
||||
|
||||
* iOS device running at least iOS 9, but iOS 10 is greatly preferred.
|
||||
* Home Assistant 0.42.4 or higher for push notification support.
|
||||
@ -34,7 +33,7 @@ Loading the `ios` component will also load the [`device_tracker`][device-tracker
|
||||
|
||||
## {% linkable_title Setup %}
|
||||
|
||||
### Automated Setup
|
||||
### {% linkable_title Automated Setup %}
|
||||
|
||||
The `ios` component will automatically be loaded under the following circumstances:
|
||||
|
||||
@ -45,7 +44,7 @@ Automated discovery and component loading only happens at first install of the a
|
||||
|
||||
After the first automated setup you need to add `ios:` to your configuration so that the component loads by default even after restarting Home Assistant.
|
||||
|
||||
### Manual Setup
|
||||
### {% linkable_title Manual Setup %}
|
||||
|
||||
You may also manually load the `ios` component by adding the following to your configuration:
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
redirect_from: /getting-started/installation-docker/
|
||||
---
|
||||
|
||||
Installation with Docker is straightforward. Adjust the following command so that `/path/to/your/config/` points at the folder where you want to store your config and run it:
|
||||
Installation with Docker is straightforward. Adjust the following command so that `/path/to/your/config/` points at the folder where you want to store your configuration and run it:
|
||||
|
||||
### {% linkable_title Linux %}
|
||||
|
||||
@ -20,7 +20,7 @@ $ docker run -d --name="home-assistant" -v /path/to/your/config:/config -v /etc/
|
||||
|
||||
### {% linkable_title macOS %}
|
||||
|
||||
When using `docker-ce` (or `boot2docker`) on macOS, you are unable to map the local timezone to your Docker container ([Docker issue](https://github.com/docker/for-mac/issues/44)). Instead of `-v /etc/localtime:/etc/localtime:ro`, just pass in the timezone environment variable when you launch the container, ex: `-e "TZ=America/Los_Angeles"`. Replace "America/Los_Angeles" with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
|
||||
When using `docker-ce` (or `boot2docker`) on macOS, you are unable to map the local timezone to your Docker container ([Docker issue](https://github.com/docker/for-mac/issues/44)). Instead of `-v /etc/localtime:/etc/localtime:ro`, just pass in the timezone environment variable when you launch the container, e.g, `-e "TZ=America/Los_Angeles"`. Replace "America/Los_Angeles" with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
|
||||
|
||||
If you wish to browse directly to `http://localhost:8123` from your macOS host, meaning forward ports directly to the container, replace the `--net=host` switch with `-p 8123:8123`. More detail can be found in [the docker forums](https://forums.docker.com/t/should-docker-run-net-host-work/14215/10).
|
||||
|
||||
@ -28,7 +28,7 @@ If you wish to browse directly to `http://localhost:8123` from your macOS host,
|
||||
$ docker run -d --name="home-assistant" -v /path/to/your/config:/config -e "TZ=America/Los_Angeles" -p 8123:8123 homeassistant/home-assistant
|
||||
```
|
||||
|
||||
Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking docs] (https://docs.docker.com/engine/userguide/networking/#default-networks). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
|
||||
Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking docs](https://docs.docker.com/engine/userguide/networking/#default-networks). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
|
||||
|
||||
### {% linkable_title Windows %}
|
||||
|
||||
@ -84,31 +84,24 @@ As QNAP within QTS now supports Docker (with a neat UI), you can simply install
|
||||
|
||||
The steps would be:
|
||||
|
||||
- Install “Container Station” package on your Qnap NAS
|
||||
- Launch Container Station and move to “Create Container”-section
|
||||
- Search image “homeassistant/home-assistant” with
|
||||
docker hub and click on “Install”
|
||||
- Install "Container Station" package on your Qnap NAS
|
||||
- Launch Container Station and move to "Create Container"-section
|
||||
- Search image "homeassistant/home-assistant" with Docker hub and click on "Install"
|
||||
- Choose "latest" version and click next
|
||||
- Choose a container-name you want (e.g.
|
||||
“homeassistant”)
|
||||
- Click on “Advanced Settings”
|
||||
- Within “Shared Folders” click on "Volume from host" > "Add" and
|
||||
choose either an existing folder or add a new folder. The “mount
|
||||
point” has to be “/config”, so that Home Assistant will use it for
|
||||
the configs and logs.
|
||||
- Within “Network” and select Network Mode to “Host”
|
||||
- To ensure that Home Assistant displays the correct
|
||||
timezone go to the “Environment” tab and click the plus sign then add
|
||||
`variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
|
||||
- Click on “Create”
|
||||
- Choose a container-name you want (e.g., "homeassistant")
|
||||
- Click on "Advanced Settings"
|
||||
- Within "Shared Folders" click on "Volume from host" > "Add" and choose either an existing folder or add a new folder. The "mount point has to be `/config`, so that Home Assistant will use it for the configuration and logs.
|
||||
- Within "Network" and select Network Mode to "Host"
|
||||
- To ensure that Home Assistant displays the correct timezone go to the "Environment" tab and click the plus sign then add `variable` = `TZ` & `value` = `Europe/London` choosing [your correct timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
|
||||
- Click on "Create"
|
||||
- Wait for some time until your NAS has created the container
|
||||
- Your Home Assistant within Docker should now run and will serve the web interface from port 8123 on your Docker host (this will be your Qnap NAS IP address - for example `http://192.xxx.xxx.xxx:8123`)
|
||||
|
||||
Remark: to update your Home Assistant on your Docker within Qnap NAS, you just remove container and image and do steps again (Don't remove "config" folder)
|
||||
Remark: To update your Home Assistant on your Docker within Qnap NAS, you just remove container and image and do steps again (Don't remove "config" folder).
|
||||
|
||||
If you want to use a USB Bluetooth adapter or Z-Wave USB Stick with Home Assistant on Qnap Docker, Fallow this step:
|
||||
If you want to use a USB Bluetooth adapter or Z-Wave USB stick with Home Assistant on Qnap Docker, follow those steps:
|
||||
|
||||
**Z-wave:**
|
||||
#### {% linkable_title Z-Wave %}
|
||||
|
||||
- Connect to your NAS over SSH
|
||||
- Load cdc-acm kernel module(when nas restart need to run this command)
|
||||
@ -123,16 +116,16 @@ If you want to use a USB Bluetooth adapter or Z-Wave USB Stick with Home Assista
|
||||
`-v` is your config path
|
||||
`-e` is set timezone
|
||||
|
||||
- Edit configuration.yaml
|
||||
- Edit `configuration.yaml`
|
||||
|
||||
```
|
||||
```yaml
|
||||
zwave:
|
||||
usb_path: /dev/ttyACM0
|
||||
```
|
||||
|
||||
That will tell Home Assistant where to look for our Z-wave radio.
|
||||
|
||||
**Bluetooth:**
|
||||
#### {% linkable_title Bluetooth %}
|
||||
|
||||
- Connect to your NAS over SSH
|
||||
- Run Docker command:
|
||||
@ -141,9 +134,9 @@ That will tell Home Assistant where to look for our Z-wave radio.
|
||||
First `-v` is your config path
|
||||
`-e` is set timezone
|
||||
|
||||
- Edit configuration.yaml
|
||||
- Edit the `configuration.yaml` file
|
||||
|
||||
```
|
||||
```yaml
|
||||
device_tracker:
|
||||
- platform: bluetooth_tracker
|
||||
```
|
||||
@ -180,10 +173,12 @@ $ docker-compose up -d
|
||||
|
||||
### {% linkable_title Exposing Devices %}
|
||||
|
||||
In order to use z-wave, zigbee or other components that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your docker command:
|
||||
In order to use Z-Wave, ZigBbee or other components that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your docker command:
|
||||
|
||||
```bash
|
||||
$ docker run -d --name="home-assistant" -v /path/to/your/config:/config -v /etc/localtime:/etc/localtime:ro --device /dev/ttyUSB0:/dev/ttyUSB0 --net=host homeassistant/home-assistant
|
||||
$ docker run -d --name="home-assistant" -v /path/to/your/config:/config \
|
||||
-v /etc/localtime:/etc/localtime:ro --device /dev/ttyUSB0:/dev/ttyUSB0 \
|
||||
--net=host homeassistant/home-assistant
|
||||
```
|
||||
|
||||
or in a `docker-compose.yml` file:
|
||||
|
||||
@ -26,11 +26,11 @@ For more details about the GPIO layout, visit the [documentation](https://www.ra
|
||||
Permission have been given to the `homeassistant` user to use the GPIO pins and all of the following components should require no underlying changes to work.
|
||||
Just follow the component pages for each on how to add them to your Home Assistant installation.
|
||||
|
||||
- [DHT Sensor](/components/sensor.dht/).
|
||||
- [Raspberry Pi Cover](/components/cover.rpi_gpio/).
|
||||
- [Raspberry Pi GPIO Binary Sensor](/components/binary_sensor.rpi_gpio/).
|
||||
- [Raspberry Pi GPIO Switch](/components/switch.rpi_gpio/).
|
||||
- [Raspberry Pi RF Switch](/components/switch.rpi_rf/).
|
||||
- [DHT Sensor](/components/sensor.dht/)
|
||||
- [Raspberry Pi Cover](/components/cover.rpi_gpio/)
|
||||
- [Raspberry Pi GPIO Binary Sensor](/components/binary_sensor.rpi_gpio/)
|
||||
- [Raspberry Pi GPIO Switch](/components/switch.rpi_gpio/)
|
||||
- [Raspberry Pi RF Switch](/components/switch.rpi_rf/)
|
||||
|
||||
### {% linkable_title Raspberry Pi Camera %}
|
||||
|
||||
|
||||
@ -10,6 +10,10 @@ footer: true
|
||||
redirect_from: /getting-started/installation-synology/
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
Synology only provide Python 3.5.1, which is not compatible with Home Assistant 0.65.0 or later. Until Synology offer an updated version of Python, Home Assistant 0.64 is the most recent version that will be able to be installed. You can manually specify the version of Home Assistant to install, for example to install version 0.64.3 you would do `./python3 -m pip install homeassistant==0.64.3`
|
||||
</p>
|
||||
|
||||
There are 2 alternatives, when using Home Assistant on Synology NAS:
|
||||
1. using Docker
|
||||
2. directly running on DSM
|
||||
@ -26,7 +30,7 @@ Running these commands will:
|
||||
|
||||
Using the Synology webadmin:
|
||||
|
||||
- Install python3 using the Synology Package Center (be aware, this provides 3.5.1, which is not compatible with Home Assistant 0.65.0 or later)
|
||||
- Install python3 using the Synology Package Center
|
||||
- Create homeassistant user and add to the "users" group
|
||||
|
||||
SSH onto your synology & login as admin or root
|
||||
@ -51,16 +55,12 @@ Install PIP (Python's package management system)
|
||||
# ./python3 -m ensurepip
|
||||
```
|
||||
|
||||
Use PIP to install Homeassistant package
|
||||
Use PIP to install Homeassistant package 0.64.3
|
||||
|
||||
```bash
|
||||
# ./python3 -m pip install homeassistant
|
||||
# ./python3 -m pip install homeassistant==0.64.3
|
||||
```
|
||||
|
||||
<p class='note'>
|
||||
Until Synology offer an updated version of Python, Home Assistant 0.64 is the most recent version that will be able to be installed. You can manually specify the version of Home Assistant to install, for example to install version 0.64.3 you would do `./python3 -m pip install homeassistant==0.64.3`
|
||||
</p>
|
||||
|
||||
Create homeassistant config directory & switch to it
|
||||
|
||||
```bash
|
||||
|
||||
@ -14,7 +14,7 @@ redirect_from: /getting-started/updating/
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [Hassbian](/docs/installation/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
</p>
|
||||
|
||||
Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check `<config-dir>/home-assistant.log` for details about broken components.
|
||||
Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
|
||||
|
||||
The default way to update Home Assistant to the latest release, when available, is:
|
||||
|
||||
@ -22,7 +22,13 @@ The default way to update Home Assistant to the latest release, when available,
|
||||
$ pip3 install --upgrade homeassistant
|
||||
```
|
||||
|
||||
After updating, you must restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.
|
||||
For a Docker container, simply pull the latest one:
|
||||
|
||||
```bash
|
||||
$ sudo docker pull homeassistant/home-assistant:latest
|
||||
```
|
||||
|
||||
After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.
|
||||
|
||||
<p class='note'>
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Hass.io](/hassio/), [Hassbian](/docs/hassbian/installation/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
|
||||
|
||||
@ -43,8 +43,8 @@ The discovery topic need to follow a specific format:
|
||||
```
|
||||
|
||||
- `<component>`: One of the supported components, eg. `binary_sensor`.
|
||||
- `<node_id>`: (*Optional*) id of the node providing the topic.
|
||||
- `<object_id>`: "The ID of the device. This is only to allow for separate topics for each device and is not used for the `entity_id`."
|
||||
- `<node_id>` (*Optional*): ID of the node providing the topic.
|
||||
- `<object_id>`: The ID of the device. This is only to allow for separate topics for each device and is not used for the `entity_id`.
|
||||
- `<>`: The topic `config` or `state` which defines the current action.
|
||||
|
||||
The payload will be checked like an entry in your `configuration.yaml` file if a new device is added. This means that missing variables will be filled with the platform's default values. All configuration variables which are *required* must be present in the initial payload send to `/config`.
|
||||
|
||||
@ -205,7 +205,7 @@ The first run after adding a device is when the `zwave` component will take time
|
||||
|
||||
### {% linkable_title Component could not be set up %}
|
||||
|
||||
Sometimes the device may not be accessible and you'll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path:
|
||||
Sometimes the device may not be accessible and you'll get an error message upon startup about not being able to set up Z-Wave. Run the following command for your device path (here we're using `/dev/ttyAMA0` for our Razberry board):
|
||||
|
||||
```bash
|
||||
$ ls -l /dev/ttyAMA0
|
||||
@ -224,6 +224,18 @@ $ sudo chgrp dialout /dev/ttyAMA0
|
||||
$ sudo chmod g+rw /dev/ttyAMA0
|
||||
```
|
||||
|
||||
Check too that the account you're running Home Assistant as is in the `dialout` group. For instance, if you're using `homeassistant`:
|
||||
|
||||
```bash
|
||||
$ groups homeassistant
|
||||
```
|
||||
|
||||
That should include `dialout`, if it doesn't then:
|
||||
|
||||
```bash
|
||||
$ sudo usermod -G dialout homeassistant
|
||||
```
|
||||
|
||||
### {% linkable_title Device path changes %}
|
||||
|
||||
If your device path changes when you restart, see [this guide](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/) on fixing it.
|
||||
|
||||
@ -566,6 +566,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@armills]: https://github.com/armills
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[homekit docs]: https://www.home-assistant.io/components/homekit/
|
||||
[light.mqtt_json docs]: https://www.home-assistant.io/components/light.mqtt_json/
|
||||
[sensor.mysensors docs]: https://www.home-assistant.io/components/sensor.mysensors/
|
||||
[homekit docs]: /components/homekit/
|
||||
[light.mqtt_json docs]: /components/light.mqtt_json/
|
||||
[sensor.mysensors docs]: /components/sensor.mysensors/
|
||||
|
||||
@ -0,0 +1,37 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant 🤝 Ubiquiti Networks"
|
||||
description: "Ubiquiti Networks has hired Paulus Schoutsen, the founder of Home Assistant, to support Home Assistant’s goals of making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations."
|
||||
date: 2018-04-12 00:01:00
|
||||
date_formatted: "April 12, 2018"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Announcements
|
||||
og_image: /images/blog/2018-04-ubiquiti-and-home-assistant/paulus.jpg
|
||||
---
|
||||
|
||||
TL;DR: Ubiquiti Networks has hired Paulus Schoutsen, the founder of Home Assistant, to support Home Assistant’s goals of making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations.
|
||||
|
||||
Home Assistant is an open source project that thus far has been run by people in their spare time. In the last four and a half years it has grown from just me building a tiny framework with a handful of integrations to having our own operating system, over a 1000 integrations, superb performance, contributions by over 900 people, and our main Docker image has been pulled over 10 million times!
|
||||
|
||||
Observing this growth and passionate community, Ubiquiti Networks approached us.
|
||||
|
||||
Ubiquiti Networks currently focuses on 3 main technologies: high-capacity distributed Internet access, unified information technology, and next-gen consumer electronics for home and personal use. Their enterprise quality combined with their affordability has made them very popular among our users. They also share another passion of ours: trying to avoid clouds. Take for example their [UniFi Video] IP surveillance solution: it is a completely local hosted solution.
|
||||
|
||||
They recognize great potential in Home Assistant becoming the defacto platform for the home: fast, open source and local. They also want to deepen the integration of Ubiquiti Networks products in Home Assistant and may even support hosting Home Assistant instances on their hardware.
|
||||
|
||||
And so we have agreed that I (Paulus, founder Home Assistant) will join Ubiquiti Networks as a full time employee to focus on growing Home Assistant. I’ll now be able to devote my full energy to making Home Assistant easier to configure for users, improving the integration with device makers and making it easier to create, maintain and evolve integrations.
|
||||
|
||||
Ubiquiti Networks will not acquire any ownership of Home Assistant. We will remain an independent and open source project, just improving faster than ever with the support of Ubiquiti Networks.
|
||||
|
||||
I’m very excited about this opportunity and 2018 will be a really really great year for Home Assistant!
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
src='/images/blog/2018-04-ubiquiti-and-home-assistant/paulus.jpg'
|
||||
alt='Photo of Paulus, the founder of Home Assistant, standing in front of a Ubiquiti Networks logo wearing a Home Assistant t-shirt.' />
|
||||
Paulus Schoutsen, founder of Home Assistant, at the NYC Ubiquiti office.
|
||||
</p>
|
||||
|
||||
[UniFi Video]: https://www.ubnt.com/unifi-video/unifi-video-camera-g3/#unifi-video-camera-hybrid-technology
|
||||
@ -11,7 +11,7 @@ footer: true
|
||||
|
||||
Home Assistant is built from the ground up to be easily extensible using components. Home Assistant uses [Python 3](https://www.python.org/) for the backend and [Polymer (Web components)](https://www.polymer-project.org/) for the frontend.
|
||||
|
||||
Home Assistant is open-source and MIT-licensed. Here are links to the source:
|
||||
Home Assistant is open-source and licensed under [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0). Here are links to the source:
|
||||
|
||||
- [home-assistant](https://github.com/home-assistant/home-assistant): Python server backend.
|
||||
- [home-assistant-polymer](https://github.com/home-assistant/home-assistant-polymer): Polymer UI.
|
||||
|
||||
@ -28,6 +28,7 @@ Some things to keep in mind:
|
||||
- Use the constants defined in `const.py`
|
||||
- Import `PLATFORM_SCHEMA` from the parent component and extend it
|
||||
- Preferred order is `required` first and `optional` second
|
||||
- Starting with Home Assistant 0.64 `voluptuous` requires default values for optional configuration keys to be valid values. Don't use a default which is `None` like `vol.Optional(CONF_SOMETHING, default=None): cv.string`, set the default to `default=""` if required.
|
||||
|
||||
### {% linkable_title Snippets %}
|
||||
|
||||
|
||||
@ -106,37 +106,39 @@ The config for an add-on is stored in `config.json`.
|
||||
}
|
||||
```
|
||||
|
||||
| Key | Required | Description |
|
||||
| --- | -------- | ----------- |
|
||||
| name | yes | Name of the add-on
|
||||
| version | yes | Version of the add-on
|
||||
| slug | yes | Slug of the add-on
|
||||
| description | yes | Description of the add-on
|
||||
| arch | no | List of supported arch: `armhf`, `aarch64`, `amd64`, `i386`. Default all.
|
||||
| url | no | Homepage of the addon. Here you can explain the add-ons and options.
|
||||
| startup | yes | `initialize` will start addon on setup of Hass.io. `system` is for things like databases and not dependent on other things. `services` will start before Home Assistant, while `application` is started afterwards. Finally `once` is for applications that don't run as a daemon.
|
||||
| webui | no | A URL for web interface of this add-on. Like `http://[HOST]:[PORT:2839]/dashboard`, the port needs the internal port, which will be replaced with the effective port. It is also possible to bind the proto part to a config options with: `[PROTO:option_name]://[HOST]:[PORT:2839]/dashboard` and he lookup if they is True and going to `https`.
|
||||
| boot | yes | `auto` by system and manual or only `manual`
|
||||
| ports | no | Network ports to expose from the container. Format is `"container-port/type": host-port`.
|
||||
| host_network | no | If that is True, the add-on run on host network.
|
||||
| host_ipc | no | Default False. Allow to share the IPC namespace with others.
|
||||
| host_dbus | no | Default False. Map Host dbus service into add-on.
|
||||
| devices | no | Device list to map into the add-on. Format is: `<path_on_host>:<path_in_container>:<cgroup_permissions>`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm`
|
||||
| auto_uart | no | Default False. Auto mapping all UART/Serial device from host into add-on.
|
||||
| hassio_api | no | This add-on can access to Hass.io REST API. It set the host alias `hassio`.
|
||||
| homeassistant_api | no | This add-on can access to Hass.io Home-Assistant REST API proxy. Use `http://hassio/homeassistant/api`.
|
||||
| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN`, `SYS_RAWIO`, `SYS_TIME`, `SYS_NICE`
|
||||
| map | no | List of maps for additional Hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Defaults to `ro`, which you can change by adding `:rw` to the end of the name.
|
||||
| environment | no | A dict of environment variable to run add-on.
|
||||
| audio | no | Boolean. Mark this add-on to use internal an audio system. The available environment variables are `ALSA_INPUT` and `ALSA_OUTPUT` which provide internal information to access alsa.
|
||||
| gpio | no | Boolean. If this is set to True, `/sys/class/gpio` will map into add-on for access to GPIO interface from kernel. Some library need also `/dev/mem` and `SYS_RAWIO` for read/write access to this device.
|
||||
| stdin | no | Boolean. If that is enable, you can use the STDIN with Hass.io API.
|
||||
| legacy | no | Boolean. If the docker image have no hass.io labels, you can enable the legacy mode to use the config data.
|
||||
| options | yes | Default options value of the add-on
|
||||
| schema | yes | Schema for options value of the add-on. It can be `False` to disable schema validation and use custom options.
|
||||
| image | no | For use with Docker Hub.
|
||||
| timeout | no | Default 10 (second). The timeout to wait until the docker is done or will be killed.
|
||||
| tmpfs | no | Mount a tmpfs file system in `/tmpfs`. Valide format for this option is : `size=XXXu,uid=N,rw`. Size is mandatory, valid units (`u`) are `k`, `m` and `g` and `XXX` has to be replaced by a number. `uid=N` (with `N` the uid number) and `rw` are optional.
|
||||
| Key | Type | Required | Description |
|
||||
| --- | ---- | -------- | ----------- |
|
||||
| name | string | yes | Name of the add-on
|
||||
| version | string | yes | Version of the add-on
|
||||
| slug | string | yes | Slug of the add-on
|
||||
| description | string | yes | Description of the add-on
|
||||
| arch | list | no | List of supported arch: `armhf`, `aarch64`, `amd64`, `i386`. Default all.
|
||||
| url | url | no | Homepage of the addon. Here you can explain the add-ons and options.
|
||||
| startup | bool | yes | `initialize` will start addon on setup of Hass.io. `system` is for things like databases and not dependent on other things. `services` will start before Home Assistant, while `application` is started afterwards. Finally `once` is for applications that don't run as a daemon.
|
||||
| webui | string | no | A URL for web interface of this add-on. Like `http://[HOST]:[PORT:2839]/dashboard`, the port needs the internal port, which will be replaced with the effective port. It is also possible to bind the proto part to a config options with: `[PROTO:option_name]://[HOST]:[PORT:2839]/dashboard` and he lookup if they is True and going to `https`.
|
||||
| boot | string | yes | `auto` by system and manual or only `manual`
|
||||
| ports | dict | no | Network ports to expose from the container. Format is `"container-port/type": host-port`.
|
||||
| host_network | bool | no | If that is True, the add-on run on host network.
|
||||
| host_ipc | bool | no | Default False. Allow to share the IPC namespace with others.
|
||||
| host_dbus | bool | no | Default False. Map Host dbus service into add-on.
|
||||
| devices | list | no | Device list to map into the add-on. Format is: `<path_on_host>:<path_in_container>:<cgroup_permissions>`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm`
|
||||
| auto_uart | bool | no | Default False. Auto mapping all UART/Serial device from host into add-on.
|
||||
| hassio_api | bool | no | This add-on can access to Hass.io REST API. It set the host alias `hassio`.
|
||||
| homeassistant_api | bool | no | This add-on can access to Hass.io Home-Assistant REST API proxy. Use `http://hassio/homeassistant/api`.
|
||||
| privileged | list | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN`, `SYS_RAWIO`, `SYS_TIME`, `SYS_NICE`
|
||||
| apparmor | bool | no | Enable or disable AppArmor support. If it is enable, you can also use custom profiles.
|
||||
| seccomp | bool | no | Enable or disable Seccomp support. If it is enable, you can also use custom profiles.
|
||||
| map | list | no | List of maps for additional Hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Defaults to `ro`, which you can change by adding `:rw` to the end of the name.
|
||||
| environment | dict | no | A dict of environment variable to run add-on.
|
||||
| audio | bool | no | Boolean. Mark this add-on to use internal an audio system. The ALSA configuration for this add-on will be mount automatic.
|
||||
| gpio | bool | no | Boolean. If this is set to True, `/sys/class/gpio` will map into add-on for access to GPIO interface from kernel. Some library need also `/dev/mem` and `SYS_RAWIO` for read/write access to this device.
|
||||
| stdin | bool | no | Boolean. If that is enable, you can use the STDIN with Hass.io API.
|
||||
| legacy | bool | no | Boolean. If the docker image have no hass.io labels, you can enable the legacy mode to use the config data.
|
||||
| options | dict | yes | Default options value of the add-on
|
||||
| schema | dict | yes | Schema for options value of the add-on. It can be `False` to disable schema validation and use custom options.
|
||||
| image | string | no | For use with Docker Hub.
|
||||
| timeout | integer | no | Default 10 (second). The timeout to wait until the docker is done or will be killed.
|
||||
| tmpfs | string | no | Mount a tmpfs file system in `/tmpfs`. Valide format for this option is : `size=XXXu,uid=N,rw`. Size is mandatory, valid units (`u`) are `k`, `m` and `g` and `XXX` has to be replaced by a number. `uid=N` (with `N` the uid number) and `rw` are optional.
|
||||
|
||||
### {% linkable_title Options / Schema %}
|
||||
|
||||
|
||||
@ -47,3 +47,7 @@ A changelog is a file which contains a curated, chronologically ordered list of
|
||||
If you are in need of a guide on keeping a changelog, we would recommend checking the [keep a changelog](http://keepachangelog.com) website. They have developed a standard that is used by many opensource projects around the world.
|
||||
|
||||
In future versions of Hass.io, the `CHANGELOG.md` file will be displayed in the Home Assistant frontend.
|
||||
|
||||
## {% linkable_title Extended Security %}
|
||||
|
||||
You can use own security profile for you Add-on with Seccomp or AppArmor. Default it is enabled and use the docker default profile. Put `apparmor` or `seccomp.json` file into your Add-on folder and it will load this file as primary profile.
|
||||
|
||||
@ -11,7 +11,7 @@ footer: true
|
||||
|
||||
If you have an installation, a setup or a configuration issue please use our [Forum](https://community.home-assistant.io/) to get help. We have a big community which will help you if they can.
|
||||
|
||||
If you found a bug then please report it in one of our [trackers](help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markddown](https://guides.github.com/features/mastering-markdown/).
|
||||
If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markddown](https://guides.github.com/features/mastering-markdown/).
|
||||
|
||||
Use the command below to get the Home Assistant release you are running from a command-line.
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
Loading…
x
Reference in New Issue
Block a user