Boxee Box as an extender? (xbmc perhaps?)

[PiX64]

Have you tried completely removing the application from the boxee ui, shutting down boxee, removing the sagetv folder int he boxee/apps directory, and then redownloading it from the repository within boxee?

reason i ask is i have had this happen to me early on in this project. It seems that my settings got hosed up for some reason and it was causing the app not to launch.

Im not saying this is def. your problem, but something to try. I didn't see anything that jumps out at me in the log. I see wher eyou are failing, but it doesn' tmean much to me. the app in its startup decodes a json object, and for some reason it isn't finding the json object....my thought on this is that it is unable to reach your server to get the json object to decode...

[PiX64]

try this and see if you get a reply in you rbrowser

Originally Posted by Slugger

In a web browser, load this URL:

http://host:port/sagex/api?c=GetOS&encoder=json

Replace host and port with the host and port of your Jetty plugin. Do you get a response? If so, what is it? If you don't get a response saying something like:

{"Result":"Windows XP"}

Then the Boxee app will never load. Of course, sub the OS name as appropriate for your system. You must have the sagex remote APIs plugin installed on your Sage server and the HTTP interface must be enabled (it is by default). If you get a response like the one above then the remote APIs are working. If the boxee app still won't load then make sure you're specifying the settings properly. If it's still not working, enable debug logging in Boxee and try to load the app again. Then provide the log file with debug log statements shown.

[Slugger]

From whatever machine you're running boxee on, load this URL into your browser:

http://192.168.1.104:8080/sagex/api?size=50000&encoder=json&c=EvaluateExpression&1=Size%28GetOS%28%29%29+%3E+0

What's the response?

[rnadeau]

When I enter that into my browser it gives me error 404, Problem accessing /sagex/api. Reason:

NOT_FOUND
I did a cold boot before trying this. I verified sagex has the latest update. I can use jetty to access bmt and sage. Do I need to open a port in my router?

[Slugger]

Originally Posted by rnadeau

When I enter that into my browser it gives me error 404, Problem accessing /sagex/api. Reason:

NOT_FOUND
I did a cold boot before trying this. I verified sagex has the latest update. I can use jetty to access bmt and sage. Do I need to open a port in my router?

Nope, the same port is used. What this probably means is that you don't have the sagex remote services plugin installed on your Sage server. Verify that it's installed, install it if it's not, then try again.

As long as that URL says NOT_FOUND then the sagex remote services plugin is not install/not configured properly. And as long as that's the case, the boxee app can never work.

[rnadeau]

I know sagex is installed because I checked installed plugins to see if it could be configured like jetty and saw there was an update available and I installed it. Where would I go to configure it?

[Slugger]

There are two separate plugins in play here...

sagex-api, the remote APIs jar, which is probably installed already. But then there is a second one called sagex remote services (or something to that effect). That's the plugin that enables the HTTP interface for the remote APIs and is the one you appear to be lacking. If that's installed then something's wrong with it and you'll have to start investigating in the sagetv_0.txt log file along with any logs provided by sagex. However, my gut tells me it's simply not installed.

[rnadeau]

That was it. I had the sagex api installed but not the remote services. It now responds properly to the address you gave me to try. Thanks for all the help!

[Slugger]

Originally Posted by rnadeau

That was it. I had the sagex api installed but not the remote services. It now responds properly to the address you gave me to try. Thanks for all the help!

Score one for the gut!

[rnadeau]

Well I got the sage ui showing and can see the recorded shows. When I click on a show a window pops up to play the show. I click play and nothing happens. It just goes back to the previous screen that shows my recordings. Do I have to install a decoder on the boxee machine?

[Slugger]

Originally Posted by rnadeau

Well I got the sage ui showing and can see the recorded shows. When I click on a show a window pops up to play the show. I click play and nothing happens. It just goes back to the previous screen that shows my recordings. Do I have to install a decoder on the boxee machine?

boxee.log, please. My gut, at the risk of ruining my current winning streak, tells me you need to map local paths to UNC paths. When you load the boxee sagetv app, go to the settings. The expected mapping values are documented somewhere in this thread.

[Savage1701]

Probably old news, but apparently there is an alpha of Sage DVR interface control being ported to Boxee:

http://gigaom.com/video/sagetv-dvr-a...ming-to-boxee/

* merged *

[rnadeau]

Sorry it took so long. I was gone for a short while. Here is the log file. I have also had a problem every so often with boxee quitting and a window pop up saying this app has caused an error and gives me the option to send it to microsoft. I sent it and nothing happened. This has happened on 2 different computers. Is boxee unstable as far as you know? Both times it was while scanning movie folders. It also only shows 63 of the 561 movies I have on 5 drives. Have you run across this? Thanks!

[Slugger]

Originally Posted by rnadeau

Sorry it took so long. I was gone for a short while. Here is the log file. I have also had a problem every so often with boxee quitting and a window pop up saying this app has caused an error and gives me the option to send it to microsoft. I sent it and nothing happened. This has happened on 2 different computers. Is boxee unstable as far as you know? Both times it was while scanning movie folders. It also only shows 63 of the 561 movies I have on 5 drives. Have you run across this? Thanks!

You will need to enable debug logging in Boxee and try again.

[rnadeau]

Here is the log. I used debug option in the logging options. I tried to play 3 shows.

[Slugger]

Originally Posted by rnadeau

Here is the log. I used debug option in the logging options. I tried to play 3 shows.

Which three files did you try to play back? I don't see anything in the log showing you tried to start playback. The remote APIs are working, I can see the evidence of that. So it appears to be a playback issue only, but I can't find anything showing an attempt to playback files. It just might be lost in the clutter of the debug log so if I have the file names you tried to play back then I can search the log for them.

[rnadeau]

They were 3 different episodes of Warehouse 13.

[Slugger]

Found it:

15:03:35 T:18880 M:436289536   ERROR: InputStream: Error opening, C:\Shows\Warehouse13-S02E11-Reset-28913-0.mpg

Boxee can't open the file as specified. Are you running Boxee on a different system than your Sage server? If so, you have to share your recordings dir on the network and then map the path in Boxee so Boxee can read the files. That's done in the Sage app settings in Boxee.

[rnadeau]

I do have the folder shared on my sage server. How do I get to the sage app settings in Boxee?

[Slugger]

Originally Posted by rnadeau

I do have the folder shared on my sage server. How do I get to the sage app settings in Boxee?

Load the app, go to Settings > Boxee