Problem with IP Tuning

[freewheeling]

I was having problems because the DirecTV receiver was switching on the screensaver and the IP Tuning wasn't turning it off. I modified the file for DirecTV HTTP Tuning by defining a "Select" command in the file with a string of hex codes from the USBUIRT tuner "learning" that I had from previous use of the USBUIRT for tuning, and now the Service shuts off every time I try to use the HDPVR. I have tried uninstalling SageTV7.1.9 and reinstalling it, and have also updated the driver for the HDPVR but it just won't work. I also removed the changes I had made to the *.ir file. I have removed the HDPVR Source and tried to reinstall it, but again as soon as I indicate that the HDPVR setting uses Components Sage TV stops and says it has lost the connection to the server. Something on the system has been corrupted but I have no idea what it is. I was going to see if the Total Media program works, but it looks like they no longer have a download for the latest version, because I guess they want me to buy a new CD for it.

Oh yes, after removing SageTV using the setup program it appears that it's not really removed because after reboot I was going to reinstall it and it was already running in the system tray, so something is pretty twisted up.

Any ideas what might have been corrupted? Has SageTV just faded away?

I should also say that I have an HVR 2250 and it still seems to work, so it's just the HDPVR.

Update: I tried to use the Hauppauge Scheduler but when it was time to start recording I got the popup message "Open registry key failed!"

[BobPhoenix]

Originally Posted by freewheeling

Update: I tried to use the Hauppauge Scheduler but when it was time to start recording I got the popup message "Open registry key failed!"

Hopefully you can get these problems resolved. This one make me want to try a registry repair. If you haven't already I would search on internet to see what you can do to repair it. There was a Microsoft knowledge base entry that I used when permissions in the registry got messed up on me. I ran the batch file which took an hour or so and fixed all the permissions on every registry entry. But your problem sounds worse than just a permissions issue.

[freewheeling]

Originally Posted by BobPhoenix

Hopefully you can get these problems resolved. This one make me want to try a registry repair. If you haven't already I would search on internet to see what you can do to repair it. There was a Microsoft knowledge base entry that I used when permissions in the registry got messed up on me. I ran the batch file which took an hour or so and fixed all the permissions on every registry entry. But your problem sounds worse than just a permissions issue.

By continued stubbornness I kept uninstalling and installing SageTV while intermittently using a program to repair the registry and eventually got to the point where the program would hang during boot specifically on the DirecTV Tuner.dll. I then went in and deleted all parts of that tuner plugin. At that point SageTV would boot up, so I installed the EXEMultiTunerPlugin, which was a someone more involved process. I now have it to the point where it will display the HD vid and record, but I still can't change the channel.

I noticed that in the Sage.properties file there are still the following references:

mmc/encoders/-431556906/5/0/brightness=128
mmc/encoders/-431556906/5/0/broadcast_standard=
mmc/encoders/-431556906/5/0/contrast=64
mmc/encoders/-431556906/5/0/device_name=StubDevice
mmc/encoders/-431556906/5/0/hue=125
mmc/encoders/-431556906/5/0/last_channel=202
mmc/encoders/-431556906/5/0/provider_id=29436723253
mmc/encoders/-431556906/5/0/saturation=64
mmc/encoders/-431556906/5/0/sharpness=128
mmc/encoders/-431556906/5/0/tuning_mode=
mmc/encoders/-431556906/5/0/tuning_plugin=C\:\\Program Files (x86)\\SageTV\\Common\\EXEMultiTunerPlugin.dll
mmc/encoders/-431556906/5/0/tuning_plugin_port=0
mmc/encoders/-431556906/5/0/video_crossbar_index=0
mmc/encoders/-431556906/5/0/video_crossbar_type=5
mmc/encoders/-431556906/90/0/available_channels=
mmc/encoders/-431556906/90/0/brightness=128
mmc/encoders/-431556906/90/0/broadcast_standard=
mmc/encoders/-431556906/90/0/contrast=64
mmc/encoders/-431556906/90/0/device_name=StubDevice
mmc/encoders/-431556906/90/0/hue=127
mmc/encoders/-431556906/90/0/last_channel=202
mmc/encoders/-431556906/90/0/provider_id=0
mmc/encoders/-431556906/90/0/saturation=64
mmc/encoders/-431556906/90/0/sharpness=128
mmc/encoders/-431556906/90/0/tuning_mode=
mmc/encoders/-431556906/90/0/tuning_plugin=C\:\\Program Files (x86)\\SageTV\\Common\\DirecTVTuner.dll
mmc/encoders/-431556906/90/0/tuning_plugin_port=0
mmc/encoders/-431556906/90/0/video_crossbar_index=0
mmc/encoders/-431556906/90/0/video_crossbar_type=90

It looks like to me that the same encoder is assigned to DirecTVTuner.dll and EXEMultiTunerPlugin. There's a whole bunch of junk in reference to old tuners that seems to have bee accreted so I'm not sure what to do to fix thing. After stopping the service and shutting down SageTV I did change the value of the following line from true to false. I figured that might get rid of some of the junk.

