diff --git a/source/_includes/asides/getting_started_navigation.html b/source/_includes/asides/getting_started_navigation.html index 9d41bb402b1..771a222c91b 100644 --- a/source/_includes/asides/getting_started_navigation.html +++ b/source/_includes/asides/getting_started_navigation.html @@ -2,14 +2,14 @@ {% include edit_github.html %}
-

Getting Started Guide

+

Getting Started

diff --git a/source/getting-started/automation-2.markdown b/source/getting-started/automation-2.markdown deleted file mode 100644 index a7cb8201c32..00000000000 --- a/source/getting-started/automation-2.markdown +++ /dev/null @@ -1,108 +0,0 @@ ---- -layout: page -title: "Your Second Automation" -description: "Step by step guiding through making your second automation." -date: 2016-04-24 08:30 +0100 -sidebar: true -comments: false -sharing: true -footer: true -redirect_from: /getting-started/automation-create-first/ ---- - -After the scratch on the Automation surface, let's dive deeper and create the automation rule: **Turn on the lights when the sun sets** - -We are defining a [trigger](/docs/automation/trigger/) to track the sunset and tell it to fire when the sun is setting. When this event is triggered, the service `light.turn_on` is called without any parameters. Because we specify no parameters, it will turn on all the lights. - -```yaml -# Example configuration.yaml entry -automation: - alias: Turn on the lights when the sun sets - initial_state: true - hide_entity: false - trigger: - platform: sun - event: sunset - action: - service: light.turn_on -``` - -Starting with 0.28 automation rules can be reloaded from the [frontend](/components/automation/) and are shown by default. With [`hide_entity:`](/components/automation/) you can control this behavior. It's convenient if you are working on your rules, but when a rule is finished, and you don't want to see that rule in your frontend, you can set `hide_entity:` to `true`. To set an automation to be disabled when Home Assistant starts set `initial_state:` to `false`. - -After a few days of running this automation rule, you come to realize that this automation rule is not sufficient. It was already dark when the lights went on, and the one day you weren't home, the lights turned on anyway. Time for some tweaking. Let's add an offset to the sunset trigger and a [condition](/docs/automation/condition/) to only turn on the lights if anyone is home. - -```yaml -# Example configuration.yaml entry -automation: - alias: Turn on the lights when the sun sets - trigger: - platform: sun - event: sunset - offset: "-01:00:00" - condition: - condition: state - entity_id: group.all_devices - state: 'home' - action: - service: light.turn_on -``` - -Now you're happy, and all is good. You start to like this automation business and buy some more lights, this time you put them in the bedroom. But what you now realize is that when the sun is setting, the lights in the bedroom are also being turned on! Time to tweak the automation to only turn on the living room lights. - -The first thing you do is to look at the entities in the developer tools (second icon) in the app. You see the names of your lights, and you write them down: `light.table_lamp`, `light.bedroom`, `light.ceiling`. - -Instead of hard coding the entity IDs of the lights in the automation rule, we will set up a group. This will allow us to see the living room separate in the app and be able to address it from automation rules. - -So we tweak the config to add the group and have the automation rule only turn on the group. - -```yaml -# Example configuration.yaml entry -group: - living_room: - - light.table_lamp - - light.ceiling - -automation: - alias: Turn on the light when the sun sets - trigger: - platform: sun - event: sunset - offset: "-01:00:00" - condition: - condition: state - entity_id: group.all_devices - state: 'home' - action: - service: light.turn_on - entity_id: group.living_room -``` - -Christmas is coming along, and you decide to buy a remote switch to control the Christmas lights from Home Assistant. You can't claim to live in the house of the future if you're still manually turning on your Christmas lights! - -We hook the switch up to Home Assistant and grab the entity ID from the developer tools: `switch.christmas_lights`. We will update the group to include the switch and will change our [action](/docs/automation/action/). We are no longer able to call `light.turn_on` because we also want to turn on a switch. This is where `homeassistant.turn_on` comes to the rescue. This service is capable of turning on any entity. - -```yaml -# Example configuration.yaml entry -group: - living_room: - - light.table_lamp - - light.ceiling - - switch.christmas_lights - -automation: - alias: Turn on the lights when the sun sets - hide_entity: true - trigger: - platform: sun - event: sunset - offset: "-01:00:00" - condition: - condition: state - entity_id: group.all_devices - state: 'home' - action: - service: homeassistant.turn_on - entity_id: group.living_room -``` - -### [Next step: Presence detection »](/getting-started/presence-detection/) diff --git a/source/getting-started/automation.markdown b/source/getting-started/automation.markdown index 2f420b19db4..e57580e4b6f 100644 --- a/source/getting-started/automation.markdown +++ b/source/getting-started/automation.markdown @@ -1,31 +1,52 @@ --- layout: page title: "Automating Home Assistant" -description: "Instructions to get started with Automation using Home Assistant." -date: 2016-09-26 21:00 +description: "A quick intro on getting your first automation going." +date: 2016-04-24 08:30 +0100 sidebar: true comments: false sharing: true footer: true +redirect_from: + - /getting-started/automation-create-first/ + - /getting-started/automation-2/ --- -When your devices are set up, it's time to put the cherry on the pie: **automation**. Home Assistant offers [a few built-in automations](/components/#automation) – but you'll be using the automation component to set up your own rules, for the most part. +When your devices are set up, it's time to put the cherry on the pie: automation. In this guide we're going to create a simple automation rule to **turn on the lights when the sun sets**. -If you added a random sensor in the previous step then you can use that sensor for your very first automation: +In Home Assistant, open the menu by clicking on the top-left icon and click on configuration. Now click on automations. This is the automation screen from which you can manage all the automations in Home Assistant. -```yaml -automation: - - alias: Check sensor value and show notification - trigger: - platform: numeric_state - entity_id: sensor.random_sensor - above: 10 - action: - service: persistent_notification.create - data: - message: "Sensor value greater than 10" -``` +Click on the orange button at the bottom right to create a new automation. You are presented with a blank automation screen. -For further details about automation, please take the next step or the [automation documentation](/docs/automation/). +

