User:Weegeeweeg

2026-04-07T04:42:30Z

Weegeeweeg: Created page with "I don't like saas. I pay exactly $0.00 a year in saas fees. Copying bytes is free. Server upkeep costs aren't my problem. My hardware (Fitbit Surge) was remotely disabled by Google LLC, which owns Fitbit LLC. It's likely running freeRTOS 8.x and Nordic SoftDevice S130 v1.0. It cannot tell the time because their servers silently reject its oauth1 authentication due to their endpoints expecting oauth2. They never released a firmware update for the device except to patch a..."

I don't like saas. I pay exactly $0.00 a year in saas fees. Copying bytes is free. Server upkeep costs aren't my problem.

My hardware (Fitbit Surge) was remotely disabled by Google LLC, which owns Fitbit LLC. It's likely running freeRTOS 8.x and Nordic SoftDevice S130 v1.0. It cannot tell the time because their servers silently reject its oauth1 authentication due to their endpoints expecting oauth2. They never released a firmware update for the device except to patch a memory readout that would have allowed me to take control of the device and actually use it since they abandoned it as soon as they launched it, like every other product they have launched. I just wanted to use the thing that cost me like 3 hundred bucks and was advertised as a "Super Watch" and really was at the time but they crippled the hell out of it and left everybody without any way to bypass their servers which abandoned support for it. Now I've become hyper-aware of every transaction and all of the lies being sold with each new product that contains firmware that depends on some private endpoint that will be tampered with. Companies should not be allowed to distribute products whose core functions depend on some computer somewhere else running software you'll never see.

It's really unfortunate that industries have evolved from creating artificial scarcity on machine code to creating artificial scarcity on server authentication. Copying bytes is free. Server upkeep costs aren't my problem.

Fitbit

2026-04-07T01:48:50Z

Weegeeweeg: this company is total scum

{{Stub}}
{{CompanyCargo
| Founded = 2007-03-26
| Industry = Activity trackers
| Logo = Google Fitbit logo.svg
| ParentCompany = Google
| Type = Subsidiary
| Website = http://store.google.com/category/watches_trackers
| Description = Subsidiary of Google that sells fitness tracking smartwatches. Devices have had faulty strap connectors, burned users, and had functionality removed.
}}

'''[[wikipedia:Fitbit|Fitbit]]''', now a subsidiary of [[Google]], is a company that produces fitness tracking devices, some of which also function as smartwatches. They acquired [[Pebble]] in 2016, and produced the Ionic, Versa series and Sense series with Pebble-like SDKs, OSes and features, but skipped out on a lot of the openness and consumer freedom that Pebble users enjoyed. Most of the anti-consumer practices came following Google's purchase of the company in 2021.

==Fitbit Charge 3 / 4 Faulty Strap Connectors (2018, 2020)==
Unlike the Charge devices that came before and after them, the Charge 3 and 4 have plastic strap connectors that snap off from the device with regular use, this often happened in under a year. Fitbit was willing to provide replacement devices in many cases, but never admitted to this fault publicly.

==Music Limitations (2020 - 2023)==
Fitbit supported syncing music from your PC to your smartwatch to play offline. Supported devices for this were:

*Fitbit Blaze (2016)
*Fitbit Ionic (2017)
*Fitbit Versa (2018)
*Fitbit Versa 2 (2019)

With the release of the Versa 3 and Sense in 2020, Fitbit removed this functionality, instead mandating that users either use a paid Deezer / Pandora subscription to sync offline music to their device (with DRM), or control music playing from their phone.

With the release of the Versa 4 and Sense 2 in 2022, the remaining music functionality in the previous device was scrapped, and Google later added support for YouTube Music controls, requiring the user to have their phone nearby and a YouTube Premium subscription.

In 2022, Google shut down the necessary servers and software for syncing music to the older 2016 - 2019 devices.

In 2023, Google terminated Fitbit's partnership with Deezer and Pandora and disabled those apps on the relevant devices.

