Fitbit OS 3.0 - Versa Firmware Release (32.33.1.30)

[AlessFitbit]

Fitbit Update 1/10/19: 

Hi all!

Big thanks to everyone for your feedback on the release of Fitbit OS 3.0!

Since the majority of users have now updated to 3.0, I will be closing this thread from further comments to help keep our Community discussions on-topic.

If you are experiencing an issue outside of the firmware update process, I invite you to start a new thread on this forum and we will be happy to assist you there. 

Thanks again and happy stepping! 

---

Fitbit Update 12/26:

Hey, everyone! We're aware that some of you may have noticed a fast battery drain on your Versa watches after completing this firmware update. Our team is investigating the root cause of this issue and whether it was caused by this update or other factors are involved. 

In the meantime, if you're experiencing this problem please try a restart on the device then consider switching to a Fitbit made clock face! Many 3rd party clockfaces (especially those with animations) are known to use up more battery. If you try this out and are still seeing a fast battery drain, we can connect you with Customer Support for next steps or you can reach out to them and create a case. 

We look forward to getting you all back on track! 

---

Fitbit Update 12/22: 

We've released Fitbit OS 3.0 out to 100% of users. Please make sure you have the latest version of the Fitbit app (2.84) before downloading the newest firmware. 

We're excited for you all to have the newest Fitbit OS, but please let us know if you have any questions about this update. Happy Holidays, everyone! 

---

Hi, everyone!

I am excited to announce the release of Fitbit OS 3.0! (Firmware Version: 32.33.1.30)

We've started to roll out this update and it's currently out to 20% of Versa users. This is a progressive rollout, and all Versa users can expect to have it soon. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed.

WHAT'S CHANGED?

Please check out this help article to see what's new in this update.

HOW DO I UPDATE?

Step by step instructions for updating your Versa can be found here. We recommend updating your Versa over a home Wi-Fi network as this can greatly reduce the time it can take to get set up. For more information on connecting your Versa to Wi-Fi, check out this article.

If you run into trouble updating your Versa, please follow these steps:

1. Restart the watch. 
2. "Remove" the watch from your account inside of the Fitbit app.  
3. "Forget" the watch from your phone's Bluetooth settings (along with any other Fitbit devices paired to your phone)
4. Try the update again.  

*If anyone isn't seeing the TODAY app after updating, please try the following:

1. Make sure you're running the newest version of the Fitbit app (version 2.84) 

2. Connect to Wi-Fi in the Fitbit app, plug your Versa into the charger and let it sit. This will automatically update the Today app. 

Looking forward to hearing everyone's feedback on the latest release. If you have questions, please let me know in this thread!

[Susie2057]

So far the charge seems to be fine today. I turned off the heart rate under today. The class ck face I have is a third party one only because it is the only one I can see with out my glasses being on. It’s an anolog clock with clearly visible hands. I can’t read any of the digital ones without glasses. 

[oma7144]

Thank you lenny4d for taking the time to answer here! Still in my view it is up to Fitbit to come up with an open communication what the issue is and how to resolve it. At least to regain trust. So, I agree anything here is speculation.

A good strategy on Android devices is a clean installation. The OS 3.0 firmware update does not force it and Fitbit do not recommend it. So, this might be hard work for the runtime compiler with some funny results in specific cases. The issues with thrid party apps will be gone when compiled with the new SDK 3.0.

In my view the serious issues are driven by the hardware abstraction layer. Fitbit knows best which different components (for market availibility or cost or whatever reasons) are assembled in which production lot. As there is not S/N specific firmware there must be a common kernel.

From this perspective it could be there is no high battery drain as the table in the kernel simply does not work for a specific PMU and the kernel shuts down the clock at 5 % although the battery is still at a good voltage level.

And for sure a firmware can damage the hardware. For example when a hardware component related firmware is flashed by the kernel itself. Wrong firmware and the hardware component is dead. Consequently the clock too.

