Synology SPK for DVR Record Engine

[MNOiSY]

Installed the new package and getting some errors when I try to delete recordings from the dashboard.

I click delete and I get a pop up saying

Error invalid Status:
405 not allowed
nginx
status 405

[demonrik]

Installed the new package and getting some errors when I try to delete recordings from the dashboard.

I click delete and I get a pop up saying

Error invalid Status:
405 not allowed
nginx
status 405

yeah - I see it..
Sorry about that..
I know what the issue is.. I should have read the changelog better.
Before the default for the recorded_files returned all recordings so was a quick way to get full list sorted in recorded order from most recent.
But now it defaults to the root folder which basically is a list of series (and is in alphabetical order), so when you click delete it tries to delete a recording that isn't a recording and fails.
So I need to implement a full break down of each series 1 by 1 and then sort on date which is going to get messy
I have the basic workings of the code over in the HDHR_DVRUI, just need to port it and rework a few things.. so bear with me.

[MNOiSY]

Installed the new package and getting some errors when I try to delete recordings from the dashboard.

I click delete and I get a pop up saying

Error invalid Status:
405 not allowed
nginx
status 405

yeah - I see it..
Sorry about that..
I know what the issue is.. I should have read the changelog better.
Before the default for the recorded_files returned all recordings so was a quick way to get full list sorted in recorded order from most recent.
But now it defaults to the root folder which basically is a list of series (and is in alphabetical order), so when you click delete it tries to delete a recording that isn't a recording and fails.
So I need to implement a full break down of each series 1 by 1 and then sort on date which is going to get messy
I have the basic workings of the code over in the HDHR_DVRUI, just need to port it and rework a few things.. so bear with me.

I appreciate your patience and hard work just to help the community! I look forward to the update whenever you have it done!

[Sion]

Installed the new package and getting some errors when I try to delete recordings from the dashboard.

I click delete and I get a pop up saying

Error invalid Status:
405 not allowed
nginx
status 405

yeah - I see it..
Sorry about that..
I know what the issue is.. I should have read the changelog better.
Before the default for the recorded_files returned all recordings so was a quick way to get full list sorted in recorded order from most recent.
But now it defaults to the root folder which basically is a list of series (and is in alphabetical order), so when you click delete it tries to delete a recording that isn't a recording and fails.
So I need to implement a full break down of each series 1 by 1 and then sort on date which is going to get messy
I have the basic workings of the code over in the HDHR_DVRUI, just need to port it and rework a few things.. so bear with me.

So... should we avoid installing the May26 version for now? No hurry/pressure, just curious if its safe / good to go.

[demonrik]

Installed the new package and getting some errors when I try to delete recordings from the dashboard.

I click delete and I get a pop up saying

Error invalid Status:
405 not allowed
nginx
status 405

yeah - I see it..
Sorry about that..
I know what the issue is.. I should have read the changelog better.
Before the default for the recorded_files returned all recordings so was a quick way to get full list sorted in recorded order from most recent.
But now it defaults to the root folder which basically is a list of series (and is in alphabetical order), so when you click delete it tries to delete a recording that isn't a recording and fails.
So I need to implement a full break down of each series 1 by 1 and then sort on date which is going to get messy
I have the basic workings of the code over in the HDHR_DVRUI, just need to port it and rework a few things.. so bear with me.

So... should we avoid installing the May26 version for now? No hurry/pressure, just curious if its safe / good to go.

its safe to do - you lose the functionality of seeing the recordings properly
in next release I'm going to remove that anyway.
Trying to decide if on next release I will remove the UI completely and just move to something like I did for docker, and just have the conf file somewhere handy and have the start script just fetch the engine.. would remove most of the support pains.

[demonrik]

Removed - see OP for correct version and link

[Beerman]

I use both a QNAP and Synology to record (dual record engines). The QNAP install went fine and it appeared the Synology did but as I would like the recordings to default to the Synology, it only records to the QNAP. I noticed there is no Storage ID shown, just the message, "StorageID not Set". I don't know how to set the storage ID though I do know what that ID is.
How can I do this?

Thanks for all your hard work. As I said before, I'd gladly donate to the cause!

[demonrik]

I use both a QNAP and Synology to record (dual record engines). The QNAP install went fine and it appeared the Synology did but as I would like the recordings to default to the Synology, it only records to the QNAP. I noticed there is no Storage ID shown, just the message, "StorageID not Set". I don't know how to set the storage ID though I do know what that ID is.
How can I do this?

Thanks for all your hard work. As I said before, I'd gladly donate to the cause!

Are you saying the Synology won't record at all, or just that it won't default to it?
Make sure you update the MaxRecordedStreams for the latter - should be 0 on the QNAP.

I will look at the storageID thing..
would not be set if the user running the record engine can't write to the config file.. which is a bug.
The engine gets the UID for the storage and ID and writes to the config file.

[Beerman]

Yes but you are so fast and so good, you got back to me before I restarted the NAS. After a restart, it shows the Storage ID and does work now. I think it's supposed to record to the NAS with the biggest amount of space and that would be my Synology.
Not sure why I had to restart but I finally remembered needing to when I first installed your wonderful program.

I'll put this thru lots of recordings the rest of this week and post back if I find any oddities. This one was on me!
Thanks for the uber quick reply!

[demonrik]

Yes but you are so fast and so good, you got back to me before I restarted the NAS. After a restart, it shows the Storage ID and does work now. I think it's supposed to record to the NAS with the biggest amount of space and that would be my Synology.
Not sure why I had to restart but I finally remembered needing to when I first installed your wonderful program.