+ +The automation editor. +

-### [Next step: Home Assistant Automation Part 2 »](/getting-started/automation-2/) +The first thing we will do is to set a name. Enter "Turn Lights On at Sunset". + +The second step is defining what should trigger our automation to run. In this case we want to use the event of the sun setting to trigger our automation. However, if we would turn on the lights when the sun actually sets, it would be too late as it already gets quite dark while it's setting. So we're going to add an offset. + +In the trigger section, click on the dropdown and change trigger type to "Sun". It allows us to pick between sunrise and sunset, go ahead and pick sunset. As we discussed, we want our automation to be triggered a little before the sun actually sets, so let's add `-0:30` to the offset. This indicates that we will trigger 30 minutes before the sun actually sets, neat! + +

+ +A new automation with a sun trigger filled in. +

+ +Once we have defined our trigger, scroll down to the action section. Make sure trigger type is set to "Call Service" and change the service to `light.turn_on`. For this automation we're going to turn on all lights, so let's change the service data to `{ "entity_id": "all" }`. + +

+ +A new automation with the action set up to turn on the lights. +

+ +Click the orange button to save the automation. Now wait till it's 30 minutes until the sun sets and see your automation magic! + +Further reading on automations: + +- [Triggers](/docs/automation/trigger/) +- [Conditions](/docs/automation/condition/) +- [Actions](/docs/automation/action/) + +### [Next step: Presence detection »](/getting-started/presence-detection/) diff --git a/source/getting-started/configuration.markdown b/source/getting-started/configuration.markdown index 54bd795bbb5..dc342ae21c8 100644 --- a/source/getting-started/configuration.markdown +++ b/source/getting-started/configuration.markdown @@ -1,6 +1,6 @@ --- layout: page -title: "Configure Home Assistant" +title: "Advanced Configuration" description: "Instructions to get Home Assistant configured." date: 2016-09-26 21:00 sidebar: true @@ -9,85 +9,43 @@ sharing: true footer: true --- -