In my case I just reported a different counting (sensor) behavior after the update form OS 2.1 to OS 3.0.

Just my two cents.

Cheers.

[lenny4d]

@SunsetRunner  "mention your problem but also the serial number of your Versa. Each and every Versa has it's own unique serial number." --- where is it listed? 🙂 It is not on the back of the Versa (not with mine), not under settings > about either. Neither in the app??

Under settings > about > regulatory info it says

Model FB505

And then a whole lot of numbers, presumably related to all the kind of different regulations that apply (wifi, bluetooth, you name it).

There is also a FB504, which is the model without NFC.

@oma7144Many thanks for your feedback, good points. "The issues with third party apps will be gone when compiled with the new SDK 3.0." --- yes, but in the meantime MANY apps will remain idle and (possibly) disfunct. It would have been "trivial" to split the apps per OS and show what they are compiled for, and offer the appropriate selections. A bit like Google Play. Google play will not show any app that doesn't work on your device, or will show it but says it won't work and you can't install it. 

[SunsetRunner]

Sorry, forgot to mention where you can find it. You'll find it on the box. On the bottom of the box is a barcode with numbers underneath it. 

[BlueCC]

After days of my Versa not working and doing nothing but backlight itself at random, I contacted their customer support and they determined my Fitbit is beyond repair and they are sending a replacement. I’m pleased they are replacing it, but I am worried that when I set it up on the new OS that I will continue to have problems. 

For those of you who are setting up a new Versa, are you running into any issues?

[lenny4d]

@SunsetRunner... "You'll find it on the box. On the bottom of the box is a barcode with numbers underneath it. " 

