Getting to grips with the Wetek myself, finally have TVHeadend up and running on OpenELEC.
Getting picons sorted I found was the hardest part!
Generally I'm a Windows user, but have a small bit of Linux experience - I run a small Ubuntu Linux fileserver.
Tried generating my own picons for 28.2e satellite as outlined here:
https://github.com/picons/picons-source
Easy enough to follow once I sorted out dependencies, but kept giving an error when generating the picons whichever method I chose (snp or srp). I'm getting a syntax error for the 'readlink' part of the script.
Fortunately you can download pre-generated picons using picon-source here:
https://picons.xyz/
As a Windows user, I find WinSCP an easy way to transfer files to the Wetek. TAR archives can be extracted on the Wetek using it also.
Some caveats:
When I downloaded and extracted the snp (service name) picons (various 220 x 132px styles) many seemed to be missing, for example BBC channels.
Switched to SRP (service reference) instead. Much better, used hardlinked rather than symlinked. All channel picons (I'm just using free-to-air ones) were visible, except the few HD channels (e.g. BBC One HD).
For example, the default service reference picon for BBC One HD is:
1_0_1_1B1D_802_2_11A0000_0_0_0.png
My TVHeadend service reference for BBC One HD is:
1_0_19_1B1D_802_2_11A0000_0_0_0.png
... there's the number '9' digit added in fact to all HD channels.
Now with Freesat there's only 12 HD channels so easy enough to copy and rename.
Just wondering if this is a peculiarity of my setup or the picons generated from picons.xyz?
Also if anyone can shed any light on my 'readlink' errors that would be educational! From looking it appears files are not being copied to the temporary directory generated. Being unfamiliar with BASH scripting I left it alone, just examined the code to find dependencies.
