Synology SPK for DVR Record Engine

Downloads & Instructions
Post Reply
PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

No firewall on the NAS.

The router had firewall set to ‘medium’. I set to off temporarily but it made no difference.

I don’t get why my HDHomeRun does not show up at http://my.hdhomerun.com even though it’s working?

I feel if I can solve that the DVR will follow.

signcarver
Expert
Posts: 9114
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F 15300C36

Re: Synology SPK for DVR Record Engine

Post by signcarver »

If I am understanding the issue you are having, most likely it isn't with the engine. I would check the engines logs.

Double check that the tuner has access to the internet as the DVR can't work (other than live/ serving recordings) without proper DeviceAuth. Check the logs of the tuner for web errors and also check that it has proper DeviceAuth (the tuner's discover.json page) Try rebooting the tuner and then restarting the engine.

There are many other reasons a device wouldn't show up at my.hdhomerun.com including public ip address being different (no vpn/proxy).

Though I don't think it would necessarily be an issue for installing to a nas, I don't know how demonrik wrote this installer though would probably expect a few "extras" not to work on web pages as many web apps rely on my.hdhomerun.com for discovery but the engine itself doesn't need such.

PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

This is the log (I think?) from the DVR manager below. But it does not find the HDHomeRun either;

---------- OS and ENV VARIABLES --------------------------------------------------
Operating System = Linux NAS 2.6.32.12 #25426 Tue May 12 04:42:15 CST 2020 armv5tel
HTTP_HOST = 192.168.3.106
SERVER_NAME = 192.168.3.106
SERVER_ADDR = 192.168.3.106
SERVER_SOFTWARE = nginx/1.16.1
SYS TEMP = /var/services/tmp
---------- PHP INFO -------------------------------------------------------------
php version = 7.2.29
php.ini file = /volume1/@appstore/PHP7.2/misc/php-fpm.ini
php.ini date.timezone =
date_default_timezone_get() = UTC
---------- DVRUI VARS -----------------------------------------------------------
DVRUI_DEBUG =
DVRUI_name = HDHomeRun DVR Manager
DVRUI_version = 1.0.0
DVRUI_TZ =
---------- PERMISSIONS ----------------------------------------------------------
style = 0755
style/style.css = 0755
---------- 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 = []
---------- HDHR TUNERS-----------------------------------------------------------
---------- HDHR DVR ENGINES------------------------------------------------------
---------- HDHR Account -----------------------------------------------------------
curl extension = not available
stream returned =
------------ DVR Series ------------------------------------------------------
?DisplayGroupID=root
------------ DVR Recordings ------------------------------------------------------

signcarver
Expert
Posts: 9114
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F 15300C36

Re: Synology SPK for DVR Record Engine

Post by signcarver »

That wasn't the log I was referring to but the actual Engine's log which should be in your recording folder if it started. I would not expect a tuner to show up there if you don't see it at my.hdhomerun.com but there isn't a need to discover a tuner to get the engine installed (though demonrik may have written the code to need such before going on to the next bit... He may also rely on such for StorageID but that should get set when engine is first run and has proper settings of restrictions to the .conf file)

What I was trying to see is if the engine discovered the tuner (reaches out with broadcast discovery, not reliant on my.hdhomerun.com).

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

PeterAG wrote:
Mon Jul 27, 2020 1:30 pm
I don’t get why my HDHomeRun does not show up at http://my.hdhomerun.com even though it’s working?
I feel if I can solve that the DVR will follow.
Most likely
Note: Just because the DVR Manager is working doesn't mean the engine is.. at the bottom is a status bar, and it should say 'HDHomeRun RECORD running'
i.e.
Image
not
Image
If you can open http://nasip:59090 and get the record engine page back then is running - should look similar to
Image
Then the record engine is installed and running.
If it comes back with an error - then the record engine is likely not running

As @signcarver suggest - go look at the engine logs on your NAS.. maybe there is something in there.

