![]() ![]() Well, good to know we can eliminate passwords. Feedback is appreciated, you will probably think of something I missed. So, your Chromecast for speech experience my not be 100%. I’ve added a longer delay before resetting the player to try to minimize this. Sometimes this manifests as a speech event not playing on the first attempt. Second, the server has to reconnect if the connection has been terminated or interrupted. Things that do matter, volume is set by default to only update while actively connected. However, if you implement Phllipe’s Chromecast plugin in LMS, please read his documentation. Even though Chromecast devices report as SqueezeLite, they do not appear to have this issue, I think due to different connection methods. So, if you see this problem, add more words to your announcement. I can’t test for this if you are using BIg Talker 2 as a music player, since it is already padding duration information beyond the minimum. To help prevent this, there is an option on the player handler to mark it as a SqueezeLite, and a warning message will be generated if the resulting speech track is too short. The solution is more verbose speech, usually adding a phrase to get beyond 11-12 words is enough. The player will appear to be playing, but produce no sound, and the timer will continue to increase or loop. ![]() However, the SqueezeLite implementation has a known problem with very short tracks, under 5 seconds seems to be the limit I found. Speech, in general, produces a short track to play. All play music fine, but speech presented a few issues to overcome. I have been testing this with a Boom, a piCorePlayer, a Google Home, and a Google Home Mini. Several new player settings to customize player action, see Git documentation. New commands associated with this are button1(), button2(), and button3(). With this you should be able to automate music. See documentation on Git on how to do this. You will need to load a LMS HTTP API command into the settings. These are to allow starting music within Smartthings. ![]() Shuffle may result in a different song, since saving a playlist is shuffle order isn’t supported in the API being use. The speak command will attempt to restore the player to it’s state before the speech event is sent. It seems to work fine as either a music player or speech synthesis device. Report back if you find issues with it or other apps, I’ll be curious to see what happens. I’ve tested this a bit with Big Talker 2. The speak(msg) command has been implemented using Smartthings text to speech. As usual, there will probably be issues, since my testing is limited to me. ![]() This version includes new functionality and a smartapp for voice/routine control. Just finished uploading new version of the code. Suggest additional items and if any one item should be tackled first.įinally, thanks to all those in the community that have helped me realize that something like this was even possible. I have a wish list of items I hope to tackle. I’m sure there will be bugs and I welcome help, feedback and suggestions. This is mainly a “because I want to see if I can” effort, but I wanted to share my results. Player status information is updated from the server. Multiple players can be controlled individually with one server. It only requires two device handlers and no bridge program. There have been several discussions and attempts at controlling Squeezebox (Logictech Media Server) in Smartthings. UPDATE - Version 2.0 has been uploaded See below post. I’ve since given up on the Smartthings ecosystem. The last time I checked a few months ago, the future of LAN devices was unknown. The unknowns of of the new developer’s platform made this too much to pursue further. I am no longer updating or supporting this code. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |