QNAP-TS233 Setup

[themusj]

I ditched my old WD MyCloud Ext2 Ultra for DVR recording (the last time I tried to install it, it never could find it) for installation on my Qnap.

But even though I have installed, removed and re-installed the installer, hdhomerun_windows_20250815, it fails to see the Qnap NAS as well now.

What is even more odd, under the DVR tab, there is Store recordings on this PC (which works) and Store recordings on a Western Digital NAS device. (NAS Install).

I don't know why specifically what it says on a Western Digital NAS device.

I have a shared folder on the Qnap HDHomeRun and I have SSH enabled.

The installer just does not see the Qnap unit. I have to keep my PC on for recordings until I get this resolved.

Help would be appreciated.

[signcarver]

For the "installer" to see the NAS it does so by upnp so typically one has to have a DLNA server active on the NAS to use the installer. I believe with the installer and qnap it will not autostart if the NAS reboots.

It is usually must better to install on the qnap yourself either through SSH or a docker package (if the nas supports it and I believe that model does).

[themusj]

Is there some guide on "install on the qnap yourself either through SSH?" I have SSH enabled and go from there if there is a process besides the installer and docker. IE link.

I had the WD MyCloud handling this for about four years and honestly don't recall the app not auto starting upon reboot. But those units are EOL and the Qnap is more user friendly and has more support.

[signcarver]

The my cloud was the only NAS that SD autostarted the engine from a "NAS install"... the docker container (and the even older qnap package) will autostart.

Personally I would go the container/docker route but if you just want to install, follow the linux manual install instructions.
The old qnap package thread is at: viewtopic.php?t=31745 and the docker thread is at: viewtopic.php?t=73757 (which has links for instructions to install on qnap)

[themusj]

"to see the NAS it does so by upnp so typically one has to have a DLNA server active on the NAS to use the installer.:"

---I have it working this route now at this moment. This route does not auto start so a person has to run the installer app after a reboot each time?
IE. how to you start it up again after a reboot??

Looking at the docker now. Does that auto restart if I go that route??

The answer to both is Yes.

[themusj]

Well I have the docker up and running. I believe correctly. Do I just select a TV Show or Movie to record as normal and the file ends up in the Recordings directory of the share?

In other words, once the docker is up and running (properly) the files should automatically record on the NAS where the container is stored?

[rikd]

Well I have the docker up and running. I believe correctly. Do I just select a TV Show or Movie to record as normal and the file ends up in the Recordings directory of the share?

In other words, once the docker is up and running (properly) the files should automatically record on the NAS where the container is stored?

yes.. it will store recordings wherever you mapped '/dvrrec' to on your NAS.

[themusj]

Interesting twist.

Turned off the configuration to the HDHomeRun install on my Qnap NAS using their installer (HDHomeRun Setup). IE Store Recordings on this PC or Store Recordings on ... NAS.

Docker container running recorded three programs with no issue. Nice.

Fourth program oddly is now recording on the configuration based on the installer even though I checked and neither settings for local PC recording or NAS recording is checked.

As a test, I even tried a Live recording and it too is going back to the directory of the HDHomeRun installer.

I just ran several more recordings and all default to the old (I believe installer version). The docker is up and running with no errrors.

What do I need to do to get it to point to the docker rather than the 'ghost' installer version which isn't even set.

[signcarver]

If you used the installer, restart the nas as that shouldn't autostart (unless wd). The installer (setup) itself only controls whether the pc is used or not... any engine that is up is fair game to be used, typically will be the one reporting the most space. Assuming all are modern engines that have proper StorageID, I'd check both https://ipv4-api.hdhomerun.com/discover and https://ipv6-api.hdhomerun.com/discover and see your various engines to help you track such down.

[themusj]

Deleting the 'installer' folder location and rebooting the NAS fixed the issue.

It was interesting. Anything scheduled previously to the docker was recording on the installer location. Anything new was recording on the new docker location.

Appreciate your help. Been with a subscription for over five years so I value this product and support.