I'll put this thru lots of recordings the rest of this week and post back if I find any oddities. This one was on me!
Thanks for the uber quick reply!

hmm - implies something is sticking during the upgrade. Have seen it once before, but haven't been able to replicate again.. it's as if the record engine doesn't shut down during the upgrade.. but you should only need to do the restart via the app center and not full restart.
You are right about storage size though..

[MNOiSY]

Having the identical issue. StorageID is not set.

I have tried:
Restarting the app
Restarting the diskstation
Restarting hdhomerun device
Done both a fresh install and upgrade install with no success

0.8.3 was working (limping but working) but the new version won't seem to find the HDHomeRunDVR device.

Permissions seem correct (I think). I SSH'd in to manually add my storageid to the hdhomerun.conf file but was unable to since the file owner is hdhomerundvr.

The log on the dashboard (possible sensitive content replaced with *** for privacy) shows:

---------- Config File ----------------------------------------------------------
Location = /volume1/@appstore/HDHomeRunDVR/etc/HDHomeRunDVR.conf
RecordPath = /volume1/HDHomeRunDVR
RecordStreamsMax = 16
ServerPort = 59090
StorageID = StorageID not Set
---------- CONNECTIVITY CHECKS --------------------------------------------------
DVRUI_apiurl = http://api.hdhomerun.com/
Discover URL = http://api.hdhomerun.com/discover
Ping to api.hdhomerun.com success
curl extension = not available
checking alternative connection
stream returned = [ { "DeviceID": "********", "LocalIP": "192.168.0.120", "ConditionalAccess": 1, "BaseURL": "http://192.168.0.120", "DiscoverURL": "http://192.168.0.120/discover.json", "LineupURL": "http://192.168.0.120/lineup.json" }, { "StorageID": "******-****-****-****-******DEF6", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" }, { "StorageID": "******-****-****-****-******DEF6", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" }, { "StorageID": "******-****-****-****-******0B56", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" } ]
---------- HDHR TUNERS-----------------------------------------------------------
tuner(0) id: ********
tuner(0) model: HDHR3-CC
tuner(0) firmware: 20200521
tuner(0) baseurl: http://192.168.0.120
tuner(0) auth: guG-***********************
---------- HDHR DVR ENGINES------------------------------------------------------
---------- HDHR Account -----------------------------------------------------------
curl extension = not available
stream returned = { "AccountEmail": "************", "AccountDeviceIDs": [ "********" ], "DvrActive": 1, "AccountState": "Active" }
------------ DVR Series ------------------------------------------------------
?DisplayGroupID=root
------------ DVR Recordings ------------------------------------------------------

I am not sure if it matters but the last storageid seems to be different that the first two in the above log.

I also noticed when I tested 0.8.3 that the storage ID is completely different from the ones listed in the current log above.

Any ideas?

[demonrik]

Having the identical issue. StorageID is not set.

Have tried restarting the app, restarting the diskstation, and restarting hdhomerun device multiple times with no success. 0.8.3 was working (limping but working) but the new version wont seem to find the hdhomerun device. Done fresh install as well as upgrade install for the spk.

Permissions seem correct. I even SSH'd in to manually add my storageid to the hdhomerun.conf file but was unable to since the owner is hdhomerundvr.

Any ideas?

I don't know - need to go investigate..
I checked the installer and it sets the permissions correctly.. so something else is sticking such that the new user can't update the conf file..
I'll keep digging

[demonrik]

stream returned = [ { "DeviceID": "********", "LocalIP": "192.168.0.120", "ConditionalAccess": 1, "BaseURL": "http://192.168.0.120", "DiscoverURL": "http://192.168.0.120/discover.json", "LineupURL": "http://192.168.0.120/lineup.json" }, { "StorageID": "******-****-****-****-******DEF6", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" }, { "StorageID": "******-****-****-****-******DEF6", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" }, { "StorageID": "******-****-****-****-******0B56", "LocalIP": "192.168.0.170:59090", "BaseURL": "http://192.168.0.170:59090", "DiscoverURL": "http://192.168.0.170:59090/discover.json", "StorageURL": "http://192.168.0.170:59090/recorded_files.json" } ]

I am not sure if it matters but the last storageid seems to be different that the first two in the above log.

I also noticed when I tested 0.8.3 that the storage ID is completely different from the ones listed in the current log above.

Any ideas?

you're seeing 3 entries there for the 192.168.0.170 device because on restarting the storageID is not persistent so the engine makes up a new one and thus registers as a new device.
Need to fix the storage ID being persisted..

[MNOiSY]

It looks like it must be some type of permission issue.

Just to test, I created a new share at /volume1/HDHomeRun. Updated the location in the app settings, restarted the app and boom, it worked fine and found the record engine. If I change the location in the app back to the default /volume1/HDHomeRunDVR and restart the app, it will not work again.

I moved my recordings to the new share and it seems to be working fine now. I will simply keep this configuration until its resolved.

Thanks for all your hard work!!!!! I look forward to seeing what might be causing this.

[demonrik]

I can't replicate the issue

Can one of you SSH to the box and have a look at the conf file, e.g.

Code: Select all

ls -l /volume1/\@appstore/HDHomeRunDVR/etc

should see something like

Code: Select all

rik@NAS:/$ ls -l
total 4
-rw-rw-r-- 1 hdhomerundvr http 142 Jul  8 15:13 HDHomeRunDVR.conf