If for some reason the engine is running, and nothing obvious is in the logs then you might have something else going on preventing the record engine being detected.
  • Firewall on NAS - you confirmed turning off didn't change, but did you restart the engine afterwards?
  • VPN Client on NAS - some folks use the multimedia functions use VPN for various connections, this will mean the record engine will be on that network and not your local one!
  • Did your DVR registration expire maybe?

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

PeterAG wrote:
Mon Jul 27, 2020 1:55 pm
This is the log (I think?) from the DVR manager below. But it does not find the HDHomeRun either;

---------- OS and ENV VARIABLES --------------------------------------------------
Operating System = Linux NAS 2.6.32.12 #25426 Tue May 12 04:42:15 CST 2020 armv5tel
HTTP_HOST = 192.168.3.106
SERVER_NAME = 192.168.3.106
SERVER_ADDR = 192.168.3.106
SERVER_SOFTWARE = nginx/1.16.1
SYS TEMP = /var/services/tmp
---------- PHP INFO -------------------------------------------------------------
php version = 7.2.29
php.ini file = /volume1/@appstore/PHP7.2/misc/php-fpm.ini
php.ini date.timezone =
date_default_timezone_get() = UTC
---------- DVRUI VARS -----------------------------------------------------------
DVRUI_DEBUG =
DVRUI_name = HDHomeRun DVR Manager
DVRUI_version = 1.0.0
DVRUI_TZ =
---------- PERMISSIONS ----------------------------------------------------------
style = 0755
style/style.css = 0755
---------- 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 = []
---------- HDHR TUNERS-----------------------------------------------------------
---------- HDHR DVR ENGINES------------------------------------------------------
---------- HDHR Account -----------------------------------------------------------
curl extension = not available
stream returned =
------------ DVR Series ------------------------------------------------------
?DisplayGroupID=root
------------ DVR Recordings ------------------------------------------------------
No Tuners and No HDHR account indicates a problem with your network - or you have no tuners and thus no authorization code to find.
That the connectivity checks doesn't return anything yet the ping is ok is worrying
signcarver wrote:
Mon Jul 27, 2020 2:02 pm
That wasn't the log I was referring to but the actual Engine's log which should be in your recording folder if it started. I would not expect a tuner to show up there if you don't see it at my.hdhomerun.com but there isn't a need to discover a tuner to get the engine installed (though demonrik may have written the code to need such before going on to the next bit... He may also rely on such for StorageID but that should get set when engine is first run and has proper settings of restrictions to the .conf file)
The engines bit in the diagnostics log isn't enabled for the DVR Manager (reuse from DVRUI)
What I was trying to see is if the engine discovered the tuner (reaches out with broadcast discovery, not reliant on my.hdhomerun.com).
You should have log files at the bottom of the DVR Manager
Image

PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

I can find the HDHomerun at its IP address, and I can ping it successfully. Works ok, and I can't see any error in the below log.

I only have basic level knowledge on these things, but I am assuming HDHomerun needs to contact the SD server over the internet. SO do I need to check if a particular port should be open, or made open? Or do I need to enter an IP address in as "whitelisted" on the router?

