jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-17 06:16:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed all {{site_root}} entries from links (#14873)

Browse Source
This commit is contained in:
Ron Klinkien 2020-10-04 12:47:06 +02:00 committed by GitHub
parent 9247c84a50
commit c7b6673cc8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
52 changed files with 76 additions and 76 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_docs/automation/editor.markdown
View File

@ -10,19 +10,19 @@ From the UI choose **Configuration** which is located in the sidebar, then click
Choose a meaningful name for your automation rules.
<p class='img'>
<img src='{{site_root}}/images/docs/automation-editor/new-automation.png' />
<img src='/images/docs/automation-editor/new-automation.png' />
</p>
If the value of the sensor is greater than 10, then the automation rule should apply.
<p class='img'>
<img src='{{site_root}}/images/docs/automation-editor/new-trigger.png' />
<img src='/images/docs/automation-editor/new-trigger.png' />
</p>
Firing a [persistent notification](/integrations/persistent_notification/) is the result.
<p class='img'>
<img src='{{site_root}}/images/docs/automation-editor/new-action.png' />
<img src='/images/docs/automation-editor/new-action.png' />
</p>
As "Service Data" we want a simple text that is shown as part of the notification.

2
source/_docs/frontend.markdown
View File

@ -6,7 +6,7 @@ description: "Frontend of Home Assistant."
The frontend of Home Assistant is built with [Polymer](https://www.polymer-project.org/).
<p class='img'>
<img src='{{site_root}}/images/screenshots/ui2015.png' />
<img src='/images/screenshots/ui2015.png' />
</p>
The [User Interface section](/cookbook/#user-interface) can give you some starting points to expand the frontend.

2
source/_integrations/automation.markdown
View File

@ -15,7 +15,7 @@ Please see [Automating Home Assistant](/docs/automation/) for in-depth
documentation on how to use the automation integration.
<p class='img'>
<img src='{{site_root}}/images/screenshots/automation-switches.png' />
<img src='/images/screenshots/automation-switches.png' />
</p>
## Configuration

2
source/_integrations/config.markdown
View File

@ -36,7 +36,7 @@ This section enables you to manage the name, location, and unit system of your H
This section enables you to control Home Assistant from within Home Assistant. Check your configuration, reload the core, groups, scripts, automations, and the Home Assistant process itself with a single mouse click.
<p class='img'>
<img src='{{site_root}}/images/screenshots/server-management.png' />
<img src='/images/screenshots/server-management.png' />
</p>
### Persons

2
source/_integrations/cups.markdown
View File

@ -19,7 +19,7 @@ You will need to install the `python3-dev` or `python3-devel` package and the de
To set up the sensor the "Queue Name" of the printer is needed. The fastest way to get it, is to visit the CUPS web interface at "http://[IP ADDRESS PRINT SERVER]:631" and go to "Printers".
<p class='img'>
<img src='{{site_root}}/images/screenshots/cups-sensor.png' />
<img src='/images/screenshots/cups-sensor.png' />
</p>
## Configuration

4
source/_integrations/datadog.markdown
View File

@ -12,13 +12,13 @@ The `datadog` integration sends all state changes to [Datadog](https://www.datad
Datadog allows you to analyze, monitor, cross-reference and alert upon your data. You can use it to detect statistical anomalies, see graphs across multiple sources in real-time, send critical alerts to Slack, etc.
<p class='img'>
<img src='{{site_root}}/images/screenshots/datadog-board-example.png' />
<img src='/images/screenshots/datadog-board-example.png' />
</p>
The integration also sends events from the logbook into Datadog, allowing you to correlate these events with your data.
<p class='img'>
<img src='{{site_root}}/images/screenshots/datadog-event-stream.png' />
<img src='/images/screenshots/datadog-event-stream.png' />
</p>
To use the `datadog` integration in your installation, add the following to your `configuration.yaml` file:

6
source/_integrations/discord.markdown
View File

@ -42,7 +42,7 @@ token:
Bots can send messages to servers and users or attach local available images. To add the bot to a server you are an admin on, get the details of the bot from the [Discord My Apps page](https://discordapp.com/developers/applications/me).
<p class='img'>
<img src='{{site_root}}/images/screenshots/discord-bot.png' />
<img src='/images/screenshots/discord-bot.png' />
</p>
Now use the Discord Authorization page with the **Client ID** of your [bot](https://discordapp.com/developers/docs/topics/oauth2#bots).
@ -50,7 +50,7 @@ Now use the Discord Authorization page with the **Client ID** of your [bot](http
`https://discordapp.com/api/oauth2/authorize?client_id=[CLIENT_ID]&scope=bot&permissions=0`
<p class='img'>
<img src='{{site_root}}/images/screenshots/discord-auth.png' />
<img src='/images/screenshots/discord-auth.png' />
</p>
Wait for the confirmation which should say "Authorized".
@ -58,7 +58,7 @@ Wait for the confirmation which should say "Authorized".
Once the bot has been added to your server, get the channel ID of the channel you want the bot to operate in. In The Discord application go to **Settings** > **Appearance** > **Check developer mode**.
<p class='img'>
<img src='{{site_root}}/images/screenshots/discord-api.png' />
<img src='/images/screenshots/discord-api.png' />
</p>
Right click channel name and copy the channel ID (**Copy ID**).

2
source/_integrations/dweet.markdown
View File

@ -14,7 +14,7 @@ ha_domain: dweet
The `dweet` integration makes it possible to transfer details collected with Home Assistant to [Dweet.io](https://dweet.io/) and visualize them with [freeboard.io](https://freeboard.io). Keep in mind that your information will be public!
<p class='img'>
<img src='{{site_root}}/images/screenshots/dweet-freeboard.png' />
<img src='/images/screenshots/dweet-freeboard.png' />
</p>
<div class='note warning'>

4
source/_integrations/ecobee.markdown
View File

@ -65,8 +65,8 @@ api_key:
{% endconfiguration %}
<p class='img'>
<img src='{{site_root}}/images/screenshots/ecobee-sensor-badges.png' />
<img src='{{site_root}}/images/screenshots/ecobee-thermostat-card.png' />
<img src='/images/screenshots/ecobee-sensor-badges.png' />
<img src='/images/screenshots/ecobee-thermostat-card.png' />
</p>
You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Integrations** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.

2
source/_integrations/filter.markdown
View File

@ -17,7 +17,7 @@ The `filter` platform enables sensors that process the states of other entities.
`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph](/lovelace/history-graph/) component.
<p class='img'>
<img src='{{site_root}}/images/screenshots/filter-sensor.png' />
<img src='/images/screenshots/filter-sensor.png' />
</p>
## Configuration

4
source/_integrations/flock.markdown
View File

@ -16,13 +16,13 @@ The `flock` platform uses [Flock.com](https://flock.com) to deliver notification
Go to the [Flock.com Admin website](https://admin.flock.com/#!/webhooks) and create a new "Incoming Webhooks". Choose a channel to send the notifications from Home Assistant to, specify a name and press *Save and Generate URL*.
<p class='img'>
<img src='{{site_root}}/images/integrations/flock/flock-webhook.png' />
<img src='/images/integrations/flock/flock-webhook.png' />
</p>
You will need the last part of the URL which is the `access_token` for your room.
<p class='img'>
<img src='{{site_root}}/images/integrations/flock/new-webhook.png' />
<img src='/images/integrations/flock/new-webhook.png' />
</p>
## Configuration

2
source/_integrations/garadget.markdown
View File

@ -67,7 +67,7 @@ If provided, the **access_token** will be used, otherwise the **username** and *
## Example
<p class='img'>
<img src='{{site_root}}/images/integrations/garadget/cover_garadget_details.png' />
<img src='/images/integrations/garadget/cover_garadget_details.png' />
</p>
{% raw %}

2
source/_integrations/geo_rss_events.markdown
View File

@ -15,7 +15,7 @@ The `geo_rss_events` sensor retrieves events from a GeoRSS feed and shows inform
This sensor is particularly useful if events occur unexpectedly in the vicinity of the home while the GeoRSS feed also contains many events representing distant unrelated entries. Typical examples are bush fires alerts or earthquakes.
<p class='img'>
<img src='{{site_root}}/images/screenshots/geo-rss-incidents-group-screenshot.png' />
<img src='/images/screenshots/geo-rss-incidents-group-screenshot.png' />
</p>
The reference point for comparing the distance is by default defined by `latitude` and `longitude` in the basic configuration.

4
source/_integrations/geonetnz_volcano.markdown
View File

@ -25,11 +25,11 @@ to show on the default map automatically.
The data is updated every 5 minutes.
<p class='img'>
<img src='{{site_root}}/images/integrations/geonetnz_volcano/map.png' />
<img src='/images/integrations/geonetnz_volcano/map.png' />
</p>
<p class='img'>
<img src='{{site_root}}/images/integrations/geonetnz_volcano/sensor.png' />
<img src='/images/integrations/geonetnz_volcano/sensor.png' />
</p>
<div class='note'>

4
source/_integrations/history.markdown
View File

@ -24,8 +24,8 @@ history:
```
<p class='img'>
<a href='{{site_root}}/images/screenshots/component_history_24h.png'>
<img src='{{site_root}}/images/screenshots/component_history_24h.png' />
<a href='/images/screenshots/component_history_24h.png'>
<img src='/images/screenshots/component_history_24h.png' />
</a>
</p>

4
source/_integrations/hp_ilo.markdown
View File

@ -15,7 +15,7 @@ If the ILO or specified jsonpath query returns only a single value (e.g., a temp
Some more details about what can be retrieved from these sensors is available in the [python-hpilo documentation](https://seveas.github.io/python-hpilo/).
<p class='img'>
<img src='{{site_root}}/images/screenshots/hp_ilo.png' />
<img src='/images/screenshots/hp_ilo.png' />
</p>
## Configuration
@ -114,7 +114,7 @@ sensor:
```
<p class='img'>
<img src='{{site_root}}/images/screenshots/hp_ilo_sensors.png' />
<img src='/images/screenshots/hp_ilo_sensors.png' />
</p>
## Hardware specifics

2
source/_integrations/ign_sismologia.markdown
View File

@ -23,7 +23,7 @@ on the default map automatically, or on a map card by defining the source
of each entity.
<p class='img'>
<img src='{{site_root}}/images/screenshots/ign-sismologia-feed-map.png' />
<img src='/images/screenshots/ign-sismologia-feed-map.png' />
</p>
The data is updated every 5 minutes.

6
source/_integrations/isy994.markdown
View File

@ -292,7 +292,7 @@ A device is created by creating a directory, with the name for the device, under
A program, named *status*, is required under the program device directory. A program, named *actions*, is required for all program devices except for binary_sensor. Any other programs in these device directories will be ignored. The *status* program requires that you create a variable with the name of your choice. This variable will store the actual status of the new device and will be updated by the *action* program.
<p class='img'>
<img src='{{site_root}}/images/isy994/isy994_CoverExample.png' />
<img src='/images/isy994/isy994_CoverExample.png' />
</p>
The *status* program in this directory is what indicates the state of the device:
@ -304,7 +304,7 @@ The *status* program in this directory is what indicates the state of the device
- *switch* on if the clause returns true, otherwise off.
<p class='img'>
<img src='{{site_root}}/images/isy994/isy994_SwitchStatusExample.png' />
<img src='/images/isy994/isy994_SwitchStatusExample.png' />
</p>
The *actions* program indicates what should be performed for the following device services:
@ -315,7 +315,7 @@ The *actions* program indicates what should be performed for the following devic
- *switch* the THEN clause is evaluated for the turn_on service, the ELSE clause is evaluated for the turn_off service.
<p class='img'>
<img src='{{site_root}}/images/isy994/isy994_SwitchActionsExample.png' />
<img src='/images/isy994/isy994_SwitchActionsExample.png' />
</p>
The example program above shows how to control a legacy X10 device from Home Assistant using an ISY controller.

4
source/_integrations/lifx.markdown
View File

@ -32,11 +32,11 @@ Change the light to a new state.
| `zones` | List of integers for the zone numbers to affect (each LIFX Z strip has 8 zones, starting at 0).
| `infrared` | Automatic infrared level (0..255) when light brightness is low (for compatible bulbs).
| `power` | Turn the light on (`True`) or off (`False`). Leave out to keep the power as it is.
| `...` | Use `color_name`, `brightness` etc. from [`light.turn_on`]({{site_root}}/integrations/light/#service-lightturn_on) to specify the new state.
| `...` | Use `color_name`, `brightness` etc. from [`light.turn_on`](/integrations/light/#service-lightturn_on) to specify the new state.
## Light effects
The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`]({{site_root}}/integrations/light/#service-lightturn_on) service, for example like this:
The LIFX platform supports several light effects. You can start these effects with default options by using the `effect` attribute of the normal [`light.turn_on`](/integrations/light/#service-lightturn_on) service, for example like this:
```yaml
automation:
- alias: ...

2
source/_integrations/light.markdown
View File

@ -18,7 +18,7 @@ The `.default` suffix should be added to the entity identifier of each light to
### Service `light.turn_on`
Turns one light on or multiple lights on using [groups]({{site_root}}/integrations/group/).
Turns one light on or multiple lights on using [groups](/integrations/group/).
Most lights do not support all attributes. You can check the integration documentation of your particular light for hints, but in general, you will have to try things out and see what works.

2
source/_integrations/limitlessled.markdown
View File

@ -116,7 +116,7 @@ automation:
### Properties
Refer to the [light]({{site_root}}/integrations/light/) documentation for general property usage, but keep in mind the following notes specific to LimitlessLED.
Refer to the [light](/integrations/light/) documentation for general property usage, but keep in mind the following notes specific to LimitlessLED.
- **RGBWW** (Only supported on v6 bridges)
- *Color*: There are 25,856 color possibilities along the LimitlessLED color spectrum. For colors, hue and saturation can be used, but not lightness. If you select a color with lightness, Home Assistant will calculate the nearest valid LimitlessLED color. In white mode, the temperature can be set.

2
source/_integrations/locative.md
View File

@ -18,7 +18,7 @@ Install on your smartphone:
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
<p class='img'>
<img src='{{site_root}}/images/screenshots/locative.png'/>
<img src='/images/screenshots/locative.png'/>
</p>
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".

2
source/_integrations/mpchc.markdown
View File

@ -13,7 +13,7 @@ The `mpchc` platform allows you to connect a [Media Player Classic Home Cinema](
For this integration to function, you will need to enable the Web Interface in the MPC-HC options dialog.
<p class='img'>
<img src='{{site_root}}/images/screenshots/mpc-hc.png' />
<img src='/images/screenshots/mpc-hc.png' />
</p>
If the server running Home Assistant is not the same device that is running MPC-HC, you will need to ensure that the *allow access from localhost only* option is not set.

2
source/_integrations/mystrom.markdown
View File

@ -160,7 +160,7 @@ The `mystrom` switch platform allows you to control the state of your [myStrom](
Make sure that you have enabled the REST API under **Advanced** in the web frontend of the switch.
<p class='img'>
<img src='{{site_root}}/images/integrations/mystrom/switch-advanced.png' />
<img src='/images/integrations/mystrom/switch-advanced.png' />
</p>
To use your myStrom switch in your installation, add the following to your `configuration.yaml` file:

2
source/_integrations/nest.markdown
View File

@ -272,7 +272,7 @@ Please note due to limitations with the European Nest Thermostat E, integration
</div>
<p class='img'>
<img src='{{site_root}}/images/screenshots/nest-thermostat-card.png' />
<img src='/images/screenshots/nest-thermostat-card.png' />
</p>
## Sensor

2
source/_integrations/netdata.markdown
View File

@ -17,7 +17,7 @@ The `netdata` sensor platform allows you to display information collected by [Ne
Getting the details to configure the sensors is a bit tricky as Netdata uses different name for the `element:` value that is required. To get the value for the `data_group:` use Netdata's web interface. `1.` marks the name for the `data_group:`. `2.` are the names for the element to show in Home Assistant. The name that is shown can be different than the name under which the metrics are available.
<p class='img'>
<img src='{{site_root}}/images/integrations/netdata/details.png' />
<img src='/images/integrations/netdata/details.png' />
</p>
To check if the `element:` name matches the name in the Netdata frontend, use `curl` with the IP address of your Netdata instance, its port and the `data_group`:

2
source/_integrations/nmbs.markdown
View File

@ -59,6 +59,6 @@ show_on_map:
{% endconfiguration %}
<p class='img'>
<img src='{{site_root}}/images/screenshots/nmbs-card-example.png' />
<img src='/images/screenshots/nmbs-card-example.png' />
<p>Example using the <a href="https://github.com/custom-cards/entity-attributes-card">Lovelace Attributes custom card</a> </p>
</p>

4
source/_integrations/nsw_rural_fire_service_feed.markdown
View File

@ -13,13 +13,13 @@ ha_domain: nsw_rural_fire_service_feed
The `nsw_rural_fire_service_feed` platform lets you integrate a GeoJSON feed provided by the [NSW Rural Fire Service](https://www.rfs.nsw.gov.au/fire-information/fires-near-me) with information about bush fires, grass fires, hazard reductions and more. It retrieves incidents from a feed and shows information of those incidents filtered by distance to Home Assistant's location.
<p class='img'>
<img src='{{site_root}}/images/screenshots/nsw-rural-fire-service-feed-entities.png' />
<img src='/images/screenshots/nsw-rural-fire-service-feed-entities.png' />
</p>
Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity.
<p class='img'>
<img src='{{site_root}}/images/screenshots/nsw-rural-fire-service-feed-map.png' />
<img src='/images/screenshots/nsw-rural-fire-service-feed-map.png' />
</p>
The entity's information can be used for example if a bush fire that produces smoke or embers is reported close to your home, and you want to automatically close windows, turn on a sprinkler system or simply send yourself a reminder to clean the gutters from dry leaves.

2
source/_integrations/opengarage.markdown
View File

@ -76,7 +76,7 @@ covers:
**Example with more detail:**
<p class='img'>
<img src='{{site_root}}/images/integrations/opengarage/cover_opengarage_details.jpg' />
<img src='/images/integrations/opengarage/cover_opengarage_details.jpg' />
</p>
{% raw %}

2
source/_integrations/pyload.markdown
View File

@ -52,5 +52,5 @@ ssl:
If everything is setup correctly, the download speed will show up in the frontend.
<p class='img'>
<img src='{{site_root}}/images/integrations/pyload/pyload_speed.png' />
<img src='/images/integrations/pyload/pyload_speed.png' />
</p>

2
source/_integrations/qld_bushfire.markdown
View File

@ -23,7 +23,7 @@ on the default map automatically, or on a map card by defining the source
of each entity.
<p class='img'>
<img src='{{site_root}}/images/screenshots/qld-bushfire-feed-map.png' />
<img src='/images/screenshots/qld-bushfire-feed-map.png' />
</p>
The data is updated every 5 minutes.

2
source/_integrations/sabnzbd.markdown
View File

@ -14,7 +14,7 @@ The `sabnzbd` integration will allow you to monitor and control your downloads w
If SABnzbd is discovered on your network, you can enter your API Key in the Configurator. Press "CONFIGURE" to do it.
<p class='img'>
<img src='{{site_root}}/images/screenshots/sabnzbd-configure.png' />
<img src='/images/screenshots/sabnzbd-configure.png' />
</p>
This will create services for interacting with SABnzbd in scripts and automations, but no sensors will be created.

2
source/_integrations/seven_segments.markdown
View File

@ -130,7 +130,7 @@ image_processing:
```
<p class='img'>
<img src='{{site_root}}/images/screenshots/ssocr.png' />
<img src='/images/screenshots/ssocr.png' />
</p>
With the help of a [template sensor](/integrations/template), the value can be shown as badge.

2
source/_integrations/statistics.markdown
View File

@ -62,5 +62,5 @@ precision:
{% endconfiguration %}
<p class='img'>
<img src='{{site_root}}/images/screenshots/stats-sensor.png' />
<img src='/images/screenshots/stats-sensor.png' />
</p>

2
source/_integrations/supervisord.markdown
View File

@ -20,7 +20,7 @@ port=127.0.0.1:9001
After a restart of `supervisord` you should be able to access the web interface. If needed then this could be added as an [iFrame panel](/integrations/panel_iframe/).
<p class='img'>
<img src='{{site_root}}/images/screenshots/supervisor.png' />
<img src='/images/screenshots/supervisor.png' />
</p>
To use this sensor in your installation, add the following to your `configuration.yaml` file:

2
source/_integrations/tellduslive.markdown
View File

@ -19,7 +19,7 @@ ha_domain: tellduslive
The `tellduslive` integration let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick Net or Tellstick ZNet connected gear at home.
Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery]({{site_root}}/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery](/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
## Configuration

2
source/_integrations/time_date.markdown
View File

@ -32,5 +32,5 @@ sensor:
- **display_options** array (*Required*): The option to display. The types *date_time*, *date_time_utc*, *time_date*, and *date_time_iso* shows the date and the time. The other types just the time or the date. *beat* shows the [Swatch Internet Time](https://www.swatch.com/en_us/internet-time).
<p class='img'>
<img src='{{site_root}}/images/screenshots/time_date.png' />
<img src='/images/screenshots/time_date.png' />
</p>

2
source/_integrations/trafikverket_weatherstation.markdown
View File

@ -91,7 +91,7 @@ Please click [here](https://api.trafikinfo.trafikverket.se/) and register to obt
Click [here](https://www.trafikverket.se/trafikinformation/vag/?TrafficType=personalTraffic&map=1/606442.17/6886316.22/&Layers=RoadWeather%2b) to get a map of valid weather stations. Once a station is found, copy the name according to the below picture and paste it in your `configuration.yaml` file as the `station` variable.
<p class='img'>
<img src='{{site_root}}/images/screenshots/get_trafikverket_weather_station_example.png' />
<img src='/images/screenshots/get_trafikverket_weather_station_example.png' />
</p>
## Examples

4
source/_integrations/transmission.markdown
View File

@ -21,13 +21,13 @@ The `transmission` integration allows you to monitor your downloads with [Transm
To use the monitoring, your transmission client needs to allow remote access. If you are running the graphical transmission client (transmission-gtk) go to **Edit** -> **Preferences** and choose the tab **Remote**. Check **Allow remote access**, enter your username and your password, and uncheck the network restriction as needed.
<p class='img'>
<img src='{{site_root}}/images/integrations/transmission/transmission_perf.png' />
<img src='/images/integrations/transmission/transmission_perf.png' />
</p>
If everything is set up correctly, the details will show up in the frontend.
<p class='img'>
<img src='{{site_root}}/images/integrations/transmission/transmission.png' />
<img src='/images/integrations/transmission/transmission.png' />
</p>
## Configuration

4
source/_integrations/usgs_earthquakes_feed.markdown
View File

@ -13,13 +13,13 @@ ha_domain: usgs_earthquakes_feed
The `usgs_earthquakes_feed` platform lets you integrate a GeoJSON feed provided by the [U.S. Geological Survey](https://earthquake.usgs.gov/) with information about seismic events like earthquakes. It retrieves incidents from a feed and shows information of those incidents filtered by distance to Home Assistant's location.
<p class='img'>
<img src='{{site_root}}/images/screenshots/usgs-earthquake-hazards-program-feed-entities.png' />
<img src='/images/screenshots/usgs-earthquake-hazards-program-feed-entities.png' />
</p>
Entities are generated, updated and removed automatically with each update from the feed. Each entity defines latitude and longitude and will be shown on the map automatically. The distance in kilometers is available as the state of each entity.
<p class='img'>
<img src='{{site_root}}/images/screenshots/usgs-earthquake-hazards-program-feed-map.png' />
<img src='/images/screenshots/usgs-earthquake-hazards-program-feed-map.png' />
</p>
The data is updated every 5 minutes.

2
source/_integrations/watson_tts.markdown
View File

@ -32,7 +32,7 @@ tts:
You can get these tokens after you generated the credentials on the IBM Cloud console:
<p class='img'>
<img src='{{site_root}}/images/screenshots/watson_tts_screen.png' />
<img src='/images/screenshots/watson_tts_screen.png' />
</p>
{% configuration %}

2
source/_integrations/wsdot.markdown
View File

@ -87,5 +87,5 @@ WSDOT does provide information about ferry schedules, mountain passes, tolls, et
Here's an example of the sensor in use:
<p class='img'>
<img src='{{site_root}}/images/screenshots/wsdot_sensor.png' />
<img src='/images/screenshots/wsdot_sensor.png' />
</p>

8
source/_posts/2014-12-26-home-control-home-automation-and-the-smart-home.markdown
View File

@ -18,9 +18,9 @@ There is no widely adopted open standard for smart device communication. This pr
As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers **home control**.
<p class='img'>
<a href='{{site_root}}/images/screenshots/nexus_7_dashboard.png'>
<a href='/images/screenshots/nexus_7_dashboard.png'>
<img alt='Hub dashboard example'
src='{{site_root}}/images/screenshots/nexus_7_dashboard.png' />
src='/images/screenshots/nexus_7_dashboard.png' />
</a>
Example of a hub's dashboard. Showing the state of 2 persons, 4 lights and the sun.
</p>
@ -38,9 +38,9 @@ A glimpse today at how the future can look is the [Nest thermostat](https://nest
All this results in the following overview of Home Automation.
<p class='img'>
<a href='{{site_root}}/images/architecture/home_automation_landscape.png'>
<a href='/images/architecture/home_automation_landscape.png'>
<img alt='Home Automation landscape'
src='{{site_root}}/images/architecture/home_automation_landscape.png' />
src='/images/architecture/home_automation_landscape.png' />
</a>
Overview of the home automation landscape.
</p>

2
source/_posts/2015-01-04-hey-pushbullet-nice-talking-to-you.markdown
View File

@ -13,7 +13,7 @@ One of the things that was missing in Home Assistant for a while was a way to co
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome [PushBullet](https://www.pushbullet.com/) but any other messaging platform can be easily added.
<p class='img'>
<img src='{{site_root}}/images/screenshots/pushbullet_moto360.png' />
<img src='/images/screenshots/pushbullet_moto360.png' />
A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
</p>

2
source/_posts/2015-01-11-bootstrapping-your-setup-with-discovery.markdown
View File

@ -20,4 +20,4 @@ To enable the discovery component, add the following to your `home-assistant.con
[discovery]
```
A new [discovery section]({{site_root}}/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.
A new [discovery section](/developers/add_new_platform/#discovery) has been added to the Adding a new platform page with instructions how to make your platform discoverable.

2
source/_posts/2015-01-13-nest-in-da-house.markdown
View File

@ -11,7 +11,7 @@ categories: Release-Notes
For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we're expanding the supported devices. Today, we're proud to introduce Nest Thermostat integration for Home Assistant contributed by [Stefano Fiorini](https://github.com/sfiorini)!
<p class='img'>
<img src='{{site_root}}/images/screenshots/nest-thermostat-card.png' />
<img src='/images/screenshots/nest-thermostat-card.png' />
</p>
The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package [python-nest by jkoelker](https://github.com/jkoelker/python-nest) to talk to the Nest.

4
source/_posts/2015-02-07-looking-at-the-past.markdown
View File

@ -20,8 +20,8 @@ Adding history to the UI was a challenge on itself because the old UI did not su
The history component will be enabled for new users by default. For current users, run `scripts/update` to upgrade to the latest version and add `[history]` to your `home-assistant.conf` file.
<p class='img'>
<a href='{{site_root}}/images/screenshots/component_history_24h.png'>
<img src='{{site_root}}/images/screenshots/component_history_24h.png' />
<a href='/images/screenshots/component_history_24h.png'>
<img src='/images/screenshots/component_history_24h.png' />
</a>
</p>

2
source/_posts/2015-03-08-new-logo.markdown
View File

@ -13,6 +13,6 @@ It is well known that you are either a good programmer or a good designer. It's
The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).
<p class='img'>
<img src='{{site_root}}/images/blog/ha-logo-history.png' />
<img src='/images/blog/ha-logo-history.png' />
The old logo, the new detailed logo and the new simple logo.
</p>

4
source/_posts/2016-08-27-notifications-hue-fake-unification.markdown
View File

@ -59,7 +59,7 @@ We have some excellent upgrades to the notification system coming to you in 0.27
This release adds support for [HTML5] push notifications on Chrome/Firefox/Opera on both desktop and Android devices. This means that you can send a notification to your phone even when your Home Assistant is not open in your mobile browser. When using Chrome you can even include 2 action buttons so that you can control your Home Assistant from your phone's lock screen, allowing you to do things like sound alarms or unlock your front door, all without leaving the notification. Thanks again to me ([@robbiet480]) and Paulus ([@balloob]) for all the hard work on this!
<p class='img'>
<img src='{{site_root}}/images/screenshots/html5-notify.png' />
<img src='/images/screenshots/html5-notify.png' />
</p>
#### Notification Groups
@ -83,7 +83,7 @@ hass --script check_config
This release includes a big push on making sure all platforms contain proper configuration validation. This should help in getting your configuration right. Thanks to [@fabaff], [@pavoni], [@pvizeli], [@nkgilley] for all the hard work on this, you all rock!
<p class='img'>
<img src='{{site_root}}/images/screenshots/config-validation.png' />
<img src='/images/screenshots/config-validation.png' />
</p>
### FFMpeg motion/noise sensing

2
source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
View File

@ -15,7 +15,7 @@ It's already time for 0.28 thanks to our super short release cycles. Now, it' of
This release brings you a huge improvement of the [automation] and [group] handling. Both can be reloaded without a Home Assistant restart by calling their new reload services. The automations can be controlled directly from the frontend.
<p class='img'>
<img src='{{site_root}}/images/screenshots/automation-switches.png' />
<img src='/images/screenshots/automation-switches.png' />
</p>
### Raspberry Pi installation guide

4
source/_posts/2016-10-08-hassbian-rest-digital-ocean.markdown
View File

@ -21,7 +21,7 @@ To reduce the run-time of your tests, [@balloob] did a lot of tweaking. For now
All configuration sample entries are now minimized. This should help to avoid problem for starters and newbies as they only get what's needed and not a full sample with all optional entries. If there is an issue with an entry in your `configuration.yaml` file the error message will provide you an URL that point to the documentation.
<p class='img'>
<img src='{{site_root}}/images/screenshots/config-validation-url.png' />
<img src='/images/screenshots/config-validation-url.png' />
</p>
As soon as the [Hacktoberfest] started there were a lot of incoming Pull Requests for the documentation. A huge "Thank you" to all participants. Especially, we would like to give a cookie to [@hillaryfraley]. She created around a dozen Pull Requests so far and didn't only fix typos but complete sections. The [Hacktoberfest] is still on-going and we are looking forward to get more Pull Requests.
@ -31,7 +31,7 @@ As soon as the [Hacktoberfest] started there were a lot of incoming Pull Request
With the [statistics sensor][stats-sensor] we would like to introduce a new sensor that is similar to the [template sensor][template-sensor] or the [trend sensor][trend-sensor]. This sensor is consuming values from another sensor and is doing some statistical analysis of the data. Over a group of samples is the average/mean, the min/max, the total, the standard deviation, and the variance calculated which can be used in your automation rules. If the source is a binary sensor then the state changes are counted.
<p class='img'>
<img src='{{site_root}}/images/screenshots/stats-sensor.png' />
<img src='/images/screenshots/stats-sensor.png' />
</p>
As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest [notebook] for doing statistics with your Home Assistant database.

6
source/_posts/2017-05-20-automation-editor-zwave-panel-ocr.markdown
View File

@ -16,7 +16,7 @@ Welcome to another great release of Home Assistant! While some of contributors a
First thing for this release is a feature that has been requested a lot: an automation editor! It's still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you're all good to go. Otherwise check [these instructions](/docs/automation/editor/) to get your automations ready for editing in the UI.
<p class='img'>
<img src='{{site_root}}/images/blog/2017-05-0.45/trigger.png' />
<img src='/images/blog/2017-05-0.45/trigger.png' />
</p>
Check this [video](https://youtu.be/0j_hWdCTip4) by [Ben](https://twitter.com/BRUHautomation) from [BRUHautomation](http://www.bruhautomation.com/) to see the new release in action.
@ -30,7 +30,7 @@ As the editor is experimental, there are some limitations. These include that Ch
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to [@turbokongen]! You will now be able to change config parameters and manage your devices.
<p class='img'>
<img src='{{site_root}}/images/blog/2017-05-0.45/zwave.png' />
<img src='/images/blog/2017-05-0.45/zwave.png' />
</p>
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
@ -45,7 +45,7 @@ Next to that [@armills] has lead the charge and managed to get full test coverag
This release also contains two integrations which could help you to make non-smart devices a little smarter. The [`file` sensor][sensor.file docs] and the [`seven_segments` OCR image processing platform][image_processing.seven_segments docs]. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
<p class='img'>
<img src='{{site_root}}/images/blog/2017-05-0.45/power-meter.png' />
<img src='/images/blog/2017-05-0.45/power-meter.png' />
</p>
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!