You're seeing a settings page like this and wondering what to do about it.
Why me?
This is happening because our settings pages restore your settings through a WebSocket connection with the Pebble mobile app.
For some reason, this WebSocket connection between our settings page & your Pebble app is not working.
How to fix
Here are a few potential solutions, in order of severity.
First method: force-close your Pebble app.
On Android, you can do this through your phone's settings app. Find the Pebble app, and click the "Force Stop" (or similarly titled) button.
On iOS, you can do this by opening your multi-tasking view (swipe and hold from the bottom of your phone / double click your home button) and then swiping the Pebble app up to force-close it.
After force closing, open your Pebble app and try our settings page again.
Second method: relaunch your watchface.
You can do this by opening the app menu on your Pebble (doing so "closes" your watchface) and then "open" your watchface again.
Third method: reinstall your watchface.
Delete it through the Pebble mobile app, and then find it again on the Pebble App Store and reinstall it anew.
Fourth method: factory reset your watchface.
We have a hidden factory reset button in our settings page which will reset your watchface to its original state and allow you to clear this error, log in, and set it up again.
How to access the factory reset button
- Open settings for your watchface
- Tap the Lignite logo at the top of the page around five times
- A hidden "Factory reset watchface" button should appear
- Tap that button and it will reset your watchface so that you can set it up again
Unfortunately this will wipe your previously configured settings too, but it should help you to fix the error and set everything up again.
Fifth method: contact us.
If you have tried the above four methods and none of them helped you, please reach out to us.
We only just added this syncing feature in April 2026, so it is fairly new. Bugs are possible - and hopefully a fix is, too.
Comments
0 comments
Article is closed for comments.