Kodi Community Forum

Full Version: pvr.mythtv add-on
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
So I was using MythTV 0.28 but found it was a bit too 'bleeding' edge for me...

Thus I have purged and reinstalled MythTV 0.27.5 (deleted DB as well to start fresh).

Had some issues getting it started, but now that it's running none of my Kodi FE's can 'see' the backend.

This just repeats over&over, on both my Windows Kodi installation and the RPi2 Kodi install (which is the one I really care about!)

Code:
11:44:44 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: Failed to connect to MythTV backend on 192.168.0.99:6543
11:44:44 T:1794110528   ERROR: AddOnLog: MythTV PVR Client:
11:44:44 T:1794110528   ERROR: PVR - couldn't get the capabilities for add-on 'unknown'. Please contact the developer of this add-on: Christian Fetzer, Jean-Luc Barrière
11:44:49 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:44:49 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)InitWSAPI: invalid response
11:44:49 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:44:49 T:1794110528   ERROR: Previous line repeats 1 times.
11:44:49 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: Failed to connect to MythTV backend on 192.168.0.99:6543
11:44:49 T:1794110528   ERROR: AddOnLog: MythTV PVR Client:
11:44:49 T:1794110528   ERROR: PVR - couldn't get the capabilities for add-on 'unknown'. Please contact the developer of this add-on: Christian Fetzer, Jean-Luc Barrière
11:44:54 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:44:54 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)InitWSAPI: invalid response
11:44:54 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:44:54 T:1794110528   ERROR: Previous line repeats 1 times.
11:44:54 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: Failed to connect to MythTV backend on 192.168.0.99:6543
11:44:54 T:1794110528   ERROR: AddOnLog: MythTV PVR Client:
11:44:54 T:1794110528   ERROR: PVR - couldn't get the capabilities for add-on 'unknown'. Please contact the developer of this add-on: Christian Fetzer, Jean-Luc Barrière
11:45:00 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:45:00 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)InitWSAPI: invalid response
11:45:00 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:45:00 T:1794110528   ERROR: Previous line repeats 1 times.
11:45:00 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: Failed to connect to MythTV backend on 192.168.0.99:6543
11:45:00 T:1794110528   ERROR: AddOnLog: MythTV PVR Client:
11:45:00 T:1794110528   ERROR: PVR - couldn't get the capabilities for add-on 'unknown'. Please contact the developer of this add-on: Christian Fetzer, Jean-Luc Barrière
11:45:04 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:45:04 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)InitWSAPI: invalid response
11:45:04 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)__connectAddr: failed to connect (111)
11:45:04 T:1794110528   ERROR: Previous line repeats 1 times.
11:45:04 T:1794110528   ERROR: AddOnLog: MythTV PVR Client: Failed to connect to MythTV backend on 192.168.0.99:6543
11:45:04 T:1794110528   ERROR: AddOnLog: MythTV PVR Client:
11:45:04 T:1794110528   ERROR: PVR - couldn't get the capabilities for add-on 'unknown'. Please contact the developer of this add-on: Christian Fetzer, Jean-Luc Barrière

Full log from rpi2
http://hastebin.com/pikucuqafa.vhdl

Do I need a different version of the client in order to communicate with 0.27?

Thanks!!
Have you set the backend pin to 0000?
(2015-10-20, 20:35)nickr Wrote: [ -> ]Have you set the backend pin to 0000?

Sorry I should have mentioned this in my post - the backend PIN is 0000. I'll doublecheck it, but when I configured it last night it had '0000' in there by default.

Edit - derp, needed the IP of the server not loopback in general config.
Please try to connect with your favorite internet browser to this URL and let see what happen:

http://192.168.0.99:6544/Channel/GetChannelInfoList

Then try to pin with this URL:

http://192.168.0.99:6544/Myth/GetConnect...o?pin=0000

If you haven't right response encapsulated with xml, then your MythTV server is not yet configured to allow connection from client.
(2015-10-20, 21:17)janbar Wrote: [ -> ]Please try to connect with your favorite internet browser to this URL and let see what happen:

http://192.168.0.99:6544/Channel/GetChannelInfoList

Then try to pin with this URL:

http://192.168.0.99:6544/Myth/GetConnect...o?pin=0000

If you haven't right response encapsulated with xml, then your MythTV server is not yet configured to allow connection from client.

janbar, appreciate the response - issue was in my configuration of the backend.

"Edit - derp, needed the IP of the server not loopback in general config."

Thanks!!
I'm running an unofficial build of OpenElec http://forum.kodi.tv/showthread.php?tid=231955 running Kodi 15.2

I have a myth back end (Mythbuntu)

I installed the Myth PVR add on

I can browse the EPG and play back recordings.

I can't watch live TV.

