|
|
(One intermediate revision by the same user not shown) |
Line 1: |
Line 1: |
− | = <big>Hub Location, Time, and Time Zone</big> =
| |
− | <big>Your hub depends on having accurate location (latitude and longitude) configured in order to create automations based on sunrise or sunset times and on having an accurate time zone for both these and any time-based automation. If you are having problems with scheduled jobs not executing when you expect, checking for correct correct hub time, location, and time zone are good first steps.</big>
| |
| | | |
− | <big>To do this:</big> | + | <big>'''We're moving!''' Please visit http://docs2.hubitat.com for the latest documentation.</big> |
| | | |
− | * <big>Navigate to '''Settings > Hub Details''' to...</big>
| + | <big> |
− | *# <big>Verify '''Latitude''' and '''Longitude''' (can be calculated from a postal code, if available in your region, or can be put in manually; select the '''How do I find my latitude/longitude?''' link to find precise values for your location, which you may want if used for geopresence in the mobile app, below).</big>
| + | This document is available at: http://docs2.hubitat.com/en/how-to/verify-location-settings |
− | *# <big>Verify that '''Time Zone''' is set correctly for your actual location. For example, a user in New York City should select '''US/Eastern''' (time zones named after regions will automatically account for daylight saving time/summer time, if used in that region).</big>
| + | </big> |
− | *# <big>Verify that '''Current Hub Time''' matches your current time (as of the time of page load; this does not update after the pge is loaded).</big>
| |
− | *#* <big>If this time is not correct, you can select '''Update from browser''' to sync the hub time with time reported by your web browser at this moment</big>
| |
− | *#* <big>If your hub time routinely drifts, note that:</big>
| |
− | *#** <big>hub time is not persisted across a shutdown and must be synced from a time server after any time the hub is powered off</big>
| |
− | *#** <big>the hub's default NTP (time) server requires Internet access; if you have a local NTP server available, the hub can be configured to use this instead, which requires custom code (search community.hubitat.com for some examples)</big>
| |
− | | |
− | <big>See the Hub Details document for more information on this Settings page.</big>
| |
− | | |
− | == <big>Mobile App</big> ==
| |
− | <big>The optional Hubitat Elevation mobile app can be enabled for geopresence to serve as a presence sensor—e.g., to detect whether you are home or away and perform or modify automations based on this status.</big>
| |
− | | |
− | <big>The mobile app geopresence area is defined by two components. One is the configured location of your hub (see above; verify '''Latitude''' and '''Longitude''' for your location). The other is the radius around this location, inside which you will be considered home. Use the slider at the top (iOS) or bottom (Android) to make the circle around your location larger or smaller, as desired.</big>
| |
− | | |
− | <big>For this to work, two settings must be enabled:</big>
| |
− | | |
− | * <big>Location permissions for the Hubitat mobile app in your mobile device operating system (you should be prompted to allow these permissions when first installing and launching the app; consult your phone operating system documentation to learn how to verify or change these settings afterwards, if needed)</big>
| |
− | * <big>'''Enable GeoFence''' in the Hubitat mobile app '''Settings''' page (can be disabled if you do not want to use the app as a geopresence sensor and do not want to grant locaiton permissions to the app)</big>
| |
− | | |
− | <big>When configured correctly, the presence status of your Hubitat mobile app device in your Devices list on Hubitat should update presence status (to "present" or "not present"), according to your settings. This device can be used to trigger or restrict automations that support using presence devices for this purpose.</big>
| |
− | | |
− | *
| |