diff --git a/FAQ.md b/FAQ.md
index 03127788..0896ebb3 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -31,7 +31,7 @@
  - [Power monitoring shows wrong values](#Power-monitoring-shows-wrong-values)
  - [Power monitoring resets Energy Today mid-day](../issues/5571)
  - [Sensors don't show values](#Sensors-dont-show-values)
- - [Timers trigger at wrong time](#Timers-trigger-at-wrong-time)
+ - [Timers trigger at the wrong time](#Timers-trigger-at-the-wrong-time)
  - [Auto-discovery in Home Assistant doesn't work](#Auto-discovery-in-Home-Assistant-doesnt-work)
  - [Why is my changed configuration not loaded?](#Why-is-my-changed-configuration-not-loaded)
  - [How do I invert the output of the green LED on the Sonoff Basic so the LED is on when the relay is off?](#How-do-I-invert-the-output-of-the-green-LED-on-the-Sonoff-Basic-so-the-LED-is-on-when-the-relay-is-off)
@@ -279,8 +279,16 @@ In case you're using a template you created yourself or found in our Templates R
 Make sure your sensor is properly wired and the GPIOs assigned. 
 Your vanilla `sonoff.bin` doesn't have complete sensor support. Make sure you've installed sonoff-sensors.bin that support the largest number of sensors. Some sensors require enabling in the code and compiling your own binary. See [Builds](Builds) for a comprehensive list of supported components.
 
-### Timers trigger at wrong time
-Check if Tasmota is updating its device time over the preconfigured NTP servers and that the time matches your local time. If not, adjust your [`TimeZone`](Commands#timezone) or Daylight Saving Time 
+### Timers trigger at the wrong time
+Check the log in the web UI Console to see if the device's time is set correctly. There are two elements to setting the time: 1. obtaining the UTC time, and, 2. local Daylight Saving Time policies.  
+
+Check the information about your router's features. If the router provides an NTP server, be sure to configure it properly. If the Tasmota device receives its IP address via DHCP from the router, Tasmota will request its time sync from the router's time server. This is managed by the Arduino core, not Tasmota. Therefore, if the NTP server on the router is not configured, or configured improperly, the time on the Tasmota device could be wrong. If the router does not have a time server, this is not the problem.  
+
+If you cannot configure your router's time server to the correct time (e.g., a router provided by your ISP with no access to administration functions), you will need to set a static IP address on the Tasmota device. If the device does not request its address from a DHCP server (i.e., uses a static IP address), the time sync request is forced to `NTPSERVER1`. If can't connect, it tries `NTPSERVER2`. And finally `NTPSERVER3`. Ensure that these parameters are set appropriately and that the device can reach at least one of these time servers. You may want to consider setting up an NTP server locally. As long as the computer is able to set its time at some point from an Internet time server, this computer can serve as an NTP server for your Tasmota device(s). This can be the same computer that hosts your MQTT broker or home automation hub.  
+
+You must also set the [`TimeZone`](Commands#timezone) and Daylight Saving Time policies ([`TimeDST`](Commands#timestd)/[`TimeSTD`](Commands#timedst)).  
+
+If you have timers that use the sunset or sunrise times, you must set your [latitude](Commands#latitude) and [longitude](Commands#longitude) in order for these times to be calculated correctly for your location.
 
 ### Auto-discovery in Home Assistant doesn't work
 The `sonoff-basic.bin` firmware binary (which comes packaged with Tuya-Convert) does not support auto-discovery. Please upgrade to `sonoff.bin` or a similar firmware variant that supports this feature.