Skip to content

NTP Settings

Screenshot

NTP Settings

Settings / Parameters

NTP Configuration

OpenDTU needs a proper synced clock to start fetching the inverter. (Every request contains the time. This synchronises the clock in the inverter at the same time. This is particularly important for the event display.)

Time Server

Hostname or IP address of your NTP1 server. The default value is ok unless your WiFi does not provide access to the internet. In this case you have to enter your own NTP server (mostly the IP of your router e.g. 192.168.178.1).

Timezone

Select the city or timezone you are in. NTP1 deliver the current time as UTC2. The timezone is used to calculate your specific current time.

Timezone Config

This information shows how the time zone is interpreted internally. It contains information regarding offsets to UTC2 and also regarding DST3.

Location Configuration

The location coordinates are required to determine the sunset and sunrise. The sunset type adds an offset to that value. This is used e.g. to stop polling the inverter at night.

Latitude

Latitude of the location of your inverter in degree.

Longitude

Longitude of the location of your inverter in degree.

Sunset type

There are differnt "Sunset types" which add different offsets to the calculated time. The following values are possible:

  • Standard dawn (90.8°)
  • Nautical dawn (102°)
  • Civil dawn (96°)
  • Astronomical dawn (102°)

For some locations there might be even no sunset / sunrise because the sun shines everytime or never. See here for further explanation.

Manual Time Synchronization

Current OpenDTU Time

Shows the current time of the ESP MCU. This value is used for all further calculations.

Current Local Time

Shows the current time detected from your web browser.

Synchronize Time

Press this button to manually synchronize the ESP time with your local time. This can be usefull if no NTP server is available.

Note

Keep in mind, that the time gets lost after a power cycle. Also note, that the time accuracy will be skewed badly, as it can not resynchronised regularly using a NTP server and the ESP32 microcontroller does not have a RTC4.