Skip to content

The ticker keeps restarting to reach my Wi-Fi

Symptoms

I couldn’t connect: the reason, then about to restart and try again, 1 of 3 times Changed your Wi-Fi? Restart me 5 times quickly to set it up One more try: restarting to reach your Wi-Fi, 1 of 3, if this doesn’t work I’ll open setup mode

At start-up the ticker tries its saved network three times (Try 1 of 3 - 10s each), then shows I couldn't connect. with the reason and About to restart & try again. / 1 of 3 times., then a yellow hint — Changed your Wi-Fi? (or New password? / New Wi-Fi router?) / Restart me 5 times / quickly to set it up. — and then the story: One more try... / Restarting to reach / your Wi-Fi (1 of 3). / If this doesn't work, / I'll open setup mode. The first time it also explains, one card per restart:

Wi-Fi trouble: your Wi-Fi can take longer to wake up than I do, like after a power cut No worries! I’ll restart and try again, up to 3 more times, this often fixes it Fallback plan: I’ll open setup to pick a Wi-Fi or fix your password, restart me anytime to start over

After the third restart: That was my last try. / Opening my setup mode., and the setup cards begin with Heads up / I can't find your Wi-Fi.

That was my last try, opening my setup mode

Cause

This is a ticker that has a saved network but never completed its setup on it — the join was interrupted before You're all set!, or the details were saved for a network that was not in range. Such a ticker does not wait indefinitely the way a set-up ticker does; it restarts to retry three times, because a router that is slow after a power cut usually comes back within that, and then opens setup so you can fix whatever is wrong. If the router answered and refused it, it skips the restarts and goes straight to setup.

Fix

  1. If your router is restarting or was off, do nothing. Each restart is another try, and the ticker joins when the router is back.
  2. If the router is on and the ticker still restarts, let it reach Opening my setup mode. It then shows its setup cards with Heads up and the reason.
  3. Join the CT network and enter the network and password again; the setup page’s first card names the network and what happened. See Join the ticker's setup network.
  4. If the ticker joins the network and then fails in the same way every time, follow the reason it gives: The password was refused, No address was given to me, Joined, but my server is quiet.

If that didn’t work