Sorry that commit has been in oe-alliance for a month https://github.com/oe-alliance/XMLTV...0d449c250925fb
I have used various service type's with channels.xml reading 1: so I can't make sense of that
Two issues are being tackled right now:
1. Unreliability of some websites. For this a LasUpdate file has been created. This file is checked, and if the the date in this file is too old. No files are downloaded from this website.
However, 1 website has problems with this approach. A solution for this is found, but requires another change to the plug-in (not programmed at the moment). This problem was not anticipated and only surfaced when the change was rolled out.
2. For IPTv channels, some cheats had to be apllied. The famous changing of the 4097:0:1: to 1:0:1: in the EPG import channels file.
This cheat is not needed anymore. But as consequence files which still apply the cheat do not work anymore.
There has been some code developed which re-enables the cheat, and also allow the normal naming of the service ref for IPTV channels (4097:0:1:...)
This code is under testing now.
So it is work in progress. And despite testing, unforeseen problems cropped up, which are now ironed out
Willy
~~Rytec Team~~
Xtrend ET6000 OpenPli (used as mediaplayer)
Xtrend ET 9500 OpenPli 3TB HDD
Vu+ Duo OpenPli 1500gb HDD Samsung Spinpoint (backup)
Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*
Ok I can't test yet but as I previously said with the current code I have been using 1: in the channels.xml and 5002 or 5001 in the bouquet files without issues.
That was supposed to have not worked a month ago.
Could you possibly ask athoik what exactly that commit does as far as I can understand it just stops the fake recordings
https://github.com/OpenPLi/enigma2-p...bcd2582852cbaa
we can simply disable the check when URL detected on service reference.Code:EPGImport: do not try fake recording for services containing url This commit allows using service references other than 1:0:1 on custom channels. Previously it could work only for 4097 and servicemp3, but once serviceapp was used the following error occured: [EPGImport] Parsing channels from '/etc/epgimport/MyTest.channels.xml' [eNavigation] record: -1 record returned non-zero Invalid serviceref string: 4097:0:1:A0A2:0:0:0:0:0:3:http%3a//...m3u8:Radio Contact Vision HD That is happening because serviceapp, doesn't support recording yet. So instead of adding fake recording on serviceapp/hisi/... we can simply disable the check when URL detected on service reference. Finally the instructions in https://forums.openpli.org/topic/47658-epg-for-iptv-channels/ must change since "Also the 4097 has to be replaced by a 1" is not valid any more. Any service referene on channel should work now, as long as there is a url included. Related: https://devtools.openpli.org/issues/283
To me that means we can use any type's as long as the reference has a url in it.
Last edited by dsayers; 16-09-18 at 15:02.
Ok download latest oe allience EPG Import from github and now receive
[EPGImport] Error at start: [Errno -2] Name or service not known
EPG Import_Erno2.jpg
Attached is epgimport log
I add back the previous version and that Imports fine
EPG Import.jpg
Could it be anything to do with this? https://github.com/oe-alliance/XMLTV...dbf23dab29ff8d
Last edited by dsayers; 16-09-18 at 23:40.
The original EPGImport doesn't have this IPv6 Legacy support, so I think that you should check on this side.
Last edited by pr2; 17-09-18 at 09:25.
This is Freesat UK.
I'm not sure if this would matter but I have Google hostname and dhpc to no.
Please check if this has been missed on fix merge https://github.com/oe-alliance/XMLTV...c07fbbfba658b9
So now the IPv6 stuff needs adding upstream.
So can we remove the ipv6 stuff till sorted?
No, it was there from before without causing an issue. It just needs to be tweaked. I have just commented on the commit. I've tagged you too. I'm sure it will be fixed soon.
The way to test is to go through the commits, find the responsible one and comment on it, preferably with a suggested solution.
Once working fine, we can add the ipv6 stuff upstream to avoid future merge issues.
dsayers (17-09-18),jenseneverest (17-09-18)