diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown index df767826ac6..488f0d75cf8 100644 --- a/source/_addons/samba.markdown +++ b/source/_addons/samba.markdown @@ -4,7 +4,7 @@ description: "Manage your Home Assistant and custom add-ons over Samba." featured: true --- -This add-on allows you to set up a [Samba](https://samba.org/) server to access Hass.io folders using Windows network shares. +This add-on allows you to set up a [Samba](https://www.samba.org) server to access Hass.io folders using Windows network shares.
diff --git a/source/_components/asuswrt.markdown b/source/_components/asuswrt.markdown index d4886aaac05..09e7cfa2edb 100644 --- a/source/_components/asuswrt.markdown +++ b/source/_components/asuswrt.markdown @@ -85,7 +85,7 @@ sensors:
-You need to [enable telnet](https://www.asus.com/support/faq/1005449/) on your router if you choose to use `protocol: telnet`. +You need to enable telnet on your router if you choose to use `protocol: telnet`.
diff --git a/source/_components/cppm.markdown b/source/_components/cppm_tracker.markdown similarity index 97% rename from source/_components/cppm.markdown rename to source/_components/cppm_tracker.markdown index d30b472ec27..c8d86e219fc 100644 --- a/source/_components/cppm.markdown +++ b/source/_components/cppm_tracker.markdown @@ -6,6 +6,8 @@ ha_category: - Presence Detection ha_release: "0.90" ha_iot_class: Local Polling +redirect_from: + - /components/cppm/ --- This platform allows you to detect presence by looking at connected devices to [Aruba Clearpass](https://www.arubanetworks.com/products/security/network-access-control/). diff --git a/source/_components/gc100.markdown b/source/_components/gc100.markdown index b073fba7e30..11765aaa454 100644 --- a/source/_components/gc100.markdown +++ b/source/_components/gc100.markdown @@ -17,7 +17,8 @@ hardware device which has an array of relays, RS232 serial ports, and flexible p There is currently support for the following device types within Home Assistant: -- [Binary Sensor](binary-sensor) +- [Configuration](#configuration) +- [Binary Sensor](#binary-sensor) - [Switch](#switch) Currently, only relays and ports configured to be digital inputs are supported in Home Assistant. For IR support, please use the [iTach remote platform](/components/remote.itach/), but note that it will likely not function concurrently on the same GC100 due to limitations in the TCP socket server implementation used by Global Caché. diff --git a/source/_components/introduction.markdown b/source/_components/introduction.markdown deleted file mode 100644 index 265de216c48..00000000000 --- a/source/_components/introduction.markdown +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "Introduction" -description: "Details about the introduction within Home Assistant." -logo: home-assistant.png -ha_qa_scale: internal -ha_release: 0.7 ---- - -
-This integration has been removed in Home Assistant 0.92. The UI will now take care of this text. -
- -The introduction integration will show a card in the UI with 'Welcome Home!' and steps on how to get started. It will also print the same message to the console when starting up. - -The introduction integration is loaded by default on a new Home Assistant instance. - -```yaml -# Example configuration.yaml entry -introduction: -``` - -To disable this component, remove the `introduction:` entry from your `configuration.yaml` file. diff --git a/source/_components/luci.markdown b/source/_components/luci.markdown index 531ef336064..4830ee51947 100644 --- a/source/_components/luci.markdown +++ b/source/_components/luci.markdown @@ -9,7 +9,7 @@ redirect_from: - /components/device_tracker.luci/ --- -_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/device_tracker.openwrt/)._ +_This is one of multiple ways we support OpenWRT. For an overview, see [openwrt](/components/openwrt/)._ This is a presence detection scanner for OpenWRT using [luci](http://wiki.openwrt.org/doc/techref/luci). diff --git a/source/_components/mercedesme.markdown b/source/_components/mercedesme.markdown deleted file mode 100644 index 43f57f29790..00000000000 --- a/source/_components/mercedesme.markdown +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: "Mercedes me" -description: "Instructions on how to integrate Mercedes car with Mercedes me into Home Assistant." -logo: mercedesme.png -ha_category: - - Car - - Binary Sensor - - Presence Detection - - Sensor -ha_release: 0.63 -ha_iot_class: Cloud Polling -redirect_from: - - /components/binary_sensor.mercedesme/ - - /components/device_tracker.mercedesme/ - - /components/sensor.mercedesme/ ---- - -The `mercedesme` integration offers integration with the [Mercedes me](https://www.mercedes-benz.com/de/mercedes-me/) cloud service and provides presence detection as well as sensors such as doors, tires, windows, and service interval. - -This integration provides the following platforms: - -- Binary Sensors: Windows, tires, doors and lock. -- Sensors:Fuel status, service interval, remaining km, etc. -- Device tracker: To track location of your car. - -Platforms will be automatically configured if Mercedes me integration is configured. - -
- The integration was removed. The vendor disabled the API endpoint and a new API is not available currently. -
diff --git a/source/_components/qwikswitch.markdown b/source/_components/qwikswitch.markdown index 56b08c28e58..b54ba2605e7 100644 --- a/source/_components/qwikswitch.markdown +++ b/source/_components/qwikswitch.markdown @@ -22,12 +22,12 @@ There is currently support for the following device types within Home Assistant: - Binary Sensor - Light -- Sensor -- Switch +- [Sensor](#qwikswitch-sensors) +- [Switch](#switch) -The `qwikswitch` integration discovers all devices from QS Mobile. Currently, Relays and LED dimmers are discovered in Home Assistant. Relay devices are [lights](/components/light.qwikswitch/) by default, and can be configured as [switches](/components/switch.qwikswitch/). +The `qwikswitch` integration discovers all devices from QS Mobile. Currently, Relays and LED dimmers are discovered in Home Assistant. Relay devices are lights by default, and can be configured as [switches](#switch). -Configuration +## Configuration ```yaml # Example configuration.yaml entry diff --git a/source/_components/recollect_waste.markdown b/source/_components/recollect_waste.markdown index 90b66fdd41d..d409d181630 100644 --- a/source/_components/recollect_waste.markdown +++ b/source/_components/recollect_waste.markdown @@ -10,7 +10,7 @@ redirect_from: - /components/sensor.recollect_waste/ --- -The `Recollect Waste` platform allows you to track the next scheduled waste pickup and what type of waste from [Recollect](https://recollect.net/solutions/waste/). To use this sensor your city's waste company must be Recollect and you will need to find your place_id and service_id. +The `recollect_waste` integration allows you to track the next scheduled waste pickup and what type of waste from [Recollect](https://recollect.net/private-waste-haulers/). To use this sensor your city's waste company must be Recollect and you will need to find your place_id and service_id. 1. In Chrome open developer tools and go to the network tab. 2. Go to your city's Recollect collection calendar. diff --git a/source/_components/tikteck.markdown b/source/_components/tikteck.markdown index 1cb6013bca9..e237c431538 100644 --- a/source/_components/tikteck.markdown +++ b/source/_components/tikteck.markdown @@ -41,7 +41,7 @@ devices: type: string {% endconfiguration %} -The password can be obtained from an Android device using an app like [aLogcat](https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en) or the `adb logcat` command for phones in developer mode. Look for a line like: +The password can be obtained from an Android device using an app like [aLogcat](https://play.google.com/store/apps/details?id=rs.pedjaapps.alogcatroot.app&hl=en) or the `adb logcat` command for phones in developer mode. Look for a line like: ``` E LedoBleSDK: login =skName=======[Smart Light]=======skPw==[password] diff --git a/source/_components/todoist.markdown b/source/_components/todoist.markdown index 4d97b34a28f..f8fc8c8cc50 100644 --- a/source/_components/todoist.markdown +++ b/source/_components/todoist.markdown @@ -91,7 +91,7 @@ As you can see, there are 4 custom projects here: You can mix-and-match these attributes to create all sorts of custom projects. You can even use [IFTTT](https://ifttt.com/todoist) to create a task with a certain label, then have Home Assistant do some kind of automation when a task with that label comes due. -Home Assistant does its best to [determine what task in each project is "most" important](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/calendar/todoist.py#L432), and it's that task which has its state reported. You can access the other tasks you have due soon via the `all_tasks` array (see below). +Home Assistant does its best to [determine what task in each project is "most" important](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/todoist/calendar.py), and it's that task which has its state reported. You can access the other tasks you have due soon via the `all_tasks` array (see below). ### Sensor attributes diff --git a/source/_components/updater.markdown b/source/_components/updater.markdown index 3b5f99d0709..b991e36bc54 100644 --- a/source/_components/updater.markdown +++ b/source/_components/updater.markdown @@ -10,7 +10,7 @@ ha_release: 0.8 The `updater` integration will check daily for new releases. It will show a badge in the frontend if a new version is found. As [Hass.io](/hassio/) has its own schedule for release it doesn't make sense to use this integration on Hass.io. -The updater integration will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/updater.py#L91). +The updater integration will also collect basic information about the running Home Assistant instance and its environment. The information includes the current Home Assistant version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python [source code](https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/updater). ## Configuration diff --git a/source/_components/vlc-telnet.markdown b/source/_components/vlc_telnet.markdown similarity index 98% rename from source/_components/vlc-telnet.markdown rename to source/_components/vlc_telnet.markdown index 7bef2182ebd..d15e8a4fb32 100644 --- a/source/_components/vlc-telnet.markdown +++ b/source/_components/vlc_telnet.markdown @@ -6,6 +6,8 @@ ha_category: - Media Player ha_release: 0.95 ha_iot_class: Local Polling +redirect_from: + - /components/vlc-telnet --- The `vlc_telnet` platform allows you to control a [VLC media player](http://www.videolan.org/vlc/index.html) using the built in telnet interface. diff --git a/source/_cookbook/perform_actions_based_on_input_select.markdown b/source/_cookbook/perform_actions_based_on_input_select.markdown index 2fc59a90bb7..bead33bdf04 100644 --- a/source/_cookbook/perform_actions_based_on_input_select.markdown +++ b/source/_cookbook/perform_actions_based_on_input_select.markdown @@ -4,7 +4,7 @@ description: "Example playing media to Chromecast based on input select element" ha_category: Automation Examples --- -This example uses an [`input_select`](/components/input_select/) element to pick which mp3 file to play on a [Chromecast](components/media_player.cast/). +This example uses an [`input_select`](/components/input_select/) element to pick which mp3 file to play on a [Chromecast](/components/cast/). ```yaml # Define our dropdown list diff --git a/source/_docs/ecosystem/appdaemon.markdown b/source/_docs/ecosystem/appdaemon.markdown index 58b20ea4642..f4c05863a79 100755 --- a/source/_docs/ecosystem/appdaemon.markdown +++ b/source/_docs/ecosystem/appdaemon.markdown @@ -101,4 +101,4 @@ Of course, if I wanted to make this App or its predecessor reusable, I would hav In addition, Apps can write to `AppDaemon`'s log files, and there is a system of constraints that allows you to control when and under what circumstances Apps and callbacks are active to keep the logic clean and simple. -For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/appdaemon.md) make it easy to install. +For full installation instructions, see the [AppDaemon Project Documentation pages](http://appdaemon.readthedocs.io/en/stable/). If you're using Hassbian, then the [Hassbian scripts](https://github.com/home-assistant/hassbian-scripts/blob/dev/docs/suites/appdaemon.md) make it easy to install. diff --git a/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown b/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown index ddf0f0edbe1..3940cf811bb 100644 --- a/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown +++ b/source/_posts/2019-02-11-hass-cli-0-dot-5-area-entity-registry-and-event-cli.markdown @@ -144,7 +144,7 @@ Minor fixes: * fix bad typing [499b544](http://github.com/home-assistant/home-assistant-cli/commit/499b5449b0441b546ea48aff212754433457dbd5) @maxandersen * fix editor formatting [86d9bf8](http://github.com/home-assistant/home-assistant-cli/commit/86d9bf8bf6bfb5bec1a9f28177c105f84912a91b) @maxandersen * Fix version [3765a03](http://github.com/home-assistant/home-assistant-cli/commit/3765a03ccf11f0865baa7e70937279bcaa245352) @maxandersen -* Fix version marker [edbe4bf](http://github.com/homeassistant/homeassistant-cli/commit/edbe4bf42e7d0993d68a367ca04ad80217aac395) @maxandersen +* Fix version marker [edbe4bf](http://github.com/home-assistant/home-assistant-cli/commit/edbe4bf42e7d0993d68a367ca04ad80217aac395) @maxandersen Have fun! diff --git a/source/_posts/2019-04-24-release-92.markdown b/source/_posts/2019-04-24-release-92.markdown index 8ef8d80b108..58984611a7c 100644 --- a/source/_posts/2019-04-24-release-92.markdown +++ b/source/_posts/2019-04-24-release-92.markdown @@ -229,7 +229,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Always set latest pin ([@balloob] - [#23328]) ([cloud docs]) (beta fix) - Add sensor and binary senseor to default expose ([@balloob] - [#23332]) ([google_assistant docs]) (beta fix) - Support unicode in configuration migration ([@awarecan] - [#23335]) (beta fix) -- Remove ghost folder ([@awarecan] - [#23350]) (aws_lambda docs) ([aws_sns docs]) ([aws_sqs docs]) (beta fix) +- Remove ghost folder ([@awarecan] - [#23350]) (aws_lambda docs) (aws_sns docs) (aws_sqs docs) (beta fix) ## All changes @@ -301,7 +301,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Google Assistant: Add support for open/close binary sensors ([@balloob] - [#22674]) ([binary_sensor docs]) ([google_assistant docs]) - Update light/services.yaml ([@emontnemery] - [#22662]) - Fix connection loss issues for Harmony ([@ehendrix23] - [#22687]) ([harmony docs]) -- Remove aws_* notify platforms ([@awarecan] - [#22698]) (aws_lambda docs) ([aws_sns docs]) ([aws_sqs docs]) +- Remove aws_* notify platforms ([@awarecan] - [#22698]) (aws_lambda docs) (aws_sns docs) (aws_sqs docs) - Add manifests ([@balloob] - [#22699]) - Add a .codecov.yml to control coverage statuses and enable notifications ([@robbiet480] - [#22707]) - Raise ConfigEntryNotReady for MQTT connection exception ([@aav7fl] - [#22540]) @@ -542,7 +542,7 @@ Experiencing issues introduced by this release? Please report them in our [issue - Always set latest pin ([@balloob] - [#23328]) ([cloud docs]) (beta fix) - Add sensor and binary senseor to default expose ([@balloob] - [#23332]) ([google_assistant docs]) (beta fix) - Support unicode in configuration migration ([@awarecan] - [#23335]) (beta fix) -- Remove ghost folder ([@awarecan] - [#23350]) (aws_lambda docs) ([aws_sns docs]) ([aws_sqs docs]) (beta fix) +- Remove ghost folder ([@awarecan] - [#23350]) (aws_lambda docs) (aws_sns docs) (aws_sqs docs) (beta fix) [#19590]: https://github.com/home-assistant/home-assistant/pull/19590 [#20256]: https://github.com/home-assistant/home-assistant/pull/20256 @@ -966,8 +966,6 @@ Experiencing issues introduced by this release? Please report them in our [issue [automation docs]: /components/automation/ [awair docs]: /components/awair/ [aws docs]: /components/aws/ -[aws_sns docs]: /components/aws_sns/ -[aws_sqs docs]: /components/aws_sqs/ [axis docs]: /components/axis/ [binary_sensor docs]: /components/binary_sensor/ [bloomsky docs]: /components/bloomsky/ diff --git a/source/developers/credits.markdown b/source/developers/credits.markdown index 45b545902d3..4769d6ad038 100644 --- a/source/developers/credits.markdown +++ b/source/developers/credits.markdown @@ -4541,7 +4541,7 @@ This page contains a list of people who have contributed in one way or another t - [jaminh (@jaminh)](https://github.com/jaminh "1 total commits to the Home Assistant orga: 1 commit to open-zwave ") -- [JammyDodger231 (@JammyDodger231)](https://github.com/JammyDodger231 "6 total commits to the Home Assistant orga: +- [JamesMcClelland (@JamesMcClelland)](https://github.com/JamesMcClelland "6 total commits to the Home Assistant orga: 6 commits to home-assistant.io ") - [Jan Almeroth (@jalmeroth)](https://github.com/jalmeroth "8 total commits to the Home Assistant orga: @@ -7698,7 +7698,7 @@ This page contains a list of people who have contributed in one way or another t 12 commits to home-assistant 9 commits to home-assistant.io ") -- [Nick Zelei (@zelein)](https://github.com/zelein "1 total commits to the Home Assistant orga: +- [Nick Zelei (@nickzelei)](https://github.com/nickzelei "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") - [Nicko van Someren (@nickovs)](https://github.com/nickovs "9 total commits to the Home Assistant orga: @@ -8350,7 +8350,7 @@ This page contains a list of people who have contributed in one way or another t - [Peter Tisovčík (@mienkofax)](https://github.com/mienkofax "1 total commits to the Home Assistant orga: 1 commit to open-zwave ") -- [Peter Weidenkaff (@hansgans)](https://github.com/hansgans "1 total commits to the Home Assistant orga: +- [Peter Weidenkaff (@weidenka)](https://github.com/weidenka "1 total commits to the Home Assistant orga: 1 commit to home-assistant.io ") - [Peter Zsak (@wroadd)](https://github.com/wroadd "1 total commits to the Home Assistant orga: diff --git a/source/images/supported_brands/mercedesme.png b/source/images/supported_brands/mercedesme.png deleted file mode 100644 index 008791b1a70..00000000000 Binary files a/source/images/supported_brands/mercedesme.png and /dev/null differ