Update failed, error 1066

Hi ​@OliverPersch 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with receiving a 1066 error when trying to update your speakers.

We have heard a couple of such reports recently, and are trying to gather data on them.

Could you please submit a support diagnostic and reply here when done? Please don’t share the number given. Thanks.

Once that has been done, please try rebooting the speakers, the router (switch off for at least 30 seconds) and the device running the Sonos app, then try updating again.

I hope this helps.

Hi, I have the same probleme. 
Installing, connecting to my wifi, choosing the room and BOOM error 1066… on my whole devices (play1, one, ikea, boost). 

Hi ​@kevkev 

Welcome to the Sonos Community!

Sorry to hear that! Please follow the same steps I gave above. Thanks.

​@Corry P Ok but the diagnostic number isn’t a sensitive information, is it ? 

Apparently, it is, which would be why he asked for it not to be shared. 

I’ve sent diagnostics data, have reset everything and still no good. What do I do with this number is gave me? 
 

FYI. I have another Sonos play 3 that literally added to network and updated 15 mins before this without an issue. 

You would need to call Sonos Support directly to discuss it.

Or wait for ​@Corry P to have a chance to pick it up and look at it, now that he’s aware of it. 

​@Airgetlam ​@Corry P Ok diagnostic submited. I will try to reinstall it after rebooting speaker, router and phone.

Note, ​@Corry P is the Sonos employee who has access to this data, I’m just a fellow user like you. I can’t see the data in a diagnostic. 

Same issue here. My Sub Mini lost connection every few seconds. Tried to reinstall it but now stuck on error 1066. Can’t use it at all..

I’d try both the process of submitting a system diagnostic within 10 minutes of experiencing this problem, and calling Sonos Support to discuss it. Don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

I would be awfully tempted to try a power cycle, too, by unplugging it for two minutes, plugging it back in, waiting for it to reconnect, then trying the update process again. It would hurt, if possible, to wire it temporarily to your router, too. 

I have the same error on my brand new Arc ultra. Spent two hours on the phone with support on Wednesday trying to get this fixed but in the end had to leave for a doctors appointment. Got escalated to level two support and they couldn’t come up with anything either. Just had me resetting everything over and over, and changing settings on my Orbi router.

Just tried resetting everything again this morning (router, network switch, Arc, reinstalled apps on phone, iPad, Mac) and still have the same problem (wi-Fi and ethernet). Also tried connecting a Sonos Roam gen one that I’ve been using as a Bluetooth speaker for the past three years because I didn’t want to set up the rest of my system on S2.

I guess is that it could be an incompatibility with the Orbi router. What is everybody else using?

My system suddenly required an update every time I turn Roam 2 on but message saying it couldn’t update.  Rebooted all speakers , rebooted router twice.   Eventually reset Roam 2. It’s now added to speakers and so the system is usable again , however states it’s not registered and when I try to (re) register it I get the 1066 message !  

I’m curious as to what Sonos Support said, when you called them?

I wasn’t able to call them today. I will be able to call them tomorrow. I figured I’m more likely to be able to get through to a senior advisor during regular working hours anyway.

last night I also tried to add an era 300. That took several attempts to get it onto the network but once I did, I again hit the 1066 issue and was unable to proceed further. 
 

I was also running iOS beta so I tried everything again with an iPad running 18.4 and got the same results.

At this point, I guess it’s some sort of incompatibility between the latest version of the S2 app, and the Orbi firmware, given that I am experiencing the same error on brand new hardware and older kit that I’ve owned for a couple of years.

Will update when I have more news