Thank you! Integration of Sonos was something I always had on my wish-list !

Some points about V1.8:

- overall look&feel: works very nice already !

- additon of the Sonos Zone name would be helpful definitely. I have 4 zones and consistently forget which IP-address is assigned to which room...

- would be nice to be able to rearrange some of the button assignments, especially Sonos-Volume, but I'm not sure how this could be done with a module. As workaround I assigned my Amps Volume to the CH+/- buttons in the Sonos activity also. I think many people interested in this Sonos-module will set their Sonos-Volume to a 'fixed' level and use their Receiver/Processor as D/A converter, at least in their main systems.

- some functions could be faster, eg: search in a large music library is slow compared with the Sonos CR100 or the iPhone Sonos app. Nevertheless entering the actual search string is much quicker and easier compared to the original Sonos CR100 :-)

- I'm looking forward to the next release with Radio support on Sonos FW 3.0+ hopefully.

Thanks again, I use this module on a daily base already, really a great addition to Pronto and to Sonos - makes a combined system much easier to handle with just one remote control.

Seems like they could have an "option" parameter page to allow you to use your system volume control vs. having the module override it. That and having the Zone names available (I just added another zone and now have 5 in our home) would also help. Hope they read these forums.... SJ

I agree, most of the code is already in place.

Some of the screen objects, such as the keyboard, re-size for the 9400. The track time bar will work just fine if it is re-sized. I think that with a little more work, the module will run in landscape or portrait mode.

I'm all up and running with a Sonos ZP90. Works a treat. Searching seems quite quick on my modest 16Gb music collection. Great interface. Looking forward to the radio support in the next release.

Great work Prontoteam!

Cheers, Lee

Spoke a little too soon. Trying to use the Denon RS232 module for volume causes the command to constantly repeat.

Simply sending a single RS232 command, without the call to the volume page, works for now.

I don't have any Sonos equipment at the moment but I was thiking of getting some to use with the Pronto. But I don't understand what the problem is (that's being discussed in this thread) with the volume control.

I have installed the Sonos module on my Pronto and if I tick the 'Use System Properties' box for the hard volume buttons in PEP2, it uses the volume IR codes for my amp on those buttons. The volume button then controls volume on my amp with the screen displaying the Sonos module. So I don't see a problem there.

Can you search for music by either artist, album or song title, by the way?

I did this and it does not work. Are you selecting the Sonos module pages? I have tried both "use system properties" (which is the default) and actually overrode with a specific vol up/down command - does not work either way. Maybe because it is not finding Sonos zones on your system and therefore has nothing to control?

On mine, the only Sonos module page I can access is the 'Now playing' one, and the volume control works OK on that.

Of course, to use my method you need to have the volume hard buttons set to control the amp under System -> System Properties.

As you say, it's possible that mine might behave differently because I don't have any Sonos hardware connected, but it seems strange that it would do that.

I bet that is the case. My setup is exactly what you describe. My volume hard buttons are set to control my processor under system - system properties. When you have hardware connected, a sonos volume screen comes up (showing that the prontoscript is controlling these hard buttons). That's why I had to assign vol up/down to the channel +/- hard button as a work around. This is a first good step for Pronto, but the interface is far from complete. We use Sonos controllers and now mostly our iPhones/iTouches to control. These interfaces are really slick, but not as integrated as our pronto remotes. SJ

So what happens if you go into the Sonos module properties in PEP2 and select the hard buttons - does it just not allow you to tick the 'Use System Properties' box?

Does it let you delete the prontoscript for the hard buttons?

When I tick the 'Use System Properties' box it seems to delete the code that was there initially under the hard buttons. When I untick it, the code doesn't come back.

Just a thought, but maybe it would work if you start again and, initially, do what I have done (i.e. just merge the Sonos module into your project without changing anything, and change the vol hard buttons to control your amp). Then only after the vol hard buttons work with your amp, you set up the module to connect to your Sonos hardware.

Marcus, it's no difference if you or I go into the Sonos module properties in PEP2 and select the hard buttons - as long as we are talking about the same module, and I don't think we are.

There are two different Sonos modules:

- the old AVD module as .xcf-file, downloadable from the Pronto module site
- the new Philips module as .gef-file, downloadable from [Link: pronto.philips.com]

You said that you have seen some ProntoScript code on those buttons initially. I think you are talking about the older Sonos-module (the one from AVD which needs additional HW to control a Sonos system). With the new module from Philips, there is no need for additional HW to control Sonos and the new module comes not as .xcf-file as the one from AVD, but as .gef-file (ProntoScript module which can be imported). You do not see any ProntoScript in PEP after importing the .gef-file, just some pages (actual pages are named as Zone Menu, Music Menu, Keyboard, and others).
In PEP I think you see actually a Sonos activity with pages like Now Playing, Menu, Queue and others - that will be the old AVD module.

I have a similar setup as SJ and have set the volume hard buttons to control my processor on a system level. If I go into the Sonos module in PEP I have tried 'Use System Properties' selected and not selected with some local definitions - and neither works.

About another topic (the missing zone names): I've added a small panel on the Zone Menu page on the bottom right with some text like:

ZonePlayers:
...28: living room
...33: guest room
...40: kitchen
...43: children

That is my interim solution to figure out which IP address listed on the Sonos activity belongs to what room since I always forget which IP address belongs to which room :-)
Rene

Not sure I understand.... There is no prontoscript for the hard buttons to delete. It is all part of the module. yes, it allows me to tick the "use system properties", but this does not change anything. The volume pronto script variable (e.g. PS_VOLUME_UP) is being controlled by this module which I can not change. Maybe I could unplug all of my Sonos zones and see what happens? However, lots of folks have reported the exact same issue. Probably because you are testing without any Sonos zones so there is nothing for the volume to control.... SJ

Well, I unplugged my zones and it still does not work! Crazy. Assume yours just shows "searching for zones" and then use select NOW PLAYING. SJ

OK, as soon as I exclude (uncheck) the Sonos module from the activity, everything works fine with my volume. However, when I select to include the module, it doesn't work. Still not sure why yours works! Oh well... SJ

The sonos module is included in the script librabry and you can open this with any editor. It uses the PS_VOLUME_UP and DOWN prontoscript labeling so that's why it is always talking to the sonos regardless of what you do to the firmkeys within the action.

We also need this modified so we can post the "volume-control" free module as soon as we are done! Otherwise find it in the script and disable it, voila!