How to setup FreeNAS / TrueNAS with Fritzbox DVR connection

Live TV & DVR
, , ,
1

Server Version#: 1.20.2.3402
Tuner Make/Model: FritzBox 6591 Cable
TrueNas Core 12-RC1

Hi, as this lovely board software closes down any existing thread after 90 days without the possibility to open it again, another thread needs to be opened.
Last thread (closed automatically a week ago) was this one: FreeNAS Plex Plugin DVR FRITZ!Box 6660 Cable

I’m trying to do the same here. Use my FritzBox 6591 Cable for LiveTV / DVR function on Plex.
Got the plex-plexpass-beta plugin in TrueNas working, DHCP and VNET is set.
DVB-C(-IP) is working fine on the Fritzbox (double checked with VLC on Windows and fireTV 4k Stick, both on the same physical Ethernet switch).

There is no additional firewall set, but I’m new to FreeBSD jails, so I do not know if there is any separation layer within the iocage vnet stuff there.

The plex search is not discovering anything, manual hostname or ip does not bring up anything as well.

Why am I posting this in plex forums and not ixSystems?
I need to know, how the search / manual ip discovery is working and where to look for something failing.

If I knew what plex is expecting, I could try do serve it through TrueNas iocage.

Thanks for the support @Plex!

Edit: The http://192.168.178.1:49000/satipdesc.xml can be downloaded perfectly from within the plex jail. In the logfiles, there is not one single sign about the “add IP manually” try.

2

What tuner are you trying to use? Here is the supported list; https://support.plex.tv/articles/225877427-supported-dvr-tuners-and-antennas/

3

As I stated above I’m using the Fritzbox 6951 with integrated DVB-C tuner as SAT/IP provider.
Read some positive results about that combination, but no real how to.
The auto discovery seems to be bound to some discovery.json file, which is not supported by Fritzbox.
Did a quick test with xteve on my windows machine, that worked.
But as I read other threads and posts it should be possible to work directly (at least in older Plex versions).
Need to build a jail with xteve otherwise, but a direct integration with Plex and SAT/IP standard would save the hassle :slight_smile:

The official lost is short and known.

Best regards
Jonas

4

“It just works” is true for Linux and Windows Plex installations.
For FreeBSD Plex installations i didn’t find any indication for it working with AVM at all.

5

Your thread was my inspiration to create a new one, because I want to understand the difference.
Either there is a problem in the FreeBSD binaries or libraries of plex or in the plugin/jail configuration.
But to analyze this, I need more information, how the connection is done successfully on Windows/Linux and what is failing exactly on FreeBSD.

Currently I’m stuck with superficial log-entries :frowning:

Any hints, how to make the problem visible?

Oct 15, 2020 13:49:37.709 [0x8045a3f00] INFO - Plex Tuner Service v1.0.0.0 - FreeBSD PC amd64 - build: 
Oct 15, 2020 13:49:37.714 [0x8045a3f00] INFO - FreeBSD version: 12.2-PRERELEASE (FreeBSD 12.2-PRERELEASE 4912790fb32(HEAD) TRUENAS), language: en-US
Oct 15, 2020 13:49:37.714 [0x8045a3f00] INFO - Processor Intel(R) Atom(TM) CPU C3758 @ 2.20GHz
Oct 15, 2020 13:49:37.714 [0x8045a3f00] INFO - /usr/local/share/plexmediaserver-plexpass/Plex Tuner Service /usr/local/share/plexmediaserver-plexpass/Resources/Tuner/Private /usr/local/share/plexmediaserver-plexpass/Resources/Tuner/Shared 1.20.2.3402-0fec14d92 32600 /waitmutex
Oct 15, 2020 13:49:37.658 [0x80455a000] INFO - [I] broker_t::start...
Oct 15, 2020 13:49:37.776 [0x80455a000] INFO - [I] device_manager_t::init.
Oct 15, 2020 13:49:37.776 [0x80455a000] INFO - [I] device_manager_t::init. Initialize provider manager
Oct 15, 2020 13:49:37.776 [0x80455a000] INFO - [I] device_manager_t::init. Initialize all device auxes
Oct 15, 2020 13:49:37.776 [0x80455a000] INFO - [I] dvb_device_factory_t::get_aux_list
Oct 15, 2020 13:49:37.779 [0x80455a000] INFO - [I] web_server_t::start. Starting web server on port 32600
Oct 15, 2020 13:49:44.762 [0x8045a4900] INFO - [I] web_service_t::process_device_discovery
Oct 15, 2020 13:49:44.762 [0x8045a4900] INFO - [I] device_reactor_t::get_device_list ()
Oct 15, 2020 13:49:44.762 [0x8045a4900] INFO - [I] dvb_device_factory_t::get_device_list ()
Oct 15, 2020 13:49:46.772 [0x8045a4900] INFO - [I] SAT2IP - discover_satip_servers(): no servers found
Oct 15, 2020 20:06:10.846 [0x8045a5d00] INFO - [I] web_service_t::process_device_discovery
Oct 15, 2020 20:06:10.846 [0x8045a5d00] INFO - [I] device_reactor_t::get_device_list ()
Oct 15, 2020 20:06:10.846 [0x8045a5d00] INFO - [I] dvb_device_factory_t::get_device_list ()
Oct 15, 2020 20:06:12.875 [0x8045a5d00] INFO - [I] SAT2IP - discover_satip_servers(): no servers found

This log was created with “extended logging” switched on - looks the same as without the option.

Tried xTeVe, found everything, thought “wow - what a great experience with this EPG, recommended show, etc” - just to discover that plex is not able to stream one single stream, regardless of the client :frowning:

6

yeah i know this log :sweat_smile:
Spend some time in there. I didn’t want to dive deep in freebsd satip source so i just f*d it and now i wait for freenas on linux. aka TrueNAS CORE 12
But it is definitely a freebsd “problem” (more like a feature no one with coding experience wants).
On a GhostBSD machine i couldn’t even use a satip client with fritzbox.

7

I believe you mean TrueNAS SCALE? TrueNAS CORE is still going to be based on FreeBSD. There are no plans to move the entire product line to a Linux base at this time.

8

probably he was talking about scale. did run it for test while waiting for hardware, there are some reasons, why a stable version is expected next year, not sooner. Like linux, like docker (and alike), did not know freebsd until two weeks ago.
now I’m running 10 jails, 4 of them configured completely myself and I start to like it.

Anyway, next try with TVHeadend, still searching “services”, but still not one reply from @Plex about what COULD have gone wrong :frowning:

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.