Its been a year and I still seem to have the same issue. But I figured that perhaps someone else has some sort of idea why this may be happening. I am using a Mikrotik router, its 2.4 is set to 20mhz on ch 11 using "N" only and the OS2 is <1m away from the access point. Group key update is...

Having security off will definitely not work anymore. Best to follow the links to get your selfcare set up with an access password for your hotspot. Then add that same password to the OS2 and you should be in business.

Be VERY mindful of that approach. I did the same thing with my OS2 and my AT&T phone. AT&T does not differentiate voice packets from data packets and hence...there is no QOS on their network to make sure that your voice packets get priority through the network so expect dropouts here and the...

Good idea to TG4000 from the radio before going to the next TG you want to talk on. Or just do it from the OS2 web gui.

Sometimes people just key up for no reason, others key up if they are on a repeater that has that TG as a PTT TG and not static.

Also try another browser other than IE. The OS2 does not care much for it. I use Brave, FF or Chrome and it works. Sometimes a page refresh wakes it up too.

Hmmm, if you have the proper NTP server name and valid DNS addresses...other than the gateway address (which I believe must be your router), your OS2 should be on the internet just fine and your OS2 should get time and hitting the sync now should work.

If you go to the OS2 settings tab you can do a manual sync. I use us.pool.ntp.org and it works fine. If it cant resolve the URL then I would suspect you may not have the proper DNS server listed in the OS2 as well. Do you have your DNS set to something like 8.8.8.8??

Makes it somewhat confusing to see UTC from the OS2 and the rest of my devices show local time.

Will have to make do with that small inconvenience. Would be nice to see an option in a future release to allow the user to decide though

The OS2 local logs show EDT as they should and the time is properly set via NTP So why is my syslog server showing EDT+4 (UTC) timestamps? I dont see a way to change what the OS2 sends to the server as far as timestamping goes BTW all my other logs from my routers and raspberry pi's show local time ...