From 4e7bbfad66816f348348a4ca47946cb23bd1a47d Mon Sep 17 00:00:00 2001 From: rpitera Date: Mon, 15 May 2017 03:47:40 -0400 Subject: [PATCH 01/33] Add icon template instructions (#2629) Propose adding icon template instructions to this and the template switch docs. --- source/_components/binary_sensor.template.markdown | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/source/_components/binary_sensor.template.markdown b/source/_components/binary_sensor.template.markdown index 15129c4ae28..39ea85e7d22 100644 --- a/source/_components/binary_sensor.template.markdown +++ b/source/_components/binary_sensor.template.markdown @@ -92,3 +92,17 @@ binary_sensor: - sensor.kitchen_co_status - sensor.wardrobe_co_status ``` +### {% linkable_title Change the icon %} + +This example shows how to change the icon based on the day/night cycle. + +```yaml +sensor: + - platform: template + sensors: + day_night: + friendly_name: 'Day/Night' + value_template: {% raw %}'{% if is_state("sun.sun", "above_horizon") %}Day{% else %}Night{% endif %}'{% endraw %} + icon_template: {% raw %}'{% if is_state("sun.sun", "above_horizon") %}mdi:weather-sunny{% else %}mdi:weather-night{% endif %}'{% endraw %} + +``` From b9fdb713b84eea5bd5def14ef311c5cf5edc4743 Mon Sep 17 00:00:00 2001 From: deisi Date: Mon, 15 May 2017 09:53:23 +0200 Subject: [PATCH 02/33] Update osramlightify description (#2633) Says a word about #7376 --- source/_components/light.osramlightify.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/light.osramlightify.markdown b/source/_components/light.osramlightify.markdown index 75dc48fd55e..86fa342c9b3 100644 --- a/source/_components/light.osramlightify.markdown +++ b/source/_components/light.osramlightify.markdown @@ -23,4 +23,5 @@ light: Configuration variables: - **host** (*Required*): IP address of the Osram Lightify bridge, eg. `192.168.1.50`. +- **allow_lightify_groups** (*Optional*): (true/false) Edit this to stop homeassistant from importing the lightify groups. From 84158a848e7d031abcb330af39584ed9b3d261a3 Mon Sep 17 00:00:00 2001 From: Johan Bloemberg Date: Mon, 15 May 2017 13:23:58 +0200 Subject: [PATCH 03/33] Update docs with sensor_type values. (#2634) --- source/_components/sensor.rflink.markdown | 38 ++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/source/_components/sensor.rflink.markdown b/source/_components/sensor.rflink.markdown index ab94b7c92b2..04207698f3b 100644 --- a/source/_components/sensor.rflink.markdown +++ b/source/_components/sensor.rflink.markdown @@ -42,10 +42,46 @@ Configuration variables: Device configuration variables: - **name** (*Optional*): Name for the device, defaults to RFLink ID. -- **sensor_type** (*Required*): Override automatically detected type of sensor. +- **sensor_type** (*Required*): Override automatically detected type of sensor. For list of values see below. - **unit_of_measurement** (*Optional*): Override automatically detected unit of sensor. - **aliasses** (*Optional*): Alternative RFLink ID's this device is known by. +Sensor type values: + +- average_windspeed +- barometric_pressure +- battery +- weather_forecast +- doorbell_melody +- command +- co2_air_quality +- current_phase_1 +- current_phase_2 +- current_phase_3 +- distance +- firmware +- humidity_status +- humidity +- hardware +- kilowatt +- light_intensity +- meter_value +- total_rain +- rain_rate +- total_rain +- revision +- noise_level +- temperature +- uv_intensity +- version +- voltage +- watt +- windchill +- winddirection +- windgusts +- windspeed +- windtemp + ### {% linkable_title Hiding/ignoring sensors %} Sensors are added automatically when the RFLink gateway intercepts a wireless command in the ether. To prevent cluttering the frontend use any of these methods: From 025d184d61d598a8673a0d993fd13e393f253192 Mon Sep 17 00:00:00 2001 From: jhemzal Date: Mon, 15 May 2017 13:58:54 +0200 Subject: [PATCH 04/33] Update sensor.snmp.markdown (#2621) --- source/_components/sensor.snmp.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/sensor.snmp.markdown b/source/_components/sensor.snmp.markdown index d73d049fdb9..3252dedb66c 100644 --- a/source/_components/sensor.snmp.markdown +++ b/source/_components/sensor.snmp.markdown @@ -34,6 +34,7 @@ Configuration variables: - **community** (*Optional*): The SNMP community which is set for the device. Most devices have a default community set to to `public` with read-only permission (which is sufficient). - **baseoid** (*Required*): The OID where the information is located. It's advised to use the numerical notation. - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any. +- **version** (*Optional*) version of SNMP protocol, `1` or `2c` defaults to `1`. Version `2c` is needed to read data from 64-bit counters. The OIDs may vary on different system because they are vendor-specific. Beside the device's manual is the [OID Repository](http://www.oid-info.com/) a good place to start if you are looking for OIDs. The following OIDs are for the load of a Linux systems. From 94592924eeab4ce013d300c1b7a8299bad4361ce Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 14 May 2017 12:12:53 +0200 Subject: [PATCH 05/33] Fix typo --- source/_components/binary_sensor.ffmpeg_motion.markdown | 2 +- source/_components/binary_sensor.ffmpeg_noise.markdown | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/binary_sensor.ffmpeg_motion.markdown b/source/_components/binary_sensor.ffmpeg_motion.markdown index 07b9fa548e0..92cdaa2304a 100644 --- a/source/_components/binary_sensor.ffmpeg_motion.markdown +++ b/source/_components/binary_sensor.ffmpeg_motion.markdown @@ -17,7 +17,7 @@ redirect_from: /components/binary_sensor.ffmpeg/ The `ffmpeg` platform allows you to use any video feed with [FFmpeg](http://www.ffmpeg.org/) for motion sensors in Home Assistant.

-If the `ffmpeg` process is broken, the sensor will be unavailable. To controll the ffmpeg process of sensor, use the service *ffmpeg.start*, *ffmpeg.stop*, *ffmpeg.restart*. +If the `ffmpeg` process is broken, the sensor will be unavailable. To control the ffmpeg process of sensor, use the service *ffmpeg.start*, *ffmpeg.stop*, *ffmpeg.restart*.

### {% linkable_title Motion %} diff --git a/source/_components/binary_sensor.ffmpeg_noise.markdown b/source/_components/binary_sensor.ffmpeg_noise.markdown index c1f0c2eab2e..16b18761430 100644 --- a/source/_components/binary_sensor.ffmpeg_noise.markdown +++ b/source/_components/binary_sensor.ffmpeg_noise.markdown @@ -16,7 +16,7 @@ ha_release: 0.27 The `ffmpeg` platform allows you to use any video or audio feed with [FFmpeg](http://www.ffmpeg.org/) for various sensors in Home Assistant.

-If the `ffmpeg` process is broken, the sensor will be unavailable. To controll the ffmpeg process of sensor, use the service *ffmpeg.start*, *ffmpeg.stop*, *ffmpeg.restart*. +If the `ffmpeg` process is broken, the sensor will be unavailable. To control the ffmpeg process of sensor, use the service *ffmpeg.start*, *ffmpeg.stop*, *ffmpeg.restart*.

### {% linkable_title Noise %} From aaf54d2850456d44b6091ea3f7ad36b52968e500 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 14 May 2017 13:10:54 +0200 Subject: [PATCH 06/33] Small changes --- source/_posts/2017-02-04-babyphone.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_posts/2017-02-04-babyphone.markdown b/source/_posts/2017-02-04-babyphone.markdown index 9d58c64c263..057e80b968a 100644 --- a/source/_posts/2017-02-04-babyphone.markdown +++ b/source/_posts/2017-02-04-babyphone.markdown @@ -10,7 +10,7 @@ categories: How-To og_image: /images/blog/2017-02-babyphone/social.png --- -One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed. +One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed. Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house. @@ -18,9 +18,9 @@ Obviously, you can use the setup as a general purpose surveillance system to mon ### {% linkable_title Setup %} -We need an IP camera that can capture sound in the baby's room. It is also possible to use a Raspberry Pi with a microphone and send the audio to Home Assistant with `ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000` over multicast. We can set the `input` option on the Home Assistant side to `rtp://236.0.0.1:2000` in same network. +We need an IP camera that can capture sound in the baby's room. It is also possible to use a Raspberry Pi with a microphone and send the audio to Home Assistant with `ffmpeg -f alsa -i hw:1,0 -vn -f rtp rtp://236.0.0.1:2000` over multicast. We can set the `input` option on the Home Assistant side to `rtp://236.0.0.1:2000` in the same network. -Next, we attach a FFmpeg noise binary sensor to our IP camera. The sensor has an output `option` that allows us to send the output to an [icecast2](http://icecast.org/) server for playing over speakers integrated with Home Assistant (eg. Sonos). We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don't want to play the audio after the noise sensor trigger. +Next, we attach a `ffmpeg_noise` binary sensor to our IP camera. The sensor has an output `option` that allows us to send the output to an [icecast2](http://icecast.org/) server for playing over speakers integrated with Home Assistant. We can use the binary sensor in our automation. You can ignore the icecast2 setup if you don't want to play the audio after the noise sensor trigger.

We change the platform name for binary sensor in 0.38 from `ffmpeg` to `ffmpeg_noise`. Also all service going to component and was rename from `binary_sensor.ffmpeg_xy` to `ffmpeg.xy`. @@ -47,7 +47,7 @@ We setup a icecast mount point for our babyphone and update `/etc/icecast2/iceca ``` -Now we can add the noise sensor to Home Assistant. We can lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the `duration` option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm. +Now we can add the noise sensor to Home Assistant. We lower the sensitivity of the sensor (so that you are not inundated with notifications for every cough of the baby) to 2 seconds using the `duration` option. The sensor should wait 60 seconds before restoring and it prevent us that a wine break will triggering a new alarm. We can optimize the audio stream for human voice by using a highpass filter with 300 Hz and a lowpass filter with 2500 Hz. This filters out all non-human sounds such as background noise. We can even add a volume amplifier if the microphone volume is too low (you can remove it from `extra_arguments`). For icecast2 we convert the audio stream to mp3 with samplerate of 16000 (which is the minimum for Sonos speakers). We use `peak` to set the threshold for noise detection, where 0 dB is very loud and -100 dB is low. From 3899670cfd819d945f966ded9f8be08fa3493563 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 14 May 2017 14:20:41 +0200 Subject: [PATCH 07/33] Add details about USB cameras --- source/_components/ffmpeg.markdown | 43 ++++++++++++++++++++++++++++-- 1 file changed, 41 insertions(+), 2 deletions(-) diff --git a/source/_components/ffmpeg.markdown b/source/_components/ffmpeg.markdown index eb48e451421..caa322b587b 100644 --- a/source/_components/ffmpeg.markdown +++ b/source/_components/ffmpeg.markdown @@ -25,7 +25,7 @@ ffmpeg: Configuration variables: -- **ffmpeg_bin** (*Optional*): Default 'ffmpeg'. The name or path to the `ffmpeg` binary. +- **ffmpeg_bin** (*Optional*): Default `ffmpeg`. The name or path to the `ffmpeg` binary. - **run_test** (*Optional*): Default True. Check if `input` is usable by ffmpeg. ### {% linkable_title Raspbian Debian Jessie Lite Installations %} @@ -36,7 +36,9 @@ $ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt $ sudo apt-get update $ sudo apt-get -t jessie-backports install ffmpeg ``` + We can use now following in the configuration: + ``` ffmpeg: ffmpeg_bin: /usr/bin/ffmpeg @@ -52,7 +54,44 @@ First check that your stream is playable by `ffmpeg` outside of Home Assistant w $ ffmpeg -i INPUT -an -f null - ``` -Now you should be able to see what is going wrong. The following list contains some common problems and solutions: +Now you should be able to see what is going wrong. The following list contains some common problems and solutions: - `[rtsp @ ...] UDP timeout, retrying with TCP`: You need to set an RTSP transport in the configuration with: `input: -rtsp_transport tcp -i INPUT` - `[rtsp @ ...] Could not find codec parameters for stream 0 (Video: ..., none): unspecified size`: FFmpeg needs more data or time for autodetection (the default is 5 seconds). You can set the `analyzeduration` and/or `probesize` options to experiment with giving FFmpeg more leeway. If you find the needed value, you can set it with: `input: -analyzeduration xy -probesize xy -i INPUT`. More information about this can be found [here](https://www.ffmpeg.org/ffmpeg-formats.html#Description). + +#### {% linkable_title USB cameras %} + +For `INPUT` a valid source is needed. USB camera are an easy way to test your video setup. To get all available USB cameras connected to the system, eg. use the v4l2 tools on a Linux machine. + +```bash +$ v4l2-ctl --list-devices +UVC Camera (046d:0825) (usb-0000:00:14.0-1): + /dev/video1 + +Integrated Camera (usb-0000:00:14.0-10): + /dev/video0 +``` + +Record a test video with your USB device `/dev/video1`: + +```bash +$ ffmpeg -i /dev/video1 -codec:v libx264 -qp 0 lossless.mp4 +[...] +Input #0, video4linux2,v4l2, from '/dev/video1': + Duration: N/A, start: 43556.376974, bitrate: 147456 kb/s + Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, 147456 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc +[...] +Output #0, mp4, to 'lossless.mp4': + Metadata: + encoder : Lavf57.41.100 + Stream #0:0: Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv422p, 640x480, q=-1--1, 30 fps, 15360 tbn, 30 tbc + Metadata: + encoder : Lavc57.48.101 libx264 + Side data: + cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1 +Stream mapping: + Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264)) +Press [q] to stop, [?] for help +frame= 223 fps= 40 q=-1.0 Lsize= 16709kB time=00:00:07.40 bitrate=18497.5kbits/s dup=58 drop=0 speed=1.32x +``` + From 4c523911d1d77af7b18015c4b14841f738798791 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 13 May 2017 07:26:27 +0200 Subject: [PATCH 08/33] Remove duplicate command --- source/_docs/installation/fedora.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_docs/installation/fedora.markdown b/source/_docs/installation/fedora.markdown index 574c661aa3c..8e5ffdd6df4 100644 --- a/source/_docs/installation/fedora.markdown +++ b/source/_docs/installation/fedora.markdown @@ -27,7 +27,6 @@ To isolate the Home Assistant installation a [venv](https://docs.python.org/3/li ```bash $ sudo mkdir -p /opt/homeassistant -$ cd /opt/homeassistant ``` Now switch to the new directory, setup the venv, and activate it. From fcab9fb7176808c0ef1d0b1568de382ca9cc662d Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 14 May 2017 15:50:27 +0200 Subject: [PATCH 09/33] Add requirement for netdisco --- source/_docs/installation/fedora.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/installation/fedora.markdown b/source/_docs/installation/fedora.markdown index 8e5ffdd6df4..645a76b3e5c 100644 --- a/source/_docs/installation/fedora.markdown +++ b/source/_docs/installation/fedora.markdown @@ -14,7 +14,7 @@ footer: true Install the development package of Python. ```bash -$ sudo dnf -y install python3-devel +$ sudo dnf -y install python3-devel redhat-rpm-config ``` and Home Assistant itself. From c1cd6e65d977d80d95dd4a0aede09d42a5840ca9 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 14 May 2017 15:54:00 +0200 Subject: [PATCH 10/33] Add link to firewall details --- source/_docs/installation/fedora.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/installation/fedora.markdown b/source/_docs/installation/fedora.markdown index 645a76b3e5c..cf945bbeaae 100644 --- a/source/_docs/installation/fedora.markdown +++ b/source/_docs/installation/fedora.markdown @@ -39,7 +39,7 @@ $ source bin/activate Install Home Assistant itself. ```bash -$ pip3 install homeassistant +$ pip3 install homeassistant colorlog ``` -Check the [autostart](/docs/autostart/systemd/) section in the documentation for further details. +Check the [autostart](/docs/autostart/systemd/) section in the documentation for further details and the [Firewall section](/docs/installation/troubleshooting/#no-access-to-the-frontend) if you want to access your Home Assistant installation. From 213571175734304a5003eb9877ec05d07410ad46 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 01:11:35 +0200 Subject: [PATCH 11/33] Update addon_config.markdown --- source/hassio/addon_config.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/hassio/addon_config.markdown b/source/hassio/addon_config.markdown index 0e89b719955..311921f620f 100644 --- a/source/hassio/addon_config.markdown +++ b/source/hassio/addon_config.markdown @@ -33,12 +33,11 @@ echo '{ "target": "beer" }' | jq -r ".target" ## {% linkable_title Add-on Docker file %} -All add-ons are based on Alpine Linux 3.5. Hass.io will automatically substitute the right base image based on the machine architecture. The Dockerfile is also required to have a VERSION environment variable which we will substitute with the version of the add-on. +All add-ons are based on Alpine Linux 3.5. Hass.io will automatically substitute the right base image based on the machine architecture. ``` FROM %%BASE_IMAGE%% -ENV VERSION %%VERSION%% ENV LANG C.UTF-8 # Install requirements for add-on @@ -51,6 +50,11 @@ RUN chmod a+x /run.sh CMD [ "/run.sh" ] ``` +If you don't use local build on device or our build script, make sure that the Dockerfile have also a set of labels include: +``` +LABEL io.hass.version="VERSION" io.hass.type="addon" io.hass.arch="armhf|aarch64|i386|amd64" +``` + ## {% linkable_title Add-on config %} The config for an add-on is stored in `config.json`. From cdafbad5e9176fa37249156af3586deb3466ea23 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 01:13:31 +0200 Subject: [PATCH 12/33] Update addon_testing.markdown --- source/hassio/addon_testing.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/hassio/addon_testing.markdown b/source/hassio/addon_testing.markdown index 8c8de685f14..101c98107a3 100644 --- a/source/hassio/addon_testing.markdown +++ b/source/hassio/addon_testing.markdown @@ -15,13 +15,14 @@ Right now add-ons will work with images that are stored on Docker Hub (using `im ## {% linkable_title Local run %} -You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. Replace in the Dockerfile: `%%VERSION%%` with your version and `%%BASE_IMAGE%%` with: +You can build an try the addon on your developer machine also. Move all addon stuff into a temp folder. Replace in the Dockerfile `%%BASE_IMAGE%%` with: - armhf: `resin/armhf-alpine:3.5` - aarch64: `resin/aarch64-alpine:3.5` - amd64: `resin/amd64-alpine:3.5` - i386: `resin/i386-alpine:3.5` +Add also a `LABEL io.hass.version="xy"` into your dockerfile. Use `docker` to build the test addon: `docker build -t local/my-test-addon .` Create a new folder for data and add a test _options.json_ file. After that you can run your add-on with: `docker run --rm -v /tmp/my_test_data:/data -p PORT_STUFF_IF_NEEDED local/my-test-addon` From 73c93429a063c2acf38b638fc9cac61915d60b94 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 01:14:59 +0200 Subject: [PATCH 13/33] Update addon_tutorial.markdown --- source/hassio/addon_tutorial.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/hassio/addon_tutorial.markdown b/source/hassio/addon_tutorial.markdown index e026e24e756..11ea9d13e7f 100644 --- a/source/hassio/addon_tutorial.markdown +++ b/source/hassio/addon_tutorial.markdown @@ -40,7 +40,6 @@ Once you have located your add-on directory, it's time to get started! ``` FROM %%BASE_IMAGE%% -ENV VERSION %%VERSION%% ENV LANG C.UTF-8 # Copy data for add-on From 7d9e13dc1047ab081f9a00326b93c8d4db159bf5 Mon Sep 17 00:00:00 2001 From: Gergely Peidl Date: Tue, 16 May 2017 08:14:31 +0200 Subject: [PATCH 14/33] Fixing Telegram docs (#2637) * Missing yaml formatter added for Telegram. * Fixing the url of notify.telegram --- source/_components/telegram_bot.markdown | 2 +- source/_components/telegram_bot.polling.markdown | 2 +- source/_components/telegram_bot.webhooks.markdown | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_components/telegram_bot.markdown b/source/_components/telegram_bot.markdown index e969170558a..7e427c8ca4b 100644 --- a/source/_components/telegram_bot.markdown +++ b/source/_components/telegram_bot.markdown @@ -82,7 +82,7 @@ action: An example to show the use of event_data in the action: -``` +```yaml - alias: 'Kitchen Telegram Speak' trigger: platform: event diff --git a/source/_components/telegram_bot.polling.markdown b/source/_components/telegram_bot.polling.markdown index 6536e349ada..b1a7316f106 100644 --- a/source/_components/telegram_bot.polling.markdown +++ b/source/_components/telegram_bot.polling.markdown @@ -34,5 +34,5 @@ Configuration variables: - **allowed_chat_ids** (*Required*): A list of user in the `user_id` Telegram format enabled to interact to webhook - **api_key** (*Required*): The API token of your bot. -To get your `chat_id` and `api_key` follow the instructions [here](/components.notify.telegram) . +To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram) . diff --git a/source/_components/telegram_bot.webhooks.markdown b/source/_components/telegram_bot.webhooks.markdown index 7bb8c601914..5f106a67022 100644 --- a/source/_components/telegram_bot.webhooks.markdown +++ b/source/_components/telegram_bot.webhooks.markdown @@ -37,7 +37,7 @@ Configuration variables: - **api_key** (*Required*): The API token of your bot. - **trusted_networks** (*Optional*): Telegram server access ACL as list. Defaults to `149.154.167.197-233`. -To get your `chat_id` and `api_key` follow the instructions [here](/components.notify.telegram) . +To get your `chat_id` and `api_key` follow the instructions [here](/components/notify.telegram) . Full configuration sample: From e927327cd1388535d2a5b02b7cfe1c468c896502 Mon Sep 17 00:00:00 2001 From: Ron Klinkien Date: Tue, 16 May 2017 13:51:34 +0200 Subject: [PATCH 15/33] Corrected exclude_domains argument (#2641) --- source/_components/influxdb.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown index 14b00a1a0fb..6a7f1698a3c 100644 --- a/source/_components/influxdb.markdown +++ b/source/_components/influxdb.markdown @@ -120,7 +120,7 @@ Example to run the script: ```bash $ hass --script influxdb_import --config CONFIG_DIR \ -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \ - --dbname INFLUXDB_DB_NAME --exclude-domain automation,configurator + --dbname INFLUXDB_DB_NAME --exclude_domains automation,configurator ``` Script arguments: From c12bd3c36b8f7f9d1c4068a29592ac9f3d8d7c6c Mon Sep 17 00:00:00 2001 From: Ron Klinkien Date: Tue, 16 May 2017 15:16:53 +0200 Subject: [PATCH 16/33] More argument corrections (#2642) --- source/_components/influxdb.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown index 6a7f1698a3c..270d3df1872 100644 --- a/source/_components/influxdb.markdown +++ b/source/_components/influxdb.markdown @@ -109,7 +109,7 @@ It will read all your state_change events from the database and add them as data You can specify the source database either by pointing the `--config` option to the config directory which includes the default sqlite database or by giving a sqlalchemy connection URI with `--uri`. The writing to InfluxDB is done in batches that can be changed with `--step`. -You can control, which data is imported by using the commandline options `--exclude-entities` and `--exclude-domain`. +You can control, which data is imported by using the commandline options `--exclude_entities` and `--exclude_domains`. Both get a comma separated list of either entity-ids or domain names that are excluded from the import. To test what gets imported you can use the `--simulate` option, which disables the actual write to the InfluxDB instance. From 3424892151c047b7989c3b3615b3cc31e73e5662 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 16:11:38 +0200 Subject: [PATCH 17/33] add devices support --- source/hassio/addon_config.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/hassio/addon_config.markdown b/source/hassio/addon_config.markdown index 311921f620f..7617d5d7669 100644 --- a/source/hassio/addon_config.markdown +++ b/source/hassio/addon_config.markdown @@ -90,6 +90,7 @@ The config for an add-on is stored in `config.json`. | startup | yes | `before` homeassistant will start. `after` homeassistant will start or `once` for application they don't run as deamon. | 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`. +| devices | no | Hos device list to map into add-on. Format is: `::` | map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup` | options | yes | Default options value of the add-on | schema | yes | Schema for options value of the add-on From c1a1912490d61a59c76d8ae9009be156acf96ff3 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 16:12:52 +0200 Subject: [PATCH 18/33] fix spell --- source/hassio/addon_config.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/hassio/addon_config.markdown b/source/hassio/addon_config.markdown index 7617d5d7669..a31dbd51ea0 100644 --- a/source/hassio/addon_config.markdown +++ b/source/hassio/addon_config.markdown @@ -90,7 +90,7 @@ The config for an add-on is stored in `config.json`. | startup | yes | `before` homeassistant will start. `after` homeassistant will start or `once` for application they don't run as deamon. | 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`. -| devices | no | Hos device list to map into add-on. Format is: `::` +| devices | no | Device list to map into add-on. Format is: `::` | map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup` | options | yes | Default options value of the add-on | schema | yes | Schema for options value of the add-on From 9a73e00636b81e8455be31b8ec23bcfb9be08a49 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 16 May 2017 23:46:02 +0200 Subject: [PATCH 19/33] Update addon_config.markdown --- source/hassio/addon_config.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/hassio/addon_config.markdown b/source/hassio/addon_config.markdown index a31dbd51ea0..06884d669b6 100644 --- a/source/hassio/addon_config.markdown +++ b/source/hassio/addon_config.markdown @@ -72,7 +72,7 @@ The config for an add-on is stored in `config.json`. "ports": { "123/tcp": 123 }, - "map": ["config", "ssl"], + "map": ["config:rw", "ssl"], "options": {}, "schema": {}, "image": "repo/{arch}-my-custom-addon" @@ -91,7 +91,7 @@ The config for an add-on is stored in `config.json`. | 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`. | devices | no | Device list to map into add-on. Format is: `::` -| map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup` +| map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`. Default it map it `ro`, you can change that if you add a ":rw" at the end of name. | options | yes | Default options value of the add-on | schema | yes | Schema for options value of the add-on | image | no | For use dockerhub. From 14109cf5c30ada1f89124a504629064c2dc6e0ab Mon Sep 17 00:00:00 2001 From: Beat Date: Wed, 17 May 2017 04:50:30 +0200 Subject: [PATCH 20/33] Issue 2310: Release filter on component page (#2646) * * removed duplicated code * give the search field focus on page load for faster interaction * introduced filter-by-version --- source/components/index.html | 38 +++++++++++++++--------------------- 1 file changed, 16 insertions(+), 22 deletions(-) diff --git a/source/components/index.html b/source/components/index.html index 20acc5991f5..b0b6dfed3e8 100644 --- a/source/components/index.html +++ b/source/components/index.html @@ -36,9 +36,9 @@ Support for these components is provided by the Home Assistant community.

All ({{tot}}) Featured - Added in {{ current_version }} ({{ current_version_components_count }}) - Added in {{ added_one_ago_version }} ({{ one_ago_version_components_count }}) - Added in {{ added_two_ago_version }} ({{ two_ago_version_components_count }}) + Added in {{ current_version }} ({{ current_version_components_count }}) + Added in {{ added_one_ago_version }} ({{ one_ago_version_components_count }}) + Added in {{ added_two_ago_version }} ({{ two_ago_version_components_count }}) {% for category in categories %} {% if category and category != 'Other' %} @@ -87,16 +87,14 @@ Support for these components is provided by the Home Assistant community. {% endraw %}