+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: PVR & Live TV Support (https://forum.kodi.tv/forumdisplay.php?fid=167)
+---- Forum: MythTV (https://forum.kodi.tv/forumdisplay.php?fid=170)
+---- Thread: pvr.mythtv plugin: All channels "not available" (/showthread.php?tid=339741)
pvr.mythtv plugin: All channels "not available" - dasmanul - 2019-01-25
I have just set up a new MythTV installation on a separate host and wanted to access it from Kodi running on a Raspberry Pi 3B (up to date OSMC, Kodi 18).
The plugin sees my backend and can play back recordings (with problems, but that's a different issue). However, upon selecting a channel I'm always presented with "channel not available".
Log is at http://paste.debian.net/1062490/
There are only 3 entries in the mythbackend log for the relevant time:
Code:
Jan 25 16:34:48 mythtv mythbackend: mythbackend[307]: I ProcessRequest mainserver.cpp:1738 (HandleAnnounce) MainServer: MainServer::ANN Monitor
Jan 25 16:34:48 mythtv mythbackend: mythbackend[307]: I ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding: osmc(5590461db790) as a client (events: 0)
Jan 25 16:34:48 mythtv mythbackend: mythbackend[307]: I MythSocketThread(43) mainserver.cpp:7674 (connectionClosed) Monitor sock(5590461db790) 'osmc' disconnected
Any ideas anybody? Any more information I should provide?
RE: pvr.mythtv plugin: All channels "not available" - janbar - 2019-01-25
Same issue as https://forum.kodi.tv/showthread.php?tid=339564 .
You should fix the backend addresses in mythtv setup as I explained in this thread.
RE: pvr.mythtv plugin: All channels "not available" - dasmanul - 2019-02-04
Thank you! FQDN for backend was correctly set, but I guess I was also hit by IPv6. I'm currently in the process of reinstalling MythTV (for completely unrelated reasons). When I'm done there, I'll give short feedback whether the problem is gone.
RE: pvr.mythtv plugin: All channels "not available" - dasmanul - 2019-05-20
Reinstallation took longer than expected but I'm happy to report I didn't encounter this problem again. Thanks again for your assistance!