mmc/retain_lineups_for_lost_devices=false

But maybe I should change it back to "true." Anyway, it still doesn't change the channels.

Update: I just re-read the thread on installing EXEMultiTunerPlugin and discovered that: "If you're running 64 bit, the registry locations are a bit different. There will be a Wow6432Node folder under HKEY_LOCAL_MACHINE that you will have to use.
i.e. if the instructions say HKEY_LOCAL_MACHINE\Software\Frey Technologies use HKEY_LOCAL_MACHINE\Software\Wow6432Node\Frey Technologies "

I edited the instructions just slightly to be clearer and noted that there was no "software" subdirectory under HKEY_LOCAL_MACHINE\Wow6432\ . Now seems to be working. This was also probably the reason I ran into problems with the DirecTV HTTP Tuner.

[freewheeling]

Can't get the EXEMultiTunerPlugin to work. I thought it was working, but the channel doesn't change. I changed the registry as per instructions, modified the DirecTVMultiChg.bat file so that it has the same device name as used in Sage.properties and the correct IP address. I've rebooted half a dozen time. What could be wrong??

[BobPhoenix]

Since I don't use EXEMultiTuner can't really help with that. But what you can do for the tuner using both EXEMultiTuner and the DirecTV tuner DLL is delete all the mmc/encoder lines that have -431556906 in them. That will effectively remove the tuner from SageTV and you will have to set it up again. But this time you can setup EXEMultiTuner and maybe it will change channels correctly after that.

[freewheeling]

Originally Posted by BobPhoenix

Since I don't use EXEMultiTuner can't really help with that. But what you can do for the tuner using both EXEMultiTuner and the DirecTV tuner DLL is delete all the mmc/encoder lines that have -431556906 in them. That will effectively remove the tuner from SageTV and you will have to set it up again. But this time you can setup EXEMultiTuner and maybe it will change channels correctly after that.

Tried it. No change. Also, I tried using the browser to connect to http://192.168.0.21 which is the address of the HR44/500 receiver and it won't load the page, so something is blocking the connection. I believe the browser should connect to something. I'm not running Windows Firewall and my local router is in bridge mode, so I don't know what could be blocking the connection. It has been working.

[BobPhoenix]

Originally Posted by freewheeling

Tried it. No change. Also, I tried using the browser to connect to http://192.168.0.21 which is the address of the HR44/500 receiver and it won't load the page, so something is blocking the connection. I believe the browser should connect to something. I'm not running Windows Firewall and my local router is in bridge mode, so I don't know what could be blocking the connection. It has been working.

I'll try that myself tonight when I get home and post the results. Never actually tried that with my H24 model. Know I tried something like that from the DLL thread for one of my HR21, H21 or H23 boxes. It might have been a request for info as I vaguely remember more than just IP address when I tried it.

[BobPhoenix]

Originally Posted by freewheeling

Tried it. No change. Also, I tried using the browser to connect to http://192.168.0.21 which is the address of the HR44/500 receiver and it won't load the page, so something is blocking the connection. I believe the browser should connect to something. I'm not running Windows Firewall and my local router is in bridge mode, so I don't know what could be blocking the connection. It has been working.

OK when I just use the IP address I get nothing on my H24. When I issue the following command I get the options of the STB back: http://192.168.1.148:8080/info/getOptions. You would of course want to replace the IP address with yours.

In particular I got the following:

{
  "options": [
    {
      "command": "/info/getLocations",
      "description": "List of available client locations. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        }
      ]
    },
    {
      "command": "/info/getSerialNum",
      "description": "STB serial number. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        }
      ]
    },
    {
      "command": "/info/getVersion",
      "description": "Set-top-box and SHEF information. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        }
      ]
    },
    {
      "command": "/info/mode",
      "description": "Set-top-box mode. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        }
      ]
    },
    {
      "command": "/remote/processKey",
      "description": "Process a key request from the remote control. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "hold",
          "type": "string"
        },
        {
          "isRequired": true,
          "name": "key",
          "type": "string"
        }
      ]
    },
    {
      "command": "/serial/processCommand",
      "description": "Process a command request from remote control. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": true,
          "name": "cmd",
          "type": "hex"
        }
      ]
    },
    {
      "command": "/tv/getProgInfo",
      "description": "Program information of specified channel at current or specific time. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "minor",
          "type": "int"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": true,
          "name": "major",
          "type": "int"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "time",
          "type": "long"
        }
      ]
    },
    {
      "command": "/tv/getTuned",
      "description": "Information about the currently viewed program. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "videoWindow",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        }
      ]
    },
    {
      "command": "/tv/tune",
      "description": "Tune to a channel. Warning: This command may change or be disabled in the future.",
      "formControls": [],
      "urlParameters": [
        {
          "isRequired": false,
          "name": "wrapper",
          "type": "string"
        },
        {
          "isRequired": false,
          "name": "minor",
          "type": "int"
        },
        {
          "isRequired": false,
          "name": "callback",
          "type": "string"
        },
        {
          "isRequired": true,
          "name": "major",
          "type": "int"
        },
        {
          "isRequired": false,
          "name": "source",
          "type": "int"
        },
        {
          "isRequired": false,
          "name": "clientAddr",
          "type": "string"
        }
      ]
    }
  ],
  "status": {
    "code": 200,
    "commandResult": 0,
    "msg": "OK.",
    "query": "/info/getOptions"
  }
}

