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-27 19:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

🔨 Fix broken links (part 4) (#10018)

Browse Source
This commit is contained in:
Klaas Schoute 2019-07-31 15:44:21 +02:00 committed by Franck Nijhof
parent a5533dd669
commit 3fb1e31392
28 changed files with 47 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_components/aquostv.markdown
View File

@ -75,4 +75,4 @@ Currently known supported models:
- LC-60EQ10U
- LC-60SQ15U
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/tree/current/source/_components/media_player.aquostv.markdown).
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/aquostv.markdown).

2
source/_components/binary_sensor.rfxtrx.markdown
View File

@ -90,7 +90,7 @@ automatic_add:
<div class='note warning'>
This integration and the [rfxtrx switch](/components/switch/rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`.
This integration and the [rfxtrx switch](/components/switch.rfxtrx/) can steal each other's devices when setting the `automatic_add` configuration parameter to `true`.
Set `automatic_add` only when you have some devices to add to your installation, otherwise leave it to `false`.
</div>

2
source/_components/kodi.markdown
View File

@ -299,8 +299,6 @@ script:
method: VideoLibrary.Scan
```
For a more complex usage of the `kodi_call_method` service, with event triggering of Kodi API results, you can have a look at this [example](/cookbook/automation_kodi_dynamic_input_select/)
## Notifications
The `kodi` notifications platform allows you to send messages to your [Kodi](https://kodi.tv/) multimedia system from Home Assistant.

7
source/_components/mystrom.markdown
View File

@ -18,9 +18,12 @@ The `mystrom` light platform allows you to control your [myStrom](https://mystro
There is currently support for the following device types within Home Assistant:
- [Binary Sensor](#binary-sensor)
- [Light](#light)
- [Binary Sensor](#binary-sensor)
- [Setup of myStrom Buttons](#setup-of-mystrom-buttons)
- [Switch](#switch)
- [Setup](#setup)
- [Get the current power consumption](#get-the-current-power-consumption)
## Light
@ -159,7 +162,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/components/mystrom/mystrom-advanced.png' />
<img src='{{site_root}}/images/components/mystrom/switch-advanced.png' />
</p>
To use your myStrom switch in your installation, add the following to your `configuration.yaml` file:

2
source/_components/openhome.markdown
View File

@ -11,7 +11,7 @@ redirect_from:
---
The `openhome` platform allows you to connect an [Openhome Compliant Renderer](https://www.openhome.org) to Home Assistant such as a [Linn Products Ltd](https://www.linn.co.uk) HiFi streamer. It will allow you to control media playback, volume, source and see the current playing item. Openhome devices should be discovered by using the [the discovery component](/components/discovery/), their device names are taken from the name of the room configured on the device.
The `openhome` platform allows you to connect an [Openhome Compliant Renderer](http://openhome.org/) to Home Assistant such as a [Linn Products Ltd](https://www.linn.co.uk) HiFi streamer. It will allow you to control media playback, volume, source and see the current playing item. Openhome devices should be discovered by using the [the discovery component](/components/discovery/), their device names are taken from the name of the room configured on the device.
```yaml
# Example configuration.yaml entry

2
source/_components/panasonic_bluray.markdown
View File

@ -21,7 +21,7 @@ Currently known supported models:
- DMP-BDT500
- DMP-BBT01
If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/current/source/_components/media_player.panasonic_bluray.markdown).
If your model is not on the list, then give it a try, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/panasonic_bluray.markdown).
Example configuration:

2
source/_components/panasonic_viera.markdown
View File

@ -29,7 +29,7 @@ Currently known supported models:
- TX-42AS650
- TX55ASW654
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/media_player.panasonic_viera.markdown).
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_components/panasonic_viera.markdown).
Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`.

15
source/_components/tellstick.markdown
View File

@ -17,13 +17,16 @@ redirect_from:
- /components/switch.tellstick/
---
The `tellstick` integration integrates [TellStick](https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/) devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 MHz. There are a number of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) who are selling products that work with TellStick. For more details, please check the TellStick [protocol list](http://developer.telldus.com/wiki/TellStick_conf).
The `tellstick` integration integrates [TellStick][tellstick-gateway] devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 MHz. There are a number of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) who are selling products that work with TellStick. For more details, please check the TellStick [protocol list](http://developer.telldus.com/wiki/TellStick_conf).
There is currently support for the following device types within Home Assistant:
- [Configuration](#configuration)
- [Cover](#cover)
- [Light](#light)
- [Sensor](#sensor)
- [Examples](#examples)
- [Full configuration](#full-configuration)
- [Switch](#switch)
## Configuration
@ -62,7 +65,7 @@ port:
## Cover
This `tellstick` cover platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) covers.
This `tellstick` cover platform allows you to control your [TellStick][tellstick-gateway] covers.
To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file:
@ -74,7 +77,7 @@ cover:
## Light
This `tellstick` light platform allows you to control your [TellStick](http://www.telldus.se/products/tellstick) dimmers.
This `tellstick` light platform allows you to control your [TellStick][tellstick-gateway] dimmers.
To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file:
@ -86,7 +89,7 @@ light:
## Sensor
The `tellstick` sensor platform allows you to get current meteorological data from a [TellStick](http://www.telldus.se/products/tellstick) device.
The `tellstick` sensor platform allows you to get current meteorological data from a [TellStick][tellstick-gateway] device.
To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file:
@ -148,7 +151,7 @@ sensor:
## Switch
This `tellstick` switch platform allows you to control [TellStick](http://www.telldus.se/products/tellstick) devices.
This `tellstick` switch platform allows you to control [TellStick][tellstick-gateway] devices.
To use your TellStick device, you first have to set up your [Tellstick hub](#configuration) and then add the following to your `configuration.yaml` file:
@ -157,3 +160,5 @@ To use your TellStick device, you first have to set up your [Tellstick hub](#con
switch:
- platform: tellstick
```
[tellstick-gateway]: https://telldus.com/produkt/z-wave-gateway-tellstick-znet-lite-ver-2/

2
source/_docs/ecosystem/hass-configurator.markdown
View File

@ -108,7 +108,7 @@ Since the configurator script on its own is no service, you will have to take so
`nohup sudo ./configurator.py &`
2. If your system is using systemd (that's usually what you'll find on a Raspberry Pi), there's a [template file](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.systemd) you can use and then apply the same process to integrate it as mentioned in the [Home Assistant documentation](/docs/autostart/systemd/). If you use this method you have to set the `BASEPATH` variable according to your environment.
3. If you have [supervisor](http://supervisord.org/) running on your system, [hass-poc-configurator.supervisor](https://github.com/danielperna84/hass-configurator/blob/master/hass-configurator.supervisor) would be an example configuration you could use to control the configurator.
4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](/docs/hassbian/).
4. A tool called [tmux](https://tmux.github.io/), which should be pre-installed with [HASSbian](/docs/installation/hassbian/).
5. A tool called [screen](http://ss64.com/bash/screen.html) (alternative to tmux). If it's not already installed on your system, you can do `sudo apt-get install screen` or `sudo yum install screen` to get it. When it's installed, start a screen session by executing `screen`. Then navigate to your Home Assistant directory and start the configurator like described above. Put the screen session into the background by pressing `CTRL+A` and then `CTRL+D`. It is now safe to disconnect from your SSH session.
To resume the screen session, log in to your machine and execute `screen -r`.

3
source/_posts/2016-02-13-speedtest-bloomsky-splunk-and-garage-doors.markdown
View File

@ -22,7 +22,7 @@ Not only did we gain a lot of test coverage, we also attracted a lot of new deve
- Core: Add service to restart Home Assistant ([@rmkraus])
- Core: Allow device to report as unavailable ([@MartinHjelmare])
- Core: Allow overriding polling interval in platforms and [via config][polling-config] ([@balloob])
- Core: Allow overriding polling interval in platforms and via config ([@balloob])
- Frontend: support for a [default view] have been added to replace the show all view ([@balloob])
- Component: Added [apcupsd] component ([@flyte])
- Component: Added component to log values to [Splunk] ([@miniconfig])
@ -82,7 +82,6 @@ Not only did we gain a lot of test coverage, we also attracted a lot of new deve
[@Danielhiversen]: https://github.com/Danielhiversen/
[@roqeer]: https://github.com/roqeer/
[@jaharkes]: https://github.com/jaharkes/
[polling-config]: /cookbook/customize_polling_interval/
[default view]: /components/group/
[apcupsd]: /components/apcupsd/
[Splunk]: /components/splunk/

2
source/_posts/2016-03-12-z-wave-pep257-templated-service-calls.markdown
View File

@ -49,7 +49,7 @@ automation:
`media_content_type` and `media_content_id`, to match the corresponding media
player state attributes. This change affects automations, scripts and scenes.
[services]: /topics/service_calls/#use-templates-to-decide-which-service-to-call
[services]: /docs/scripts/service-calls/#use-templates-to-decide-which-service-to-call
[Hunter Douglas Powerview]: /components/scene.hunterdouglas_powerview/
[MQTT]: /components/lock.mqtt/
[OwnTracks]: /components/device_tracker.owntracks/

2
source/_posts/2016-06-18-pandora-bt-home-hub-5-and-local-file-camera.markdown
View File

@ -88,5 +88,5 @@ netatmo:
[Swagger.yaml format]: https://github.com/home-assistant/home-assistant/blob/dev/docs/swagger.yaml
[All-in-One installer]: /getting-started/installation-raspberry-pi-all-in-one/
[standalone Raspberry Pi installation guide]: /getting-started/installation-raspberry-pi/
[Voltage sensor]: /components/sensor.bloomsky/
[Voltage sensor]: /components/bloomsky/#sensor
[SNMP]: /components/sensor.snmp/

7
source/_posts/2016-10-22-flash-briefing-updater-hacktoberfest.markdown
View File

@ -183,7 +183,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
- Notify: [Matrix] support added ([@mweinelt])
- Device tracker - nmap: Allow specifying multiple inputs for [nmap] ([@hcooper])
- Device Tracker - snmp: SNMPv3 now supported ([@T3m3z])
- Notify: [Telstra] SMS now supported ([@nvella])
- Notify: Telstra SMS now supported ([@nvella])
- Camera: [Verisure] now supported ([@turbokongen])
- Support added for [Neato] Connected Robot ([@jabesq])
- Media player: More options for [Yamaha] AVR ([@ehagan])
@ -268,19 +268,18 @@ Thanks for reading all of the above, especially since this week was a pretty lon
[Concord232]: /components/alarm_control_panel.concord232/
[HTTP]: /components/http/
[HaveIBeenPwned]: /components/sensor.haveibeenpwned/
[Matrix]: //components/notify.matrix/
[Matrix]: /components/matrix/#notifications
[Neato]: /components/switch.neato/
[Pilight]: /components/sensor.pilight/
[Proximity]: /components/proximity/
[PyPi]: https://pypi.python.org/pypi
[Synology]: /components/camera.synology/
[Telstra]: /components/notify.telstra/
[UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier
[Verisure]: /components/camera.verisure/
[WUnderground]: /components/sensor.wunderground/
[Yamaha]: /components/media_player.yamaha/
[Zoneminder]: /components/zoneminder/
[emoncms]: //components/emoncms_history/
[emoncms]: /components/emoncms_history/
[filtering]: /components/logbook/
[flash-briefing-docs]: /components/alexa/
[hacktoberfest-blog]: /blog/2016/10/02/hacktoberfest/

10
source/_posts/2017-04-24-hardware-contest-2017.markdown
View File

@ -11,10 +11,10 @@ og_image: /images/default-social.png
We have four submissions for our [Hardware Contest 2017][hardware].
- [Part of IoT-course](https://community.home-assistant.io/t/entry-for-hardware-contest-part-of-iot-course/14827)
- [Automating a nursing home!](https://community.home-assistant.io/t/entry-automating-a-nursing-home/14872)
- [Dedicated hardware for coding, testing, building, and contributing to Home Assistant](https://community.home-assistant.io/t/entry-dedicated-hardware-for-coding-testing-building-and-contributing-to-home-assistant/15515)
- [HassIO - Home Assistant hub for dummies](https://community.home-assistant.io/t/entry-hassio-home-assistant-hub-for-dummies/16037)
- Part of IoT-course
- Automating a nursing home!
- Dedicated hardware for coding, testing, building, and contributing to Home Assistant
- HassIO - Home Assistant hub for dummies
The voting is now open. To keep things simple are we using the voting feature of the [forum]. Vote for your choices.
@ -22,6 +22,6 @@ End of the voting period: April, 30 2017 - 23.59 UTC
[hardware]: /blog/2017/04/01/thomas-krenn-award/
[award]: https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/
[forum]: https://community.home-assistant.io/c/contest-2017
[forum]: https://community.home-assistant.io/t/hardware-contest-2017/42546
[twitter]: https://twitter.com/home_assistant

2
source/_posts/2017-05-01-home-assistant-on-raspberry-pi-zero-in-30-minutes.markdown
View File

@ -71,5 +71,5 @@ Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspber
To try it out, go to [http://hassbian:8123](http://hassbian:8123) or [http://hassbian.local:8123](http://hassbian.local:8123) if you're using Mac.
For further details about HASSbian, take a look at the [documentation](/docs/hassbian/).
For further details about HASSbian, take a look at the [documentation](/docs/installation/hassbian/).

2
source/_posts/2017-05-06-zigbee-opencv-dlib.markdown
View File

@ -459,7 +459,7 @@ influxdb:
[notify.html5 docs]: /components/notify.html5/
[notify.joaoapps_join docs]: /components/notify.joaoapps_join/
[notify.mailgun docs]: /components/notify.mailgun/
[notify.matrix docs]: /components/notify.matrix/
[notify.matrix docs]: /components/matrix/#notifications
[notify.smtp docs]: /components/notify.smtp/
[notify.telegram docs]: /components/notify.telegram/
[notify.webostv docs]: /components/notify.webostv/

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

@ -421,7 +421,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[vera docs]: /components/vera/
[websocket_api docs]: /components/websocket_api/
[zwave docs]: /components/zwave/
[zwave.api docs]: /components/zwave.api/
[zwave.api docs]: /components/zwave/
[forum]: https://community.home-assistant.io/
[issue]: https://github.com/home-assistant/home-assistant/issues
[#7673]: https://github.com/home-assistant/home-assistant/pull/7673
@ -433,5 +433,5 @@ Experiencing issues introduced by this release? Please report them in our [issue
[device_tracker.ubus docs]: /components/device_tracker.ubus/
[hassio docs]: /components/hassio/
[media_player.volumio docs]: /components/media_player.volumio/
[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/
[telegram_bot.__init__ docs]: /components/telegram_bot/
[discord]: https://discord.gg/c5DvZ4e

2
source/_posts/2017-06-04-release-46.markdown
View File

@ -372,7 +372,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[switch.broadlink docs]: /components/switch.broadlink/
[switch.rachio docs]: /components/switch.rachio/
[switch.rflink docs]: /components/switch.rflink/
[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/
[telegram_bot.__init__ docs]: /components/telegram_bot/
[telegram_bot.polling docs]: /components/telegram_bot.polling/
[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/
[tellduslive docs]: /components/tellduslive/

2
source/_posts/2017-06-17-release-47.markdown
View File

@ -549,7 +549,7 @@ automation:
[switch.raspihats docs]: /components/switch.raspihats/
[switch.rest docs]: /components/switch.rest/
[switch.template docs]: /components/switch.template/
[telegram_bot.__init__ docs]: /components/telegram_bot.__init__/
[telegram_bot.__init__ docs]: /components/telegram_bot/
[telegram_bot.polling docs]: /components/telegram_bot.polling/
[telegram_bot.webhooks docs]: /components/telegram_bot.webhooks/
[updater docs]: /components/updater/

2
source/_posts/2017-10-28-demo.markdown
View File

@ -44,7 +44,7 @@ switch:
</p>
## `random` platforms
Till now the frontend is static. Nothing is changing over time. Starting with 0.57 we ship a [`random` binary sensor](https://github.com/home-assistant/home-assistant.github.io/blob/next/source/_components/binary_sensor.random.markdown) platform in addition to the already available [`random` sensor](/components/sensor.random/).
Till now the frontend is static. Nothing is changing over time. Starting with 0.57 we ship a [`random` binary sensor](/components/random/#binary-sensor) platform in addition to the already available [`random` sensor](/components/sensor.random/).
By adding those platform to your `configuration.yaml` file, your demo will become more interactive.

2
source/_posts/2018-02-26-release-64.markdown
View File

@ -549,7 +549,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[scene docs]: /components/scene/
[sensor.airvisual docs]: /components/sensor.airvisual/
[sensor.alpha_vantage docs]: /components/sensor.alpha_vantage/
[sensor.bloomsky docs]: /components/sensor.bloomsky/
[sensor.bloomsky docs]: /components/bloomsky/#sensor
[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
[sensor.buienradar docs]: /components/sensor.buienradar/
[sensor.deconz docs]: /components/sensor.deconz/

2
source/_posts/2018-08-29-release-77.markdown
View File

@ -469,7 +469,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.deconz docs]: /components/sensor.deconz/
[sensor.geizhals docs]: /components/sensor.geizhals/
[sensor.glances docs]: /components/sensor.glances/
[sensor.netatmo_public docs]: /components/sensor.netatmo_public/
[sensor.netatmo_public docs]: /components/netatmo/#sensor
[sensor.noaa_tides docs]: /components/sensor.noaa_tides/
[sensor.openuv docs]: /components/sensor.openuv/
[sensor.scrape docs]: /components/sensor.scrape/

2
source/_posts/2018-10-12-release-80.markdown
View File

@ -693,7 +693,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.miflora docs]: /components/sensor.miflora/
[sensor.mqtt docs]: /components/sensor.mqtt/
[sensor.mqtt_room docs]: /components/sensor.mqtt_room/
[sensor.netatmo_public docs]: /components/sensor.netatmo_public/
[sensor.netatmo_public docs]: /components/netatmo/#sensor
[sensor.openweathermap docs]: /components/sensor.openweathermap/
[sensor.scrape docs]: /components/sensor.scrape/
[sensor.tibber docs]: /components/sensor.tibber/

2
source/_posts/2018-10-29-release-81.markdown
View File

@ -791,7 +791,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[route53 docs]: /components/route53/
[sabnzbd docs]: /components/sabnzbd/
[sensor.api_streams docs]: /components/sensor.api_streams/
[sensor.bloomsky docs]: /components/sensor.bloomsky/
[sensor.bloomsky docs]: /components/bloomsky/#sensor
[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
[sensor.dnsip docs]: /components/sensor.dnsip/
[sensor.dsmr docs]: /components/sensor.dsmr/

2
source/_posts/2019-01-09-release-85.markdown
View File

@ -838,7 +838,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.dublin_bus_transport docs]: /components/sensor.dublin_bus_transport/
[sensor.eliqonline docs]: /components/sensor.eliqonline/
[sensor.entur_public_transport docs]: /components/sensor.entur_public_transport/
[sensor.esphome docs]: /components/sensor.esphome/
[sensor.esphome docs]: /components/esphome/
[sensor.fail2ban docs]: /components/sensor.fail2ban/
[sensor.filter docs]: /components/sensor.filter/
[sensor.flunearyou docs]: /components/sensor.flunearyou/

3
source/_posts/2019-02-06-release-87.markdown
View File

@ -37,7 +37,7 @@ If you prefer a podcast over release notes, check out [the Hass Podcast](https:/
- Utility meter ([@dgomes] - [#19718]) ([utility_meter docs]) (new-platform)
- Add Co2signal sensor ([@danielsjf] - [#19204]) ([sensor.co2signal docs]) (new-platform)
- Add nilu air_quality platform ([@hfurubotten] - [#19674]) ([air_pollutants docs]) (new-platform)
- Add Iliad Italy (Mobile Telephony Provider) Sensor ([@eliseomartelli] - [#19645]) ([sensor.iliad_italy docs]) (new-platform)
- Add Iliad Italy (Mobile Telephony Provider) Sensor ([@eliseomartelli] - [#19645]) (new-platform)
- Add support for HomeKit motion sensor devices ([@Jc2k] - [#20555]) ([homekit_controller docs]) (new-platform)
- Add an Integration sensor ([@dgomes] - [#19703]) ([sensor.integration docs]) (new-platform)
- Add Synology SRM device tracker ([@aerialls] - [#20320]) ([device_tracker docs]) (new-platform)
@ -636,7 +636,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.filter docs]: /components/sensor.filter/
[sensor.fritzbox docs]: /components/sensor.fritzbox/
[sensor.history_stats docs]: /components/sensor.history_stats/
[sensor.iliad_italy docs]: /components/sensor.iliad_italy/
[sensor.imap docs]: /components/sensor.imap/
[sensor.influxdb docs]: /components/sensor.influxdb/
[sensor.integration docs]: /components/sensor.integration/

2
source/help/index.markdown
View File

@ -37,7 +37,7 @@ Have you found an issue in your Home Assistant installation? Please report it. R
- [Home Assistant - Erweiterungen (Platforms/Components)](https://github.com/home-assistant/home-assistant-assets/tree/master/german/2016-puzzle) at [Puzzle ITC](https://www.puzzle.ch/de/) - December 2016
- [Automating Your Life - Home Automation](http://slides.com/teagan42/life_automation#/) at Develop Denver 2016 - August
- [Building Online Communities: Home Assistant](https://medium.com/@gitter/building-online-communities-home-assistant-8818dff671ad#.och4x4rhx) - July 2016
- [Home Assistant Support 101 - Getting around in Home Assistant](https://www.youtube.com/watch?v=dRfk9JAlPJk) ([Slides](https://docs.google.com/presentation/d/1PUnOpeFZxNj4LEjaohGqH_1hOGQGuS5yRHD1ThHr6nk/edit?usp=sharing)) - June 2016
- [Home Assistant Support 101 - Getting around in Home Assistant](https://www.youtube.com/watch?v=dRfk9JAlPJk) (Slides) - June 2016
- [Awaken your home: Python and the Internet of Things](https://www.youtube.com/watch?v=Cfasc9EgbMU&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=1) at PyCon 2016 - June 2016
- [Automating your Home with Home Assistant](https://www.youtube.com/watch?v=4-6rTwKl6ww&list=PLKsVm4cWHDQB9JBcD7_ZfNcvC6xx47QHT&index=2) at OpenIoT 2016 - March 2016

2
source/tos/index.markdown
View File

@ -88,7 +88,7 @@ In no event will Home Assistant, or its suppliers or licensors, be liable with r
## 16. General Representation and Warranty
You represent and warrant that (i) your use of the Website will be in strict accordance with the Home Assistant [Privacy Policy](/privacy), [Community Guidelines](/guidelines), with this Agreement and with all applicable laws and regulations (including without limitation any local laws or regulations in your country, state, city, or other governmental area, regarding online conduct and acceptable content, and including all applicable laws regarding the transmission of technical data exported from the country in which this website resides or the country in which you reside) and (ii) your use of the Website will not infringe or misappropriate the intellectual property rights of any third party.
You represent and warrant that (i) your use of the Website will be in strict accordance with the Home Assistant [Privacy Policy](/privacy), [Community Guidelines](https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371), with this Agreement and with all applicable laws and regulations (including without limitation any local laws or regulations in your country, state, city, or other governmental area, regarding online conduct and acceptable content, and including all applicable laws regarding the transmission of technical data exported from the country in which this website resides or the country in which you reside) and (ii) your use of the Website will not infringe or misappropriate the intellectual property rights of any third party.
## 17. Indemnification