Issue with exporting XMLTV via channel.xmltv

[thelanofvilles]

From a PC on your network with hdhomerun_confins installed or from within the Docker run

Code:

hdhomerun_config 1252E9E0 set /tuner0/channel eu-bcast:506000000 
hdhomerun_config 1252E9E0 set /tuner0/filter "0x0000-0x1FFF"
hdhomerun_config 1252E9E0 save /tuner0 fullmux.ts

stop after a minute and make fullmux.ts available through external storoage Sub might be able to live with just filtering 0x12 but I cannot.

Without logs (Jellyfin and NextPVR I can't help) much, however since it was working as http to get the m3u and xmltv file, I will assume your https reverse proxy is failing.

Martin

So the code snippet included in the jellyfinnextpvrlogs is what happens when I use my domain name in the Nextpvr plugin on Jellyfin. I have changed my domain name from the change host in the logs taken from Jellyfin above.

When running " hdhomerun_config 1252E9E0 set /tuner0/channel eu-bcast:506000000  " . I got "ERROR: invalid channel"

Below is also is my nextpvr logs. I keep getting "unable to create file fullmux.ts" when running the last command mentioned above.

Also the certificate I am using for the NextPVR domain is a Lets Encrypt Wildcard Cert with EC-384 Key.

[mvallevand]

OK, sorry I can't help with the HDHR capture it will be close to that command line but I don't know exactly how DVB-T works. You can try changing eu-bcast to auto and playing with the number of trailing zeroes. The command syntax is here https://info.hdhomerun.com/info/hdhomerun_config


The error message is pretty clear that it is a cert error. I am not sure how to start NextPVR Docker in https mode and I am not interested in researching it.

One thing if you don't want Jellyfin to change your IP and pass through the host name to avoid this.

[2024-06-18 17:37:05.157 +00:00] [INF] [22] Jellyfin.Plugin.NextPVR.LiveTvService: Changed host from "nextpvr.media.example.com" to "10.10.0.100"

you need to enable Jellyfin IPv6 The reason for this is ffmpeg will use IPv6 when Jellyfin uses IPv4 and there is a security issue mixing IPv4 and IPv6 connections to NextPVR.

Martin

[thelanofvilles]

OK, sorry I can't help with the HDHR capture it will be close to that command line but I don't know exactly how DVB-T works.  You can try changing eu-bcast to auto and playing with the number of trailing zeroes.  The command syntax is here https://info.hdhomerun.com/info/hdhomerun_config


The error message is pretty clear that it is a cert error.  I am not sure how to start NextPVR Docker in https mode and I am not interested in researching it. 

One thing if you don't want Jellyfin to change your IP and pass through the host name to avoid this.

[2024-06-18 17:37:05.157 +00:00] [INF] [22] Jellyfin.Plugin.NextPVR.LiveTvService: Changed host from "nextpvr.media.example.com" to "10.10.0.100"

you need to enable Jellyfin IPv6  The reason for this is ffmpeg will use IPv6 when Jellyfin uses IPv4 and there is a security issue mixing IPv4 and IPv6 connections to NextPVR.

Martin

Thanks let me give what you have suggested a try.