19700101-00:00:00 System: reset reason = power on
19700101-00:00:02 System: network link 100f
19700101-00:00:05 System: ip address obtained: 192.168.3.111 / 255.255.255.0
20200726-16:05:30 System: time changed from Thu Jan 1 00:00:23 1970 to Sun Jul 26 16:05:30 2020
20200726-16:05:31 Tuner: tuner0 tuning 24 ITV4 (t8dvbt:578MHz-8330)
20200726-16:05:31 Tuner: tuner0 streaming http to 192.168.3.107:50933
20200726-16:05:44 Tuner: tuner0 http stream ended (remote closed)
20200726-16:40:30 Tuner: tuner0 tuning 15 Channel 4+1 (t8dvbt:578MHz-8452)
20200726-16:40:31 Tuner: tuner0 streaming http to 192.168.3.123:49551
20200726-16:40:39 Tuner: tuner0 http stream ended (remote closed)
20200726-16:40:39 Tuner: tuner0 tuning 17 Really (t8dvbt:594MHz-23712)
20200726-16:40:39 Tuner: tuner0 streaming http to 192.168.3.123:49552
20200726-16:40:55 Tuner: tuner0 http stream ended (remote closed)
20200726-16:47:12 Tuner: tuner0 tuning 17 Really (t8dvbt:594MHz-23712)
20200726-16:47:12 Tuner: tuner0 streaming http to 192.168.3.123:49557
20200726-16:47:17 Tuner: tuner0 http stream ended (remote closed)
20200726-17:26:20 Tuner: tuner0 tuning 24 ITV4 (t8dvbt:578MHz-8330)
20200726-17:26:20 Tuner: tuner0 streaming http to 192.168.3.107:51895
20200726-17:26:32 Tuner: tuner0 http stream ended (remote closed)
20200726-17:26:32 Tuner: tuner0 tuning 21 5 USA (t8dvbt:570MHz-12992)
20200726-17:26:33 Tuner: tuner0 streaming http to 192.168.3.107:51910
20200726-17:26:56 Tuner: tuner0 http stream ended (remote closed)
20200726-17:26:56 Tuner: tuner0 tuning 102 BBC TWO HD (t8dvbt2:586MHz-17472)
20200726-17:26:57 Tuner: tuner0 streaming http to 192.168.3.107:51913
20200726-17:38:05 Tuner: tuner0 http stream ended (remote closed)
20200726-17:38:45 Tuner: tuner0 tuning 17 Really (t8dvbt:594MHz-23712)
20200726-17:38:45 Tuner: tuner0 streaming http to 192.168.3.123:49572
20200726-17:39:22 Tuner: tuner0 http stream ended (remote closed)
20200726-17:51:09 Tuner: tuner0 tuning 17 Really (t8dvbt:594MHz-23712)
20200726-17:51:10 Tuner: tuner0 streaming http to 192.168.3.123:49585
20200726-17:51:31 Tuner: tuner0 http stream ended (remote closed)
20200727-04:05:12 System: ip address expired
20200727-04:05:22 System: ip address obtained: 192.168.3.111 / 255.255.255.0
20200727-16:05:21 System: ip address expired
20200727-16:05:35 System: ip address obtained: 192.168.3.111 / 255.255.255.0
20200727-20:20:39 Tuner: tuner3 tuning 16 QVC (t8dvbt:570MHz-13120)
20200727-20:20:39 Tuner: tuner3 streaming http to 192.168.3.108:50214
20200727-20:20:39 Tuner: tuner3 lockkey forced release by 192.168.3.108
20200727-20:20:59 Tuner: tuner3 http stream ended (remote closed)
20200727-20:21:51 Tuner: tuner3 tuning 68 BBC FOUR (t8dvbt:562MHz-4544)
20200727-20:21:52 Tuner: tuner3 streaming http to 192.168.3.108:50215
20200727-20:21:52 Tuner: tuner3 lockkey forced release by 192.168.3.108
20200727-20:36:08 Tuner: tuner3 http stream ended (remote closed)
20200728-04:05:34 System: ip address expired
20200728-04:05:53 System: ip address obtained: 192.168.3.111 / 255.255.255.0
20200728-12:21:00 Tuner: tuner0 tuning 102 BBC TWO HD (t8dvbt2:586MHz-17472)
20200728-12:21:01 Tuner: tuner0 streaming http to 192.168.3.124:54934
20200728-12:27:53 Tuner: tuner0 http stream ended (remote closed)
20200728-13:26:22 Tuner: tuner0 tuning 102 BBC TWO HD (t8dvbt2:586MHz-17472)
20200728-13:26:23 Tuner: tuner0 streaming http to 192.168.3.124:56350
20200728-13:26:33 Tuner: tuner0 http stream ended (remote closed)
20200728-13:26:33 Tuner: tuner0 tuning 101 BBC 1 Scot HD (t8dvbt2:586MHz-17596)
20200728-13:26:34 Tuner: tuner0 streaming http to 192.168.3.124:56359
20200728-13:26:44 Tuner: tuner0 http stream ended (remote closed)
20200728-16:05:52 System: ip address expired
20200728-16:06:06 System: ip address obtained: 192.168.3.111 / 255.255.255.0
20200728-16:18:14 Tuner: tuner0 tuning 101 BBC 1 Scot HD (t8dvbt2:586MHz-17596)
20200728-16:18:14 Tuner: tuner0 streaming http to 192.168.3.124:59333
20200728-16:19:04 Tuner: tuner1 tuning 17 Really (t8dvbt:594MHz-23712)
20200728-16:19:04 Tuner: tuner1 streaming http to 192.168.3.110:50543
20200728-16:19:24 Tuner: tuner1 http stream ended (remote closed)
20200728-16:19:24 Tuner: tuner1 tuning 104 Channel 4 HD (t8dvbt2:586MHz-17664)
20200728-16:19:25 Tuner: tuner1 streaming http to 192.168.3.110:50544
20200728-16:20:50 Tuner: tuner1 http stream ended (remote closed)
20200728-16:20:58 Tuner: tuner0 http stream ended (remote closed)

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

