Alexa issues when switching wifi networks

I personally would not recommend a full reset of the Home Sonos system. Such a reset rarely fixes an issue like this - maybe try the suggestion outlined in my last post. 

I know you mentioned initially that you had both the Home and Office network credentials stored in your Home Sonos setup, but presumably from your post yesterday, that is now not the case. So perhaps try these steps:

1. Add the office WiFi SSID/Password credentials (which are case sensitive) to create a mobile hotspot and enable/place that mobile device about one metre away from the office speaker.
2. Open the Sonos App on another (different) mobile/tablet device, which is connected to your Home Sonos system.
3. If the ‘Office’ speaker is not already a part of that Home Sonos system, then factory reset that one speaker only and setup/add it to the Home system using the ‘Add Product’ feature in ‘Settings/System’ in the App.
4. When the speaker is setup, add Alexa to that speaker and test that the assistant is working as expected.
5. Check the Hotspot is broadcasting the Works WiFi network, but do not connect your mobile controller to that network leave it connected to your Home WiFi. Now try the ‘Update Network’ tool in the Sonos App network settings. Run the scan and select your Office Speaker (Which is now part of your Home system).
6. You should follow the onscreen steps to connect to that speaker and continue until you get to the ‘Change Network’ screen - as seen in my earlier post. When you select to change network, a list of ‘nearby’ WiFi networks will be displayed in the next screen, including the nearby mobile hotspot which is ‘mimicking’ your Office WiFi network.
7. Select the Office network from the list and go onto enter the correct ‘case sensitive’ password for that connection.
8. It will then (hopefully) add the Office WiFi network credentials to the Office Speaker and you will later see those network settings in the Sonos App too.
9. Note after adding the credentials to the Office speaker, the ‘network update’ tool will then continue and try to propagate the Office network credentials to all the other Home speakers. I would let it do that. If any Home device are not currently powered on (a Roam for example) it will let you know they were not updated - just skip by opting to update them later (as necessary).
10. You are now done and the Office speaker (all being well - now has the correct office credentials stored). It can now be taken to work and it should automatically connect to the WiFi there, as long as you used the same SSID/Password in the mobile hotspot.
11. Switch the mobile/Controller to the Office WiFi network and open the Sonos App and you should be able to see/control your Office speaker and use it with the Alexa assistant.🤞
12. If you have ‘other’ Sonos speakers at the office, you can simply factory reset those and add them to the same Sonos system using ‘Add Product’ in the App - you do not need to take those Home - Alexa will then work at both locations Home & Office and so will all your speakers (except the Roam if you left it powered off).
13. Any mobile/controller linked to the Sonos system will work at both locations to control all your Sonos devices when on the same WiFi network.

Hope that assists and you are able to sort this without a full system reset.

@Ken_Griffiths , when you could do it effortlessly last time and many others were having the issue, what device were/are you using?

The issue that was identified and fixed affected Android devices.

I have a feeling it could be that the fix applied to a previous version has not been included (possible code fork, I don’t know) in the latest release.

My setup is much simpler than yours Ken, my whole S2 system is simply a Roam.  It sees it, asks for the WiFi details of the new network (it shows the one that the phone is connected to), accepts them, looks like it’s finalising and then fails:

We had a couple of other devices connected too.

What device are you using @ph_SD1 ?

When I’m home, I’ll simply rename my SSID and change the password and try to add it to my Roam.

That’s a very good point @sjw👍. I was using an iOS (iPhone XR) controller here.

I thought the issue last time however, was that Android users were not seeing the ‘change network’/‘other network screens’ as per the screens attached to my earlier post, but I do have an Android tablet in a drawer somewhere, so will charge that (if needed) and install the latest App and will give it a try.

I have removed the ‘swj-network’ from my system here, so I will try adding a new ‘swj2-network’ and see if the Android App lets me do that - I’ll come back and will let you know if it works (or not).

sjw,

I am using an iPhone 12 Pro. One Sonos device on my office network and three at home. 

Ken,

I will have to try the fake network trick tonight when I get home and can borrow a hotspot. I did uninstall and reinstall the Sonos app and after that it was working fine at Home on those devices. When I got to the Office I re-connected the Sonos One and did a network update. The System showed both wifi networks again - very strange that I can only see both when at work but when at home it only shows the home network SSID. I went ahead and selected the work network and the system went through setup and I could interact with Alexa. However, this was still the ‘dumb’ Alexa who says she is doing things but music doesn’t play, eg from Spotify and no daily news brief. She still can answer basic questions and perform internal functions. From prior experience I will need to disable and re-enable the Sonos skill to fix. Interestingly this procedure also re-activates my News skills even though I am not disabling and re-enabling those.The Sonos Alexa Skill seems to be buggy. Can’t yet marked this one Solved as Dumb Alexa is still popping up.

It’s definitely working @sjw on Android. I didn’t encounter any issues, but the advice still stands and that is if you do encounter an error, then it’s often best to reboot the speaker and the controller device too - In the past, I’ve got away with rebooting the speaker and fully closing the Sonos App (slide off screen) plus toggling off/on the mobile network connection.

Not sure if that assists, but maybe ensure no vpn/security software is getting in the way on the controller App.

The controller is auto-switching its households - it’s because you created a new system at work/office and then on return home you connected to the existing system. That’s why you are seeing two WiFi networks in one location (Work) and one WiFi network at the other (Home) - you are still using two different systems/households.. you will likely have a different My Sonos tab for example when at Home, compared to Work.

Can I suggest you stick to the Home setup? If so, when at Home with your office speaker, before you start the steps outlined in my lengthy post earlier in this thread, connect your mobile to the Home network, then just reset the controller app via ‘Settings/App Preferences’ - the App will close.

On reopening the App, skip past the opening screens and agree to the T&C’s and choose to connect back to the ‘existing system’ - do not create a new system and follow the instructions and let the App find your Sonos system on your Home WiFi network. Sign into your Sonos Account in the App (important) then ensure all is working and then follow the steps mentioned earlier. It will ensure you then do not auto-switch to the work Sonos Household, which will be wiped out when you go onto add the office speaker to your Home system.

Hope that makes sense and you are able to follow the things mentioned.👍