'No service enabled' in openelec.

Robert H

Anyone else with DVB-T2 problems

I used a PCTV nanostick 290e(DVB-T2) with 3.2 with no problems on openelec in the past.

I tried openelec 3 RC1 (2.99.1) and it still worked updated to 2.99.4 (tvheadend 3.3.491) and i now get the message 'No service enabled' when i try to watch any channel. deleting channels and mux's and re adding them tvheadend no longer find the HD services but does find SD services and can map to channels but gives the 'No service enabled' when I try to watch through the webui. My DVB-S2 Tevii S470 workes fine and is mainly used so at some point between openelec 3 RC1 and RC4 this bug showed up.

To further test I got a ubuntu laptop installed XBMC and tv headend from the new apt repo's.

http://apt.tvheadend.org/stable – 3.2 PCTV 290e all works as expected.

http://apt.tvheadend.org/beta – 3.3.511 PCTV 290e showing same problem described as abuve. http://apt.tvheadend.org/unstable – 3.5.66 PCTV 290e also not working but dose not have the 'No service enabled' message just blank.

Sorry I know this is more of openelec using a non stable repo issue but before I can appeal to openelec to pull a new version i wanted to check if anyone has a time-shift working tvheadend which can pickup DVB-T2 HD channels?

Robert H

A quick update

with 3.5.101 from http://apt.tvheadend.org/unstable everything now works again. HD + SD, mux's added manually.

Hope this gets moved to beta so openelec updates but at the same time prefer stable software to unstable but working 90% of the time software.

Alex Smarty

Hi,

having the same problem in all branches, even stable, which is on 3.4 now.

Using Afatech AF9033 (DVB-T) on Ubuntu 12.10 (amd64).

Alex Smarty

Pebcac: On configuration->TV adapters-> General if found a (new?) tick called "enabled". After switching it on everything works again.

Alex Smarty wrote:
> Hi,
>
> having the same problem in all branches, even stable, which is on 3.4 now.
>

> Using Afatech AF9033 (DVB-T) on Ubuntu 12.10 (amd64).

Adam Sutton

Yes that is a new option, it should have been auto-enabled for people migrating configuration. Was it not?

The reason for the box (and arguably we could have been a bit cleverer with the default state) is that we've now made it possible for users with dual frontend devices to use either (but obviously not both). But also generally its useful to be able to disable an adapter in TVH (especially when testing) so it can be used for something else.

So the decision was that since users most likely need to configure adapters before they can use them anyway we'd add that as default OFF. But true we probably should have made it a bit clearer.

Adam

Alex Smarty

Yes, was switched off after the update.