Hi!
I faced an issue with nRF Cloud Log. If I set CONFIG_LOG_TIMESTAMP_USE_REALTIME=y, I get wrong timestamps (2080 year..) in nRF Cloud Portal for all messages being logged.
I don't see any handling of CONFIG_LOG_TIMESTAMP_USE_REALTIME option in the nRF Cloud Log code. And it looks like it just handles both types of timestamps (uptime and realtime) the same way. So the resulting timestamp is "doubled" (1970 + 55 = 2025 year -> 2025 + 55 = 2080 year).
Or am I missing something or using this option in a wrong way?
My SDK version is 2.9.0.
My configuration contains:
CONFIG_LOG_TIMESTAMP_USE_REALTIME=y
CONFIG_NRF_CLOUD_LOG_BACKEND=y
This issue is currently not critical for our project.
Thank you!