Hauppauge HD-PVR2

[mvallevand]

Ok then you must attempt to "find" config.xml to get the port and if so NShared must do an pseudo install before calling localhost.

I just checked the code, and I'm pretty sure the only thing it shares from anything in NextPVR is the log file functions.

It defaults to http://127.0.0.1:8866, and pin 0000, but these can be overridden with -server:xxxxx:8866 and -pin:1234

Ok but since he is running as a user with no environment it doesn't find /var/opt/nextpvr/config.xml and it creates the .NPVR-data folder structure for logging and also the default config.xml  

Code:

/home/martin/.NPVR-data/
/home/martin/.NPVR-data/logs
/home/martin/.NPVR-data/media
/home/martin/.NPVR-data/media/shows
/home/martin/.NPVR-data/media/channels
/home/martin/.NPVR-data/scripts
/home/martin/.NPVR-data/web
/home/martin/.NPVR-data/web/temp
Config.xml does not exists. Creating it from master.

That is why I suspect the pin now.
 
Martin

[christheman]

Ok then you must attempt to "find" config.xml to get the port and if so NShared must do an pseudo install before calling localhost.

I just checked the code, and I'm pretty sure the only thing it shares from anything in NextPVR is the log file functions.

It defaults to http://127.0.0.1:8866, and pin 0000, but these can be overridden with -server:xxxxx:8866 and -pin:1234

Ok but since he is running as a user with no environment it doesn't find /var/opt/nextpvr/config.xml and it creates the .NPVR-data folder structure for logging and also the default config.xml  

Code:

/home/martin/.NPVR-data/
/home/martin/.NPVR-data/logs
/home/martin/.NPVR-data/media
/home/martin/.NPVR-data/media/shows
/home/martin/.NPVR-data/media/channels
/home/martin/.NPVR-data/scripts
/home/martin/.NPVR-data/web
/home/martin/.NPVR-data/web/temp
Config.xml does not exists. Creating it from master.

That is why I suspect the pin now.
 
Martin

Sorry about that question in my last post.  I just noticed that there is a setting to enable [movie title (year)] format.  






The pin setting is a 4 digit number of my own (-pin:3232), both in the NextPVR access settings and with the NScriptHelper command line.  Also included is the IP address as IFCONFIG reports it, and port number 8866 (-server:192.168.2.149:8866)



I haven't touched the username/password settings, and the checkbox the allow Internet access is checked, though that didn't make any difference with the updateepg option.  "Press any key to close" is my own doing, just to keep it on screen.






Here are some screen captures I made from other NScriptHelper options.  From what I can tell, NScriptHelper worked out for me here.






-isrecording



   





-status



   





-pending



   








But the updateepg option remains exactly like the red text in this image, no changes made other than [-option] at the end of the command.



   

[mvallevand]

You probably need to change the pin in the pseudo config.xml but for testing just change the web server one to 0000

Martin

[christheman]

You probably need to change the pin in the pseudo config.xml but for testing just change the web server one to 0000

Martin

Doing that just gives me the other error message that says I cannot log in.  That and it creates a user profile under my name, with both MD5 hashes between /var/opt/...config.xml and /home/chris/...config.xml being the same.

P.S. Also the directories under my user name get created with the other options that do work.  First it creates the directories, then it executes those options.

With the Nextpvr access pin set to 0000, it just won't allow it to log on.  So that wasn't even a condition for me under my own testing circumstances.  (I'm wondering about just having the null set in there, no characters or spaces)

With all the pin numbers agreeing, it doesn't give me any login errors.  It just gives the red error, exactly as I posted, and only for updateepg.

[BrettB]

Ok then you must attempt to "find" config.xml to get the port and if so NShared must do an pseudo install before calling localhost.

I just checked the code, and I'm pretty sure the only thing it shares from anything in NextPVR is the log file functions.

It defaults to http://127.0.0.1:8866, and pin 0000, but these can be overridden with -server:xxxxx:8866 and -pin:1234

Ok but since he is running as a user with no environment it doesn't find /var/opt/nextpvr/config.xml and it creates the .NPVR-data folder structure for logging and also the default config.xml  

Code:

/home/martin/.NPVR-data/
/home/martin/.NPVR-data/logs
/home/martin/.NPVR-data/media
/home/martin/.NPVR-data/media/shows
/home/martin/.NPVR-data/media/channels
/home/martin/.NPVR-data/scripts
/home/martin/.NPVR-data/web
/home/martin/.NPVR-data/web/temp
Config.xml does not exists. Creating it from master.

That is why I suspect the pin now.
 
Martin

Sorry about that question in my last post.  I just noticed that there is a setting to enable [movie title (year)] format.  






The pin setting is a 4 digit number of my own (-pin:3232), both in the NextPVR access settings and with the NScriptHelper command line.  Also included is the IP address as IFCONFIG reports it, and port number 8866 (-server:192.168.2.149:8866)



I haven't touched the username/password settings, and the checkbox the allow Internet access is checked, though that didn't make any difference with the updateepg option.  "Press any key to close" is my own doing, just to keep it on screen.






Here are some screen captures I made from other NScriptHelper options.  From what I can tell, NScriptHelper worked out for me here.






-isrecording









-status









-pending












But the updateepg option remains exactly like the red text in this image, no changes made other than [-option] at the end of the command.

With the NextPVR server accepting the command, but returning the message "Not allowed", I'm guessing this is caused by a bug with work-in-progress toward a possible multi-user/multi-permission backend. Probably something that he's going to have to fix.

[mvallevand]

The .NPVR-data folder creation and use is expected behaviour. Sub could ignore the config.xml and use the api to write a remote log entry but it is not the end of the world.

The error is likely this one https://forums.nextpvr.com/showthread.php?tid=61135 a new NShared (the one on that post isn't the latest) will probably make the difference.

Wouldn't using the build in SD support make life a lot easier?


Martin

[christheman]

The .NPVR-data folder creation and use is expected behaviour.  Sub could ignore the config.xml and use the api to write a remote log entry but it is not the end of the world.

The error is likely this one https://forums.nextpvr.com/showthread.php?tid=61135 a new NShared (the one on that post isn't the latest) will probably make the difference.

That seems like exactly the same issue to me too.

Wouldn't using the build in SD support make life a lot easier?


Martin

LOL  Yeah probably so.

Is there an import log type of function for that though?  I just want to see that the data transfer was indeed successful on the last attempt.  I am used to watching Robert Eden's script run in real time.

[mvallevand]

The logs show a lot more information by channel when using SD JSON and you will get better meta art too.

If you know know epoch time you could use

dotnet NScriptHelper.dll -service:method=system.epg.summary -pin #### as confirmation.

Martin

[christheman]

Ok. I'll look into this later on.

Thanks to all for the help.