Page 1 of 1
NTP seems not to survive reset - either manual or from a crash
Posted: 30 Jun 2017, 12:01
by nigelbe
Using v2.0.0-dev10 from the binary releases on sonoff (1 meg) or Wemos d1 mini (4 meg).
I am keen to use NTP and I have tried various NTP servers pool.ntp.org, uk.pool.ntp.org and my local network NTP server either as hostname or IP address.
It seems to be very fragile. is it not checked on boot?
Re: NTP seems not to survive reset - either manual or from a crash
Posted: 30 Jun 2017, 12:10
by papperone
Can you provide more details, with such post it close to mission impossible to help?
Here NTP works flawlessy on all release I do have for DEV and TEST environment, from R148 to 2.0-dev10.
I have several Wemos D1 Mini, Sonoff single and personal development boards.
All of them are setup to use "pool.ntp.org" and all works perfectly (just rebooted 3 test units and all of them are back up with right date/time almost instantly, so I can failry state it's not ESPEasy issue).
G.
Re: NTP seems not to survive reset - either manual or from a crash
Posted: 30 Jun 2017, 13:19
by Shardan
Hello Nigel,
Same as with papperone, i use a bunch of several ESP's from WeMOS and nodeMCU for testing, sonoffs and a lot of selfmade devices with embedded ESP.
All devices work properly on my NTP home server (Raspberry B / Raspian Jessie / DCF-Receiver + pool.ntp.org as time source).
As a lot of your devices seem not to work the reason might be somewhere in your WiFi.
But without a lot of more info it's impossible to say.
Regards
Shardan
Re: NTP seems not to survive reset - either manual or from a crash
Posted: 30 Jun 2017, 15:26
by nigelbe
Thanks all,
I think the trouble is non-empty flash storage confusing everything. I'm working on it now.
Re: NTP seems not to survive reset - either manual or from a crash
Posted: 30 Jun 2017, 16:10
by nigelbe
I'm almost certain now that the trouble was having Use SSDP: selected.