Check your WiFi against this list.

https://support.sonos.com/en-us/article/supported-wifi-modes-and-security-standards-for-sonos-products

Maybe try a simple SSID and password, DEADBEEF and MyPassword to see if it is anything odd in either of your real ones causing the glitch.

HI, @john connett , a silly question perhaps, but you haven't by any chance got Default Authenticate switched to "No" in Wireless>Wireless>WiFi Interfaces>gyour interface name]>Wireless? 

I have had it set to "No" for ages and it still catches me regularly when I forget to toggle it before setting up new clients. 

I'm still on 7.15.3 and love my Mikrotik. After a steep learning curve it has handled Sonos, and everything else, beautifully for years. Fingers crossed with every "upgrade" these days, though!

Cheers,

John

I have a hAP ax³ (CAPsMAN) and cAP ax (CAP). As their names suggest, both are 802.11ax (WiFi6) devices. They have 2.4GHz and 5GHz radios. They are configured to support both WPA3 and WPA2. I have a single subnet (no VLANs).

Roam 2 supports 802.11ac (WiFi 5) and WPA3 according to the list. This suggests that it should be compatible.

I have used my current SSID and password combination with a variety of devices without problems. Are there any reported problems with SSID and password handling with Roam 2 or other Sonos devices?

I have found no information about how the App and Roam 2 make use of mDNS during setup. It is tricky to diagnose the problem when the requirements are unknown.

I have set up a Wi-Fi Hotspot on an Ubuntu 24.04.1 LTS system with an Intel AX200. This has a simple SSID (“skylon”) and password. I connected my Pixel 7 Pro and old Galaxy S8. Ran the Sonos App on both of them in an attempt to setup my Roam 2. Had to use Other network… to find skylon. Both result in: We couldn’t connect you to skylon. Make sure you are using the right Wi-Fi and password, then try again. Two attempts then: Your Roam 2 couldn’t be set up. Adjusting your router’s settings may help.

Running the WiFi Analyzer App on my Pixel 7 Pro shows:

skylon (38:00:25:42:27:9b)
-41dBm CH 6 2437MHz ~1.1m
2452 - 2472 (20MHz)
(WPS WPA2 WPA3]
2.4 GHz
802.11n
8WPA2-PSK-CCMP]
KRSN-PSK+PSK-SHA256+SAE-CCMP]2ESS]AWPS]
SMFPC]
>PSK SAE]
INTEL CORPORATE

The Wi-Fi Hotspot has limited opportunities for Adjusting your router’s settings!

Would this be expected to work? Maybe the problem is not specific to my Mikrotik equipment?

@john connett , your level of expertise is clearly way beyond mine but, based on my experience with my Mikrotik router, my money would be squarely on the problem being with the new Roam as your old one worked on the same router. 

Not sure about the expertise. But what I do have are a very particular set of skills, skills I have acquired over a very long career.

It’s possible that the Roam was set up on my old router before I upgraded to Mikrotik. Dug out my old Buffalo WZR-HP-G300NH (rtl8366s) and installed OpenWrt 23.05.5. Still no luck with setting up the Roam 2. Even tried turning off WPA3 and enabling legacy 802.11b rates. It’s a 2.4GHz, 802.11n router so no opportunity for 5GHz problems.

The Roam 2 can advertise its own SONOS-??? network which can be seen by the WiFi Analyzer App so the Wi-Fi radio appears to be working. It will also work as a Bluetooth speaker.

I suspect a Sonos App problem. Unfortunately, there doesn’t appear to be any other options for setting up a single Roam 2.

Run out of thing to try (and patience).

This thread talks about a Roam (and other devices) and about registering. So perhaps not exactly the same situation but I’d try this if everything else fails. I copied the best answer below but there’s other discussion in that thread.

“Best answer by Mustang91

Just off the phone with Sonos support. They had me sign out of my account quit the app and then open up the app and sign back in. This seems to have fixed everything. I would recommend giving this a try.”

Hotspots aren’t supported. 

In the (massively complicated) router settings I would be trying to figure out if IGMP and mDNS are functioning correctly. Do you have more than one VLAN configured? 

It would be useful to know why Hotspots aren’t supported and which routers are know to work when setting up a single Roam 2. I found this in a best answer:

1. Factory reset your new Roam 2
2. Join the Roam 2 to the network using AirPort on my Mac
3. Add the Roam 2 to the Sonos system using the app

I’m puzzled by step 2. How do you Join the Roam 2 to the network when it is the App that sets up the network credentials? Maybe Apple do things differently?

In the (massively complicated) router settings it would be useful to have a hint which ones might need to be changed. In the words of the App, Adjusting your router’s settings may help. About as useful as a something went wrong error message!

figure out if IGMP and mDNS are functioning correctly. Any practical suggestions on how to do this? I have connected an Ubuntu system to the network and run avahi-browse --all. The output looks plausible but does not contain _sonos._tcp.

I have connected to the network advertised by the Roam 2, SONOS-AyED…, and run avahi-browse --all. The output contained:

+ wlp182s0 IPv6 Sonos-C43875C793BC@Unnamed Room               _sonos._tcp          local
+ wlp182s0 IPv4 Sonos-C43875C793BC@Unnamed Room               _sonos._tcp          local

C43875C793BC appears to be consistent with the serial number: S/N A200 2405CP **************

Do you have more than one VLAN configured? As stated earlier I have a single subnet (no VLANs).

I never imagined it would be this difficult to replace a dead Roam with a Roam 2!

Moderator edit: serial number removed

I tried a variation of this:

1. Sonos App - force stop
2. Sonos App - uninstall
3. Android - restart
4. Android - connect to network (on Mikrotik)
5. Android - install Sonos App
6. Roam 2 - Factory reset
7. Sonos App - setup

And it appears to have worked! The System section of the website shows the Roam 2 is registered (as well as the dead and gone Roam). Also managed to see my Roam 2 from the Windows App on my laptop.

Seriously weird behaviour!