No signal signal strenght on tvheadend

[aurelmarius]

I'm running satpi on ubuntu 20.04 with 2 usb WinTV dualhd dvb-c tunners. I notice that signal strenght info doesn't shows in tvheadend like my hdhomerun tunners.

[Saentist]

This is depends on "drivers" installed if used build-in in kernel not expect more then basic try https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder

[Barracuda09]

Hi @aurelmarius and @Saentist

It seems that in the screen shots there is in the Monitor Info section the Signal Strengthbut No snr So maybe something else is wrong too?

[Saentist]

Driver module is not capable to send DVBAPI 5.x information use 3.x In TVH Legacy mode /Force old status/ sometime fix this. Playing with multiplying values and checkbox sometime fix problem.

[Barracuda09]

@Saentist and @aurelmarius

I think your solution is when TVH is retrieving the signal status from the drivers. But I believe this signal is send by SatPI via RTP.

The problem is fixed with(I think) to disable this in TVH (See TV-adapters parameters):

• Check tuner-number in signal-status messages

The explanation is: When TVH is requesting a specific tuner number, but if that tuner is in use in SatPI, SatPI will use a different tuner number. And with this enabled TVH will discard the RTCP info, because is expects for example 1 and maybe SatPI uses 5 and sends that.

[aurelmarius]

I'm running media tree hwe kernel with hauppauge patches. I tried changing those settings but no luck. I can live with this, no problem 😀

[Barracuda09]

So disabling Check tuner-number in signal-status messages does not work?

Strange here it does, which version of TVH are you using?

[aurelmarius]

TVH Build: 4.3-2229~g6b5defc76 (2024-02-12T17:57:09+0000)

[Barracuda09]

So there are bars, so the data is RTCP data is send to TVH. But is not correct so it seems.

[aurelmarius]

I think the problem is that Signal strenght is 65534 and TVH expects 100 or 240. Testing with minisatip, it reports correct info.

[Barracuda09]

I think @Saentist had a point with:

Driver module is not capable to send DVBAPI 5.x information use 3.x

SatPI is probably using 5.x and only falls back to 3.x when 5.x fails.

[Saentist]

There is a simple check if is in % dvbapi 3.x if is in dBm dvbapi 5.x But not respected by all driver developers. Still some drivers report signal/quality from 0-FF (255) other from 0-FFF (4095) also 0-FFFF (65535) most strange is when is mixed ex: signal = 215 but quality = 45800 There is no Standard

@Barracuda09 If you can suggest any code improvement to TVH and post PR, I can try force thinks to be merged faster.

[aurelmarius]

If i run tvheadend on that box i get signal in %.

[Barracuda09]

@aurelmarius Did you change something in between? Because the first screen shot was 221:

---

---

And second 65534:

---

[aurelmarius]

First screen was with media tree kernel without hwe (got no bars on tvh), second is with mediatree-hwe-kernel.

[Barracuda09]

Hi @aurelmarius

EDIT: Sorry this will not work, you did not use an Enigma Box:

---

Could you please try this version satpi_1.6.2.193~g66c090c_Enigma.zip to see if the Signal status are there?

There is also a new frontend.html included, you need to update. There is now also a Force Old Style Signal Status see:

[Barracuda09]

Please checkout and build new commit 35c6341db3375a3e21bf27f3477bb9ed2cb5ab18 Please note: there is also a new frontend.html