Comet issues never end, this time the system clock got stuck in July.
I've been living on the other side of the globe from my home network since this time last year, and my brother was kind enough to get me this device to keep me connected. Unfortunately it hasn't been stable in the slightest. I'm a programmer and ran an IT department for almost a decade, and I've learned to mostly just leave things alone/stock, they either work or they don't. The comet has been *just* on the edge of "it works" or "it doesn't" the whole time.
The most recent issue is thus: It fell off tailscale three days ago. I remoted into another PC on that network [having two ways in has unfortunately become mandatory with this kvm], ssh'd into the kvm, and found its system clock was stuck in July. Well no wonder tailscale won't connect. I managed to update the clock via pinging google with date -s, which makes me wonder, why the hell couldn't it update its own clock? I want to say this thing's convenience features outweigh having to troubleshoot it every other month, but it truly has been one thing after another. I've never had *any* internet connected device just fail to update its clock before.
Maybe this kind of bad review will just get removed from the sub, but I hope that 1. people will read this and know what they're getting into and 2. the team behind the device will have another data point to convince their leadership to figure this shit out a little better.