[freewheeling]

Originally Posted by BobPhoenix

OK when I just use the IP address I get nothing on my H24. When I issue the following command I get the options of the STB back: http://192.168.1.148:8080/info/getOptions. You would of course want to replace the IP address with yours.

I tried the command http://192.168.0.021:8080/info/getOptions and again just got a timeout. I tried pinging the location and had no problem from a user prompt. Thinking that my virus protection might be the problem I disabled that, and it didn't help with the HTTP. I have, in the past, used the simpler DirecTV HTTP Tuner, but that no longer works either.

[BobPhoenix]

Originally Posted by freewheeling

I tried the command http://192.168.0.021:8080/info/getOptions and again just got a timeout. I tried pinging the location and had no problem from a user prompt. Thinking that my virus protection might be the problem I disabled that, and it didn't help with the HTTP. I have, in the past, used the simpler DirecTV HTTP Tuner, but that no longer works either.

I was using chrome not IE. If you were using IE you might try a different browser. But I really am guessing NOW!

[Skirge01]

Have you verified that the IP address you think it's at is still what the receiver thinks?

[freewheeling]

Originally Posted by Skirge01

Have you verified that the IP address you think it's at is still what the receiver thinks?

About a dozen times. It's the right address. I used both Chrome and Firefox to try the http command, so it's not the browser either. The HR44/500 can be set to either IR or RF remotes, and I can't recall which one it was on when I had http tuning working before, but it was responding to both RF and IR remotes at the same time. I don't know if that would impact the HTTP tuning at all.

[Skirge01]

Interesting. Does the receiver respond to a ping?

[freewheeling]

Originally Posted by Skirge01

Interesting. Does the receiver respond to a ping?

Yes, pings OK.

[BobPhoenix]

Originally Posted by freewheeling

Yes, pings OK.

I wonder if they changed the port from 8080 to something else. I guess you could randomly try other ports but maybe there is info about the box on the internet about the port.

[Skirge01]

Try opening up ports 8082 and 8083 on your router to see if that changes anything[1]. Also, you could try opening up all ports to the STB just to see if that resolves the issue.

[freewheeling]

Originally Posted by Skirge01

Try opening up ports 8082 and 8083 on your router to see if that changes anything[1]. Also, you could try opening up all ports to the STB just to see if that resolves the issue.

Well, access to the router is problematic. I'm working on it, but if I had access I could just look at the logs to see if it's a porting problem. The odd thing is that it was working for a few days but then cut off after I tried to send a "select" command after the channel and defined select as a series of hex numbers that I got from Girder. At that point the server started crashing. I eventually got it working again after giving up on the "select" command because I got no guidance on how to define an instruction set, but haven't been able to change channels since. I can't even define an IR set because the "learning" always generates an error after zipping through the part where I'm supposed to press a button so fast I can't even read it.

[freewheeling]

By the way, if I could figure out how to make Girder work I could probably use that since I have a full definition of the IR command set. But I've never been able to figure out how to get Girder to work and connect it to SageTV.

[jchiso]

These problems seem to be hardware-related. Do you have an Android tablet or phone? If so, download the DirecTV app and try sending commands via that route. I am able to control five STBs on four different SageTV servers using IP tuning without problems.

I'm not sure what all you've attempted, but at a minimum you should be able to invoke a command-line channel change like this:

http://192.168.1.123:8080/tv/tune?major=0229

replace "192.168.1.123" with the STB's IP address. This should tune to HGTV. I f it doesn't then check the box's IP ...

[freewheeling]

Originally Posted by jchiso

These problems seem to be hardware-related. Do you have an Android tablet or phone? If so, download the DirecTV app and try sending commands via that route. I am able to control five STBs on four different SageTV servers using IP tuning without problems.

I'm not sure what all you've attempted, but at a minimum you should be able to invoke a command-line channel change like this:

http://192.168.1.123:8080/tv/tune?major=0229

replace "192.168.1.123" with the STB's IP address. This should tune to HGTV. I f it doesn't then check the box's IP ...

I issued the command (changing the address to 192.168.0.21) and got the following back:

{"status": {
"code": 403,
"commandResult": 1,
"msg": "Forbidden.Invalid URL parameter(s) found.",
"query": "/tv/tune?major=0229"
}}

Progress?

I also noted that the configuration for STB services is for port 27161. The setup establishes the box with a static IP of 192.168.0.21. Do I need to change the STB services port?

Update: I tried the commands using port 27161 instead of 8080 and got nothing. Also when I tried the channel change again using port 8080 it no longer "worked" and it just timed out.