How to check if sntp_init() completed?

[deadmetaphor]

I am trying to get the current time using the SNTP APIs in the SDK.

It works fine except that sometimes when I call

Code: Select all

sntp_get_current_timestamp()

it returns the time equivalent to "1970.01.01 00:00:00" and logs an error

Code: Select all

please start sntp first !

How to I test if sntp_init() has completed? Or, provide a callback perhaps?

[ESP_Faye]

Hi,

So sorry for the inconvenience.

Set a timer to check if current_stamp got a real timestamp, not 0 any more.

Code: Select all

uint32 current_stamp;
current_stamp = sntp_get_current_timestamp();


We will update our example in documentation.

Thanks for your interest in ESP8266 !

[deadmetaphor]

Thanks!

[derekh]

please consider adding a callback.

also when RTOS SDK will have SNTP support?

[PaulTsai111]

Hi Espressif :

I have encountered the same question , sntp_get_real_time got 1970 ..........

Can you show me where I can find espressif Documents ? about sntp_get_real_time usage ?

I hope to correct my code thanks you !!

[ESP_Faye]

Hi,

Please refer to the documentation "ESP8266 Non-OS SDK API Guide" http://www.espressif.com/support/download/documents.

Thanks for your interest in ESP8266 !

[PaulTsai111]

Hi Espressif :

About the usage of testing the sntp I have changed to the api provided example way to do.

The results still shows sntp start first !

Does this sntp api should first connect to router ?

because connect to server right ?

[ESP_Faye]

Hi,

Yes. SNTP is getting time info from internet, it needs to connect to router first.

[eriksl]

The current (as of 1.5.2) implementation has a nasty quirk though. Time is only fetched ONCE. As the internal clock of the ESP8266 isn't quite "real time", your clock will be off by 1-60 minutes every 24h. The concept of NTP is that it's run periodically to care for clock drift. I had to workaround this by stopping and starting NTP every now and then.