diff --git a/source/_docs/authentication.markdown b/source/_docs/authentication.markdown index 81ae30d9e97..11007d29d9e 100644 --- a/source/_docs/authentication.markdown +++ b/source/_docs/authentication.markdown @@ -24,15 +24,13 @@ For the moment, other user accounts will have the same access as the owner accou ### Your Account Profile -Once you're logged in, you can see the details of your account at the _Profile_ page by clicking on the circular badge next to the Home Assistant title in the sidebar. +Once you're logged in, you can see the details of your account at the _Profile_ page by clicking on the circular at the very bottom of the sidebar. Screenshot of the profile page You can: -* Change the language you prefer Home Assistant to use. -* Change your password. -* Select the [theme](/integrations/frontend/#defining-themes) for the interface of Home Assistant. +* Change your password. * Enable or disable [multi-factor authentication](/docs/authentication/multi-factor-auth/). * Delete _Refresh Tokens_. These are created when you log in from a device. Delete them if you want to force the device to log out. * Create [Long Lived Access Tokens](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) so scripts can securely interact with Home Assistant. diff --git a/source/_docs/tools/dev-tools.markdown b/source/_docs/tools/dev-tools.markdown index d4460c61676..0272cf0c820 100644 --- a/source/_docs/tools/dev-tools.markdown +++ b/source/_docs/tools/dev-tools.markdown @@ -84,9 +84,3 @@ It has two sections, code goes on the left hand side, and the output is shown on It is a good practice to test the template code in the template editor prior to putting it in automations and scripts. For more information about jinja2, visit [jinja2 documentation](http://jinja.pocoo.org/docs/dev/templates/), and also read templating document [here](/topics/templating/) - -## MQTT - -This section is only visible if the MQTT integration is configured. To configure MQTT, add `mqtt:` to the `configuration.yaml` file. For more information, refer to the [MQTT](/integrations/mqtt/) integration. - -Even though MQTT in general provides deeper functionality, the developer tools section of MQTT is limited to publishing messages to a given topic. It supports templates for the payload. To publish a message, simply specify the topic name and the payload and click “PUBLISH” button. diff --git a/source/getting-started/presence-detection.markdown b/source/getting-started/presence-detection.markdown index 21eb5c2502c..24243b20192 100644 --- a/source/getting-started/presence-detection.markdown +++ b/source/getting-started/presence-detection.markdown @@ -26,7 +26,7 @@ During the setup of Home Assistant Companion on your mobile device, the app will -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. +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 configuration screen.
The map view will hide all devices that are home. diff --git a/source/images/docs/authentication/profile.png b/source/images/docs/authentication/profile.png index 10a445c8a6f..a6b88e17cbc 100644 Binary files a/source/images/docs/authentication/profile.png and b/source/images/docs/authentication/profile.png differ