==Oauth update renders old devices unusable (2021)==
Legacy fitbit devices (Surge and prior) used oauth1.0 to connect to Fitbit's servers. The firmware embedded onto these devices gate core functionality like setting the time, setting the clock face, logging heartrate data, setting alarms, etc. behind this authentication process. The company leaves no way to use the devices without authenticating and uploading data to their servers and having that data fed back to your client which is no longer possible on these watches due to them updating endpoints to oauth2.0, making the Fitbit Surge the "Super Watch" that could only correctly tell the time for less than a decade.

==Fitbit Ionic Recall Program (2022)==
The Fitbit Ionic was the first device to debut Fitbit's new Pebble-like SDK called "Fitbit SDK 1.0" and it released in 2017. Fitbit reportedly ignored issues of the device burning on people's wrists for 5 years until their voluntary recall program in 2022. If a user enrolled in this recall, they would be offered varying refund options, and their device, regardless of functionality, would be remotely bricked by Google. If a user did not enroll into the recall, their device would remain as-is, but without any new security patches for it's Fitbit OS.

==Fitbit Versa 4 / Sense 2 issues (2022)==
The Fitbit Versa 4 and Sense 2 were successors to Fitbit's previous smartwatches, but missed out on a lot of the features that made them "smart" despite using the same SoC as it's predecessors, likely in attempt to make them less competitive to the Pixel Watch.

===Lack of communication with developers===
Every Fitbit smartwatch since the Ionic was released alongside SDK information for developers until these two. Google refused to give clarification on development tools for months, while silently marking selected popular clockfaces as installable on these new devices. Developers found [https://github.com/cmengler/fitbit-spotify-hr-versa4 workarounds], and eventually Google silently released Fitbit SDK 7.0 in beta which was capable of building for these devices, albeit without documentation. If you attempt to submit an app compatible with these devices to the Fitbit Gallery, it will be rejected, however clockfaces are allowed. You can still sideload apps with this SDK if you know what you're doing. As of August 2025, the relevant SDK is still:

*In a "beta" state
*Only works with a deprecated version of [[wikipedia:Node.js|Node.js]]
*Has no documentation

===Missing features===
Many features were removed from these devices, including but not limited to:

*The ability to switch between clockfaces on device
*The ability to play music on device or control music from your phone (You may still do the latter if you are using YouTube Music Premium)
*Bluetooth headphone pairing

Users also reported the software on these devices to be buggy and incomplete.

==Fitbit Studio Shutdown (2023)==
In 2023, Google shut down Fitbit Studio, an online development tool for Fitbit applications and clockfaces. Many developers did not hear about this until it was too late and lost their source code, Google briefly re-opened the site to give developers a last chance to download their code, but many still did not meet the deadline. Following this shutdown, developers were required to run a deprecated version of Node.js on their system to continue building software.

==Fitbit Gallery Shutdown in EEU (2024)==
Following failure to comply with local laws, Google delisted all third party software for Fitbit smartwatch users within the EEU.

==Fitbit Dashboard Shutdown (2024)==
In 2024, Google announced that they would no longer be offering the ability for people who bought Fitbit products to access their servers from their computers (Fitbit Dashboard desktop client and Web client). All services provided can now only be accessed from a mobile app.

==Fitbit Sense and Versa 3 Battery Performance Program (2025)==
(See full article: [[Fitbit Sense and Versa 3 Battery Performance Program]])

Google released a program select Fitbit Versa 3 and Sense devices where they would be forcibly updated to a version of Fitbit OS 5 with limited battery performance. Affected users were offered $50 from Google.

==Google Assistant Shutdown (2025)==
Following Google's focus on Gemini, Google quietly deprecated Google Assistant for devices they considered "legacy". This included Fitbit Versa 3 and Sense devices that were still being newly sold just over 2 years ago, which were now only capable of using Amazon Alexa. Around this time, Google launched a marketing campaign showing their new Gemini assistant on Pixel Watch devices.

==References==
{{Reflist}}
[[Category:{{PAGENAME}}]]

Consumer Rights Wiki - User contributions [en]

User:Weegeeweeg

Fitbit