Known issues
beware : tech talk!
All issues below are the result of flaws in the firmware of your device. Some might already have been fixed and others will be fixed with the next firmware update (when your Fitbit app tells you it is time to upgrade your device).
Weather does not update regularly
Weather services are expensive. Therefore our clockfaces do not update weather every minute, or even every hour. Our strategy is to fetch weather only after 30 glances at the clockface. This way the load of requests is moderated and spread over time. If you want an instant update, simply swipe left on your watchface, start an app (workout or any other app) close it and return to your clockface. On startup of the clockface weather is fetched.
Weather does not show at all after startup
There is no BT connection with your phone, or your phone is not connected to the Internet. This is a known firmware issue. Swipe left on your watchface, start an app (workout or any other app) close it and return to your clockface. This usually fixes the issue. If not, follow this procedure.
App does not respond to configuration settings
There is no BT connection with your phone, or your phone is busy with syncing the device. Can be a firmware issue. We noticed that after a few to as much as 15 minutes connection will be restored.
Or, reset your device and phone for instant result.
App stucks on retrieving Internet data
There is no BT connection with your phone, or your phone is not connected to the Internet. Can be a firmware issue. We noticed that after a few to as much as 15 minutes connection will be restored. Or, reset your device and phone for instant result.
Slow loading of apps/faces
Probably due to syncing of the device it can take a while before the custom settings are loaded. Also fetching web data for the first time can take quite a while after startup.
Workaround is to open the settings page on the phone and make some changes
Errors displayed and blocking the app or face
Usually the BT con is lost or the firmware closed the peer socket.
Workaround is to restart the app after re-establishing proper BT connection
Created with the Personal Edition of HelpNDoc: Produce electronic books easily