Radio connection timed-out

[on4dgt]

I don't know if it's a bug or a misconfiguration somewhere.

My CloudlogCAT shows: localtime -1 Radio interface shows: localtime -1 datebase entry shows: localtime -1

live QSO shows: Radio connection timed-out: OmniRig 1 data is 60 minutes old.

catcontrol works but the "Radio connection" message won't disapear

pc set to localtime Linux server set to localtime

[magicbug]

Can you confirm your running the very latest codebase?

[on4dgt]

I am Peter. the cloudlog.sh returns "Already up-to-date"

[KE8AKW]

Can confirm I am having this issue as well. Cat control works fine but the radio connection timeout message wont disappear in Cloudlog. Everything is up to date.

[m0urs]

I updated today to the most current version and I now have that message as well. Did not appear before the update. CAT control works fine for me also.

[KE8AKW]

I believe this might be a issue with CloudLogCAT. In the bottom part of CloudLogCAT it says something like "Successfully synced with CloudLog @( current time). For whatever reason, it is showing for me 3 hours ahead hence forth why we are getting this data is old error in Cloudlog. Im not sure where CloudLogCAT gets its time from so don't know how to fix. @magicbug

[m0urs]

This is not the case here. As soon as I change e.g. frequency on my transceiver, Omnirig is updating it and in CloudLogCAT the "Last Sync" is also updating. Nevertheless I get the message

Radio connection timed-out: OmniRig 1 data is 120 minutes old.

in the Live QSO entry of Cloudlog even with Version 2.

Everything is working as expected, it is just this annoying message.