-This guide applies only if you've installed Home Assistant via Hass.io. If you've used any other install method then [see here](/docs/configuration/) instead. +Until now we have been able to configure Home Assistant purely via the user interface. However, not all options are accessible via the user interface. The other options are accessible via the Home Assistant configuration file called `configuration.yaml`. A default one is created when Home Assistant started for the first time. + +

+This final step of the getting started only applies if you've installed Home Assistant via Hass.io. If you've used another installation method, [see here](/docs/configuration/).

-If you made it here, awesome! That means that you got Home Assistant up and running. It might have already found some of your networked devices. This is going to be fun! - -Home Assistant stores its configuration in a file called `configuration.yaml`. A default one is created when Home Assistant is started for the first time. Some of the things in the configuration file can be edited via the user interface, other parts require you to edit the configuration file directly. - -There are two common approaches to edit your configuration: via Samba/Windows Networking and via the HASS Configurator. Both of these are [official add-ons for Hass.io](/addons/). - -## {% linkable_title Installing Hass.io add-ons %} - -Hass.io add-ons are installed from the add-on store embedded in the Hass.io panel: - - - Open Home Assistant by navigating to [http://hassio.local:8123][local]. - - Click on the menu icon in the top left and select Hass.io in the sidebar. - - The Hass.io panel opens, now open the add-on store by clicking the shopping bag. - -[local]: http://hassio.local:8123 +We are going to help you make your first changes to `configuration.yaml`. To do this, we are going to install an add-on from the Hass.io add-on store: the HASS Configurator. To get to the add-on store, click on the menu icon in the top left, then click on Hass.io. On the new page, open the add-on store tab.

-From the Hass.io main panel open the add-on store. +From the Hass.io main panel, open the add-on store.

-### {% linkable_title Editing config via HASS Configurator %} +Under the "Core" section you will find HASS Configurator. -The first add-on we should install is the HASS Configurator. With the HASS Configurator, you'll be able to edit your Home Assistant configuration from the web interface. + - Click on Configurator and click on INSTALL. When installation is complete, the UI will go to the add-on details page for the configurator. + - Now start the add-on by clicking on START. + - Open the user interface by clcking on OPEN WEB UI. -Go to the add-on store (see the previous step), click on Configurator and click on "INSTALL". When installation is complete, the UI will go to the add-on details page for the configurator. Here you will be able to change settings, start and stop the add-on. Follow the steps below to setup the add-on. +Now let's make a small change using the configurator: we are going to change the name and location of your Home Assistant installation. - - "START" the add-on - - You will be able to click the "OPEN WEB UI" link to open the Web UI on a new window - - Type your username and password that you recently saved - -Time for the first practice with the configurator. We're going to add the Configurator to the main Home Assistant sidebar: - - - Click the folder icon in the top left of the configurator window to open the file browser sidebar. + - Click the folder icon in the top left of the configurator window to open the file browser sidebar. - Click the `configuration.yaml` file (in the `/config/` folder) to load it into the main Configurator edit window. - - Copy and paste the following to the end of the `configuration.yaml` file: - -```yaml -panel_custom: - - name: hassio-main - sidebar_title: Configurator - sidebar_icon: hass:settings - js_url: /api/hassio/app/entrypoint.js - url_path: configurator - embed_iframe: true - require_admin: true - config: - ingress: core_configurator -``` - + - Find the `homeassistant:` configuration block, which should be the first thing in `configuration.yaml`. In this block, update `name`, `latitude`, `longitude`, `unit_system` and `time_zone` to match yours. - 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. + - Most changes in `configuration.yaml` require Home Assistant to be restarted to see the changes. You can verify that your changes are acceptable by running a config check. Do this by clicking on Configuration in the sidebar, click on General and click on the "Check Config" button. When it's valid, it will show the text "Configuration valid!". + - Now Restart Home Assistant using the "restart" in the Server management section on the same page. + +

+ +Screenshot of the "General" page in the configuration panel. +

