Posts by trogggy

    Thanks for your answer ... appreciate!
    I'm having an Intel NUC i5 with integrated IR receiver and I'm not having a physical remote. But I can configure (all) remotes with my Harmony Elite. I'm not a dev but I think as long as I'm having the right pairing on my libreelec and Harmony it should work.
    I know that there is a "working" NUC Remote on Harmony but this has very limited functionality.

    PS.: I already checked your guide but I'm getting an error message on putty when running the command "remotecfg/storage/.config/testremote.conf ... "-sh: remotecfg: not found"


    The guide is for amlogic devices - there's no amremote on your nuc so it won't work.

    What remote (device) are you using with your Harmony?

    Hi ojessie
    The setup guide link is my sig, not part of my post - guess I need to make it smaller or something.
    I doubt that's relevant to your situation, even if you're on amlogic (which you haven't said).
    I have a few 'real' MCE remotes / receivers and they all just work (with lirc), without a lircd.conf file in the .config folder.
    On the other hand I have a few media center remotes / receivers that don't work with lirc, and are recognised as keyboard / mouse. Maybe you have one of those?
    What device are you running libreelec on?
    Can you describe your remote / link to a pic?


    Thank you very much for your hint. This disables the power button but does not enable longpress for power.
    But if you change it to

    XML
    <?xml version="1.0" encoding="UTF-8"?>
    <keymap>
      <global>
        <remote>
          <power>noop</power>
          <power mod="longpress">ShutDown()</power>
        </remote>
      </global>
    </keymap>

    then it is working! So first disable the old function, then add a new one.

    Best


    Good spot, and that makes sense.


    Hi,

    I'm running LibreELEC 7 with Kodi 16.1 that has the new feature for long pressing keys. I'm fine with the default configuration for my remote in LibreELEC/Kodi except the shutdown key. I want to change only this key behaviour to shutdown LibreELEC if the key is pressed for a longer time.

    For that I created a file /storage/.kodi/userdata/keymaps/remote.xml with

    XML
    <?xml version="1.0" encoding="UTF-8"?>
    <keymap>
      <global>
        <remote>
          <power mod="longpress">ShutDown()</power>
        </remote>
      </global>
    </keymap>


    and rebooted the machine.
    Unfortunately Kodi still shuts down after one short key press on the power button. lirc (irw) detects the key KEY_POWER.
    Is there still something missing that my configuration does not overwrite the default configuration for the power button?

    Thanks!


    You've not overwritten the power button's settings, you've just added a new one for a long press.
    Maybe:

    XML
    <?xml version="1.0" encoding="UTF-8"?>
    <keymap>
      <global>
        <remote>
          <power mod="longpress">ShutDown()</power>
          <power>noop</power>
        </remote>
      </global>
    </keymap>


    where 'noop' is 'no action'.


    I would have thought the error message is obvious - it's banned.

    LE does not and will not support banned nor illegal addons.

    You're confusing the heck out of me there. :huh:
    There are banned lists - but they're things that are banned for discussion / support.
    In other words they're banned on forums, not within kodi.
    There's no specific error that will pop up if someone tries to install from a 'banned' repo.
    Maybe I've misunderstood what you're saying?

    @ the OP...
    If you can install from some repo's but not from a specific one that means there's a problem with that repo.
    If it's a banned one you'll have to look elsewhere for support.
    If the addon itself isn't banned (and a quick google suggests it's fine to me) you can always install from a standalone zip file - on the kodi forums that's seen as okay, so I imagine it's the same here.


    Create a USB stick with two partitions.
    Make it bootable with grub Legacy. (Install Grub Legacy to the stick MBR)

    Add the following stanza to /boot/grub/menu.lst file

    title OpenELEC
    root (hd0,0)
    kernel /KERNEL boot=UUID=<UUID of root partition> disk=UUID=<UUID of storage partition> quiet

    Copy both KERNEL and SYSTEM files from an image to the root partition.

    That should be all that is needed ...... I have been using this for years, since first using Openelec.


    Alternative menu.lst...

    uuid () > nul
    set UUID=%?%
    kernel /KERNEL boot=UUID=%UUID% disk=LABEL=whatever ssh quiet

    I use that with a storage partition (called 'whatever' in the above example) on the USB stick or on my hard drive.

    Quick question and a shot in the dark...
    Have you enabled the 'wait for network' option in libreelec settings?
    I ask because if kodi's starting before your network's up that will bork your pathsubs (kodi looks for them but they're not there > errors) and maybe cause the symptoms you describe.

    Edit: btw you should check the kodi wiki for changes in video cache settings in v17 - yours need to be updated.

    Now I need to find out from intel how to activate windows as NUC did not come with a key.


    You shouldn't need one - if windows 10 has activated once on a machine it's logged by some trickery with microsoft.
    On subsequent installs it should all happen automatically.
    Download the media creation tool, install to a usb stick (carefully ;) ) and boot the nuc with that. If you're asked for activation just choose 'skip'.

    There are a ton of threads on the kodi forum about this - probably because windows isn't the greatest os for sharing from. I'd suggest searching google for something like 'sharing folders in windows without homegroups' or looking on the kodi forum for threads with keywords like 'share windows'.
    Hang on... hooray... there's a wiki page: SMB/Windows - Official Kodi Wiki
    My setup is very simple - I share a few folders from windows, no homegroups, no passwords, accessible from anywhere on the LAN. In kodi I navigate to those either via IP or by browsing (windows network(smb) > workgroup > device name > share name) and set them as a source.
    As for trouble, I'm responsible for what I write here - nothing to do with you.


    Why do I even bother...

    If you're asking me then I honestly don't know.
    Someone asks how to install a zip file, which is a fairly basic, generic operation. No mention of banned addons.
    Option 1 - tell him.
    Option 2 - quiz him on what exactly he's installing, reprimand him, tell him support is now withdrawn. And if he says thanks for informing him and that he doesn't intend to install banned zips best just ignore him.
    Gotcha.