Using the HDHomeRun add in, I can, but I'd rather use the Myth add in.

There is a log at http://xbmclogs.com/pxagelrpi

Any thoughts or suggestions?
(2015-10-28, 01:25)smitopher Wrote: [ -> ]I'm running an unofficial build of OpenElec http://forum.kodi.tv/showthread.php?tid=231955 running Kodi 15.2

I have a myth back end (Mythbuntu)

I installed the Myth PVR add on

I can browse the EPG and play back recordings.

I can't watch live TV.

Using the HDHomeRun add in, I can, but I'd rather use the Myth add in.

There is a log at http://xbmclogs.com/pxagelrpi

Any thoughts or suggestions?

http://xbmclogs.com/pxixxly9l

Log with more myth debugging info (turned on setting)
@smitopher, your log file doesn't have any trace to investigate. your have to setup Kodi for debug logging: in menu System->Settings->System , Enable Settings level to Standard or Advanced or Expert to show the item "Logging". Then select item Logging and enable option "Enable debug logging".
@smitopher, to allow working of liveTV , addon has to be connected to the MASTER backend, and your master backend has to be configured correctly: In mythtv-setup / section General :

IPv4 address must to be configured with the address of ethernet card, so not localhost or such.
IPv6 address must to be nil or ::1 for majority of user because v6 network infra isn't setup at home.
IP address of master backend must to be equal to IPv4 address above.

Then configure addon with the IP address of the master backend.

Maybe it was already done for you, so to investigate we need verbose logs as explained in thread above.
(2015-10-28, 08:48)janbar Wrote: [ -> ]@smitopher, your log file doesn't have any trace to investigate. your have to setup Kodi for debug logging: in menu System->Settings->System , Enable Settings level to Standard or Advanced or Expert to show the item "Logging". Then select item Logging and enable option "Enable debug logging".
http://xbmclogs.com/p5ec19300
(2015-10-28, 10:48)janbar Wrote: [ -> ]IPv6 address must to be nil or ::1 for majority of user because v6 network infra isn't setup at home.

Maybe it was already done for you, so to investigate we need verbose logs as explained in thread above.
That was the ticket. Live tv is working...

I thought that I had a valid ipv6 network
This trac ticket, which I opened 15 months ago, has just been closed as " Not part of Kodi (third-party)"

Is it? If so, the following would be a significant enhancement to the user experience.

This issue relates to digital TV. In many areas, you have some strong, reliable channels; other channels that that you pull most of the time, but not always; and some channels that you pull in only occasionally. Flipping channels works pretty well until you hit a channel that, at the moment, is too weak to pull in. On those occasions, the system does not respond to user input until the channel tunes in or times out. When it times out, Kodi exits to the GUI. You have to manually select the next good channel from the interface. Customary channel surfing (as on a TV set) is impeded.

I think the key to correcting this behaviour is to allow user input while the channel is trying to tune in, i.e. to change the algorithm from:

• press channel up or down;
• wait until (tuned or timed out).

to

• press channel up or down;
• wait until (tuned or timed out or user input).

This would not only correct the problem, but also improve the user experience. When you are flipping channels on a TV set (or any satellite or cable box I have ever seen), you don't have to wait for the channel to tune in. You can just keep pressing channel up or down, and the TV responds to your input. That's how people are accustomed to using their TVs.
@allan87,
The channel tuning process is not interruptible, because some kodi or pvr resources cannot be shared and for the moment api does not support it.
To enhance user experience since few release ago the addon no longer try all possible tuners when tuning channel, but just the first preferred for livetv. This behavior can be changed in setting, but by default it is like that. So the tuning response will come soon depending of your tuning timeout (5 sec by default).
I think it would be possible to go back to the previous tuned channel when tuning failed. This behavior can be designed in kodi core, and we could propose this change in the corresponding thread.
(2015-11-24, 11:43)janbar Wrote: [ -> ]I think it would be possible to go back to the previous tuned channel when tuning failed. This behavior can be designed in kodi core, and we could propose this change in the corresponding thread.

This would be a good solution Janbar, your improvement previously to only use one tuner has helped, but obviously it's still not perfect... I have the issue with a number of part time channels that broadcast for example from 19:00...

I have one channel set at channel 6 and its sandwiched in between 2 full time channels. So when you zap up or down, Kodi bombs out to the main menu when you hit this non broadcasting channel. Tuning back in to the last channel would be a considerable improvement...

I guess an ideal solution (my oppinion) is if a channel can't be tuned then Kodi should display full screen "channel not broadcasting" image that keeps you in Live TV and give the user the ability to tune to another channel. - I guess this is what other STB's do...

@janbar @allan87 - it's unclear as to who was raising this in I presume the feature request forum... But I'll definitely + 1 this improvement!