PeterAG wrote:
Tue Jul 28, 2020 9:28 am
I can find the HDHomerun at its IP address, and I can ping it successfully. Works ok, and I can't see any error in the below log.

I only have basic level knowledge on these things, but I am assuming HDHomerun needs to contact the SD server over the internet. SO do I need to check if a particular port should be open, or made open? Or do I need to enter an IP address in as "whitelisted" on the router?

.....
Wrong log - that is from your HDHomerun tuner, not the record engine
Can you access the record engine at your NAS's IP? http://192.168.3.106:59090
Can you check the log in the DVR Manager?

Also - can you please check the running/not-running status message at bottom of DVR Manager

PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

I uninstalled, rebooted and re-installed the DVR manager. On the NAS in the Packages window it says it is running.

I can't access the record engine at http://192.168.3.106:59090

I can access the DVR Manager. That says RECORD not running.

It shows the HDHomerun as discovered.

The log looks as follows (with some xxxx to cover details)

---------- OS and ENV VARIABLES --------------------------------------------------
Operating System = Linux NAS 2.6.32.12 #25426 Tue May 12 04:42:15 CST 2020 armv5tel
HTTP_HOST = 192.168.3.106
SERVER_NAME = 192.168.3.106
SERVER_ADDR = 192.168.3.106
SERVER_SOFTWARE = nginx/1.16.1
SYS TEMP = /var/services/tmp
---------- PHP INFO -------------------------------------------------------------
php version = 7.2.29
php.ini file = /volume1/@appstore/PHP7.2/misc/php-fpm.ini
php.ini date.timezone =
date_default_timezone_get() = UTC
---------- DVRUI VARS -----------------------------------------------------------
DVRUI_DEBUG =
DVRUI_name = HDHomeRun DVR Manager
DVRUI_version = 1.0.0
DVRUI_TZ =
---------- PERMISSIONS ----------------------------------------------------------
style = 0755
style/style.css = 0755
---------- 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": "1250xxxx", "LocalIP": "192.168.3.111", "BaseURL": "http://192.168.3.111", "DiscoverURL": "http://192.168.3.111/discover.json", "LineupURL": "http://192.168.3.111/lineup.json" } ]
---------- HDHR TUNERS-----------------------------------------------------------
tuner(0) id: 1250xxxx
tuner(0) model: HDHR5-4DT
tuner(0) firmware: 20200521
tuner(0) baseurl: http://192.168.3.111
tuner(0) auth: so5ziDqaWWg0fteezp_xxxxx
---------- HDHR DVR ENGINES------------------------------------------------------
---------- HDHR Account -----------------------------------------------------------
curl extension = not available
stream returned = { "AccountEmail": "petexxx@gmail.com", "AccountDeviceIDs": [ "1250xxxx" ], "DvrActive": 1, "AccountState": "Active" }
------------ DVR Series ------------------------------------------------------
?DisplayGroupID=root
------------ DVR Recordings ------------------------------------------------------


Below is the most recent recording log. (I deleted a bunch of the duplicated lines to shorten it).

