Jedi EPG Xtream

The boxes I currently use are little more expensive.
I have a dinobot 4k (discontinued) and VU zero 4k. My dinobot 4k has always been my primary box.
Dinobot 4K is also the same box as
Anadol ECO 4k,
Axis His 4K (£95 ebay)

But the zgemma h7 range are a popular cheap box. Although you probably better buying a quad core box if you can afford it.
Zgemma H9 range are also popular but can be a little buggy for some.

Octagon also have got a few decent little boxes about at the moment.

Visit are forum sponsors for more choice. This thread isn't really the place to discuss hardware. (Although I started it :) )
There are plenty of threads on this forum and other forums regarding "what do you recommend" posts.

https://www.world-of-satellite.co.uk

and what does bouquet up and down do.

in which case you need to amend your keymap.xml

or the main.py file to add in your reference.

 self["actions"] = ActionMap(["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"], {
            "ok": self.ok,
            "back": self.exit,
            "cancel": self.exit,
            "red": self.exit,
            "green": self.keygreen,
            "yellow": self.keyyellow,
            "blue": self.keyblue,
            "left": self.goLeft,
            "right": self.goRight,
            "up": self.goUp,
            "down": self.goDown,
            "channelUp": self.pageUp,
            "channelDown": self.pageDown,
            "0": self.reset,
            "2": self.prevLetter,
            "8": self.nextLetter
        }, -1)

The actionmap list at the top is the sections it is looking for in the keymap.xml file

In oe-alliance keymap.xml we would have something like this

a948782982c3f14707c999.png

So in any of the listed sections

["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"]

add in

<key id="KEY_CHANNELUP" mapto="channelUp" flags="m" />

<key id="KEY_CHANNELDOWN" mapto="channelDown" flags="m" />

or alternatively edit the main.py and add in your button names

        self["actions"] = ActionMap(["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"], {
            "ok": self.ok,
            "back": self.exit,
            ...
            ...
            "channelUp": self.pageUp,
            "channelDown": self.pageDown,
            "nextBouquet": self.pageUp,
            "prevBouquet": self.pageDown,
           
        }, -1)

What image are you having issues with for fuzzywuzzy?

ignore me... just seen it says openpli 8 all over that log :)

The plugin doesn't require fuzzywuzzy to run. Although it is better if you have that package as it finds better channel matches.
There is fallback code for images that don't have fuzzywuzzy package. ie. Dreamboxes.

Does the plugin install ok, but you just get this dependancies message every time it runs.
If the IPK has installed OK, you can just remove the dependancies check. Then it wont prompt you every time it runs.

in
/usr/lib/enigma2/python/Plugins/Extensions/JediEPGXtream/main.py

look for this line (around line 116)
self.onFirstExecBegin.append(self.check_dependencies)

and replace it with
self.onFirstExecBegin.append(self.start)

nizwa that error shouldn't happen.
What are you using to create IPTV bouquets?

Have you got any IPTV bouquets?

Have you got an empty bouquet?

Try this file and see if it eliminates your crash

/usr/lib/enigma2/python/Plugins/Extensions/JediEPGXtream/

The plugin is designed to be used hand in hand with other iptv bouquet makers.

I.e my own jedimakerxtream and I assume it works with suls bouquet maker.

Once you have created iptv bouquets via one of those plugins.
You then open up this plugin which will read those bouquets and allow you to re-assign any missing epgs from alternative epg list provided.

That is all this plugin does. Nothing else.