NScriptHelper.dll

[sub]

I mean this kind of post that you and I request a lot https://forums.nextpvr.com/showthread.ph...post538897

Martin

As long as they've logged into the web app, they can open a tab and view that url. (it gets the sid from the user's existing session)

[sub]

You'll notice the browser automatically adds a .AspNetCore.Session=…… cookie to the web requests. On the server side, NextPVR determines the sid from this session.

[jcole998]

OK, I think I got it: No need to be signed in for NScriptHelper calls and SIDs are not an issue.

Finally, does NScriptHelper supply return codes? How? How is a recordings list returned? JSON? Is piping involved? Stdout? Scraping text files is lame. Web API returns nice neat JSON.

Is there a wiki somewhere?

[jcole998]

Gentle nudge...Post #23...

[jcole998]

OK. Maybe I'm stating my case poorly.

I use Powershell virtually always and have created quite a few useful scripts that help me track what I want to schedule. I'd like to keep using them and is a V5 show-stopper. Documentation of URL usage is lean and the single source I have was offered by mvallevand from source code in GitHub. Tough going but I've managed to get what I need...so far.

There is a section in that source code dealing with SIDs: "/service?method=session.initiate&ver=1.0&device=xbmc" and "/service?method=session.login&sid=%s&md5=%s", m_sid, md5.c_str()"
Questions:
- Is session.initiate required?
- Are these the exact parameters? What needs to be altered to make it work for my environment? &device? &ver?
- Is the session login required? MD5 is complicated but manageable.

I looked again at the "help" for NScriptHelper(here) and it appears that all output goes to StdOut which is not very data-friendly. There is much more information returned by URLs than NScriptHelper. (start and end times, season and episode, recording resource, etc.)

I'm hoping I can get some detailed help on URLs for V5. Community members are virtually my only source.

Thanks...

[mvallevand]

The session.initiate gets you a sid the login authenticates it. So yes you need to do it. md5 in ps seems pretty simple to me https://docs.microsoft.com/en-us/powersh...rshell-4.0

You need the parameters that you see. I only know device=emby gives richer details then device=kodi

I don't know what you mean that stdout is not data friendly. std is just a file that is displayed to the console by default. Just direct to a file if you need to.

Martin

[sub]

Sorry for the slow reply - I've been away the last few days.

Finally, does NScriptHelper supply return codes? How?

It doesn't currently, but I guess I should have it use a specific return code for failure.

How is a recordings list returned? JSON? Is piping involved? Stdout? Scraping text files is lame. Web API returns nice neat JSON.

These calls default to returning xml, but you can add &format=json to get json.

Is there a wiki somewhere?

No, not yet for v5 stuff. I'm thinking about how to address this though.

[sub]

There is a section in that source code dealing with SIDs: "/service?method=session.initiate&ver=1.0&device=xbmc" and "/service?method=session.login&sid=%s&md5=%s", m_sid, md5.c_str()"
Questions:
- Is session.initiate required?
- Are these the exact parameters? What needs to be altered to make it work for my environment? &device? &ver?
- Is the session login required? MD5 is complicated but manageable.

With NScriptHelper you wont need to worry about the session.

I looked again at the "help" for NScriptHelper(here) and it appears that all output goes to StdOut which is not very data-friendly.

Where would you want it to go?

There is much more information returned by URLs than NScriptHelper. (start and end times, season and episode, recording resource, etc.)

The NScriptHelper will return you the exact same information as the URLs when using these -service calls

dotnet NScriptHelper.dll -service:method=recording.lists&list=pending

[mvallevand]

It doesn't currently, but I guess I should have it use a specific return code for failure.

When it is an action you already send the rsp json/xml back. When there is an error you get it back too

dotnet NScriptHelper.dll -service:method=recording.lists&list=pending

I am pretty sure you need to use quotes around the method to keep it together.

Marin

[sub]

yes, you'd be right - if it's got a space of '&' character, it'd need quotes around it.