HDHomeRun RECORD 20200225 Linux 08E55D2C-A3EB-199E-28EB-68A866DE16C8
20200629-00:00:48 Status: Resource: nbk=0 dmk=294
20200629-00:00:49 Recorded: directory /volume1/HDHomeRunDVR/ with 3 subdirs and 0 recordings
20200629-00:02:48 Status: Resource: nbk=0 dmk=294
20200629-00:04:48 Status: Resource: nbk=0 dmk=294

20200629-01:47:28 Recording: sending discover using local ip 192.168.3.106
20200629-01:47:28 Recording: sending discover using local ip 192.168.3.106
20200629-01:47:28 Recording: discover response from 08E55D2C-A3EB-199E-28EB-68A866DE16C8 http://192.168.3.106:59090
20200629-01:47:28 Recording: discover response from 12503253 http://192.168.3.111:80
20200629-01:47:28 Recorded: recorded sync to record-api.hdhomerun.com
20200629-01:47:28 Recording: event download from record-api.hdhomerun.com
20200629-01:47:28 Recording: 12503253 lineup request success (found 152 channels)
20200629-01:47:30 System: server time = Mon Jun 29 01:47:30 2020 (correction of 0s)
20200629-01:47:30 Recorded: recorded sync success
20200629-01:47:30 System: server time = Mon Jun 29 01:47:30 2020 (correction of 0s)
20200629-01:47:30 Recording: event download success
20200629-01:47:30 Recording: disk space available = 3265GB
20200629-01:47:30 Recording: current time = Mon Jun 29 01:47:30 2020 (correction of 0s)
20200629-01:47:30 Recording: no timer events planned
20200629-01:48:48 Status: Resource: nbk=0 dmk=294
20200629-01:50:48 Status: Resource: nbk=0 dmk=294

20200629-03:51:32 Recording: sending discover using local ip 192.168.3.106
20200629-03:51:32 Recording: sending discover using local ip 192.168.3.106
20200629-03:51:33 Recording: discover response from 08E55D2C-A3EB-199E-28EB-68A866DE16C8 http://192.168.3.106:59090
20200629-03:51:33 Recording: discover response from 12503253 http://192.168.3.111:80
20200629-03:51:33 Recorded: recorded sync to record-api.hdhomerun.com
20200629-03:51:33 Recording: event download from record-api.hdhomerun.com
20200629-03:51:33 Recording: 12503253 lineup request success (found 152 channels)
20200629-03:51:34 System: server time = Mon Jun 29 03:51:34 2020 (correction of 0s)
20200629-03:51:34 Recorded: recorded sync success
20200629-03:51:34 System: server time = Mon Jun 29 03:51:34 2020 (correction of 0s)
20200629-03:51:34 Recording: event download success
20200629-03:51:34 Recording: disk space available = 3265GB
20200629-03:51:34 Recording: current time = Mon Jun 29 03:51:34 2020 (correction of 0s)
20200629-03:51:34 Recording: no timer events planned
20200629-03:52:48 Status: Resource: nbk=0 dmk=294
20200629-03:54:48 Status: Resource: nbk=0 dmk=294

20200629-05:50:22 Recording: sending discover using local ip 192.168.3.106
20200629-05:50:23 Recording: sending discover using local ip 192.168.3.106
20200629-05:50:23 Recording: discover response from 08E55D2C-A3EB-199E-28EB-68A866DE16C8 http://192.168.3.106:59090
20200629-05:50:23 Recording: discover response from 12503253 http://192.168.3.111:80
20200629-05:50:23 Recorded: recorded sync to record-api.hdhomerun.com
20200629-05:50:23 Recording: event download from record-api.hdhomerun.com
20200629-05:50:23 Recording: 12503253 lineup request success (found 152 channels)
20200629-05:50:24 System: server time = Mon Jun 29 05:50:24 2020 (correction of 0s)
20200629-05:50:24 Recorded: recorded sync success
20200629-05:50:24 System: server time = Mon Jun 29 05:50:24 2020 (correction of -1s)
20200629-05:50:24 Recording: event download success
20200629-05:50:24 Recording: disk space available = 3265GB
20200629-05:50:24 Recording: current time = Mon Jun 29 05:50:24 2020 (correction of -1s)
20200629-05:50:24 Recording: no timer events planned
20200629-05:50:48 Status: Resource: nbk=0 dmk=294
20200629-05:52:48 Status: Resource: nbk=0 dmk=294

