Driver for KODI - Version 0.6.0

Available on:

Current features

  • Power on the MediaPC via Wake-on-LAN
  • Optional "exit KODI", "suspend" or "shutdown" the MediaPC on power off
  • Auto reconnect KODI, if connection was lost
  • Start Kodi application on recipe launch implemented.
  • Browsing support for Video, Music, TV Shows and PVR
  • Available as ready to use docker image (currently outdated).

Control functions currently available

  • Power on / off
  • Navigation with control pad
  • Subtitle / Audio / Guide / Info
  • Page up / down
  • Skip next / previous
  • Step back / forward
  • Fast forward / rewind
  • Home / Menu / Info / Back
  • Shortcuts for Videos / Live Tv / Music / Radio

If someone is testing the driver I would appreciate your feedback and suggestions.

183replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Alexander Bauer Hi there, when i´m trying to start the neeo cli, i´m getting the following Error:


    root@NAS:/Sonstiges/NEEO/my-neeo-drivers# neeo-cli start
    Info: No Brain address configured, attempting to discover one...
    [KODI] ---------------------------------------
    [KODI]  NEEO driver for KODI - Version: 0.6.0
    [KODI] ---------------------------------------
    [KODI | Kodi - X96] Initialize KODI instance ...
    [KODI] Loading keymap file: /Sonstiges/NEEO/my-neeo-drivers/neeo-driver-kodi/kodi/lib/keymap.yml ...
    [KODI | Kodi - X96] Loading controls definition from: /Sonstiges/NEEO/my-neeo-drivers/neeo-driver-kodi/kodi/lib/controls.yml ...
    [KODI | Kodi - X96] Try connecting at ...
    Info: - Brain discovered: NEEO Wohnzimmer
    Info: Start server, connect to NEEO Brain: { brain: 'NEEO Wohnzimmer', host: 'NEEO-447afe72.local' }
          throw er; // Unhandled 'error' event
    Error: listen EADDRINUSE
        at Object._errnoException (util.js:992:11)
        at _exceptionWithHostPort (util.js:1014:20)
        at Server.setupListenHandle [as _listen2] (net.js:1355:14)
        at listenInCluster (net.js:1396:12)
        at doListen (net.js:1505:7)
        at _combinedTickCallback (internal/process/next_tick.js:141:11)
        at process._tickCallback (internal/process/next_tick.js:180:9)

    any Idea what this is?

    • Alexander Bauer i solved the Problem by myself. 

      The Error "EADDRINUSR" means that the Displayed Port 6336 was already in use.

      I changed the Port oft the other driver to 6337, restart the Server and now it works.

      • Remko
      • Remko
      • 3 yrs ago
      • Reported - view

      Benjamin Wolonkiewicz for the love of god, where can i edit this? i just rebooted the system and get this error.  i know i fixed it over a year ago, but cant seem to find it any move.. im looking in /NeeoSDK/neeo-driver-kodi/src atm.  much obliged.

    • Remko sorry for my late reply.


      Sorry i didn´t use this driver anymore and i have no more idea where you can edit this. I think that the Port 6336 is in use from the neeo-cli.

      But i can recommend this driver for Kodi

      • Remko
      • Remko
      • 3 yrs ago
      • Reported - view

      Benjamin Wolonkiewicz Thank you for the reply, after a second reboot, things whent back to normal.. I will try Niels's driver too.. thank you for the tip.

Like21 Follow