I have wired my home with whole home audio using Arylic amplifiers and ceiling speakers.
I also have my entire home setup with IOT using Hubitat.
I saw that Arylic have now partnered with Fibaro for smart home control and I am wondering what it will take to like Arylic whole home audio to Hubitat?
I wrote an up2stream integration for Hubitat. up2stream is the API that the Arylic devices use for local communication: GitHub - tomwpublic/hubitat_up2stream
I have used it with a variety of devices - including several from Arylic as well as Dayton Audio and others. I don't have it in my Hubitat Package Manager (HPM) listing yet, but the installation and usage instructions are in the readme on GitHub.
Intriguing. I was playing with the API off-and-on (see failed effort to get Hubitat virtual audio controls exposed). I have a working set of controls on my SharpTools dashboard to play/pause and adjust volume. We never really change our master & slave configurations, so I just left that alone.
Taking a look at @tomw 's GitHub link, I ran into similar problems with URI links. Having a reliable path back to your music source is the only way to really implement TTS with these. Using the API for voicerss.org is straightforward, but then there is no way to get back to, say, my wife's Pandora mix. I may have to try your integration to see if I can find a reasonable compromise.
You should be able to store away the trackData URI, do your TTS operation (my driver supports speak and playText), and then restore the URI via playTrack.
It gets you pretty close, but you'll likely get moved back to the beginning of the track (or worse, maybe the beginning of the whole playlist). I gave up at that point trying to make it any better.
Correct, I did play with that briefly and was able to get it to speak and then go back to an iHeart Radio station. Yes, it went back to the beginning of the track, as you mention. That is a manageable situation.
I will give the TTS a try later. It would be nice to remove another third party piece from this puzzle. My first swing at using playText seems to cutoff the last syllable.
There are a few other anomalies that I noticed:
Overall, very cool.
Thanks for the feedback.
The discovery was a little bit flaky, especially if the Arylic devices had been booted up for a while. I guessed that they stopped responding to the discovery commands for some reason, but rebooting the device and then running discovery always made them show back up.
My recollection is a little bit hazy on volume controls. But I think I remember that the slaves stop responding to direct volume control once they are grouped, which is why I added the slave volume adjustments to the group driver.
@tomw - I am curious as to why the driver code refreshes once per minute?
With multiple devices, this becomes quite chatty. Over the past week, it accounted for >90% of my device busy time. I just changed the interval to 30 minutes on my local copy, but wanted to make sure that I was not missing anything.
That was totally arbitrary. I set it to a low number, because at the time I was using their mobile app(s) to set tracks and wanted the status to follow reasonably quickly in Hubitat (for album art, etc).
There shouldn't be any issue with having it refresh less frequently, especially if you primarily use Hubitat to control the devices (since each successful command also triggers a refresh).
Excellent ... thanks again!
Thank you so much for this app. Works great- I am using the TTS for security notification for my whole house audio.
Only thing I can't figure out why is not working - I don't see "TrackData" or "TrackURI" in the attributes for either the group or the group master device .
Where or how do I get the trackURI of what's playing now so I can later restore or play it ?
Great, I'm glad you like it!
You can get the trackURI from the 'up2stream player' child device that corresponds to the group master. Once you have it, you can use that trackURI directly with the parent device for the group.
Download the Hubitat app
