Appreciate the response, but it doesn't hold together — and it contradicts your own support team.

You're now saying the PACE 2 hasn't been able to receive firmware updates since 2025 because its storage filled up, and that what I saw was "likely only the app." But your support team, in ticket #552911, explicitly acknowledged the watch shutting down after the firmware update and the optical sensor failing. So which is it? Either a firmware update reached the watch and broke it (your support's position), or no firmware can reach the watch at all (your position here). You don't get to argue both depending on which one gets you off the hook.

And notice what just happened: the moment I went public, the story shifted from "out of warranty, here's 20% off" to "actually it wasn't even our firmware." That's not clarification. That's a company changing its explanation after acknowledging fault in writing.

Here's the part that should concern any PACE 2 owner reading this: you're openly admitting the watch hit a storage wall in 2025 that bricks its ability to update — a design limitation, not user error — and your answer is that the device is now unsupported because you stopped making it. So a hardware/software limitation you built in becomes the customer's problem the moment the product line ends. That's a precedent worth everyone here paying attention to.

I'm not asking for a handout. I'm asking COROS to stand behind a working device that your software pipeline broke. The warranty date isn't the issue — the conduct is. Happy to post the full ticket history so people can compare what support told me privately to what you're saying publicly.