Closed l3nticular closed 3 years ago
Since of many problems (generated from routers which do not correctly provide the NTP server via DHCP) Tasmota do NOT use this way anymore. NTP servers are set in Tasmota (only).
Closing this issue as it has been answered.
See Docs for more information. See Chat for more user experience. See Code of Conduct
Thanks! Glad to know that it was intentional behavior.
This seems to conflict with https://tasmota.github.io/docs/FAQ/#timers-trigger-at-the-wrong-time but matches the behavior I've been observing. Should the documentation be updated?
It'd also be nice to have a configuration setting to use the NTP server from the DHCP response, to avoid to hardcode the server in the configuration.
@nferch Thx! Outdated info removed.
Since of many problems (generated from routers which do not correctly provide the NTP server via DHCP) Tasmota do NOT use this way anymore. NTP servers are set in Tasmota (only).
Wow, this should be a sticky/FAQ somewhere? Was trying stuff since weeks to get this running :-D
@totti4ever We have Tasmota discussions for such stuff. Normally you get a answer in a few hours. If we stick any relevant info, we would have a forrest of sticked informations. The info is there. Changelog
PROBLEM DESCRIPTION
A clear and concise description of what the problem is. One Tasmota unit does not attempt to use the NTP server listed in the DHCP option. Manually setting NTP server with "NTPServer1 10.70.70.1" works fine.
Today I set up a fresh D1 mini with Tasmota on my IoT VLAN. The other 4 Tasmota devices on this VLAN get the NTP from DHCP just fine (these are all running 8.5.0). I put 9.3.1 on the new device and it's not able to get the NTP server from the DHCP option.
DHCP+DNS server is dnsmasq running in a Docker container on a Pi (this is a standalone dnsmasq instance for the VLAN, not PiHole).
NOTE: After writing but before submitting this Issue, I completely erased the failing unit and flashed 8.5.0 with Tasmotizer. I was able to see this function correctly work on this unit. I then completely erased and flashed 9.3.1 and immediately the unit failed again (no configuration loaded, just WiFi SSID+Password manually entered).
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
There are old closed issues that seemed to have been due to malformed DHCP options. Here it's working on one version of Tasmota and not the other.
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:From failing unit + dnsmasq log: failed.txt
From working unit (v8.5.0) + dnsmasq log: working.txt
TO REPRODUCE
Set up DHCP server with IP address of desired NTP server (which happens to be the same as the DHCP server). Connect an 8.5.0 unit and a 9.3.1 unit to the network. 8.5.0 unit works, 9.3.1 unit doesn't.
EXPECTED BEHAVIOUR
Unit should use the provided NTP server and not the FW defaults.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
See attached files