After working correct for over a year in the last few days my TOTP is incorrect. Before this happened the TOTP worked for a few times without me using “onlykey-cli settime” and I’m still not getting the NOTSET message when using the onlykey without setting the time. But either way, with or without using the “onlykey-cli settime” I’m getting an incorrect 2nd factor TOTP. Is there a solution for this?
OnlyKey does require the correct time, this is set by the Onlykey app, the web app https://apps.crp.to or the CLI. If you want to test the output of OnlyKey compared to actual you can do that on the site here with a test value https://totp.danhersam.com/
The problem was I was leaving the onlykey duo plugged in after shutting down the pc then restarting. I think it should work while doing this but the solution was to just unplug the onlykey and replug it in AFTER restarting the pc.
That shouldn’t really be a problem. I’ve always had my OnlyKeys plugged in for years. After a reboot I don’t even have to re-enter the pin. (Only after a cold start.)
I’m on PopOS 22.04. What operating system are you using?
See my Profile Picture 
Debian GNU/Linux
Have you installed the UDEV rules? Should be automatic since OnlyKey v5.3.3 .deb.
Sometimes time is out of sync when the laptop has been on for several days. Then press Button 3 for longer than 5 seconds and reconnect (Enter PIN).
EDIT:
Is this possible on the DUO? I always use the original ones. The DUO is in the drawer as a backup. I actually only got it to support Tim’s Kickstarter campaign.
It’s a new desktop pc I’m having the trouble with. I’ll check the UDEV rules when I’m at that location in a few days but I think I did install them. And I’m pretty sure I’m on Onlykey v5.3.3.deb. It does work fine except for the leaving plugged in when I shutdown.