Hiding the SSID of a wireless network does next to nothing for improving security. Even a "hidden" network is still sending out information and there are lots of available software tools that can detect these networks. Hiding the SSID can also make it harder for devices to roam to another access point (which with a mesh environment like eero, is critical). It also just adds additional complexity for support personnel to have to deal with (example: when customer submits issue that they can't see their wireless network anymore, support agents would have to first verify if the SSID broadcast is enabled/disabled).

bindignavile, I'm not in any way trying to brag or be condescending, but first let me preface the following reply by clarifying what my experience level is. I have 15+ years of IT experience with several of those being the IT manager for several organizations with nearly 1,000 daily network connected devices and 70 enterprise level access points. I don't claim to be a wireless guru, but I'm far beyond just a wanna-be retail store tech.

Let me respond to the points you made in your reply:

You: With a hidden network, casual hackers will have to guess at the network SSID.
Me: My original point was that nobody has to guess at anything. Even a hidden SSID is constantly sending out beacon frames and there are several free tools that can easily read these and figure out the SSID. Properly securing your network means having a network password set. Cracking the WPA2-PSK is going to be the much harder part (but not impossible). But if someone has the desire/capability to crack your network password, I don't think there is much separation of a "casual" vs "dedicated" hacker. It's what they do after they break into your network that would probably define what level of hacker they are. But this is getting into semantics and I don't think it's worth our time to debate that, nor do I believe that is that what this community is intended for.

You: Why would I want to roam on my home network? Why would I want to roam to another access point?
Me: The whole functionality a mesh network (i.e. what eeros do) is based around the idea that your devices connect to the other APs (eeros) in your home. Roaming isn't just connecting to a different SSID, it's also connecting to another AP that is offering a better signal. If you only have one eero in your home, then there is no need for roaming, but if you have multiple eeros your devices will roam. You are correct in that a hidden SSID won't necessarily stop devices from roaming to other APs that are configured with the same SSID and security settings. But a hidden SSID forces your device to be active and to send out requests saying "hey, does anybody have this SSID?" and waiting for a reply. If your SSID isn't hidden, your device can be passive and just sit there and listen and then go "oh yea, I see that SSID and I know how to connect to it!". The active vs passive part is where roaming issues can happen and devices may not connect to a closer AP as quickly/easily. Now, I will also add that roaming isn't always perfect even with SSIDs that aren't hidden. But hidden SSIDs add even more to the already complex nature of wireless networking.

You: A customer who hides his/her network will submit a support request saying he cannot see his network anymore????
Me: Yes. Customers will do this. Eero is selling their product to the consumer market and therefore there will be a lot of people who don't have strong technical skills/understanding. That's the beauty of eero. It's a product that is simple and easy. A hidden SSID requires people know/understand how to manually add a new network to their devices. This isn't a problem for people such as you and I, but we are not the norm.

If you would like me to provide you with some further articles/discussion about why hidden SSIDs are a bad form of security, I can do so.

In summary, hidden SSIDs is a very poor level of security and introduces additional complexity that can cause technical issues. And IMHO, I would rather see eero focus on fixing existing bugs, improving performance, and developing new features that would be more applicable/desirable to the entire user base.

Jeff C. On a side note, I have a community related question. Is there a way I can contact you directly?