02-15-2018
12:46
- last edited on
02-16-2018
14:52
by
AlessFitbit
02-15-2018
12:46
- last edited on
02-16-2018
14:52
by
AlessFitbit
Fitbit Update 2/16/18 -- Since our engineering team confirmed this issue was resolved yesterday 2/15, we're going to close this thread from further discussion. Thanks to everyone that reported this here on the Forums. We appreciate you taking action and glad there was a speedy resolution.
See you around the boards!
Update 2/15/18 (Part 2) -- Our engineers have reported that the issue should now be fixed. I recommend giving your Blaze a quick restart and then try changing to the Zone clock face again. Let me know how it goes!
Update 2/15/18 -- Thanks to all of you who have reported your experience trying to change to Zone Clock face on Blaze. I've merged all relevant threads here to keep things tidy.
At this time, I recommend avoiding the Zone clock face until we remedy the issue. For those of you who are seeing the 'X' on your Blaze display after attempting to change to the Zone clock face, please do the following to get back to a working clock face:
I've flagged this issue to our engineering team who will investigate. When I hear something new, I'll update you with the latest. I appreciate your patience and please update the thread if the above workaround doesn't get rid of the X on the display.
02-15-2018 18:07 - edited 02-15-2018 18:12
02-15-2018 18:07 - edited 02-15-2018 18:12
Good work
02-15-2018 18:11
02-15-2018 18:11
Part 2 was a good job on your part. Great to finally fix the issue. Good day!
02-15-2018 22:08
02-15-2018 22:08
Thanks for trying Bonnie!
Its interesting as I am in the UK having the same issue - it has to be a software glitch in the device.
02-15-2018 23:40
02-15-2018 23:40
Thanks I can confirm I now have Xone proudly displayed once more 👏👏!
i didn’t actually restart I just changed the face to zone and synced and it worked straight away!
02-16-2018 00:11
02-16-2018 00:11
Hi Misteree13
Its been fixed, well mine has, all back to normal with Zone face.
Blaze - Runner
02-16-2018 04:41
02-16-2018 04:41
Thank for reporting the problem and trying to convey to the Fitbit rep it’s a multi person problem... man what a hassle! I will report my detailed sleep log was back to normal last night. (I haven’t checked the Zone click face yet to see if I can use). Hopefully it all gets fixed soon 😊
02-16-2018 05:34
02-16-2018 05:34
After restart today the zone face came back.
02-16-2018 07:13
02-16-2018 07:13
Thanks! I tried changing it as soon as I saw these messages & I'm glad to say it's working now. Thanks for the update Blaze Runner and thanks for the attention, Fitbit.
02-16-2018 10:15
02-16-2018 10:15
Thanks Calros. Please also raise the concern about sleep data being basic.. it was affected exactly from the day when zone clock face flipped to original.. hope it is fixed.. I like sleep insights...
02-16-2018 11:13
02-16-2018 11:13
I tweeted them and this works
Thanks for reaching out, Mickey. If you haven't done yet, we suggest that you try to change your Blaze's clock face to a different one in the meantime: . Once done, please change it back to your preferred clock face. Don't forget to sync your tracker after each change. Keep us posted.
02-16-2018 12:50
02-16-2018 12:50
Zone Face is back! YEY!
02-16-2018 12:51
02-16-2018 12:51
The zone Face is back!
02-16-2018 14:05
02-16-2018 14:05
02-16-2018 14:53
02-16-2018 14:53
Since our engineering team confirmed this issue was resolved yesterday 2/15, we're going to close this thread from further discussion. Thanks to everyone that reported this here on the Forums. We appreciate you taking action and glad there was a speedy resolution.
See you around the boards!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.