Thought to give you a little heads up on where I am with my HS4 version of the plugin. Sure by sharing here what's happening, good suggestive feedback will come, so post away!
Just the plain stuff:
The new stuff:
Below are some screenshots:
Just the plain stuff:
- HS4 has a bunch of differences over how the HS team suggest the PI author implements their stuff (for future safeness), despite the fact that HS4 still has everything from HS3 in it. One of the very fundamental difference for the HS4 PI is that I had to rewrite the PI from a "multipleInstanceSinglePI" version (in HS3) to a just one instance. So if you have scripts, the instance concept is gone but you should still be able to do what you did, just the syntax will need some tweaking.
- The UI is different, so I try to make use of that. As a result, there are some minor difference as to what controls you have on what device, but hopefully very minimal. I did write a "conversion" tool to migrate your devices from HS3 to HS4 but I haven't finished off how to do events, not sure that is even fully possible,
- Due to the new UI, all config screens and player control pages have been rewritten from scratch, I can only hope it was worth the (monumental) effort.
The new stuff:
- I added more filtering capability to the debuging functions. You should be able to only log one player or set a filter about something etc etc
- I rewrote the announcement treatment signficantly. There are still linkgoups etc. but I've been adding the option (and still look for more ideas) how to make announcements a bit more dynamic. I introduced JSON for scripting people to come up with your own configs and shoot them over to the PI to execute on.
- For those of you who have been following the Sonos development forums, Sonos introduced already a few years ago "an open API". So to remind you, for the last 10 years, all of us Sonos hackers have been using a UPNP based interface, that is reasonably well based on standards but was never an officially supported interface by Sonos. The benefit of UPNP is that it is all local, the drawback is that I suspect over time this interface will become stale, or worse, might get buttoned shut. The API on the other hand, supported by Sonos has the drawback that it runs through the Sonos cloud, so any commands come from a Sonos server. Now before we all head for the hills, Sonos has been using this cloud interface for a number of years now so if you are concerned about using this, well you might as well unplug you player. Anyway, one of the functions that the Sonos API provides is the means to play an AudioClip. The beauty of it is that it is much better supported native by the Sonos players so stop play, do clip and resume works as far as I can tell all the time. So, I added that but it will require you to authenticate your setup to Sonos.
- In HS3, you had to create "speaker clients" in HS4 that function was removed, so now you should see all your linkgroup appear and will be selectable when you create a "speak something" event. There are still some issues that I'm working on
- The player control was fully rewritten. As a background, in HS2/3 the PI would make a database of everything your players "know". I'm trying to step away from that and make navigation a 100% interaction w the Sonos player. For me the lag is acceptable but this still needs further work
- I've added support for the move player, a function to wake it up, show its battery status etc.
- I've added a "summary" device which holds a JSON string with all the info pertaining to the player (play state, link info, track , album ....), should be great for people who like to script
- You can select to hide "paired players" and "status devices'. Unfortunately, this hidding is a HS4 feature, so if you don't select to "Hide devices" it won't make a difference. I've asked a while ago if HS could support "hide" flags that were only under control of PI authors but it didn't go anywhere
- Support for Sonos Dock
- Dropped MediaAPI
Below are some screenshots:
Comment