From ec30253d461b9adddb1e6c939a7f87c7b920737d Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 24 Apr 2019 14:56:04 -0700 Subject: [PATCH 01/17] Update description --- source/_posts/2019-04-24-release-92.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2019-04-24-release-92.markdown b/source/_posts/2019-04-24-release-92.markdown index d791b5ae2da..fc6a1968919 100644 --- a/source/_posts/2019-04-24-release-92.markdown +++ b/source/_posts/2019-04-24-release-92.markdown @@ -1,7 +1,7 @@ --- layout: post title: "0.92: HEOS, Somfy MyLink, Genius Hub" -description: "Get your whole home audio " +description: "With 0.92, get your whole home auto game on with the new HEOS integration while controlling your covers with Somfy." date: 2019-04-24 00:11:03 date_formatted: "April 24, 2019" author: Paulus Schoutsen From 36864b23fe44422b70e9b4fe8b56bbef83aee37e Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 24 Apr 2019 15:47:35 -0700 Subject: [PATCH 02/17] Embed tweet --- source/_posts/2019-04-24-release-92.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/_posts/2019-04-24-release-92.markdown b/source/_posts/2019-04-24-release-92.markdown index fc6a1968919..168c8515754 100644 --- a/source/_posts/2019-04-24-release-92.markdown +++ b/source/_posts/2019-04-24-release-92.markdown @@ -19,6 +19,9 @@ It's time for the 0.92 release. We took a week extra for this release, because w This release continues to improve on our new camera streaming feature released with Home Assistant 0.90. This release adds support to Lovelace to show camera streams as part of your cards. Support has been aded to picture glance, picture entity and picture element cards. Just add `camera_view: live` to the configuration. Be careful showing live streams on mobile, camera streams can use a lot of data. We are exploring being able to add a mode to only show the streams on desktop. + + ## {% linkable_title HEOS integration %} The HEOS integration adds support for HEOS capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. The features include controlling players, viewing playing media info, selecting the source from physical inputs and HEOS favorites, and more. We have established a relationship with the lead architect for the HEOS API and look forward to adding more features through this collaboration. Thanks to [@easink] for the initial contribution. From 5e44c009b71959d469715ba956b1c09dcd545be6 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 24 Apr 2019 20:15:11 -0700 Subject: [PATCH 03/17] Update t-shirt listing (#9291) --- ...2-22-home-assistant-tshirts-have-arrived.markdown | 12 +----------- source/index.html | 2 +- 2 files changed, 2 insertions(+), 12 deletions(-) diff --git a/source/_posts/2017-02-22-home-assistant-tshirts-have-arrived.markdown b/source/_posts/2017-02-22-home-assistant-tshirts-have-arrived.markdown index 2227a71e2a1..add82986046 100644 --- a/source/_posts/2017-02-22-home-assistant-tshirts-have-arrived.markdown +++ b/source/_posts/2017-02-22-home-assistant-tshirts-have-arrived.markdown @@ -21,22 +21,12 @@ What time is it? Yep, t-shirt time. Today we're launching the first two Home Ass - [Visit the 🇺🇸 US store][store-us] - [Visit the 🇪🇺 EU store][store-eu] - - -And because we love the internet and all the things that it has brought us, **we will start with having 100% of the profit from the sales be donated to the [Electronic Frontier Foundation][eff]**. If you buy a shirt you will hit two birds with one stone (figuratively): you get to wear a kick-ass Home Assistant t-shirt and you help fund defending civil liberties in the digital world. - -The EFF is a nonprofit organization that aims to protect the rights of technology users. You might however be more familiar with one of their projects: [Let's Encrypt][le]. [Read more about what the EFF does.][eff-issues] - -So, what are you waiting for? Get yourself a shirt! [🇪🇺 EU store][store-eu] – [🇺🇸 US store][store-us] -

Family of 4 on a bench wearing the new black Home Assistant shirt. [🇪🇺 EU][black-eu] – [🇺🇸 US][black-us]

-We are using [Teespring.com][ts] to manage all the sales, production and distribution of the shirts and they will also donate our profits to the EFF. It's also how we got all these amazing stockphotos. Some extra things to note about our teespring shop: - - - Teespring shows that there is a number of days left until the end of the campaign for the shirts. Don't worry about that, it should automatically relaunch. +We are using [Teespring.com][ts] to manage all the sales, production and distribution of the shirts. It's also how we got all these amazing stockphotos. More photos after the click. diff --git a/source/index.html b/source/index.html index 03277214372..396ddc8d1bf 100644 --- a/source/index.html +++ b/source/index.html @@ -93,7 +93,7 @@ description: Open source home automation that puts local control and privacy fir Join the Home Assistant t-shirt revolution!
- All proceeds will be donated to the Electronic Frontier Foundation. + Look sharp in blue, black or gray. Wearing a HA t-shirt is okay.
From 62d366dd3713ab4e188172ddbb8e9b67d070492b Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 24 Apr 2019 22:16:57 -0700 Subject: [PATCH 04/17] Add sponsors --- source/images/sponsors/nabu_casa.svg | 1 + source/images/sponsors/ubnt.svg | 177 +++++++++++++++++++++++++++ source/index.html | 13 +- 3 files changed, 190 insertions(+), 1 deletion(-) create mode 100644 source/images/sponsors/nabu_casa.svg create mode 100644 source/images/sponsors/ubnt.svg diff --git a/source/images/sponsors/nabu_casa.svg b/source/images/sponsors/nabu_casa.svg new file mode 100644 index 00000000000..7a46a04193e --- /dev/null +++ b/source/images/sponsors/nabu_casa.svg @@ -0,0 +1 @@ +logo-text-square \ No newline at end of file diff --git a/source/images/sponsors/ubnt.svg b/source/images/sponsors/ubnt.svg new file mode 100644 index 00000000000..cd33f6fe17d --- /dev/null +++ b/source/images/sponsors/ubnt.svg @@ -0,0 +1,177 @@ + +image/svg+xml \ No newline at end of file diff --git a/source/index.html b/source/index.html index 396ddc8d1bf..ddcff4f6af7 100644 --- a/source/index.html +++ b/source/index.html @@ -141,7 +141,18 @@ description: Open source home automation that puts local control and privacy fir -
+
+
+

Home Assistant is sponsored by

+ + Ubituiti Networks logo + + Nabu Casa logo + +
+
+ +

Home Assistant in the press

From 0c305a7a543487a1fd9ce02c2440a1c4b21a7b77 Mon Sep 17 00:00:00 2001 From: cgtobi Date: Thu, 25 Apr 2019 15:31:00 +0200 Subject: [PATCH 05/17] Rename google tts to google_translate (#9300) --- source/_components/tts.markdown | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/source/_components/tts.markdown b/source/_components/tts.markdown index 5698f9a6b8f..f6f727c2013 100644 --- a/source/_components/tts.markdown +++ b/source/_components/tts.markdown @@ -19,7 +19,7 @@ To get started, add the following lines to your `configuration.yaml` (example fo ```yaml # Example configuration.yaml entry for Google TTS service tts: - - platform: google + - platform: google_translate ```

@@ -56,7 +56,7 @@ The extended example from above would look like the following sample: ```yaml # Example configuration.yaml entry for Google TTS service tts: - - platform: google + - platform: google_translate cache: true cache_dir: /tmp/tts time_memory: 300 @@ -96,8 +96,8 @@ The `say` service support `language` and on some platforms also `options` for se Say to all `media_player` device entities: ```yaml -# Replace google_say with _say when you use a different platform. -service: tts.google_say +# Replace google_translate_say with _say when you use a different platform. +service: tts.google_translate_say entity_id: "all" data: message: 'May the Force be with you.' @@ -106,7 +106,7 @@ data: Say to the `media_player.floor` device entity: ```yaml -service: tts.google_say +service: tts.google_translate_say entity_id: media_player.floor data: message: 'May the Force be with you.' @@ -115,7 +115,7 @@ data: Say to the `media_player.floor` device entity in French: ```yaml -service: tts.google_say +service: tts.google_translate_say entity_id: media_player.floor data: message: 'Que la force soit avec toi.' @@ -125,7 +125,7 @@ data: With a template: ```yaml -service: tts.google_say +service: tts.google_translate_say data_template: message: "Temperature is {% raw %}{{states('sensor.temperature')}}{% endraw %}." cache: false From bba4286fdcddd8a8050f93c91d83359fac824f5b Mon Sep 17 00:00:00 2001 From: ThaStealth Date: Thu, 25 Apr 2019 15:38:15 +0200 Subject: [PATCH 06/17] Epsonprinter (#9294) * Create epsonprinter.markdown * Update epsonprinter.markdown * Update epsonprinter.markdown * Update source/_components/epsonprinter.markdown Co-Authored-By: ThaStealth * Update epsonprinter.markdown * Update epsonprinter.markdown * :pencil2: Tweak --- source/_components/epsonprinter.markdown | 65 ++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 source/_components/epsonprinter.markdown diff --git a/source/_components/epsonprinter.markdown b/source/_components/epsonprinter.markdown new file mode 100644 index 00000000000..6f94796352b --- /dev/null +++ b/source/_components/epsonprinter.markdown @@ -0,0 +1,65 @@ +--- +layout: page +title: "Epson Printer" +description: "Instructions on how to integrate Epson Workforce Printer into Home Assistant." +date: 2019-04-09 16:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: epson.png +ha_category: Sensor +ha_release: 0.92 +ha_iot_class: Local Polling +--- + +The `epson printer` platform allows you to monitor the ink levels of a Epson Workforce printer from Home +Assistant. + +To add Epson Printer to your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: epsonprinter + host: IP_ADDRESS + monitored_conditions: + - black + - yellow + - magenta + - cyan + - clean +``` + +{% configuration %} +host: + description: The host name or address of the Epson printer + required: true + type: string +monitored_conditions: + description: The cartridge colours to monitor. + required: true + type: map + keys: + black: + description: The black ink cartridge + yellow: + description: The yellow ink cartridge. + magenta: + description: The magenta (=red) ink cartridge. + cyan: + description: The cyan (=blue) ink cartridge. + clean: + description: The cleaning cartridge. +{% endconfiguration %} + +Supported devices: + +- Epson Workforce printers who publish a HTTP page containing the ink cardridge levels + +Tested devices: + +- Epson WF3540 + +To make this module work you need to connect your printer to your LAN. +The best is to navigate to the IP of the printer to check. From 27b95f29e8b6a08ef0de50e0763f7a45967222f5 Mon Sep 17 00:00:00 2001 From: Phill Price Date: Thu, 25 Apr 2019 14:44:13 +0100 Subject: [PATCH 07/17] Updates to use Long Lived Tokens not API Password (#9287) * Updates to use Long Lived Tokens not API Password * Missed Bearer from Binary examples * Only talk about the token at one place --- source/_components/http.markdown | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/source/_components/http.markdown b/source/_components/http.markdown index 85bb255aabb..de1a455dde8 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -69,7 +69,7 @@ ssl_key: required: false type: string cors_allowed_origins: - description: "A list of origin domain names to allow [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) requests from. Enabling this will set the `Access-Control-Allow-Origin` header to the Origin header if it is found in the list, and the `Access-Control-Allow-Headers` header to `Origin, Accept, X-Requested-With, Content-type, X-HA-access`. You must provide the exact Origin, i.e. `https://www.home-assistant.io` will allow requests from `https://www.home-assistant.io` but __not__ `http://www.home-assistant.io`." + description: "A list of origin domain names to allow [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) requests from. Enabling this will set the `Access-Control-Allow-Origin` header to the Origin header if it is found in the list, and the `Access-Control-Allow-Headers` header to `Origin, Accept, X-Requested-With, Content-type, Authorization`. You must provide the exact Origin, i.e. `https://www.home-assistant.io` will allow requests from `https://www.home-assistant.io` but __not__ `http://www.home-assistant.io`." required: false type: string, list use_x_forwarded_for: @@ -139,6 +139,8 @@ The `http` platforms are not real platforms within the meaning of the terminolog To use those kind of [sensors](#sensor) or [binary sensors](#binary-sensor) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived. +Create a [Long-Lived Access Tokens](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) in the Home Assistant UI at the bottom of your profile if you want to use HTTP sensors. + All [requests](/developers/rest_api/#post-apistatesltentity_id) need to be sent to the endpoint of the device and must be **POST**. ## {% linkable_title IP filtering and banning %} @@ -189,7 +191,7 @@ The JSON payload must contain the new state and can have a friendly name. The fr For a quick test `curl` can be useful to "simulate" a device. ```bash -$ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \ +$ curl -X POST -H "Authorization: Bearer LONG_LIVED_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{"state": "off", "attributes": {"friendly_name": "Radio"}}' \ http://localhost:8123/api/states/binary_sensor.radio @@ -198,7 +200,7 @@ $ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \ To check if the sensor is working, use again `curl` to retrieve the [current state](/developers/rest_api/#get-apistatesltentity_id). ```bash -$ curl -X GET -H "x-ha-access: YOUR_PASSWORD" \ +$ curl -X GET -H "Authorization: Bearer LONG_LIVED_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ http://localhost:8123/api/states/binary_sensor.radio { @@ -223,7 +225,7 @@ As already shown on the [API](/developers/rest_api/) page, it's very simple to u ```python response = requests.post( 'http://localhost:8123/api/states/binary_sensor.radio', - headers={'x-ha-access': 'YOUR_PASSWORD', 'content-type': 'application/json'}, + headers={'Authorization': 'Bearer LONG_LIVED_ACCESS_TOKEN', 'content-type': 'application/json'}, data=json.dumps({'state': 'on', 'attributes': {'friendly_name': 'Radio'}})) print(response.text) ``` @@ -234,7 +236,7 @@ print(response.text) ```bash $ http -v POST http://localhost:8123/api/states/binary_sensor.radio \ - x-ha-access:YOUR_PASSWORD content-type:application/json state=off \ + 'Authorization:Bearer LONG_LIVED_ACCESS_TOKEN' content-type:application/json state=off \ attributes:='{"friendly_name": "Radio"}' ``` @@ -263,7 +265,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other For a quick test, `curl` can be useful to "simulate" a device. ```bash -$ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \ +$ curl -X POST -H "Authorization: Bearer LONG_LIVED_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{"state": "20", "attributes": {"unit_of_measurement": "°C", "friendly_name": "Bathroom Temp"}}' \ http://localhost:8123/api/states/sensor.bathroom_temperature @@ -272,7 +274,7 @@ $ curl -X POST -H "x-ha-access: YOUR_PASSWORD" \ You can then use `curl` again to retrieve the [current sensor state](/developers/rest_api/#get-apistatesltentity_id) and verify the sensor is working. ```bash -$ curl -X GET -H "x-ha-access: YOUR_PASSWORD" \ +$ curl -X GET -H "Authorization: Bearer LONG_LIVED_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ http://localhost:8123/api/states/sensor.bathroom_temperature { @@ -287,4 +289,4 @@ $ curl -X GET -H "x-ha-access: YOUR_PASSWORD" \ } ``` -For more examples please visit the [HTTP Binary Sensor](#examples) page. \ No newline at end of file +For more examples please visit the [HTTP Binary Sensor](#examples) page. From 721fc95e81cfce22173cd005b21f3a69dba2d7d5 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Thu, 25 Apr 2019 16:37:30 +0200 Subject: [PATCH 08/17] Update link (fixes #9248) (#9301) --- source/_docs/mqtt/broker.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/mqtt/broker.markdown b/source/_docs/mqtt/broker.markdown index 2fd03ed181b..a7cf4a08b5c 100644 --- a/source/_docs/mqtt/broker.markdown +++ b/source/_docs/mqtt/broker.markdown @@ -59,7 +59,7 @@ mqtt: ### {% linkable_title Run your own %} -Along with the embedded broker this is the most private option, but it requires a bit more work. There are multiple free and open-source brokers to pick from: e.g., [Mosquitto](http://mosquitto.org/), [EMQ](http://emqtt.io/), or [Mosca](http://www.mosca.io/). +Along with the embedded broker this is the most private option, but it requires a bit more work. There are multiple free and open-source brokers to pick from: e.g., [Mosquitto](http://mosquitto.org/), [EMQ](https://github.com/emqx/emqx) or [Mosca](http://www.mosca.io/). ```yaml # Example configuration.yaml entry From 697a6a55d6501aa01667fae0fecd70c8151b4826 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 25 Apr 2019 07:45:19 -0700 Subject: [PATCH 09/17] Update tweet --- source/_posts/2019-04-24-release-92.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_posts/2019-04-24-release-92.markdown b/source/_posts/2019-04-24-release-92.markdown index 168c8515754..9578b1e337b 100644 --- a/source/_posts/2019-04-24-release-92.markdown +++ b/source/_posts/2019-04-24-release-92.markdown @@ -19,7 +19,7 @@ It's time for the 0.92 release. We took a week extra for this release, because w This release continues to improve on our new camera streaming feature released with Home Assistant 0.90. This release adds support to Lovelace to show camera streams as part of your cards. Support has been aded to picture glance, picture entity and picture element cards. Just add `camera_view: live` to the configuration. Be careful showing live streams on mobile, camera streams can use a lot of data. We are exploring being able to add a mode to only show the streams on desktop. -