Sagex and hash's (#)

[deanm]

Not sure if this is the correct place to post this and feel free to move it.

I’m looking for some assistance with a configuration problem and wanted to know if this is me misconfiguring Sagex or an issue with a hashs (#) in Sagex or even an SageTv API issue.

If I run the following Sagex command /sagex/api?c=GetConfiguredCaptureDeviceInputs I get the following list of Capture Devices/Tuners

TBS 6281 BDA Digital Capture DVBT #2 Digital TV Tuner
TBS 6281 BDA Digital Capture DVBT Digital TV Tuner
TBS 6205 DVBC Capture 3 Digital TV Tuner
TBS 6205 DVBC Capture 2 Digital TV Tuner
TBS 6205 DVBC Capture 1 Digital TV Tuner
TBS 6205 DVBC Capture 0 Digital TV Tuner
TBS 6985 BDA Digital Capture A DVBS Digital TV Tuner
TBS 6985 BDA Digital Capture B DVBS Digital TV Tuner
TBS 6985 BDA Digital Capture D DVBS Digital TV Tuner
TBS 6985 BDA Digital Capture C DVBS Digital TV Tuner

If I now run the following command for each Capture Device I get the correct result for example

/sagex/api?c=GetCaptureDeviceInputBroadcastStandard&1=TBS 6281 BDA Digital Capture DVBT Digital TV Tuner

Will give the correct result of.

<Result><![CDATA[DVB-T]]></Result>

My issue is when I try and run the Sagex command using TBS 6281 BDA Digital Capture DVBT #2 Digital TV Tuner it fails. In fact any command using the tuner with the hash (#) in the devices name fails.

Not sure if sagex is interpreting the hash (#) as some command or arg. Is there something I missing? Should I be encapsulating the Capture Device name? I have tired single and double quotes but they all fail.

I came across this issue a few years ago and never did get to the bottom of it.

Any suggestions appreciated.

Dean

[SHS]

Dean PM Narflex he my know the answer to you question

[wnjj]

Try ## in place of one # or try %23 instead of #.

[deanm]

Originally Posted by wnjj

Try ## in place of one # or try %23 instead of #.

Finaly!!!! after trying for so long

Replacing # with %23 fixed the problem.

Big Big Thank You

Dean

[tmiranda]

The command line must be UTF-8 encoded. That replaces all special characters with the ASCII codes. (Like %23).

If you do not UTF-8 encode the command line you will run into all sorts of issues.

[Pirin]

I believe that the commands need to be URL encoded (not UTF-8 ).

[tmiranda]

Originally Posted by Pirin

I believe that the commands need to be URL encoded (not UTF-8 ).

Tough crowd