From 89175633f7ff5535e3ab881f21966a384a882456 Mon Sep 17 00:00:00 2001 From: Ionut Popovici Date: Sun, 8 Dec 2019 20:10:44 +0000 Subject: [PATCH 1/8] Update deconz.markdown (#11403) Added Lights tested for more than 30 days. OSRAM and Innr Added Xiaomi OpenClose sensors --- source/_integrations/deconz.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/deconz.markdown b/source/_integrations/deconz.markdown index fc5f1876ce4..d9a9555e262 100644 --- a/source/_integrations/deconz.markdown +++ b/source/_integrations/deconz.markdown @@ -393,6 +393,8 @@ The `entity_id` names will be `light.device_name`, where `device_name` is define - IKEA Trådfri Bulb E27 WS & RGB Opal 600lm - IKEA Trådfri Bulb GU10 W 400lm - IKEA Trådfri FLOALT LED light panel +- Innr BY-265, BY-245 +- OSRAM Classic A60 W clear - LIGHTIFY - OSRAM Flex RGBW - OSRAM Gardenpole RGBW - Philips Hue White A19 @@ -436,6 +438,8 @@ The `entity_id` name will be `sensor.device_name`, where `device_name` is define - Xiaomi Smart Home Wireless Switch - Temperature Sensor - Xiaomi Temperature/Humidity Sensor +- OpenClose Sensor + - Xiaomi Window / Door Sensor with Temperature ### deCONZ Daylight Sensor From 1adfb13afd7b37c5b635454fb75e5b59d930fe89 Mon Sep 17 00:00:00 2001 From: Dane Berryman <47973412+daneberryman@users.noreply.github.com> Date: Mon, 9 Dec 2019 21:31:25 +1100 Subject: [PATCH 2/8] Update sesame.markdown (#11404) --- source/_integrations/sesame.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/sesame.markdown b/source/_integrations/sesame.markdown index 15ceb6cdb9b..57ed4b3b0bc 100644 --- a/source/_integrations/sesame.markdown +++ b/source/_integrations/sesame.markdown @@ -12,7 +12,7 @@ The `sesame` platform allows you to control your [Sesame](https://candyhouse.co/ ## Configuration -Your Sesame needs to be paired with a mobile device running the app in *virtual station* mode, or a standalone [Wi-Fi Access Point](https://candyhouse.co/collections/frontpage/products/wi-fi-access-point). +Your Sesame needs to be paired with a standalone [Wi-Fi Access Point](https://candyhouse.co/collections/frontpage/products/wi-fi-access-point) purchased separately. You will also need to generate an API key from [my.candyhouse.co](https://my.candyhouse.co/#/credentials). From 144970a5333019587ef1882240e592ed3649ed03 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Mon, 9 Dec 2019 17:43:31 +0000 Subject: [PATCH 3/8] Adding details for FreeNAS/BSD (#10972) * Adding details for FreeNAS/BSD Adding the required commands for when people do a venv install on FreeNAS or FreeBSD, as explained by @atxbyea in the Discord server. * Update emulated_hue.markdown * Update emulated_hue.markdown --- source/_integrations/emulated_hue.markdown | 34 ++++++++++++++++++---- 1 file changed, 29 insertions(+), 5 deletions(-) diff --git a/source/_integrations/emulated_hue.markdown b/source/_integrations/emulated_hue.markdown index c184b2b0e9f..9fb8462b551 100644 --- a/source/_integrations/emulated_hue.markdown +++ b/source/_integrations/emulated_hue.markdown @@ -145,14 +145,24 @@ These attributes used to be found under the `customize` section of `homeassistan You can verify that the `emulated_hue` integration has been loaded and is responding by pointing a local browser to the following URL: -- `http://:8300/description.xml` - This URL should return a descriptor file in the form of an XML file. -- `http://:8300/api/pi/lights` - This will return a list of devices, lights, scenes, groups, etc.. that `emulated_hue` is exposing to Alexa. +- `http://:80/description.xml` - This URL should return a descriptor file in the form of an XML file. +- `http://:80/api/pi/lights` - This will return a list of devices, lights, scenes, groups, etc.. that `emulated_hue` is exposing to Alexa. -For Google Home, verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://:80/description.xml`). +Verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://:80/description.xml`). Both Google Home and Amazon Alexa/Echo (as of the 2019-08 firmware) require port 80. -For Amazon Alexa/Echo, verify that the URLs above are using port 80, rather than port 8300 (i.e. `http://:80/description.xml`). Since 2019-08 Amazon Echo firmware, Alexa no longer works with port 8300. +### Platform specific instructions -An additional step is required to run Home Assistant as a non-root user and use port 80 when using the AiO script. Execute the following command to allow `emulated_hue` to use port 80 as a non-root user. +#### Hass.io and Docker + +No further actions are required + +#### Python venv + +An additional step is required to run Home Assistant as a non-root user and use port 80. + +##### Linux + +On Linux systems (Ubuntu, Debian, etc) execute the following command to allow `emulated_hue` to use port 80 as a non-root user: ```bash sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin/python3 @@ -160,6 +170,20 @@ sudo setcap 'cap_net_bind_service=+ep' /srv/homeassistant/homeassistant_venv/bin Please note that your path may be different depending on your installation method. For example, if you followed the [Virtualenv instructions](/docs/installation/virtualenv/), your path will be `/srv/homeassistant/bin/python3`. +##### FreeBSD and FreeNAS + +On FreeBSD based systems, including FreeNAS, execute the following to allow `emulated_hue` to use port 80 as a non-root user: + +```bash +sysctl net.inet.ip.portrange.reservedhigh=0 +``` + +You can make this persist by adding the following to `/etc/sysctl.conf`: + +```bash +net.inet.ip.portrange.reservedhigh=0 +``` + ### License Much of this code is based on work done by Bruce Locke on his [ha-local-echo](https://github.com/blocke/ha-local-echo) project, originally released under the MIT License. The license is located [here](https://github.com/blocke/ha-local-echo/blob/b9bf5dcaae6d8e305e2283179ffba64bde9ed29e/LICENSE). From d49619501d6889c946b626b6a9c26dbe42e4f790 Mon Sep 17 00:00:00 2001 From: Villhellm Date: Mon, 9 Dec 2019 12:00:29 -0800 Subject: [PATCH 4/8] Add information about starting Lovelace paths with numbers (#11416) --- source/lovelace/views.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/lovelace/views.markdown b/source/lovelace/views.markdown index 1ab6ed6ec44..aad366c3b48 100644 --- a/source/lovelace/views.markdown +++ b/source/lovelace/views.markdown @@ -85,7 +85,7 @@ View config: ## Paths -You can link to one view from another view by its path. For this use cards that support navigation (`navigation_path`). Do not use special characters in paths. +You can link to one view from another view by its path. For this use cards that support navigation (`navigation_path`). Do not use special characters in paths. Do not begin a path with a number. This will cause the parser to read your path as a view index. ### Example From 7afb06352b72607f7c08e4ed0501bf794f07d9e8 Mon Sep 17 00:00:00 2001 From: Colin Frei Date: Mon, 9 Dec 2019 22:24:38 +0100 Subject: [PATCH 5/8] fix typo in docs (#11418) --- source/_integrations/webostv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index 9dde34ff73a..e765f706a52 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -149,7 +149,7 @@ data: ### Next/Previous buttons -The behaviour of the next and previsous buttons is different depending on the active source: +The behaviour of the next and previous buttons is different depending on the active source: - if the source is 'LiveTV' (television): next/previous buttons act as channel up/down - otherwise: next/previous buttons act as next/previous track From 06d2f06473c5d8315be123eadcb2738e54db7554 Mon Sep 17 00:00:00 2001 From: floatiepen Date: Tue, 10 Dec 2019 14:12:51 -0800 Subject: [PATCH 6/8] Access Token URI must use port 443 (w/ valid cert) (#11417) Amazon reps have stated this is a requirement, and stating it up front will will help many people trying to use the default port of 8123, even with a trusted certificate https://forums.developer.amazon.com/questions/74075/alexa-oauth-20-https-problem.html --- source/_integrations/alexa.smart_home.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown index 2b72bd1df37..e68f75e19cd 100644 --- a/source/_integrations/alexa.smart_home.markdown +++ b/source/_integrations/alexa.smart_home.markdown @@ -173,6 +173,7 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom - Input all information required. Assuming your Home Assistant can be accessed by https://[YOUR HOME ASSISTANT URL:PORT] * `Authorization URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/authorize * `Access Token URI`: https://[YOUR HOME ASSISTANT URL:PORT]/auth/token + - Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work * `Client ID`: - https://pitangui.amazon.com/ if you are in US - https://layla.amazon.com/ if you are in EU From be18953d5927d0a4db97bf33b5b4478e876a6a9d Mon Sep 17 00:00:00 2001 From: Daniel <44697375+azrarel783@users.noreply.github.com> Date: Tue, 10 Dec 2019 23:13:30 +0100 Subject: [PATCH 7/8] Updating callback URL (#11393) Had problems with integrating Spotiy in HA, but I found out the callback url with version 0.102.3 is send without the port. So I edited the callback URL in the Spotiy app and was able to add Spotify to HA --- source/_integrations/spotify.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown index a96557cf511..e38bd74d85e 100644 --- a/source/_integrations/spotify.markdown +++ b/source/_integrations/spotify.markdown @@ -28,10 +28,10 @@ To create the required Spotify application: - Add a **Redirect URI** in one of the following forms: If you are not using SSL: - `http://:/api/spotify` + `http:///api/spotify` If you are using SSL: - `https://:/api/spotify` + `https:///api/spotify` - Click **Save** after adding the URI. From b33627051a75d061ce4d93adaea20ff842d55663 Mon Sep 17 00:00:00 2001 From: Jardi Martinez <1088732+jardiamj@users.noreply.github.com> Date: Tue, 10 Dec 2019 23:56:41 -0800 Subject: [PATCH 8/8] Provide link to How to enable i2c on HassOS instructions. (#11425) * Provide link to How to enable i2c on HassOS instructions. * :pencil2: Tweak Co-authored-by: Franck Nijhof --- source/_integrations/mcp23017.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/mcp23017.markdown b/source/_integrations/mcp23017.markdown index 4991a3c7d67..35a241040bb 100644 --- a/source/_integrations/mcp23017.markdown +++ b/source/_integrations/mcp23017.markdown @@ -14,6 +14,8 @@ The `mcp23017` integration is the base for all related mcp23017 platforms in Hom For more details about the MCP23017 I2C I/O port expander you can find its datasheet here: [MCP23017](https://www.microchip.com/wwwproducts/en/MCP23017). +If you are using Hass.io on HassOS you can’t use existing methods to enable the I2C bus on a Raspberry Pi, you will have to [enable the I2C interface in the Hass.io configuration](https://github.com/home-assistant/hassos/blob/dev/Documentation/boards/raspberrypi.md#i2c) using a USB stick. To accomplish that, follow this step by step instructions: [Enable HassOS i2c](https://www.home-assistant.io/hassio/enable_i2c). + ## Binary Sensor The `mcp23017` binary sensor platform allows you to read sensor values from the I/O pins of your [MCP23017 I2C I/O expander](https://www.adafruit.com/product/732).