GlennNZ 83 Posted December 15, 2016 Share Posted December 15, 2016 Hi Luke I am having some major inconsistencies with PlayStateCommand Behaviour. I have created a new APIendpoint for remote control of a specified client - in line with SessionService code. (https://github.com/MediaBrowser/Emby/blob/1642b7316309c703e47094ef31b2b98be649103e/MediaBrowser.Api/Session/SessionsService.cs) Essentially sending a PlayStateCommand like [Route("/Sessions/{Id}/Playing/{Command}", "POST", Summary = "Issues a playstate command to a client")] It works - in the Web Browser for Pause (so must be sending details correctly) But no other command works - nothing else - Unpause, NextTrack PlayStateCommands sent to the web browser client - returns this error in inputmanager. Similar inconsistent control in Emby.Theatre. What is going on? Thanks Glenn Link to comment Share on other sites More sharing options...
Luke 37260 Posted December 15, 2016 Share Posted December 15, 2016 What is the issue in Theater exactly? Link to comment Share on other sites More sharing options...
GlennNZ 83 Posted December 15, 2016 Author Share Posted December 15, 2016 (edited) I stand corrected - testing back to Theatre - the SendPlayStateCommands - all function: The previous Theatre inconsistencies - was probably at my end - so when moved to Web Interface to run debug console - these other issues became apparent. Some of my testing issues - relates to restarting the server - whilst Emby Theatre reconnects to the server- the remote control does not correctly function unless theatre and server restarted Will run Theatre in Web Browser to continue to debug. Glenn Edited December 15, 2016 by GlennNZ Link to comment Share on other sites More sharing options...
Luke 37260 Posted December 15, 2016 Share Posted December 15, 2016 Ok so the issues right now are limited to the built-in web app, is that correct? Link to comment Share on other sites More sharing options...
GlennNZ 83 Posted December 15, 2016 Author Share Posted December 15, 2016 (edited) Yes. That is correct. Emby theatre correctly responses to Playstatecommands - IF closed and restarted following a server restart. If server restarted whilst theatre remains running (probably not uncommon scenario) variable response to sendplaystate commands. Build in web app - has the JavaScript errors you can see in the first post with the sendplaystate commands. (Rendering it a bit unhelpful for testing as I found) Glenn Edited December 15, 2016 by GlennNZ Link to comment Share on other sites More sharing options...
Luke 37260 Posted December 15, 2016 Share Posted December 15, 2016 Thanks for the report. Link to comment Share on other sites More sharing options...
Luke 37260 Posted January 3, 2017 Share Posted January 3, 2017 @@GlennNZ, for the next release of emby server everything should be consistent between the two apps. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now