If you have any questions / comments / improvements, tag me on twitter or below in the Comment Section.A quick note on Play:5, Five, Connect:Amp, Port and Connect The Preview script can be found on GitHub. The Demo Interface, which triggers the above actions, is console based and pretty simple:īefore you start the script, make sure you open it in ISE or Notepad and change the IP Address.

The Preview Script currently has the following 11 actions: To my surprise, that actually worked on the first try. With this knowledge, I started writing a PowerShell Script that sends an identical SOAP Action to the Playbar. In this case I triggered a simple “Play” Action. If you expand the “eXtensible Markup Language” node at the end, you can view the Envelope that has the actual instruction. Here you can see, that the HTTP Request has a SOAP Action. You should see an HTTP/XML POST request to your Destination IP, that looks like the following: Now you can trigger a Command the official Sonos Controller App. In my case I’m talking to a Sonos Playbar. To do that, you can use the following filter: ip.dst_host = IP_ADDRESS The magic solution here is called: WiresharkĪfter starting the tool, you can limit the output to the Destination IP of your Sonos Component, connected to Ethernet. The Search was quite short because there is actually none API Documentation. I actually started by looking for the Sonos API Documentation. I didn’t break anything while doing my tests, though.īefore I post the preview script, I want to give some facts about how the script works. So everything you do is at your own risk. What I am writing here is probably not supported by Sonos and is currently a preview which is not complete yet or extensively tested. I spent the Christmas days this year to be a bit creative and managed to control my Sonos Environment via Windows PowerShell.įirst things first. This blog post is a little different from my others.

Sonos for windows phone 8.1