20200629-07:52:59 Recording: sending discover using local ip 192.168.3.106
20200629-07:53:00 Recording: sending discover using local ip 192.168.3.106
20200629-07:53:00 Recording: discover response from 08E55D2C-A3EB-199E-28EB-68A866DE16C8 http://192.168.3.106:59090
20200629-07:53:00 Recording: discover response from 12503253 http://192.168.3.111:80
20200629-07:53:00 Recorded: recorded sync to record-api.hdhomerun.com
20200629-07:53:00 Recording: event download from record-api.hdhomerun.com
20200629-07:53:00 Recording: 12503253 lineup request success (found 152 channels)
20200629-07:53:01 System: server time = Mon Jun 29 07:53:01 2020 (correction of 0s)
20200629-07:53:01 Recorded: recorded sync success
20200629-07:53:01 System: server time = Mon Jun 29 07:53:01 2020 (correction of -1s)
20200629-07:53:01 Recording: event download success
20200629-07:53:01 Recording: disk space available = 3265GB
20200629-07:53:01 Recording: current time = Mon Jun 29 07:53:01 2020 (correction of -1s)
20200629-07:53:01 Recording: no timer events planned
20200629-07:54:48 Status: Resource: nbk=0 dmk=294
20200629-07:56:48 Status: Resource: nbk=0 dmk=294

PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

And now its back as it was - can't find HDHomerun, and the DVR manager does not show it either....

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

PeterAG wrote:
Tue Jul 28, 2020 10:09 am
And now its back as it was - can't find HDHomerun, and the DVR manager does not show it either....
I can't resolve your HDHomeRun tuner disappearance act..
But lets see if I can at least resolve the record engine.

As you noted - the DVR Manager says the engine is not running, and hasn't been since the end of June (date of log file).
That means on trying to get started something went wrong.
It can be many things
Of curiosity is when the DVR Manager detected the HDHomeRun tuner and managed to access api.hdhomerun.com to get a response but in other diagnostics it didn't.

In your original post I thought we had the engine running so didn't really think through the things that might stop the engine from running.
I see you upgraded.
Did you add the new user as required in the 1.0.0 post
you need to add the 'hdhomerundvr' user with read/write permissions to your RecordPath share - which looks like /volume1/HDHomeRunDVR in your case..
You can do this in the synology desktop by
  • opening up the 'Control Panel' -> 'Shared Folders'
  • select HDHomeRunDVR share
  • select Edit to open a dialog
  • select Permissions Tab
  • check the box for the hdhomerundvr user as read/write.
Once enabled try restarting the App in App Center by first stopping and then starting it and see if that resolves the engine not running.
You should see the DVR Manager status message change at the bottom
AND you should have a log file with today's date

If we still have issues....

are you ok with SSH to server and running a few commands?
In particular there is a file I create /tmp/hdhomerundvr_install.log that I could do with seeing the contents of.
Best thing is to actually delete it and start the engine and get me the output with the following commands

Code: Select all

sudo synopkgctl stop HDHomeRunDVR
sudo rm -f /tmp/hdhomerundvr_install.log
sudo synopkgctl start HDHomeRunDVR
sudo cat /tmp/hdhomerundvr_install.log
Some have seen that there is a problem with the Synology not updating the temporary extracted binary from the silicondust package.
not sure why..
So at some point it would be worth shutting down the record engine, deleting the temporary one, and then restarting with the following commands

Code: Select all

sudo synopkgctl stop HDHomeRunDVR
sudo /tmp/hdhomerun_record_arm stop
sudo rm -f /tmp/hdhomerun_record_arm 
sudo synopkgctl start HDHomeRunDVR

