quote:

Originally posted by Rey HRH:
And by rebooting the mesh system, I assume that's just disconnecting power to the main node because that's what I did?

I really couldn't say. I've zero personal experience with any mesh systems.

quote:

Originally posted by Rey HRH:
I don't see anything physical on the nodes themselves or on the app. I guess Google is making it so simple and foolproof and I'm not that ingenious of a fool.

That's part of what I was referring to when I wrote "There's too much hidden performance optimization ..." They make it "fool-proof" for the average end-user, but, they likewise don't provide any way for knowledgeable network people to see what's going on or manually tweak anything.

I recall one case where a particular automation device would simply disappear from the user's network after a time. He could see nothing, anywhere, to suggest why. At my suggestion he ran network diagnostics to watch for certain multicast/unicast network traffic upon which I knew the automation depended. The network traffic would be there, and the device working fine. Then, for no explicable reason, that traffic would disappear and so would the device.

The only way he could get it back was to reboot the mesh network. Then, in twenty-four hours or less it'd happen again.

ISTR that instance was Google's product. To me it makes little difference, because I saw similarly erratic behavior reported by users of pretty much all of them, at one time or another. (I also seem to recall he reached out to them, they conceded it was their product at fault, but, had no idea what it was doing or why.)

quote:

Originally posted by Rey HRH:
I've had similar problems with my set up a couple of times since installation in March of this year.

Both times, I ended up turning off the modem and the mesh node connected to the modem. Waited a minute, turned it back on and everything was fine again.

This, the more complex the technology, or the more shitty the infrastructure of your provider, the more often you must reboot the whole shebang. Myself I have to reboot a couple times per month, works almost every time unless the provider's infrastrucuture is misbehaving. Some wireless systems are like Windoze boxes, when they hang or misbehave, reboot is the only fix.

To make a reasonable decision the OP needs to get some info, as noted many places above. It's premature to go replace stuff until you know which piece is the problem.

That said, I've been using eero mesh systems since 2017, and while they are not inexpensive I highly recommend them - they are simple to install and set up, and they work very well. And, they have outstanding US customer support. As in, a couple of rings and someone knowledgeable picks up the phone who can help without needing to put you on hold to find someone else.

The boxes just have one, well-hidden, 'reset' button and for everything else, you use the app. Yes, if one wants to dig out one's inner pocket protector, the phone app lets you tweak to your heart's content. I haven't had to, but the options are there. DHCP? NAT? Port Forwarding? DNS? DDNS? UPnP? Client Steering? If you know (and care) about things like that, then you can tweak. If you don't care and/or are lucky (the latter being my fortunate status) those settings aren't in the way.

Between our house and the rental, I now have 8 of them. Just upgraded to WiFi6 models across the board.

The trick (with eeros, at least) is to get them on sale. Amazon and eero itself run sales fairly frequently, if often not in synch with one another, and the sales range from 20 to 40 percent discounts.

quote:

Originally posted by wrightd:
… the more complex the technology, … the more often you must reboot the whole shebang. Myself I have to reboot a couple times per month, …

If you’re having to reboot stuff that often it isn’t because it’s complex, it’s because it’s broken.

I’d wager our home network is a bunch more complex than yours or those of the majority of home users, yet I rarely have to reboot anything. (I nearly wrote “never,” but, I’m certain it has been necessary, with something, at some point.)

The same was true for the systems and networks I used to administer for a living.