Has any one integrated any of the Sonos Distributed Audio Products into AMX with any success???
joelw wrote: »
Sonos is a UPnP based device. I am working on implementing a UPnP stack in Duet. If it proves to be too slugish, Sonos integration will require an external gateway device. I've controlled the Sonos via my code in other devices such as Roku HD1000, Win32, and Linux.
If you don't see a post from me on the subject of Sonos in a couple of months, send me a private message.
Duncan Ellis wrote: »
in Netlinx, this is not an easy project the XML parsing alone is a trial!
Duncan Ellis wrote: »
I did a bit of research for the sonos devices but Sonos tend to keep their info under wraps so its not that easy.
I've just written a Netlinx module for uPnP support for the Linn DS Media Renderer - which has taken a while, to say the least - and now happily controls a mixture of upto 20 upnp media renderers and servers. I have to say that in Netlinx, this is not an easy project the XML parsing alone is a trial!
But back to Sonos, there is no real info available. However, if you fancy taking it on I would recommend that you download the Intel UPNP development tools which will allow you to see any upnp devices on the network and show you the services & devices within the Media renderer/server wrappers.
If you can't find the tools, if you private mail me I can probably find them, zip them and send them to you.
anyone use AMX with SONOS?
I use this module from "true" Version 0.0.2
It works but feedbacks are sometimes assignt to a wrong zone..
Probably anyone has got a solution or a working module for up to 14 zones on a nx controller
I've done some work with Sonos, and once you get the IP ports working properly it's actually OK - just very resource heavy as the SOAP packets are massive (and all in XML).
Check that the players are being identified properly - the event feedback uses a server port on the NX, so it doesn't follow that the same player is going to use the same port every time. Either use the DATA.SOURCEIP string to identify which player has actually connected, or parse the NOTIFY header as this also contains the IP of the connected unit.
Update the "true" Version
* Version 0.0.3 / 20. Dec. 2021
* Add / Bugfix by Jud ([email protected])
* Refactoring for workable with Sonos S1 and S2
* Refactoring for workable with NX Controllers
* Update UPNP Timeout to 13h (every 12h must send a new regsister over all speaker)
* Bugfixing with S2 IP Adress Feedback
* Bugfixing for NX Conrtrollers
* Bugfixing with Feedback Zone (use now the NOTIFY in Header)
* Add GROUPTOPOLOGY
* Add Line In Bugfix
* Add Radio Body
* Limited to 20 Sonos Speaker Zones
* Add some new functions in string.axi
Don't know if this was intended, but I get this error message: "The file you requested has been deleted"
New download link:https://drive.google.com/file/d/1MwmxFyEgVlm0B9_1N3J5zlxvfW4poHoD/view?usp=sharing