Closed ThomasWaldmann closed 3 years ago
https://github.com/ecocurious2/MultiGeiger/issues/410#issuecomment-841680073
as seen there: it can take > 20s for NTP to establish the correct time (if a network connection can be established, which is not necessarily always the case, the MultiGeiger could be without WiFi, just using LoRa or BT).
currently, we just live with the wrong time until NTP has worked.
the alternative would be blocking (by calling wait_ntp
) until we have the correct time.
decision from meeting: we do not want to block waiting for ntp, so the wait_ntp code is not needed and can be removed.
there's an implementation, but we are not calling it.