Posts by trogggy

    Firstly there's no need to stick the zip on your raspberry - it just needs to be somewhere you can access, which can be as simple as your pc downloads folder (if it's shared, obviously).

    I have an install folder on my main pc that I sling zips into. That folder is shared, so accessible from any kodi in my network.
    I added that folder as a source in the kodi file manager on each kodi (actually just by copying sources.xml across). Now when I choose 'install from zip' that install folder comes up in the options list, so it's easy to navigate to the zip.

    Just checked on my pc - either command ( systemctl stop eventlircd.service or systemctl stop eventlircd) seem to stop lirc as expected. That's on 17.0-BETA7, I should really try the latest.
    Log snippet:

    I have already tried to use keymap editor but it does not work, the buttons assigns them but do not change their basic function, in fact, to remap some functions on the remote I've used this method, for example: play stop pause. I took from your example, the command file to go into my favorites that is not a function present in the standard linux commands and I think there are also codes to scan the library, but I can not find what they are.


    You're talking about kodi's built-in functions.
    eg

    Code
    UpdateLibrary(video)


    I do it , work great ..... logitech harmony 900 based on remote for a mut@nt hd 2400 (nec protocol too)
    but
    just one key doesn't work .... the function KEY_RECORD 167 ..... :s on LibreElec 7.0.3.12 does nothing do .... , on live tv , press menu bar and select record button work , but if i pressed my REC button on the harmony ... do nothing....

    someone can confirme that KEY_RECORD doesn't work

    Just checked, and can confirm it doesn't work. The key is read but no action linked to it by default.
    Log entry:

    Code
    DEBUG: OnKey: record (0xf0c6) pressed, action is


    To make that work for record (presumably what you want?) is fairly straightforward...
    Change the hex code to decimal, make an .xml file pointing to that (or edit your existing keymap), drop it in userdata/keymaps and either reload keymaps / restart / reboot.
    eg make a file called record.xml:

    XML
    <?xml version="1.0" encoding="UTF-8"?>
    <keymap>
      <global>
        <keyboard>
            <key id="61638">Record</key>
        </keyboard>
      </global>    
    </keymap>


    Looking at the log it might even work using '<record>Record</record>' but I've not tested that.

    Could you post the remote.conf you're using for the mut@nt here? It's always handy to have alternatives.
    TIA.



    [hr]
    People with remote control issues:

    • reboot your box
    • press the buttons that do not work (and note the order of pressing)
    • post result of the following: dmesg | paste and cat /tmp/remote.conf | paste


    I have checked my boxes and all factory remotes work fine, I really need the logs to debug this.


    If you need more logs I'll upload one tomorrow - replacing a hot water tank is taking priority tonight. :@


    trogggy lsmod, please.


    New:


    Old:


    Thanks for looking.


    hi trogggy,
    home button work for you ?


    It did before the update. Not after.
    Which suggests it's not just me. Can you check your log?
    [hr]


    No idea. ? Do you have meson-ir kernel module loaded.


    Here we go...google-fu engaged...

    Mini mxiii running latest build:

    Code
    LibreELEC (community) Version: 7.90.beta1
    LibreELEC git: 869b1877659a52fb98a8d02b2d0b41d1d4b088a9
    Beelink:~ # modinfo meson-ir
    filename:       /lib/modules/3.14.29/updates/meson-ir.ko
    license:        GPL v2
    author:         Beniamino Galvani <[email protected]>
    description:    Amlogic Meson IR remote receiver driver
    depends:        rc-core
    vermagic:       3.14.29 SMP mod_unload aarch64


    Mini mxiii running 23Dec build:

    Code
    LibreELEC (community) Version: devel-20161223194610-r25062-g308adcf
    LibreELEC git: 308adcf74b448ce29e7744160bbb23a0dd183398
    Beelink2:~ # modinfo meson-ir
    modinfo: ERROR: Module meson-ir not found.


    So (presumably) yes after the update. But not before.

    I thought that you were asking about using LIRC with built-in IR receiver.

    To sum up the changes:

    • some IR drivers (I think also for devices using LIRC) were updated along with media_build update
    • LIRC with built-in IR reciever is currently not working because it requires switching off amremote (the "remote.conf" driver) and turning on meson-ir kernel module

    I might sound confusing but I actually have little knowledge on this. ;)


    Yep, I was.
    I'm using the built-in receiver - no usb receiver connected. My log is full of LIRC keypress refs and some keys aren't working (though they're detected by LIRC, so presumably I can map them easily enough).

    So all that LIRC stuff shouldn't be happening?


    It doesn't. LIRC only requires a change in device tree IIRC but I need to find time to check it.


    Now I'm confused. :D
    Are you saying I shouldn't have LIRC running with this build then?
    'cos my log is suddenly full of LIRC references on keypresses, and some at least aren't working (not checked properly, but eg pause, play, stop aren't doing anything).

    I found this hard to get my head around tbh, because I don't have your remote to match buttons to functions. So what I did was to make a test remote.conf using my numbers buttons, and test each keycode I didn't already know.
    The ones I know (from my remote.conf) I just added to yours.
    So here's what I came up with. It's in a different order (irrelevant, but you might want to tidy it up. There are probably mistakes in it - you'll no doubt find them. There are a whole bunch of buttons that are either not recognised at all by kodi or have no function attached to them.
    The ones that aren't recognised - you'll need to change the linux keycodes (second column); ideally change them to something you'll use with the remote, otherwise you'll have a lot of keymapping to do.

    The ones that are recognised but not mapped to an action - you can either do as above (change the linux keycode) or make a keymap within kodi to map the code kodi reads to an action - see the link in my sig for some discussion / examples if you need them.
    Then you'll need to work out which button corresponds to each command - ie you're linking the button to the code in the first column - and then swap them around to do what you want. Don't forget to add any repeats you want when you've finished (as per your original).
    If you look in my remote.conf you'll see a bunch of linux keycodes that are already linked to kodi functions - use those to replace the ones you have that don't work.
    My remote.conf:


    As I can't seem to find a way to post those here without the spacing being buggered up I've zipped them up here.
    Good luck.