You don't need to install the System tools add-on, you can just use nano instead of mcedit
Oh yes! mcedit is such a wonderfull editor (in comparison to nano)
You don't need to install the System tools add-on, you can just use nano instead of mcedit
Oh yes! mcedit is such a wonderfull editor (in comparison to nano)
If you are interested: Full remote control for LibreElec with Argon One V2 Case - the "not so professional" way!
I have 1 Argon One M.2, 1 Raspberry Pi 4B and and 2 ONE4ALL URC-6430 (afterwards I need just only one!)
1. Installed Libreelec (e.g. with balena etcher on a USB-Stick or microSSD)
2. SSH enabled?
3. Installed Addon "Script - System Tools"
4. Connected (ssh) from PC to libreelec box
5. Edited config.txt
LibreELEC: ~ # mount -o remount,rw /flash
LibreELEC: ~ # mcedit /flash/config.txt
LibreELEC: ~ # reboot
6. Found some scan codes
LibreELEC: ~ # ir-keytable -p nec -t
Now I had to program my remote. I have two identical "One4All URC 6430" but it should be ok with other learning remotes too. Searching for a PVR or Mulimedia Device to get as much as possible functional keys, the best ones I found, were DVICO (2153) and Digitech (2260) in the code list of my "URC 6430".
table: ONE4ALL URC 6430 : VIDAC (2153) - Digitech (2260)
kodi | scancodes | urc 6430 pvr Code 2153 |
copy | urc 6430 pvr code 2260 |
KEY_POWER | 0x4cb02 | POWER | OK | |
KEY_RED | 0x4cb41 | RED | 1 | |
KEY_GREEN | 0x4cb03 | GREEN | 2 | |
KEY_YELLOW | 0x4cb42 | YELLOW | 3 | |
KEY_BLUE | 0x4cb45 | BLUE | 4 | |
KEY_EPG | 0x73960000 | GUIDE | ||
KEY_HOME | 0x6a960000 | HOME | ||
KEY_INFO | 0x67960000 | INFO | ||
KEY_CHANNELUP | 0x21960000 | + | ||
KEY_CHANNELDOWN | 0x19960000 | - | ||
KEY_BACK | 0x4cb07 | BACK | 5 | |
KEY_VOLUMEDOWN | 0x15960000 | VOL DOWN | ||
KEY_VOLUMEUP | 0x25960000 | VOL UP | ||
KEY_MUTE | 0x5e960000 | MUTE | ||
KEY_BACKSPACE | 0x4cb46 | RETURN | 6 | |
KEY_CONTEXT_MENU | 0x4cb55 | LIST | 7 | |
KEY_UP | 0x4cb50 | UP | PLAY | |
KEY_RIGHT | 0x6f960000 | RIGHT | ||
KEY_DOWN | 0x63960000 | DOWN | ||
KEY_LEFT | 0x6b960000 | LEFT | ||
KEY_OK | 0x6e960000 | OK | ||
KEY_RECORD | 0x31960000 | REC | ||
KEY_REWIND | 0x1f960000 | REWIND | ||
KEY_PLAY | 0x4cb17 | PLAY | 8 | |
KEY_FORWARD | 0x22960000 | FORWARD | ||
KEY_STOP | 0x4cb4c | STOP | STOP | |
KEY_PLAYPAUSE | 0x4cb56 | PAUSE | 9 | |
KEY_1 | 0x1b960000 | 1 | ||
KEY_2 | 0x27960000 | 2 | ||
KEY_3 | 0x2b960000 | 3 | ||
KEY_4 | 0x17960000 | 4 | ||
KEY_5 | 0x60960000 | 5 | ||
KEY_6 | 0x64960000 | 6 | ||
KEY_7 | 0x58960000 | 7 | ||
KEY_8 | 0x5c960000 | 8 | ||
KEY_9 | 0x68960000 | 9 | ||
KEY_0 | 0x13960000 | 0 | ||
KEY_SUBTITLE | 0x2f960000 | AV | ||
KEY_TEXT | 0x4cb1b | TEXT | 0 |
The best match for me was the DVICO. Some key did not give any scan code. So I used the second remote to find any functional keys. Then copied the keys from the second remote to the functionless keys of my first remote.
7. Created my /storage/.config/rc_keymaps/custom_remote
# table custom_remote, type: NEC
0x4cb02 KEY_POWER
0x4cb41 KEY_RED
0x4cb03 KEY_GREEN
0x4cb42 KEY_YELLOW
0x4cb45 KEY_BLUE
0x73960000 KEY_EPG
0x6a960000 KEY_HOME
0x67960000 KEY_INFO
0x21960000 KEY_CHANNELUP
0x19960000 KEY_CHANNELDOWN
0x4cb07 KEY_BACK
0x4cb46 KEY_BACKSPACE
0x15960000 KEY_VOLUMEDOWN
0x25960000 KEY_VOLUMEUP
0x5e960000 KEY_MUTE
0x4cb4c KEY_STOP
0x4cb55 KEY_CONTEXT_MENU
0x4cb50 KEY_UP
0x6f960000 KEY_RIGHT
0x63960000 KEY_DOWN
0x6b960000 KEY_LEFT
0x6e960000 KEY_OK
0x31960000 KEY_RECORD
0x1f960000 KEY_REWIND
0x4cb17 KEY_PLAY
0x22960000 KEY_FORWARD
0x4cb56 KEY_PLAYPAUSE
0x1b960000 KEY_1
0x27960000 KEY_2
0x2b960000 KEY_3
0x17960000 KEY_4
0x60960000 KEY_5
0x64960000 KEY_6
0x58960000 KEY_7
0x5c960000 KEY_8
0x68960000 KEY_9
0x13960000 KEY_0
0x2f960000 KEY_SUBTITLE
0x4cb1b KEY_TEXT
Display More
8. Pointed to it
9. Now tested, if it works:
I opend two remote terminals (to watch scancode and mapped keys simultaneously)
No.1 for
LibreELEC: ~ # ir-keytable -c -w /storage/.config/rc_keymaps/custom_remote
No.2 for
LibreELEC: ~ # irw
10. Rebooted, and ...
11. I didn't get the powerbutton script working with LibreElec. So i had to flash another USB-Stick with a Raspberry OS Lite to program my power key. If you manage to run the script, you have to do this before starting with this "tutorial". Installing the OS on the Raspberry and configuring the power button is not a big deal.
I hope this may be usefull for someone and sorry for the bad english, the bad layout and the many errors!
Usefull links:
https://wiki.libreelec.tv/configuration/ir-remotes
http://wagnerstechtalk.com/argonone/#Install_Argon_ONE_Scripts_in_Pi_OS_3264-bit
Update - (Just to let you know):
There was neither a software problem nor a broken Wetek tuner.
Everything went fine, when we connected the wetek play2 in another room. It seems to be, that the signal strength of the cable is (either) to high (or to low).
We have to investigate ...
Thank you very much for your informations! This was quite helpful - now I know the the device is properly identified - I'll have to go on ...
Where did you find this line?
And do you think, the tuner is properly initialized and should function? Does ... DVB: adapter 0 frontend 0 frequency 0 out of range ... mean, the first adapter first frontend or no adapter at all?
Aaand - do you have any suggestions, what I should try next?
Thanks for your patience
I'm really struggling to get Cable TV to work:
TV signal is ok (tested with TV). I installed the tvheadend server (w/o activating Preload capmt_ca.so library and Wait for frontend initialisation in tvheadend settings). Via Web Frontend I configured tvheadend - activated the DVB-C adapter, added DVB-C network, etc. (I did this with other kodi/openelec/libreelec installations many times - with success!) But now: no scan results at all.
Maybe my problem lies here:
wetek:~ # dmesg | grep -i dvb
[ 3.480721@3] wetek-dvb dvb.49: Found Wetek i2c-1 adapter ...
[ 3.480726@3] wetek-dvb dvb.49: ts0: parallel
[ 3.<pre data-title="Quellcode">Total Wetek NIM(s) found: 1</pre>@3] wetek-dvb dvb.49: dmx rst ctl = ffffffc064e5d100
[ 3.480790@3] wetek-dvb dvb.49: asyncfifo rst ctl = ffffffc064e5d180
[ 3.480795@3] wetek-dvb dvb.49: ahbarb0 rst ctl = ffffffc064e5d200
[ 3.480801@3] wetek-dvb dvb.49: uparsertop rst ctl = ffffffc064e5d280
[ 4.297332@3] wetek-dvb dvb.49: Wetek NIM(s) detection in progress ...
[ 4.297340@3] wetek-dvb dvb.49: Checking for Sony CXD2837 DVB-C/T/T2 demod ...
[ 4.297644@3] i2c i2c-1: cxd2841er_attach(): attaching CXD2837ER DVB-T/T2/C/ISDB-T frontend
[ 4.298412@3] wetek-dvb dvb.49: Failed to find MxL603 tuner!
[ 4.338813@3] wetek-dvb dvb.49: Total Wetek NIM(s) found: 1
[ 7.293383@1] wetekdvb: module license 'Proprietary' taints kernel.
[ 7.295698@1] DVB: registering new adapter (wetek)
[ 7.295718@1] wetek-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Sony CXD2837ER DVB-T/T2/C demodulator)...
[ 11.168326@2] wetek-dvb dvb.49: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..1002000000)
Display More
The device seems to be detected - but no adapter, no frontend ...
I'm stuck ...
Your help btw. suggestions would be really appreciated.
(I should mention, that I am about 200 km away from the wetek play 2 -> no problem with RDP and phone )