Plex Live TV not finding any channels

Hi All,

I recently purchased the TVButler TC100 and tried to get it up and running with my Plex Media Server (1.12.2.4929). The TVButler gets autodetected by PMS without any issues:

My problem now is that when I try to search for channels, non get found. I get the following warings within the Plex Tuner Service.log:

Apr 07, 2018 11:29:20.192 [0xaeaff420] WARN - [E] onetv_factory::StartDevice. Device 1:1 not found
Apr 07, 2018 11:29:20.192 [0xaeaff420] WARN - [E] CTVSStreamSource::LoadAndInitDriver. Failed to start device path 1:1, type 4, frontend 0
Apr 07, 2018 11:29:20.192 [0xaf4ff420] WARN - [E] CTVSChannelScanner::Tune. Failed to tune to a transponder
Apr 07, 2018 11:29:20.192 [0xaf4ff420] WARN - [E] dvb_channel_scanner_t::do_scan. Tune failed for 849833,8
Apr 07, 2018 11:29:20.193 [0xaf4ff420] INFO - * channel_scanner_t::scan_channels. Scanned 142 transponder out of 144. Channels found 0
Apr 07, 2018 11:29:21.469 [0xb26ff420] INFO - * web_service_t::process_device_status

I’m wondering why it trys to startup the Device 1:1, because the TVButler is the Device 1:2, as lsusb outputs below:

Bus 001 Device 002: ID 1d19:0100 Dexatek Technology Ltd.

I’m running PMS on the following system:
Raspbian stretch (latest patch level)

PS: I tried to find channels using the DVBLink software directly and its working without any issues.

Thank you in advance for any advice!
Viktor

Eventually found the issue and it was trivial, as expected. The PMS was running under the plex user and had by default no wirte access to the device. Just in case somebody faces the same issue:

In order to resolve it you’d have to either run PMS as root (not recommended) or follow the steps detailed below:

  1. Find out the devices vendor id and device id (using lsusb)
  2. Create a new file named 30-plex.rules within the /etc/udev/rules.d/ directory with the following content SUBSYSTEMS==“usb”, ATTRS{idVendor}==“1d19”, ATTRS{idProduct}==“0100”, GROUP=“plex”, MODE=“0660” (Adapt IdVendor, idProduct and the GROUP to your needs. The goup has to exist on the system)
  3. Reboot the server or run udevadm control --reload
  4. Verifiy that the group has been correctly assigned to the device e.g.:

Have fun!
Viktor