QSO-date and -time differs from lotw-last-upload

[dg9vh]

Describe the bug

QSO-date and -time differ unplausibly from lotw-last-upload-timestamp of callsign, see screenshot:

Maybe an timezone-issue of the timestamp? Do we need here to convert the used timezone on the ARRL-system to UTC?

[dg9vh]

To be a bit clearer: Here in this case, the QSO-partner confirmed a QSO visually on a time that was before the QSO happend :-)

[int2001]

GM Kim.
Misunderstanding. The Timestamp of the green "L" has nothing todo with your particular QSO. It doesn't show when (or if) your QSO was confirmed. It is just showing that the other Station is using LotW and his last upload.

That Data isn't generated out of your own QSOs, it's a service from LotW where Wavelog downloads that data and displays it. Usecase: You can see (before/during/after the QSO), if the User is active on LotW.

Doesn't mean that he confirmed your QSO (or others) at that time. On-Top: That data is sometimes a little outdated (ARRL-Problems).

HTH?

[dg9vh]

It is not a thing of conversion - I also have entries that differs more than 3 days into the past from the QSO-date... It looks like, that the last-update-timestamp from LOTW is not correctly updated when updating LOTW-data (via cron or manually). It seems that the state is saved at the moment, the QSO is logged and this data for this callsign is fetched for the first time.

[HB9HIL]

The "Last Upload" data provided by LotW is not what we would call "Live".

It's a CSV which is generated every few day's and served by LotW. So it can happen, that the User uploaded his Log, you got the confirmation but the Last Upload data is not updated.

Unfortunately we can't solve that in Wavelog.

https://lotw.arrl.org/lotw-help/developer-query-lotw-users/

[HB9HIL]

I transfered this issue to a discussion in Q&A

maybe other users have this question aswell :)