### {% linkable_title Editing config via Samba/Windows Networking %} -Maybe you are not a big fan of our web editor and want to use a text editor on your computer instead. This is possible by sharing the configuration over the network using the Samba add-on, which can be installed from the Hass.io add-on store. +Maybe you are not a big fan of our web editor and want to use a text editor on your computer instead. This is possible by sharing the configuration over the network using the Samba add-on, which can also be installed from the Hass.io add-on store. This will make your configuration accessible via the network tab on your computer. -After you have installed it, click on START. Hass.io should now be available in the networking tab on your computer. Use a text editor like the free [Visual Studio Code](https://code.visualstudio.com/) to edit `configuration.yaml`. +Go to the add-on store and look for Samba in the core section. After you have installed the add-on, click on START. Hass.io should now be available in the networking tab on your computer. -## {% linkable_title Configuring integrations %} - -Now that you are able to edit the configuration, it's time to set up some of your devices and services. Each service and device will have its own instructions on how to be integrated. Find your devices and services on the [components overview page](/components/). - -

YAML can be a little daunting at first. A lot is possible! [Here is some more info.](/docs/configuration/devices/)

- -For your first integration, you'll create a virtual sensor that generates a random integer value between 0 and 20 every 30 seconds. - -To create this random value sensor [random values](/components/sensor.random/), enter the following to the bottom of your `configuration.yaml` file, and restart Home Assistant (remember it may take up to a minute for the service to restart): - -```yaml -sensor: - - platform: random -``` - -You'll know it worked when you see the new random sensor in your overview page. On the next page, we'll create an automation that uses this sensor to take an action. - -### [Next step: Automate Home Assistant »](/getting-started/automation/) +We suggest that to edit `configuration.yaml`, you use the free text editor [Visual Studio Code](https://code.visualstudio.com/) in combination with the [Home Assistant Config Helper extension](https://marketplace.visualstudio.com/items?itemName=keesschollaart.vscode-home-assistant). diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index eade77a5557..7635cb1c396 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -9,29 +9,47 @@ sharing: true footer: true --- -The goal of this getting started guide is to install [Hass.io](/hassio/) on a Raspberry Pi. Hass.io is our own all in one solution that turns your Raspberry Pi or another device into the ultimate home automation hub. +{% comment %} -Follow this guide if you want to get started with Home Assistant easily, or if you have no or little Linux experience. +Note for contributors: -

