[wyild1]

Ok I've done a bit more investigating using my 0.27.4 backend:

With mythweb showing the first four entries as:
Conflict Heartbeat: Dog Days 110 - ITV3 +1 Fri Nov 13, 2015 (06:55 PM) 1 hr 5 mins Record This Never Record
Conflict Coronation Street 105 - ITV1 Fri Nov 13, 2015 (07:00 PM) 30 mins Record This Never Record
Conflict ITV News Wales at Six 106 - ITV1 +1 Fri Nov 13, 2015 (07:00 PM) 30 mins Record This Never Record
DVB-S HDThe One Show 001 - BBC One HD Fri Nov 13, 2015 (07:00 PM) 30 mins Don't Record Never Record

Using OE 6.0 (Kodi 15.2) on an RPi2 with pvr.mythtv 2.7.4 shows:
ITV3+1 Heartbeat 13/11/2015 18:55 to 20:00 Conflict error
ITV1 Coronation Street 13/11/2015 19:00 to 19:30 Conflict error
ITV1+1 ITV News Wales at Six 13/11/2015 10:99 to 19:30 Conflict error
BBC One HD The One Show 13/11/2015 19:00 to 19:30 Enabled

And the home screen widget shows:
Next recording
Start time - 13/11/2015 18:55
Heartbeat - (ITV3 +1)

Using a Millhouse 16.0 Jarvis build on an RPi with janbar's latest 'doityourself' with some custom hacks of my own:
ITV3+1 Heartbeat 13/11/2015 18:55 to 20:00 Record this Conflict error
ITV1 Coronation Street 13/11/2015 19:00 to 19:30 Record this Conflict error
ITV1+1 ITV New Wales at Six 13/11/2015 10:99 to 19:30 Record this Conflict error
BBC One HD The One Show 13/11/2015 19:00 to 19:30 Record this Enabled

And the home screen widget shows:
Next recording
Start time - 13/11/2015 18:55
Heartbeat - (ITV3 +1)

Conclusions

• The mythtv backend and pvr.mythtv correctly identify these as 'broken conflicts' - i.e. won't record in all cases.
  
• The timers list shows the conflicts correctly 'Conflict error'
  
• The home screen widget incorrectly displays simply the first 'upcoming' as the next 'upcoming recording' (both Isengard and Jarvis), completely disregarding the fact that it wont record because is has status 'Conflict not OK'.
  

I'm busy this weekend but will try and work on a patch some time next week (unless ksooo or someone fixes it first). Feel free to check kodi's bug database to see if it's already been reported. If not, raise a new bug referring to this thread and post a link here.

http://trac.kodi.tv/ticket/16374

Cheers!

[metaron]

Created https://github.com/xbmc/xbmc/pull/8386

[negge]

You'll probably need to look in PVRGUIInfo.cpp, that's where these types of values come from. Like you've concluded yourself it's probably a case of picking the first upcoming timer without regarding its validity.

[metaron]

A fix for this is now merged into the working version of Jarvis.
It should be available in Beta 2, or if you're on RPi and can't wait, try the latest Millhouse build :-)...
(http://forum.kodi.tv/showthread.php?tid=231092)

[wyild1]

A fix for this is now merged into the working version of Jarvis.
It should be available in Beta 2, or if you're on RPi and can't wait, try the latest Millhouse build :-)...
(http://forum.kodi.tv/showthread.php?tid=231092)

Great! I'm android and Linux so ill wait for the beta to test! thanks!!

Cheers!