PeterAG
Posts: 7
Joined: Sun Jul 26, 2020 10:31 am

Re: Synology SPK for DVR Record Engine

Post by PeterAG »

Well, in the end I started over. Uninstalled the DVR manager. Deleted the /volume1/HDRHomeRunDVR folder. Rebooted. Then followed the instructions from the start, set the permissions etc via ssh and now it all works perfectly! Even my.hdhomerun.com now shows HDHomeRun CONNECT QUATRO and HDHomeRun RECORD.

No idea what the problem was, but somewhere along the line the reinstall fixed it.

Many thanks demonrik and signcarver - your willingness to offer advice and guidance was much appreciated!

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

PeterAG wrote:
Wed Jul 29, 2020 7:26 am
Well, in the end I started over. Uninstalled the DVR manager. Deleted the /volume1/HDRHomeRunDVR folder. Rebooted. Then followed the instructions from the start, set the permissions etc via ssh and now it all works perfectly! Even my.hdhomerun.com now shows HDHomeRun CONNECT QUATRO and HDHomeRun RECORD.

No idea what the problem was, but somewhere along the line the reinstall fixed it.

Many thanks demonrik and signcarver - your willingness to offer advice and guidance was much appreciated!
You're very welcome.
Glad you got up and running.

NTC
Posts: 25
Joined: Sat Apr 13, 2019 2:26 pm
Device ID: 10751B42

Re: Synology SPK for DVR Record Engine

Post by NTC »

Hello Rik. Well, another problem solved, another to take its place.

Let me start by saying I first unistalled the HDHomeRunDVR package (V 0.8.3), then I installed the latest verion (1.0). After doing so, I am having a slight problem with new and old recordings. I can schedule a recording via the HDHomeRun app on my Android (Oreo) TV and it records fine, but new recordings do not show up on the app. It also does not show up in the DVR Manager.

Here is a portion of my volume1/HDHomeRunDVR directory, showing some old recorded files plus new. As you mentioned in your instructions, the user:group has changed.

drwxrwxrwx+ 37 http http 4096 Jul 29 14:50 .
drwxr-xr-x 13 root root 4096 Jul 29 14:48 ..
-rwxrwxrwx+ 1 hdhomerundvr users 49023 Jul 28 18:59 20200728.log
-rwxrwxrwx+ 1 hdhomerundvr users 42258 Jul 29 15:07 20200729.log
drwxrwxr-x 2 http http 4096 Jul 13 2019 Endeavour on Masterpiece
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 29 14:39 Great Performances
-rwxr-x--- 1 hdhomerundvr http 1511164 Jul 2 02:00 hdhomerun_record
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 24 13:34 Muscle Shoals to Music Row
drwxrwx--- 3 http http 4096 Jul 12 15:06 Saturday Night Live
drwxrwxrwx+ 2 http root 4096 Jul 4 10:29 Simply Ming
drwxrwx--- 3 http http 4096 Nov 14 2019 The 53rd Annual CMA Awards
drwxrwxrwx+ 3 http root 4096 Jul 18 21:59 The Johnny Cash Show
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 18 17:30 This Old House

Below are a couple of response to command line querys.

ls -l /volume1/\@appstore/HDHomeRunDVR/etc
total 4
-rw-rw-r-- 1 hdhomerundvr http 143 Jul 24 13:35 HDHomeRunDVR.conf



sudo synoacltool -get /volume1/HDHomeRunDVR
ACL version: 1
Archive: has_ACL,is_support_ACL
Owner: [http(user)]
---------------------
[0] user:http:allow:rwxp-DaARWc--:fd-- (level:0)
[1] user:hdhomerundvr:allow:rwxpdDaARWc--:fd-- (level:0)
[2] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
[3] group:http:allow:rwxpdDaARWc--:fd-- (level:0)

I should also point out that going to the HDHomeRunDVR shared folder properties via the DSM Control Panel, under permissions, the only checked boxes are for Local User:hdhomerundvr, and Local Groups:administrator and http. There is no user as http, there is only a http group.