If life was so simple, presuming one still has the box in the first place!! : with me there are two barcodes! (on the same sticker that is on the box that is INSIDE the main wrapping). One UPC-A barcode (8-16137-02904-9) which is the general product bar code for the Versa (see also https://www.barcodelookup.com/816137029049) and one smaller (and difficult to read manually) long Code39 barcode (20992FBDE24A) - I presume the latter might be the serial number that you refer to (but didn't mention specifically).

NOW, this thread: https://community.fitbit.com/t5/Charge-HR/How-to-find-the-serial-number-to-the-Charge-HR-without-original-packaging/td-p/1032832 says something almost the same, namely the device ID (S/N) is in the URL on fitbit.com, for me it is 4ae2bd2f9920, which is the same as the 2nd bar-code except one is little endian, the other bigendian hex number. Hallelujah.

The good thing then is that you really don't need to give fitbit your serial number because they have it anyway, as the tracker and S/N is uniquely coupled to your account in the firstplace. Good to get that out of the way!

[lenny4d]

@BlueCC  There is no backlight, no idea where you keep getting that from. Maybe the display lighted up in a way resembling a backlight. But there is none.

Indeed, if you see something that looks like a backlight, something with the display is broken (either physically or the display controller), just like some people get a striped pattern. Good you get the replacement! Shhhit happens, but at least the customer service was not "broken" 🙂

[GRAVESlikedead]

Since the update, I am using the watch face called STATS. The year keeps cycling and can’t figure out its 2018. It keeps going through all 100 years of options until my battery dies which takes about 6 hours. Maybe your bug is with the year.

[mingke]

@GRAVESlikedead
I use STATS too but do not have battery problem and Year problem

Sent from my Huawei Mobile

[Salcy]

So by 6am my battery was at 29%.  It is now 3pm and my battery is 19%.  No jogging or use of bluetooth headphones.  I charged it on 12/23 late at night.  Had two 30 minute jogging sessionz since the, using assisted gps and bluetooth headphones.  So the Versa will not break the 3 day mark... FitBit what should I do???  Should I live with it or tey to address it with you you?

[SunsetRunner]

Hi, regarding this: "NOW, this thread: https://community.fitbit.com/t5/Charge-HR/How-to-find-the-serial-number-to-the-Charge-HR-without-ori... says something almost the same, namely the device ID (S/N) is in the URL on fitbit.com, for me it is 4ae2bd2f9920,", tried this also but I see only my device and no numbers at all. Regarding your remark that Fitbit is aware of the S/N of my Fitbit, how do they know that when I bought one online (I live in the Netherlands)?

[AlessFitbit]

Fitbit Update 12/26:

Hey, everyone! We're aware that some of you may have noticed a fast battery drain on your Versa watches after completing this firmware update. Our team is investigating the root cause of this issue and whether it was caused by this update or other factors are involved. 

In the meantime, if you're experiencing this problem please try a restart on the device then consider switching to a Fitbit made clock face! Many 3rd party clockfaces (especially those with animations) are known to use up more battery. If you try this out and are still seeing a fast battery drain, we can connect you with Customer Support for next steps or you can reach out to them and create a case. 

We look forward to getting you all back on track! 

[wiseman13]

FYI I have done a factory reset and that has not helped battery life either. I will switch over to a fitbit watch face and test that next.

[BlueCC]

Backlight, screen lighting up and staying black, a dark glow...does it really matter?  The fact remains it worked fine until I installed the newest OS, then it did not work at all. The display did not display. It showed nothing but an occasional black lit screen that would turn on at random when it was sitting on a table beside me. 

Many people are reporting the same issue so they need to figure out a fix or they’re going to be sending out a lot of replacement devices. I am lucky mine is still under warranty and was purchased through an approved vendor so mine is being replaced. Many others having the same issue will be out of luck if their warranty has expired. 

[Shetona]

Ok

Sent from my Samsung Galaxy smartphone.

[oma7144]

Yeah, love my Versa and need it back working like before. When it is damaged by the firmware update I should be fine with an replacement.

Cheers.

[lenny4d]

@BlueCC"Backlight, screen lighting up and staying black, a dark glow...does it really matter? "  ---- YES, if you want the community to understand what you mean and what really your problem is, it matters a lot!". As there is no backlight people get confused what type of problem you are trying to describe. Good you get a replacement!

@SunsetRunner"tried this also but I see only my device and no numbers at all. Regarding your remark that Fitbit is aware of the S/N of my Fitbit, how do they know that when I bought one online"   --- You get it when on fitbit.com you click on your device under the toothwheel in the top-right corner on the webpage. This takes you to your Versa page with an URL that looks like https://www.fitbit.com/settings/device/tracker/4ae2bd2f9920   When you configure your device for the very first time the device sends its serialnumber to the server, a.o. Since fitbit knows your username, it also knows your trackers and the serialnumbers for each tracker. And they probably have a manufacturing/batch database from which they can get further specifics if this turns out to be relevant.

FYI (and somewhat off-topic): There is also an unique key associated with the serial number that is used by the mobile app and the tracker to identify each-other (authenciate) so the app knows it is talking to the correct tracker, and the tracker knows it is talking to the correct mobile app/user. That's not relevant, but I thought I mention it for your interest.

[JoeSchwartz]

I'm using the Windows 10 app (version 2.39.1779), and although it successfully updated my Versa to firmware version 32.33.1.30, my Today app seems to be stuck on the old version -- the only tile options I see in Settings are Core Stats, Hourly Steps, and Heart Rate. Is there a way to update the Today app with Windows 10?

[SunsetRunner]

Hi, the way to get your Today app to function as it should, is twofold:

1. Go to your Fitbit app - apps - my apps. you will see the Today option. see whether it needs updating (right side of the screen).

2. Put your Versa in the charger and connect it to your PC and let it rest there for at least 2 hours. After that time your Today app shoukld be updated automatically with the seven activity possibilities to track.

Good luck.

[Fbuonvino]

Has anyone noticed heart rate readings are a lot higher since the update on the Versa?  Mine is constantly 15-20% higher.