-For advanced users or if you have no Raspberry Pi at hand, check our [alternative installation methods](/docs/installation/). The [FAQ](/faq/#home-assistant-vs-hassio) explains more about the differences. -

+The getting started guide aims at getting new users get Home Assistant up and +running as fast as possible. Nothing else. All other things should not be +written down, as it creates a spaghetti of links and the user will lose focus. + +So here are guidelines: + + - Focus on the bare necessities. No remote port, no securing installation. The + defaults are good enough to get a system up and running for the first guide. + - Avoid or explain technical terms. + - Do not talk about YAML if it can be partially/fully done in UI. + - Do not tell people about stuff they can do later. This can be added to a + 2nd tier guide. + - The first page of the guide is for installation, hence hass.io specific. + Other pages should not refer to it except for the page introducing the last + page that introduces `configuration.yaml`. + +{% endcomment %} + +The goal of this getting started guide is to get Home Assistant running on a Raspberry Pi. The easiest way to do this is by using [Hass.io](/hassio/, which is our own all in one solution that turns Raspberry Pi's and another devices into the ultimate home automation hubs. + +Follow this guide if you want to get started with Home Assistant easily, or if you have no or little Linux experience. For advanced users or if you don't have a [device that is supported by this guide][supported], check our [alternative installation methods](/docs/installation/). Once you finish your alternative installation, you can continue at the [next step][next-step]. + +[supported]: /hassio/installation/ ### {% linkable_title Suggested hardware%} -We will need a few things to get started with installing Home Assistant. For best performance, we suggest the latest Raspberry Pi 3 Model B+. Links below are linking to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country. +We will need a few things to get started with installing Home Assistant. The latest Raspberry Pi model makes a good and affordable starting point for your home automation journey. Links below are linking to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country. - [Raspberry Pi 3 Model B+](http://a.co/ak2SQor) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A) - [Micro SD Card](http://a.co/gslOydD). Get one that is Class 10 as they are more reliable. Size 32 GB or bigger recommended. - SD Card reader. Part of most laptops, and also available as [standalone USB sticks](http://a.co/5FCyb0N) (the brand doesn't matter, just pick the cheapest) - Ethernet cable (optional, Hass.io can work with WiFi as well) -- A USB-Stick (optional, allows for unattended configuration) ### {% linkable_title Software requirements %} - Download the Hass.io image for [your device](/hassio/installation/) - Download [balenaEtcher] to write the image to an SD card -- Text Editor like [Visual Studio Code](https://code.visualstudio.com/) [balenaEtcher]: https://www.balena.io/etcher @@ -39,29 +57,23 @@ We will need a few things to get started with installing Home Assistant. For bes 1. Put the SD card in your SD card reader. 1. Open balenaEtcher, select the Hass.io image and flash it to the SD card. -1. WiFi and Static IP setup only: +1. Unmount the SD card and remove it from your SD card reader. +1. Only if you want to configure WiFi or a Static IP (requires USB stick): - Format a USB-Stick to FAT32 with volume-name `CONFIG`. - Create a folder named `network` in the root of the newly formatted USB-stick. - Within that folder create a file named `my-network` without extension. - - Copy one of [the examples] to the `my-network` file. + - Copy one of [the examples] to the `my-network` file and adjust accordingly. - Plug the USB-stick into the Raspberry Pi 3. -1. Unmount the SD card and remove it from your SD card reader. + 1. Insert the SD card into your Raspberry Pi 3. If you are going to use an Ethernet cable, connect that too. 1. Connect your Raspberry Pi to the power supply, so it turns on. 1. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant, which will take about 20 minutes. -1. Home Assistant will be available at [http://hassio.local:8123][local]. Shortly after the download has started, a simple preparation status page will be available at this URL. Point your browser there. The page refreshes automatically, and Home Assistant will be shown when the download is complete (this typically takes around 20 minutes). -1. Please remember to [secure your installation][secure] once you've finished with the installation process. +1. Home Assistant will be available at [http://hassio.local:8123][local]. If you are running an older Windows or have stricter network configuration, you might need to access Home Assistant at [http://hassio:8123][host]. [local]: http://hassio.local:8123 +[host]: http://hassio:8123 [the examples]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md -[secure]: /docs/configuration/securing/ -

-If your router doesn't support mDNS, then you'll have to use the IP address of your Pi instead of `hassio.local`. For example, `http://192.168.0.9:8123`. You should be able to find the IP address of your Pi from the admin interface of your router. -

+### [Next step: Onboarding »][next-step] -

-When you're done, remember to set up regular backups of your configuration. These backups will protect you from hardware failure and mistakes. On Hass.io you have snapshots (which you should copy off to another system), but you can back up to [GitHub](/docs/ecosystem/backup/backup_github/), [DropBox](/docs/ecosystem/backup/backup_dropbox/) and many other ways. All that matters is that you set them up and test them regularly. -

- -### [Next step: Configuring Home Assistant »](/getting-started/configuration/) +[next-step]: /getting-started/onboarding/ diff --git a/source/getting-started/join-the-community.markdown b/source/getting-started/join-the-community.markdown new file mode 100644 index 00000000000..4b3afcf04d0 --- /dev/null +++ b/source/getting-started/join-the-community.markdown @@ -0,0 +1,24 @@ +--- +layout: page +title: "Join the Community" +description: "Part of the Home Assistant experience is the large world-wide community of tinkerers. Join us." +date: 2019-04-19 00:01 +sidebar: true +comments: false +sharing: true +footer: true +--- + +You made it here? Good job! You've been able to install Home Assistant and get a small taste of all the things that are possible. + +Now that you've got that going, let's see what is next: + + - Learn about [advanced configuration](/getting-started/configuration/) using `configuration.yaml` in our bonus step of the getting started guide. + - Join the community in [our forums] or [our chat]. + - Check out [video tutorials] on a wide range of Home Assistant related topics + +You're now ready to be a part of our world-wide community of tinkerers. Welcome! + +[our forums]: https://community.home-assistant.io/ +[our chat]: /join-chat/ +[video tutorials]: https://www.youtube.com/results?search_query=home+assistant diff --git a/source/getting-started/onboarding.markdown b/source/getting-started/onboarding.markdown new file mode 100644 index 00000000000..80fbe7013e1 --- /dev/null +++ b/source/getting-started/onboarding.markdown @@ -0,0 +1,29 @@ +--- +layout: page +title: "Onboarding Home Assistant" +description: "Instructions to get Home Assistant configured." +date: 2019-04-19 00:01 +sidebar: true +comments: false +sharing: true +footer: true +--- + +Alright, you made it here. The tough part is done. + +With Home Assistant installed, it's time for doing the initial configuration. Here you will create the owner account of Home Assistant. This account will be an administrator and will always be able to change everything. Enter a name, username, password and click on "create account". + +Now you're brought to the main screen of Home Assistant: the states screen. The states screen will show all your devices. So let's get that screen filled up! + +Open the menu on the top left and click on Configuration. On the next screen, click on Integrations. At this screen you will be able to set up integrations with Home Assistant. You might notice a "discovered" section, these are integrations that we found on your network and can easily be added with a few clicks. If your integrations are not discovered, find them in the list and click on configure. + +

+ +The integrations page in the configurations panel shows you all your configured integrations. +

+ +When each integration is done setting up, it will ask you to put the new devices in areas. Areas allow you to organize all the devices in your home. + +When you're done, navigate back to the states panel and voila, your devices are ready for you to control. + +### [Next step: Automate Home Assistant »](/getting-started/automation/) diff --git a/source/getting-started/presence-detection.markdown b/source/getting-started/presence-detection.markdown index f1c51fcfa9f..1d84ce20386 100644 --- a/source/getting-started/presence-detection.markdown +++ b/source/getting-started/presence-detection.markdown @@ -9,10 +9,6 @@ sharing: true footer: true --- -

-We care about privacy. Collected data is only stored in your instance of Home Assistant. -

- Presence detection detects if people are home, which is the most valuable input for automation. Knowing who is home or where they are, will open a whole range of other automation options: - Send me a notification when my child arrives at school @@ -23,34 +19,31 @@ Presence detection detects if people are home, which is the most valuable input Screenshot of Home Assistant showing a school, work and home zone and two people.

-### {% linkable_title Setting it up %} +### {% linkable_title Adding presence detection %} -The device tracker component offers presence detection for Home Assistant. It supports three different methods for presence detection: scan for connected devices on the local network, scan for Bluetooth devices within range, and connect to third-party service. +There are different ways of setting up presence detection. Usually the easiest way to detect presence is by checking which devices are connected to the network. You can do that if you have one of our [supported routers][routers]. By leveraging what your router already knows, you can easily detect if people are at home. -Scanning for connected devices is easy to setup; options include [supported routers][routers] and [scanning the network using Nmap][nmap]. This approach does have its limitations, however: it will only be able to detect if a device is at home, and modern smartphones may show as not home inaccurately (as they disconnect from WiFi if idle). +It's also possible to run an app on your phone to provide detailed location information to your Home Assistant instance. If you're on iOS we suggest to use the [Home Assistant iOS app](/ios/). For Android, we suggest [OwnTracks][ha-owntracks]. -You can scan for [Bluetooth][ha-bluetooth] and [Bluetooth LE][ha-bluetooth-le] devices. Unlike with WiFi, modern smartphones don't turn off Bluetooth automatically, though the range is lower. - -Home Assistant currently supports multiple third-party services for presence detection, such as [OwnTracks over MQTT][ha-owntracks-mqtt], [OwnTracks over HTTP][ha-owntracks-http] [GPSLogger][ha-gpslogger] and [Locative][ha-locative]. - -There is a wide [range of options][ha-presence] available, both for scanning your local network and third-party services. +
+ +
### {% linkable_title Zones %} -Home Assistant will know the location of your device if you are using a device tracker that reports a GPS location (such as OwnTracks, GPS Logger, the iOS app, and others). By [setting up zones][zone] you will be able to add names to the locations of your devices. This way you can easily spot on the state page where the people in your house are and use it as [triggers][trigger] and [conditions][condition] for automation. +Zones allow you to name areas on a map. These areas can then be used to name the location a tracked user is, or use entering/leaving a zone as an automation [trigger] or [condition]. Zones can be set up from the integration page in the configurations screen.

-If you're looking at the [map view][ha-map] then any devices in your Home zone won't be visible, this is by design. +The map view will hide all devices that are home.

[routers]: /components/#presence-detection [nmap]: /components/device_tracker.nmap_tracker/ [ha-bluetooth]: /components/device_tracker.bluetooth_tracker/ [ha-bluetooth-le]: /components/device_tracker.bluetooth_le_tracker/ -[ha-owntracks-mqtt]: /components/device_tracker.owntracks/ -[ha-owntracks-http]: /components/device_tracker.owntracks_http/ +[ha-owntracks]: /components/owntracks/ [ha-locative]: /components/device_tracker.locative/ [ha-gpslogger]: /components/device_tracker.gpslogger/ [ha-presence]: /components/#presence-detection @@ -61,4 +54,4 @@ If you're looking at the [map view][ha-map] then any devices in your Home zone w [condition]: /getting-started/automation-condition/#zone-condition [ha-map]: /components/map/ -### [Next step: Use Home Assistant »](/getting-started/use/) +### [Next step: Join the Community »](/getting-started/join-the-community/) diff --git a/source/getting-started/use.markdown b/source/getting-started/use.markdown deleted file mode 100644 index 941d78e02df..00000000000 --- a/source/getting-started/use.markdown +++ /dev/null @@ -1,22 +0,0 @@ ---- -layout: page -title: "Manage Home Assistant" -description: "Instructions about how to manage Home Assistant." -date: 2016-09-26 21:00 -sidebar: true -comments: false -sharing: true -footer: true ---- - -If you are using Hassbian, browse to [http://hassbian.local:8123](http://hassbian.local:8123) to open the Home Assistant frontend. - -To reload your configuration, go to **Configuration** in your side panel and choose "CHECK CONFIG". - -You will have to restart Home Assistant for most changes to `configuration.yaml` to take effect. You can load changes to [automations](/docs/automation/), [customize](/docs/configuration/customizing-devices/), [groups](/components/group/), and [scripts](/components/script/) without restarting. - -

- -

- -Now that you saw a glimpse of what is possible, take a look at the [documentation](/docs/), ask your questions in our [forum](https://community.home-assistant.io/), join us for a [chat](https://discord.gg/c5DvZ4e), or report your [issues](https://github.com/home-assistant/home-assistant/issues). diff --git a/source/images/getting-started/automation-new-action.png b/source/images/getting-started/automation-new-action.png new file mode 100644 index 00000000000..bd87cdf0fe1 Binary files /dev/null and b/source/images/getting-started/automation-new-action.png differ diff --git a/source/images/getting-started/automation-new-blank.png b/source/images/getting-started/automation-new-blank.png new file mode 100644 index 00000000000..adc63eaba9a Binary files /dev/null and b/source/images/getting-started/automation-new-blank.png differ diff --git a/source/images/getting-started/automation-new-name-trigger.png b/source/images/getting-started/automation-new-name-trigger.png new file mode 100644 index 00000000000..1633c64978c Binary files /dev/null and b/source/images/getting-started/automation-new-name-trigger.png differ diff --git a/source/images/getting-started/integrations.png b/source/images/getting-started/integrations.png new file mode 100644 index 00000000000..d582d25eb5d Binary files /dev/null and b/source/images/getting-started/integrations.png differ