r/eero•
Fant2

One eero keeps showing up yellow

I have 4 eeros (1st Gen) .. 3 of them are hardwired thru moca adapters and 1 in my upstairs hallway is wireless. The one upstairs keeps showing up in yellow in the eero app. When I click on it in the eero app I shows "Connecting". .. a few minutes later it shows connected and connection shows strong connection. But it's still yellow in the eero app and flip flops between connecting and connected. What could be the issue? All seem to be on the latest firmware.

Posted Jan 19, 2019, 3:54 PM UTC

55
MAscooby•

I'd call eero support.

That sounds similar to an issue I had with one of mine. eero support took a look at the eero (remotely), confirmed it was "flapping" between connected and connecting, walked me through some tests, and eventually ended up replacing the unit for me.

It may not be a hardware problem but eero support can look at some log data and help figure it out.

4
Fant2OP•

Thanks. Let's see I unplugged it for a few minutes and plugged it back in and it looks like it's staying connected ... Not happy that I had to intervene as I thought they would reboot themselves if they ran into an issue.

2
MAscooby•

The flapping between connected and connecting may be the eero resetting itself because it's running into trouble.

Mine was ok sometimes but not ok other times and got worse over time.

eero support can pull your logs and help figure it out though.

2
lgreenberg98•

I’ve been experiencing this with two of my eeros. The first one I called support about and they had me hard reset it and then re-add it. It hasn’t happened since. Another one started doing it yesterday and I simply power cycled it and it’s been fine so far.

1
6roybatty6Developer (Mesh/OS)•

There are actually five different kinds of restart an eero can do, and they range in severity:

  • The least intense is "thrashing the radios", where the eero will power down its radios and reboot them. eeros do this occasionally when they think a radio might be stuck; radios are complicated little computers with an antenna connected to the universe attached, so this helps reliability. They restart fast enough (about a tenth of a second) that you don't normally notice that this happened at all.
  • More severe than this is a device reboot. The eero will be offline for about a minute and all the clients will reconnect, sometimes to different eeros. eeros do this when they find themselves in a corner they can't get out of, like some critical piece of system software crashing, connectivity failures that thrashing the radios didn't fix, radio firmware crashes rather than hangs, ethernet state machine failure to make progress, running out of memory, detecting corrupt filesystem, or failure to update system state. A short reset button press or a reboot action sent from the app also can trigger this to happen.
  • More severe than this is a reboot with a switch to the alternate partition. This is noticeable as an eero going offline and coming back with an older eeroOS version. This happens when filesystem corruption is detected, an especially hard system crash occurs, or as a result of cosmic ray corruption of the flash memory. The eero will immediately attempt to download a fresh system image to the partition that was corrupted. This is also (obviously) part of an eeroOS update- the new version is downloaded to the alternate partition and then the device reboots into it.
  • More severe than this is a reboot with state discarded; a medium-length button press (light turns yellow) will trigger this. It erases the system state partition and regenerates it from the eero's neighbour nodes. Corrupted system state will cause this to happen automatically, and it's also possible to trigger it from the cloud.
  • Finally, the most severe reset is the long button press (light turns red). This deletes all state from the node, notifies the cloud that the node is no longer part of a network, and essentially returns it to factory state. The node will be blinking blue and in setup mode when it reboots. This also deletes the node's logs, so there will be no way for eero support to figure out what went wrong- that's why it's important to call support before doing this if you're trying to debug an issue.

eeros generally do restart themselves when they determine that something is up with their configuration; you shouldn't have to do this at all, and if it is happening then it generally means something is up- maybe drop support a line and see if they can figure out what's going wrong.

1