AVM FRITZ!WLAN Repeater DVB-C

gary tan · 2015-10-05T21:34:12+00:00

I'm looking to get a cable equivalent version of sat>ip and am wondering how the AVM FRITZ!WLAN Repeater DVB-C performs. Hdhomerun devices are too expen...

Anthony Thomas

Ruth Server wrote:
> The repeater works great.
> And this setup works also for the AVM Fritz!Box cable 6490.
>
> But any idea how to use the 6490 AND the repeater together? Or what about having more than one repeater?
>
> With "--satip_xml http://192.168.0.254:49000/satipdesc.xml" it's only possible to add one device.
> And TVH uses the given IP.
>

> So if the device cannot be found via autodiscover it's needed to add an option to add more than one device manually.

You can add multiple satip servers by just adding another to the startup argument eg

"--satip_xml http://192.168.0.254:49000/satipdesc.xml --satip_xml http://otherdeviceIP:49000/satipdesc.xml "

Kurt M.

Hi,

first of all, thank you for writing this tutorial and participating.

For my system (Synology DS716+II) the key was to add the parameter "--satip_XMl" to "start-stop-status" script.

Everything worked fine, even with oscam. But after 1.5 days everything broke together without touching anything. No EPG, no tuning at all ...

1.) I figured out that there are no tuner settings and I also get a "RTSP cmd error 7". Here is the log:
@-------------
2017-01-31 08:15:59.523 satip: Triggered new server discovery
2017-01-31 08:16:21.533 satips: SAT>IP server announces an empty tuner list to a client 192.168.1.39 (missing tuner settings - global config)
2017-01-31 08:16:25.485 http: 192.168.1.39: using ticket 8E4E27B1D79DBF94400D69D7B14F400AB45074AA for /stream/channel/2d1b76bf14e2afa299e2f37c247b46b1
2017-01-31 08:16:25.485 mpegts: 794MHz in avm_dvbc - tuning on SAT>IP DVB-C Tuner #1 (192.168.1.254)
2017-01-31 08:16:25.486 subscription: 0006: "HTTP" subscribing on channel "BBC HD", weight: 100, adapter: "SAT>IP DVB-C Tuner #1 (192.168.1.254)", network: "avm_dvbc", mux: "794MHz", provider: "Unitymedia", service: "BBC HD", profile="pass", hostname="192.168.1.39", client="VLC/2.2.4 LibVLC/2.2.4"
2017-01-31 08:16:25.488 satip: SAT>IP DVB-C Tuner #1 (192.168.1.254) - RTSP cmd error 7 (Unknown error -7) [8-500]
2017-01-31 08:16:27.485 subscription: 0006: service instance is bad, reason: Tuning failed
2017-01-31 08:16:27.486 mpegts: 794MHz in avm_dvbc - tuning on SAT>IP DVB-C Tuner #2 (192.168.1.254)
2017-01-31 08:16:27.486 subscription: 0006: "HTTP" subscribing on channel "BBC HD", weight: 100, adapter: "SAT>IP DVB-C Tuner #2 (192.168.1.254)", network: "avm_dvbc", mux: "794MHz", provider: "Unitymedia", service: "BBC HD", profile="pass", hostname="192.168.1.39", client="VLC/2.2.4 LibVLC/2.2.4"
2017-01-31 08:16:27.488 satip: SAT>IP DVB-C Tuner #2 (192.168.1.254) - RTSP cmd error 7 (Unknown error -7) [8-500]
2017-01-31 08:16:29.485 subscription: 0006: service instance is bad, reason: Tuning failed
2017-01-31 08:16:30.486 subscription: 0006: "HTTP" unsubscribing from "BBC HD", hostname="192.168.1.39", client="VLC/2.2.4 LibVLC/2.2.4"

@-------------

As you can see in the attached screenshot: Settings are saved. To change and save it again doesn't help.

2.) The log file /var/messages/ gave me this response:
@-------------
2017-01-30T23:18:55+01:00 nas tvheadend[3703]: cwc: Can not descramble service "sixx HD", access denied (seqno: 55514 Req delay: 145 ms) from cwc-192.168.1.50-15000-098E
2017-01-31T04:29:02+01:00 nas tvheadend[3703]: cwc: read error 104 (Connection reset by peer)
2017-01-31T04:29:13+01:00 nas tvheadend[3703]: cwc: read error 110 (Connection timed out)
2017-01-31T08:09:23+01:00 nas tvheadend[32572]: satips: use --satip_bindaddr parameter to select the local IP for SAT>IP
2017-01-31T08:09:23+01:00 nas tvheadend[32572]: satips: using Google lookup (might block the task until timeout)
2017-01-31T08:09:25+01:00 nas tvheadend[32572]: satips: SAT>IP server announces an empty tuner list to a client 192.168.1.52 (missing tuner settings - global config)
2017-01-31T08:09:27+01:00 nas tvheadend[32572]: satips: SAT>IP server announces an empty tuner list to a client 192.168.1.39 (missing tuner settings - global config)
2017-01-31T08:16:21+01:00 nas tvheadend[32572]: satips: SAT>IP server announces an empty tuner list to a client 192.168.1.39 (missing tuner settings - global config)
2017-01-31T08:16:25+01:00 nas tvheadend[32572]: satip: SAT>IP DVB-C Tuner #1 (192.168.1.254) - RTSP cmd error 7 (Unknown error -7) [8-500]
2017-01-31T08:16:27+01:00 nas tvheadend[32572]: subscription: 0006: service instance is bad, reason: Tuning failed
2017-01-31T08:16:27+01:00 nas tvheadend[32572]: satip: SAT>IP DVB-C Tuner #2 (192.168.1.254) - RTSP cmd error 7 (Unknown error -7) [8-500]
2017-01-31T08:16:29+01:00 nas tvheadend[32572]: subscription: 0006: service instance is bad, reason: Tuning failed

@-------------

3.) After that "break down" it seems that there is no tuning at all possible with the 6490. Even if I try to stream it directly from the fritz.box interface.
There is also the error message "no channels available. Please check your cables and search for channels." ("Es sind keine Sender verfügbar. Bitte überprüfen Sie Ihre Kabel und starten Sie den Sendersuchlauf.") - see attached screenshot.

Even though, channels are listed in menu DVB-C on fritz.box. To search again via fritz.box doesn't change anything.

4.) The only fix that helped me was to completely delete tvheadend and start the whole setup process from the beginning. But I won't do that every 1.5 days ... :(

Can anybody help?

Steve O

Hello Kurt,

are you sure the issue is caused by tvheadend? Since I was setting mine up a year ago it is running without problems 24/7. If I take a look at the Fritz-event logs it shows sometimes some errors like "03.04.17 14:03:48 Der TV-Tuner wurde mit Fehlergrund 1 zurückgesetzt.".

I assume there are still some bugs in the Fritz firmware. Were you able to watch TV using the Fritz-App when tvheadend could not connect?
<<

« Previous Page