mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-28 11:47:00 +00:00
Spelling fixes (#6349)
* Articles, comma * Article * Fix cases of "Nmap" word's letters * Fix prepositions
This commit is contained in:
WofWca
Franck Nijhof
parent
71eb1b509d
commit
43996efb0e
@ -38,4 +38,4 @@ To configure Locative, you must set up the app to send a `GET` request to your H
|
||||
|
||||
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".
|
||||
|
||||
To use Locative in combination with another device tracker, such as [nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
|
||||
To use Locative in combination with another device tracker, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
|
||||
|
||||
@ -38,17 +38,17 @@ device_tracker:
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **hosts** (*Required*): The network address to scan (in any supported NMap format). Mixing subnets and IPs is possible.
|
||||
- **home_interval** (*Optional*): The number of minutes nmap will not scan this device, assuming it is home, in order to preserve the device battery.
|
||||
- **exclude** (*Optional*): Hosts not to include in nmap scanning. Scanning the host where Home Assistant is running can cause problems (websocket error), so excluding that host is a good idea.
|
||||
- **scan_options** (*Optional*): Configurable scan options for nmap. Default to `-F --host-timeout 5s`
|
||||
- **hosts** (*Required*): The network address to scan (in any supported Nmap format). Mixing subnets and IPs is possible.
|
||||
- **home_interval** (*Optional*): The number of minutes Nmap will not scan this device, assuming it is home, in order to preserve the device battery.
|
||||
- **exclude** (*Optional*): Hosts not to include in Nmap scanning. Scanning the host where Home Assistant is running can cause problems (websocket error), so excluding that host is a good idea.
|
||||
- **scan_options** (*Optional*): Configurable scan options for Nmap. Default to `-F --host-timeout 5s`
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
A full example for the `nmap` tracker could look like the following sample:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for nmap
|
||||
# Example configuration.yaml entry for Nmap
|
||||
# One whole subnet, and skipping two specific IPs.
|
||||
device_tracker:
|
||||
- platform: nmap_tracker
|
||||
@ -60,7 +60,7 @@ device_tracker:
|
||||
```
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml for nmap
|
||||
# Example configuration.yaml for Nmap
|
||||
# One subnet, and two specific IPs in another subnet.
|
||||
device_tracker:
|
||||
- platform: nmap_tracker
|
||||
|
||||
@ -19,7 +19,7 @@ A lot of WiFi access points and WiFi routers support the Simple Network Manageme
|
||||
This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
|
||||
</p>
|
||||
|
||||
The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker component page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/device_tracker.ping/) or [NMAP](/components/device_tracker.nmap_tracker/) instead.
|
||||
The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker component page](/components/device_tracker/) than desirable. It is recommended to use [Ping](/components/device_tracker.ping/) or [Nmap](/components/device_tracker.nmap_tracker/) instead.
|
||||
|
||||
| Brand | Device/Firmware | OID |
|
||||
|---|---|---|---|
|
||||
|
||||
@ -15,7 +15,7 @@ ha_release: pre 0.7
|
||||
|
||||
The `tomato` platform requires an extra config variable called `http_id`. The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code.
|
||||
|
||||
Because of a limitation in Tomato's API, this platform will only track wireless devices. If tracking wired devices like a Philips Hue Hub is necessary, it is possible to use another platform like [NMAP](/components/device_tracker.nmap_tracker/).
|
||||
Because of a limitation in Tomato's API, this platform will only track wireless devices. If tracking wired devices like a Philips Hue Hub is necessary, it is possible to use another platform like [Nmap](/components/device_tracker.nmap_tracker/).
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ footer: true
|
||||
ha_category: Automation Examples
|
||||
---
|
||||
|
||||
This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar component.
|
||||
This will send a message when someone in your known devices list connects to your local network. In other words, when someone arrives home. It will only work if you are using the [Nmap](/components/device_tracker.nmap_tracker/) device tracker or a similar component.
|
||||
|
||||
This example uses [Telegram](/components/notify.telegram/) to send the notification.
|
||||
|
||||
|
||||
@ -1596,7 +1596,7 @@ for tracker in trackers:
|
||||
|
||||
### {% linkable_title get_tracker_state() %}
|
||||
|
||||
Get the state of a tracker. The values returned depend in part on the configuration and type of device trackers in the system. Simpler tracker types like `Locative` or `NMAP` will return one of 2 states:
|
||||
Get the state of a tracker. The values returned depend in part on the configuration and type of device trackers in the system. Simpler tracker types like `Locative` or `Nmap` will return one of 2 states:
|
||||
|
||||
- `home`
|
||||
- `not_home`
|
||||
|
||||
@ -12,7 +12,7 @@ redirect_from: /docs/frontend/webserver/
|
||||
|
||||
It was only a matter of time until the first queries for tools like [https://www.shodan.io](https://www.shodan.io/search?query=Home+Assistant) to search for Home Assistant instances showed up.
|
||||
|
||||
To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [nmap device tracker](/components/device_tracker/).
|
||||
To get an idea about how your Home Assistant instance looks to a network scanner, you can use `nmap`. The `nmap` tool is already available if you are using the [Nmap device tracker](/components/device_tracker/).
|
||||
|
||||
```bash
|
||||
$ nmap -sV -p 8123 --script=http-title,http-headers 192.168.0.3
|
||||
|
||||
@ -36,9 +36,9 @@ From the Hass.io main panel open the add-on store.
|
||||
|
||||
### {% linkable_title Editing config via 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.
|
||||
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.
|
||||
|
||||
Go to the add-on store (see 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.
|
||||
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.
|
||||
|
||||
- Set a password on the Config box, don't forget to use quotes on your password
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ 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 other device into the ultimate home automation hub.
|
||||
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.
|
||||
|
||||
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 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.
|
||||
|
||||
|
||||
@ -27,13 +27,13 @@ Screenshot of Home Assistant showing a school, work and home zone and two people
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
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).
|
||||
|
||||
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 are a wide [range of options][ha-presence] available, both for scanning your local network and third-party services.
|
||||
There is a wide [range of options][ha-presence] available, both for scanning your local network and third-party services.
|
||||
|
||||
### {% linkable_title Zones %}
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ description: Open-source home automation platform running on Python 3. Track and
|
||||
</div>
|
||||
<div class='join-community material-card text'>
|
||||
<h1>Join The Community</h1>
|
||||
We love to help & talk home automation.
|
||||
We love to help with & talk about home automation.
|
||||
|
||||
<div class='links'>
|
||||
<a href='https://community.home-assistant.io'>Forums</a>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user