I expected the old recording not to show up, but since I can schedule and record new programs, I expected to see these new recordings in the app. By uninstalling the old and installing the new, did that cause this problem? Any help would be appreciated.

Norm

demonrik
Posts: 1316
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: Synology SPK for DVR Record Engine

Post by demonrik »

NTC wrote:
Thu Jul 30, 2020 1:59 pm
Hello Rik. Well, another problem solved, another to take its place.

Let me start by saying I first unistalled the HDHomeRunDVR package (V 0.8.3), then I installed the latest verion (1.0). After doing so, I am having a slight problem with new and old recordings. I can schedule a recording via the HDHomeRun app on my Android (Oreo) TV and it records fine, but new recordings do not show up on the app. It also does not show up in the DVR Manager.
Well the DVR Manager no longer shows any recordings due to the changes in how it works.
But you should be able to open up the Silicon Dust page for the NAS at http://NAS-IP:59090
and should look something like
Image

It's very odd that the new recordings don't show up but the old ones do.. I would have expected if anything the other way round.
drwxrwxrwx+ 37 http http 4096 Jul 29 14:50 .
drwxr-xr-x 13 root root 4096 Jul 29 14:48 ..
-rwxrwxrwx+ 1 hdhomerundvr users 49023 Jul 28 18:59 20200728.log
-rwxrwxrwx+ 1 hdhomerundvr users 42258 Jul 29 15:07 20200729.log
drwxrwxr-x 2 http http 4096 Jul 13 2019 Endeavour on Masterpiece
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 29 14:39 Great Performances
-rwxr-x--- 1 hdhomerundvr http 1511164 Jul 2 02:00 hdhomerun_record
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 24 13:34 Muscle Shoals to Music Row
drwxrwx--- 3 http http 4096 Jul 12 15:06 Saturday Night Live
drwxrwxrwx+ 2 http root 4096 Jul 4 10:29 Simply Ming
drwxrwx--- 3 http http 4096 Nov 14 2019 The 53rd Annual CMA Awards
drwxrwxrwx+ 3 http root 4096 Jul 18 21:59 The Johnny Cash Show
drwxrwxrwx+ 3 hdhomerundvr users 4096 Jul 18 17:30 This Old House
This looks healthy. The 2 recent log files and the record engine binary suggest everything is at least working :)
And the new recording folders have the right permissions.
Maybe check in to one of the recording folders? should be similar permissions
Below are a couple of response to command line querys.

ls -l /volume1/\@appstore/HDHomeRunDVR/etc
total 4
-rw-rw-r-- 1 hdhomerundvr http 143 Jul 24 13:35 HDHomeRunDVR.conf



sudo synoacltool -get /volume1/HDHomeRunDVR
ACL version: 1
Archive: has_ACL,is_support_ACL
Owner: [http(user)]
---------------------
[0] user:http:allow:rwxp-DaARWc--:fd-- (level:0)
[1] user:hdhomerundvr:allow:rwxpdDaARWc--:fd-- (level:0)
[2] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
[3] group:http:allow:rwxpdDaARWc--:fd-- (level:0)

I should also point out that going to the HDHomeRunDVR shared folder properties via the DSM Control Panel, under permissions, the only checked boxes are for Local User:hdhomerundvr, and Local Groups:administrator and http. There is no user as http, there is only a http group.

I expected the old recording not to show up, but since I can schedule and record new programs, I expected to see these new recordings in the app. By uninstalling the old and installing the new, did that cause this problem? Any help would be appreciated.

Norm
All looks good - is perplexing that the NEW recordings aren't coming up.
And no - is nothing to do with uninstall and install.
Can you run

Code: Select all

sudo ps -ef | grep hdh 
Hoping it's running as hdhomerundvr (the logs kind of suggest it).

Might be worth seeing if doing a chown on the /volume1/HDHomeRunDVR to hdhomerundvr might fix it..

Code: Select all

sudo synopkgctl stop HDHomeRunDVR
sudo chown -R hdhomerundvr:http /volume1/HDHomeRunDVR
sudo synopkgctl start HDHomeRunDVR

Post Reply