- #Logitech media server page issues how to#
- #Logitech media server page issues install#
- #Logitech media server page issues update#
- #Logitech media server page issues code#
#Logitech media server page issues code#
The speak command will need to be modified to accept a voice, and the code then modified to recognize and give priority to that voice. Preferences can’t be changed in the code.
#Logitech media server page issues how to#
I will make a note to include them when I make updates, and am glad you figured out how to add them yourself.Īs to a bi-lingual speaker, it’s a creative idea. Thanks for letting me know about the new voices. It accepts the exact same format as the presets, so if you have something that you only use through WebCore/smartapp, it’s an option that will expand the number of things you can access in LMS and save your presets. Note on WebCore and smartapps, if you want to send a command, but don’t want to waste a preset button, the custom( command) is available. I appreciate Ron sharing his solution with everyone. Now you can have a Spotify playlist start as part of your Good Morning, Return Home, or other routines, and in WebCore. I agree about the Spotify integration, awesome. This isn’t too hard to figure out, but because it is menu driven, it can change as other stations/playlists are added, but this is probably targeted to something that is going build and select stations, not grab a specific item, so I went the saved playlist route. The “.4” means the 5th item on the “Your Stations” menu. In the example the zero means the first choice (numbering begins with 0, so always uses (n-1)) inside Pandora, in this case, “Your Stations”. I’ve tried it for Pandora, so it should work for Spotify. Then I have something stable to use, so I can then use this in a preset Instead, my solution was to manually start playing the desired station/playlist, then save it as a LMS playlist with a meaningful “playlistname”. I’ll explain it at the end, but since it is based on a potentially changing menu structure, I don’t use it for a preset. Spotify probably uses an API that makes creating the address tricky, thus the plugin. The method you were trying “playlist”,“play”,“path”, requires the path to be something LMS can navigate to. If not, you are going to need it to do the heavy lifting for you, but, since I don’t use it, can’t help you with it. Not a Spotify user, so can’t help with specifics there, but here are some suggestions.įirst, I am assuming you have the Spotify plugin enabled and can navigate to the desired playlist through the web interface or other LMS control. While it made my head hurt, it’s been fun. I also had to put together two different methods to handle sequential server commands, the difference being how responses are handled. Additional functionality will be based on finding new needs, and requests that sound interesting.įor those of you that do coding, this code is parent-child device handlers that receive responses back from the server using Hubaction with a JSON body.
#Logitech media server page issues install#
I now consider this project fairly complete, unless I decide to try to write a player install helper smartapp. This was a big rewrite, and I have attempted to test, but expect you may still find issues. Temporary playlist saved used for announcements is now deleted after the announcement completes.Īdditional voices to support additional languages for speech have been added to the player settings. Power button and on() and off() commands have been added to players. The new interface removes the requirement that LMS be set to English. For example, p0=playlist&p1=play&p2=Morning%20Mix, is now “playlist”,“play”,“Morning Mix”. Documentation has been updated to reflect this. If you are using the preset buttons, they need to be changed to the JSON format.
#Logitech media server page issues update#
There is no need to reinstall devices, just update and publish the new versions. No changes to the Button manager smartapp. Both the Server and Player Device Handlers are updated. This is the change to the LMS JSON interface.
0 kommentar(er)
