OK. I touched base with the original author, and we’re good to go.
I’ve rallied all of the various code bits I can find, including my own recent fixes for TTS, and posted them on Github: https://github.com/toggledbits/Sonos-Vera
I am calling the current repository version a development version, not an official release, numbered 1.4.3.
Please try this version out if you are so inclined, but please be aware of the following:
- I have no way to be sure that every change that has ever been published has been incorporated. The project became very fragmented since its last official release, and I’ve run across one complete ZIP file and several single-file updates with a lot of non-overlapping changes. I’ve tried to make sure that this version incorporates (at least in intent) all of the changes I know about, but I suspect there have been some that I haven’t yet found. It’s not easy sleuthing this stuff out of the considerable volume of two sets of forums. It’s therefore reasonable to expect bugs and missing features/fixes. Don’t panic. Just bring it to my attention and we’ll figure it out.
You would do well to back up your Vera and/or
scpa copy of the plugin files you are currently using to a safe spot, if only because they may be helpful to me in getting my hands on a version of the code I didn’t yet find that contains some feature/fix you needed.
- I wasn’t happy with the way changes to TTS support for openLuup were made in the versions of code I found (they seemed to break Vera), so I revised them into something that works for both. openLuup users will need to set the
TTSBaseURLvariables. See the “Special TTS Configuration for openLuup” section of the README in the Github repo for details.
- ResponsiveVoiceTTS is working again. It was broken because RV started redirecting to an HTTPS endpoint, and it seems current versions of
wgeton Vera firmware don’t like that. I just changed the code to use
curland it’s much happier now. I also changed the default URL (now
https://code.responsivevoice.org) to remove the extra step of following a redirect.
- GoogleTTS is effectively well and truly dead. The reason it’s unreliable is that Google is blocking the service after a few queries with a very low periodic limit. The service being used isn’t being used as Google intended–it’s part of Google Translate, not a public service (at least, as now intended). Google has a replacement service, so maybe we’ll get around to that at some point.
- The use of the UPnP Event Proxy with this plugin is highly recommended. When not installed, this plugin will poll the zone player(s) and generate extra load and network traffic trying to keep up-to-date on the current state of the player. I’ve had versions of code that polled out of control–continuously (that was interesting). This version polls every 15 seconds, hard-coded. I’ll work at making that configurable, and maybe dynamic (e.g. faster when it knows the player is doing something, slower when it’s idle).
- I only have one old ZP100 in my network, so I’m not a great test case. Would appreciate anyone with multiple units testing, particularly the group behaviors. I have no idea what state these are in.
Please report successes and failures in this category, preferably in this very topic until the release is made “official”.