T3200M and wireless digital boxModem, WAP and wireless digital box. Ensure the signal strength indicator on the front of the wireless digital box has at least 4 bars. For low signal strength see these troubleshooting steps.
Reboot your modem by unplugging the power source for 10 seconds. Allow for 2 minutes for TV to be restored.Note: If the problem persists, reboot your wireless digital box. Ensure the signal strength indicator on the front of the wireless digital box has at least 4 bars. For low signal strength see these troubleshooting steps. Ensure the switch on the back of the WAP is switched to ‘AP’. If the problem persists, reboot your WAP and modem by unplugging the power source for 10 seconds.
Allow for 2 minutes for TV to be restored.Note: If the problem persists, reboot your wireless digital box.Note: Restarting or resetting your equipment may only provide a temporary fix to your problem. If you find the issue reoccurs in order for us to identify and fix the root cause of your problem.
Jan 19, 2019 - Kodi releases do not include any pre-installed PVR client addons by default. To install a PVR client addon, please visit the Add-on manager.
SYSTEM CONFIGURATIONLE 7.90.009 on Play v1 with ATSC tunerThese add-ons were installed from LE repoVDR ConfigurationVDR PVR BackendVDR VNSI ClientConfigured as shown herePROBLEM DESCRIPTION1. At boot: PVR manager is starting up (never completes)pop-up message VDR VNSI client: server is unreachable2. Enable PVR option does not appear in Settings / PVR & Live TV3.
VDR Configuration add-on channel configuration returns error:'Unable to connect to VDR restfull API'4. Wscan works - channels are detected and output file was created at:/storage/.kodi/userdata/addondata/service.multimedia.vdr-addon/config/channels.conf(see )But.still no channels appear in Kodi TV menu (same errors, PVR manager will not start)and no FM radio services are detected(see also)KODI.LOG. Reinstalled the following items through Add-ons / My add-ons / manual updateAll from LE repo, no other sources shownVDR Configuration 8.1.100 by libreelec.tvVDR PVR Backend 8.1.103 by libreelec.tvVDR VNSI Client 2.6.9 by FernetMenta, Team KodiAlso confirmed that /storage/.kodi/addons/script.config.vdr was not missing.Versions all look the same as before, and all issues still persist.Digging deeper, found a post I had overlooked before in my research; the problem description is very similar but the answer was missing drivers.My tuner is an official Wetek component. They said it was supported in LE/OE.(some other discussions about it).but here the tuner is detected# dmesg grep -i dvb. At boot, Event Log says:TVheadend HTSP Client - Server is unreachable.TVheadend HTSP Client - Access denied.PVR manager does not start. TVheadend web interface works, but I can not login to configure the tuner.The default login does not work.Kodi Log says:ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - unable to connect to 127.0.0.1:9982ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - Command authenticate failed: Access deniedI am confused now.
Tvheadend was working on previous builds. Code.
10:33:39.122 T:24 ERROR: AddOnLog: VDR VNSI Client: SignalConnectionLost - connection lost!!!. 10:33:39.558 T:24 ERROR: AddOnLog: VDR VNSI Client: Login - failed to read greeting from server. 10:33:40.574 T:24 NOTICE: AddOnLog: VDR VNSI Client: Logged in at '+0' to 'VDR-Network-Streaming-Interface (VNSI) Server' Version: '1.5.0' with protocol version '9'. 10:33:40.601 T:16 NOTICE: PVRManager - stopping. 10:33:40.616 T:20 WARNING: CPVRRecording::CPVRRecording - unable to determine channel type. Defaulting to TV.
10:33:40.705 T:32 WARNING: Previous line repeats 119 times. 10:33:40.706 T:32 NOTICE: Start - EPG thread started. 10:33:40.749 T:20 WARNING: CPVRRecording::CPVRRecording - unable to determine channel type. Defaulting to TV. Just for sanity check, could you disable vdr (backend, vdr.vnsi.) and install Tvheadend 4.2 and after that have a look if the adaptor appear in the webui? The adapter appears correctly and channel reception is working now with TV Headend. But the OTA EPG grabber has never worked.
This is why I wanted to use VDR instead. I have now updated to LE 7.90.010 but the problem with VDR still exists ('Unable to connect to restfull api')Does anyone with a Wetek Play have OTA tuner + EPG working 100% correctly?
Did you activated into the vdr adonn wait for dvb device #1?This was the current setting:Wait for frontend initialization = enableNumber of adapters to wait for = 1I tried the DEFAULTS button in VDR backend, now the error at boot is gone and PVR manager starts OK. I guess the VDR user preferences file was corrupted. But I dont know how it happened. So PVR manager is working now, but VDR Wirbelscan still does not work (freezes at start of scan). Kodi still works, I can use the back button to escape Wirbelscan. This is what happens when I scan for channels in VDR Config. Code.
kodi4:/.kodi/userdata/addondata/service.multimedia.vdr-addon/config # wscan -. s S19E2 -c DE -f s lt.conf.
wscan -s S19E2 -c DE -f s. wscan version 20141122 (compiled for DVB API 5.10). using settings for 19.2 east Astra 1F/1G/1H/1KR/1L. scan type SATELLITE, channellist 67. output format vdr-2.0. WARNING: could not guess your codepage. Falling back to 'UTF-8'.
output charset 'UTF-8', use -C to override. Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 - SATELLITE 'Availink AVL6211+AV2011 DVB-S/S2': very good:-)). Using SATELLITE frontend (adapter /dev/dvb/adapter0/frontend0). Getting frontend capabilities-. Using DVB API 5.10. frontend 'Availink AVL6211+AV2011 DVB-S/S2' supports.
INVERSIONAUTO. DVB-S. DVB-S2. FREQ (0.95GHz. 2.15GHz).
![Pvr Manager Stuck Loading Channels From Clients Pvr Manager Stuck Loading Channels From Clients](/uploads/1/2/5/4/125464286/127179156.jpg)
SRATE (0.800MSym/s. 50.000MSym/s). using LNB 'UNIVERSAL'. trying 'S2 f = 10729 kHz V SR = 22000 2/3 0,35 8PSK (0:0:0)'. (time: 00:00.000) signal ok: S2 f = 10729 kHz V SR = 22000 2/3 0,35 8PSK (0:0:0)Display Moreand the system freezes.it does not freeze, when the SAT-Cable is NOT connected.
so there must be sth wrong with the driver i'd sayEDIT:istn't that too much dvr's? Shouldn't that be only one? Code. kodi4:/dev/dvb/adapter0 # ls -l. total 0.
crw-rw- 1 root video 212, 4 Jan 1 2015 demux0. crw-rw- 1 root video 212, 20 Jan 1 2015 demux1. crw-rw- 1 root video 212, 36 Jan 1 2015 demux2. crw-rw- 1 root video 212, 5 Jan 1 2015 dvr0. crw-rw- 1 root video 212, 21 Jan 1 2015 dvr1.
crw-rw- 1 root video 212, 37 Jan 1 2015 dvr2. crw-rw- 1 root video 212, 3 Jan 1 2015 frontend0. crw-rw- 1 root video 212, 7 Jan 1 2015 net0. crw-rw- 1 root video 212, 23 Jan 1 2015 net1. crw-rw- 1 root video 212, 39 Jan 1 2015 net2Display More.