maybeWrapAsError Issue

[ianm2k4]

I have the problem where the exception is thrown. Has this been fixed?

Airsonos 0.2.5
Node 0.12.9
Ubuntu server 15.04

I have removed the Bridge. I have a wired Playbar to the router and it has a Sub, and other Play 1's wireless. Reading a few issues it seems that this problem still exists with a surround sound setup. Is the Sub the problem?

Also the --diagnostics never actually finishes (it does find the speakers but never returns to the command prompt). What is the cause of this?

[xuncia]

I don't think is the sub, because also in my system without the sub but with a soundbar and two player 1 with surrond system I have the same error.....

[ianm2k4]

Look in 'About My Sonos' and check that all the entries have WM:1 against them. I.E. ensure that SonosNet is present. To stop SonosNet and have WM:1 you need to wire one of your plays' playbars to your router. Sonos should then turn off SonosNet. I have all mine on WM:1 except for my Sub's (I cannot get a wire to them) and when I turn of my Sub's airsonos works fine.

See https://sonos.custhelp.com/app/answers/detail/a_id/3144/~/switching-wireless-network

[xuncia]

@ianm2k4 : Thank you, I think you are right. I checked remotly and the two new players 1 are on WM0(sonosnet), tonight when I get back home I'll put them on WM1 using temporarily an ethernet cable. I'll let you know.
Thanks again for the fast reply!

[xuncia]

I tried but unfortunately it seems that it works everything if I don't enable the surround, in this case the two player 1 are on WM1 and airsonos works, but as soon as I add the surround (Player 1 as right and left speakers) the WM 1 changes automatically in WM0 and airsonos stop working.....

[ianm2k4]

That would make sense then. The surrounds in your setup and the subs in mine are using sonos net to communicate with the master player.. The playbar. I got it to work by turning off the sonos net items my subs. The surrounds in your case. Run air sonos to find the players, then just turn on the surrounds. It will keep working. A hack workaround but it works until you restart air sonos.

[xuncia]

Yes it makes sense. Thank you again.

[jens-maus]

FYI: This issue seems to be a very prominent one which can be potentially be fixed with integrating the following pull request: stephen/node-sonos#4