192.168.1.4
and listening on port 8123. If you use Hass.io
and haven’t changed any of the defaults, Home Assistant will also be reachable at http://hassio.local:8123.my-home.duckdns.org
) that is supported to be updated via your router to always point to your public address. If you have created the port-forward of TCP 8123 on your router’s public interface to TCP 8123 on your internal Home Assistant IP (say 192.168.1.4
), your Home Assistant is now available on the web. You could declare victory at this point and stop but don’t – because everything at this point is unencrypted and we want you to enjoy HA in a private, secure manner.http://my-home.duckdns.org:8123
– if it works, you have hairpin NAT working and can go on to the next section. Most current routers will support NAT hairpinning out of the box, there are however some routers (especially if you got your router from your ISP) that do not have this ability or have it disabled. If this is the case, you need to check if you can enable it on your router or, if you can’t, you will need to set up Split Brain DNS.http://my-home.duckdns.org:8123
works, but anyone could be reading your traffic. Let’s change that! The DuckDNS Hass.io
add-on will create a free, trusted and valid LetsEncrypt SSL certificate to use on your Home Assistant. Just follow the installation instructions here and here and you will have secure, public access to your Home Assistant. What’s great about using the DuckDNS add-on is that it uses the LetsEncrypt DNS challenge, whereby during requesting the certificate it proves “ownership” of the domain by creating a temporary DNS record. If you use a different DNS provider other than DuckDNS, you can use the LetsEncrypt add-on for Hass.io
which supports proving ownership of the name either via the DNS or the http challenge. The latter requires port-forwarding TCP Port 80 on your router to your internal Home Assistant IP on TCP Port 80.base_url: my-home.duckdns.org:8123
to the http:
section of your configuration.yaml. This is not strictly necessary but will help with auto-detection during onboarding of the iOS app, as the app will know where and how to reach your Home Assistant.my-home.duckdns.org
. Why is that? Because valid encryption via https and SSL certificates only works for public DNS names. What this means is that the certificate name on your server needs to match the DNS name you enter in your browser or app. This is fine with hairpin NAT available but becomes an issue when it’s not. In this case you need to “split” the answer your browser/app gets when it looks up the IP address behind my-home.duckdns.org
– you need one answer for devices on your home network that points to the internal IP address of your Home Assistant (e.g. 192.168.1.4
) and another answer for when you’re out and about [e.g. 104.25.25.31
.Settings
->DNS settings
, then scroll down to the bottom where you have a box titled: DNS rewrites
Add DNS rewrite
and enter your my-home.duckdns.org
and the internal IP 192.168.1.4
of your Home Assistant, followed by clicking on save
. What happens now is that all DNS queries for the address my-home.duckdns.org
from inside your home network will be answered by AdGuard via its own rewrite table, thus pointing toward the internal address of your Home Assistant instead of asking public DNS servers on the web which will all answer with the public IP of your router.https://my-home.duckdns.org:8123
and the setup will finish with that address in the External URL
Youtube downloader save from net. field in the app connection settings. There should be no need to enter an internal URL as the same address will work regardless of where your phone is connected.http://hassio.local:8123
192.168.1.4
as well as an IPv6 address of e897:5571:5f66:21dc:51c1:28d8:3bdc:6724
. Here’s where our advice for not changing the TCP port you forward to Home Assistant comes in:192.168.1.4:8123
and[e897:5571:5f66:21dc:51c1:28d8:3bdc:6724]:8123
my-home.duckdns.org
: An A-record pointing to your routers public IPv4 address which will be port-forwarded to your HA hosts internal address and an AAAA-record, which points directly to the IPv6 address of your HA host. Now when you access your HA remotely either protocol could be used, since all you’re entering will be https://my-home.duckdns.org:8123
. If you had changed the Port on your Router to the https default 443, the connection would now fail if you suddenly ended up with a working IPv6 setup as nothing is listening on [e897:5571:5f66:21dc:51c1:28d8:3bdc:6724]:443
.TCP 443
to your Home Assistant internal IP 192.168.1.4 Port 443
. Do NOT create a forward to 192.168.1.4 Port 8123
as that is now unencrypted http and should only be accessible from your local network.https://my-home.duckdns.org
both internally and externally while having http://192.168.1.4:8123
available to be used as unencrypted endpoint for things like konnected.io
.configuration.yaml
(example for Netgear):Parameter | Default | Description |
---|---|---|
interval_seconds | 12 | Seconds between each scan for new devices. This only applies to local device trackers, not applications that push updates. |
consider_home | 180 | Seconds to wait till marking someone as not home after not being seen. This parameter is most useful for households with Apple iOS devices that go into sleep mode while still at home to conserve battery life. iPhones will occasionally drop off the network and then re-appear. consider_home helps prevent false alarms in presence detection when using IP scanners such as Nmap. consider_home accepts various time representations, (e.g., the following all represents 3 minutes: 180 , 0:03 , 0:03:00 ) |
track_new_devices: false
will still result in new devices being recorded in known_devices.yaml
, but they won’t be tracked (track: false
).known_devices.yaml
is being phased out and no longer used by all trackers. Depending on the integration you use this section may no longer apply. This includes OwnTracks, GeoFency, GPSLogger, Locative and Huawei LTE.device_tracker
is enabled, a file will be created in your configuration dir named known_devices.yaml
. Edit this file to adjust which devices to be tracked.devicename
refers to the detected name of the device. For example, with nmap
, this will be the MAC address (with byte separators omitted).Parameter | Default | Description |
---|---|---|
name | Host name or “Unnamed Device” | The friendly name of the device. |
mac | None | The MAC address of the device. Add this if you are using a network device tracker like Nmap or SNMP. |
picture | None | A picture that you can use to easily identify the person or device. You can also save the image file in a folder “www” in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use picture: /local/favicon-192x192.png . The path ‘local’ is mapped to the ‘www’ folder you create. |
icon | mdi:account | An icon for this device (use as an alternative to picture ). |
gravatar | None | An email address for the device’s owner. If provided, it will override picture . |
track | [uses platform setting] | If yes /on /true then the device will be tracked. Otherwise its location and state will not update. |
consider_home | [uses platform setting] | Seconds to wait till marking someone as not home after not being seen. Allows you to override the global consider_home setting from the platform configuration on a per device level. |
'home'
if it is in the home zone, detected by your network or Bluetooth based presence detection. If you’re using a presence detection method that includes coordinates then when it’s in a zone the state will be the name of the zone (case sensitive). When a device isn’t at home and isn’t in any zone, the state will be 'not_home'
.device_tracker.see
service can be used to manually update the state of a device tracker: Van helsing part 2 full movie in hindi free hd.Service data attribute | Optional | Description |
---|---|---|
dev_id | no | The second half of the entity_id , for example tardis for device_tracker.tardis |
location_name | no | The location, home , not_home , or the name of the zone |
host_name | yes | The hostname of the device tracker |
mac | yes | The MAC address of the entity (only specify if you’re updating a network based tracker) |
gps | yes | If you’re providing a location, for example [51.513845, -0.100539] |
gps_accuracy | yes | The accuracy of the GPS fix |
battery | yes | The battery level of the device |