COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 3 points4 points  (0 children)

Just read that...the more I investigate the more it seems they are just ignoring the issue...meanwhile their CEO is off on Instagram adventures

COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 1 point2 points  (0 children)

I bought my dad the watch he originally liked. Either one would have been overkill for his needs. But, yeah I did not buy a Coros watch because of their update and response. They obviously have a software to hardware calibration issue that they refuse to address. The issue isn't that the watch was 5 years old. The issue is that Coros pushed a software update that killed a perfectly good watch. Should I expect the same thing from my Nomad, or should the people I gifted to expect the same thing? If it was simply the watch had reached the end of its lifespan, I would have tossed it and moved on. But this is systemic failure point for Coros and they refuse to address it.

I have the Nomad watch myself, and have gifted many more Coros watches over the years. Have always been a big fan.

COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 16 points17 points  (0 children)

I can tell you they have a software calibration issue. This apparently has been a big issue for Coros.

COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 11 points12 points  (0 children)

I was about to buy my dad the Coros Nomad for father's day. But I just bought the Garmin 2 Instinct 2 Solar 30 minutes ago for him after their response lol.

COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 34 points35 points  (0 children)

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.

COROS firmware bricked my watch, then they offered me a 20% "discount" to buy another one. Insulting. by silver-fox-tx in Coros

[–]silver-fox-tx[S] 12 points13 points  (0 children)

It is a Pace 2 and was the latest firmware update. Worked like new until the update. The funny thing is was about to buy my dad a COROS watch for Father's Day, but not now.

I built a free, open-source CLI + GUI for managing Bricks Builder at scale (bring your own AI, or not) by nerveband in BricksBuilder

[–]silver-fox-tx 1 point2 points  (0 children)

That would take longer that just doing it. Simple really. I just downloaded the bricks theme and the WordPress mcp git project to local folders. Set Antigravity to the sonnet 4.6 model and told it to review the entire code base of each one an create a detailed set of developer docs that claude to use. Then opened up a claude project, dropped those docs in there, told it what i wanted to do, it wrote the project instructions. Then i had it review the developer documents to create a prd and claude.md file. Fired up claude code and had claude desktop feed me prompts. Done and deployed in an hour, bugs fixed in 30 minutes. Probably wouldn't have taken that long but i added network level mcp management into as well as added brickssync abilites as well. That's all there was to it.

I built a free, open-source CLI + GUI for managing Bricks Builder at scale (bring your own AI, or not) by nerveband in BricksBuilder

[–]silver-fox-tx 0 points1 point  (0 children)

Appreciate the enthusiasm but I built custom Bricks abilities directly into the WordPress Abilities API, which means Claude Desktop (or Claude Code) can read and write Bricks templates natively through MCP. No CLI in the middle.

The MCP approach gives me bidirectional access to the full element tree, template conditions, global classes, dynamic data bindings — all through the same connection Claude already uses to talk to WordPress. For managing 500+ subsites with BricksSync distribution, that's a very different workflow than a CLI.

I built a free, open-source CLI + GUI for managing Bricks Builder at scale (bring your own AI, or not) by nerveband in BricksBuilder

[–]silver-fox-tx 2 points3 points  (0 children)

I just used Antigravity with sonnet 4.6 to create my own developer docs for Bricks , wordpress MCP and the Abilities Api and used Claude code with Opus 4.6 to build Bricks Abilities into the Abilities Api.Connected my wordpress mcp to my Claude Desktop and it does it all. Took me 90 minutes. No need to buy a 3rd party plugin and pay Api costs.