GlennNZ 83 Posted January 24, 2016 Share Posted January 24, 2016 Hi all, Have been struggling through a few things by a bit of trial and error - but latest issue is cannot get Remote Control Commands to work. POSTs - as described in Wiki. Authenicated, passing Emby Token. Initally was getting this error setting up new API endpoint - thought would simplify - and still get same error in simple ConsoleApp. ??? Any help Thanks 2016-01-24 12:05:21.8637 Error HttpServer: Error processing request for /Sessions/cee34456d5a702be30cf5be5dccb0c61/Playing/Unpause *** Error Report *** Version: 3.0.5847.0 Command line: C:\Users\Vwin7\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Vwin7\AppData\Roaming\Emby-Server Application Path: C:\Users\Vwin7\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Object reference not set to an instance of an object. ServiceStack.HttpError No Stack Trace Available Link to comment Share on other sites More sharing options...
Luke 37272 Posted January 24, 2016 Share Posted January 24, 2016 Hi, have you compared your http requests to what the web client sends out when it remote controls? Link to comment Share on other sites More sharing options...
GlennNZ 83 Posted January 24, 2016 Author Share Posted January 24, 2016 Wow- thanks for the quick reply. Checking that now - does seem the same as webclient - Checking Headers etc. Swagger UI (finally got going) gives a appversion cannot be null error? Link to comment Share on other sites More sharing options...
GlennNZ 83 Posted January 24, 2016 Author Share Posted January 24, 2016 (edited) Thanks Luke More trial and error - Have it working in test console app. Not sure what the difference was - did change Authorization to X-Emby-Authorization, plus a few other minor changes. If I track down my issue - I'll update this post for future reference. ---> Back you go to Home Theatre! Glenn Edited January 24, 2016 by GlennNZ Link to comment Share on other sites More sharing options...
ebr 14960 Posted January 24, 2016 Share Posted January 24, 2016 Looks like maybe your connection wasn't properly initiated with all the needed data (appVersion, specifically). Link to comment Share on other sites More sharing options...
GlennNZ 83 Posted January 25, 2016 Author Share Posted January 25, 2016 Thanks That appVersion error - was only with Swagger. Was harder to track down other error - believe it was client Id doesn't support remote control (ie. new home theatre) Thanks Link to comment Share on other sites More sharing options...
ebr 14960 Posted January 25, 2016 Share Posted January 25, 2016 Thanks That appVersion error - was only with Swagger. Was harder to track down other error - believe it was client Id doesn't support remote control (ie. new home theatre) Thanks Ahhh.. yes, then that is actually proper behavior. The item trying to do the remote-controlling should be looking at the capabilities of the target device before attempting to send commands. 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