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.
 

Reply
183replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
    • Gerard Brouwer
    • Sales Agent and consulting for HomeCinema and whole house controlling
    • Gerard_Brouwer
    • 1 yr ago
    • Reported - view

    Hi Alex I am a new NEEO user and I want to know more about making Drivers. Your Kodi driver is what i like. However working on a Mac with Node installed and using visual studio code and doing what you’re READ ME says. The last part START the driver I get an error that the Kodi-ws is missing. 

    Can you point me in the right direction?

    thanks!

    Reply Like
  • Maybe you forgot:

    Change into the src directory and install required the packages with npm

    npm install
    
    Reply Like
  • Hi,

    i'm totaly a newbies in sdk setup and some small knowladge, it's possible to create a tuto from start to run the Kodi Neeo SDK to a Kodi running on windows 10 ?

     

    i have install node.js on windows, try to setup the config.js but nothing happen when i try to run node index.js

     

    i have this message on the powershell :

     

    PS C:\neeo-driver-kodi-master\src> node index.js
    module.js:540
        throw err;
        ^

    Error: Cannot find module 'kodi-ws'
        at Function.Module._resolveFilename (module.js:538:15)
        at Function.Module._load (module.js:468:25)
        at Module.require (module.js:587:17)
        at require (internal/module.js:11:18)
        at Object.<anonymous> (C:\neeo-driver-kodi-master\src\kodiApi.js:6:16)
        at Module._compile (module.js:643:30)
        at Object.Module._extensions..js (module.js:654:10)
        at Module.load (module.js:556:32)
        at tryModuleLoad (module.js:499:12)
        at Function.Module._load (module.js:491:3)

    Reply Like
    • Gauvain DUTHEIL Hi, go to the src folder and run the command npm install.

      Reply Like
  • What device should I search for in the neeo app? Couldn't find kodi there. The driver seems to be working:

    C:\kodineeo\neeo-driver-kodi-master\src>node index.js
    ---------------------------------------
     NEEO driver for KODI - Version: 0.4.2
    ---------------------------------------
    [NEEO] Connecting Brain ( 192.168.1.106 ) ...
    [NEEO] Starting API server and connect to Brain: 192.168.1.106 ...
    [NEEO] Api is ready and running!
    
    [NEEO] ===> Use the NEEO app to search for "KODI" device. <===
    
    [KODI] Try connecting at 192.168.1.103:9090 ...
    [KODI] Successfully connected.
    [KODI] Active players = 1
    Reply Like
  • Alexander Bauer Thanks man! Got it to work inside docker (kubernetes) :)

    Something worried for me was following:

    config.neeo.port = Port which my Driver Serviceis running on (not the Port from the Neeo Brain)
    config.neeo.baseUrl = URL which is used to reach my driver service (if brain can not reach ip/url directly as configured above... configure this)

    So I would suggest to adjust the description to something like "port your driver service is running on" or "Custom URL driver service is reachable"

    For me the name assumes that I should put the port neeo brain listen on... 

    So communication with default config.js is:

    Brain -> Driver (Docker):  tcp6336
    Driver (Docker) -> Brain: tcp3000
    Driver -> Kodi: tcp8080 and tcp9090

    Reply Like
  • i've some errors with the docker container. Everytime I restart it, I get this:

    Unhandled rejection Error: INVALID_DEVICE_REQUESTED_apt-3e2ecd77f6129bcd4b1067b59ac8b894a7c99e42
        at BluePromise (/neeo-driver-kodi/node_modules/neeo-sdk/lib/device/db.js:92:16)
        at Promise._execute (/neeo-driver-kodi/node_modules/bluebird/js/release/debuggability.js:303:9)
        at Promise._resolveFromExecutor (/neeo-driver-kodi/node_modules/bluebird/js/release/promise.js:483:18)
        at new Promise (/neeo-driver-kodi/node_modules/bluebird/js/release/promise.js:79:10)
        at Database.getDeviceByAdapterId (/neeo-driver-kodi/node_modules/neeo-sdk/lib/device/db.js:90:12)
        at RequestHandler.getDeviceByAdapterId (/neeo-driver-kodi/node_modules/neeo-sdk/lib/device/handler/RequestHandler.js:30:32)
        at /neeo-driver-kodi/node_modules/neeo-sdk/lib/expressBrainDriver/routes/deviceroute.js:10:25
        at paramCallback (/neeo-driver-kodi/node_modules/express/lib/router/index.js:404:7)
        at param (/neeo-driver-kodi/node_modules/express/lib/router/index.js:384:5)
        at Function.process_params (/neeo-driver-kodi/node_modules/express/lib/router/index.js:410:3)
        at next (/neeo-driver-kodi/node_modules/express/lib/router/index.js:275:10)
        at Function.handle (/neeo-driver-kodi/node_modules/express/lib/router/index.js:174:3)
        at router (/neeo-driver-kodi/node_modules/express/lib/router/index.js:47:12)
        at Layer.handle [as handle_request] (/neeo-driver-kodi/node_modules/express/lib/router/layer.js:95:5)
        at trim_prefix (/neeo-driver-kodi/node_modules/express/lib/router/index.js:317:13)
        at /neeo-driver-kodi/node_modules/express/lib/router/index.js:284:7
        at Function.process_params (/neeo-driver-kodi/node_modules/express/lib/router/index.js:335:12)
        at next (/neeo-driver-kodi/node_modules/express/lib/router/index.js:275:10)
        at jsonParser (/neeo-driver-kodi/node_modules/body-parser/lib/types/json.js:109:7)
        at Layer.handle [as handle_request] (/neeo-driver-kodi/node_modules/express/lib/router/layer.js:95:5)
        at trim_prefix (/neeo-driver-kodi/node_modules/express/lib/router/index.js:317:13)
        at /neeo-driver-kodi/node_modules/express/lib/router/index.js:284:7
    

    I think this is because the container doesn't have a persistent storage attached... but I can't find something in the Readme. Where does it store the information about registred devices etc.? Only mount the config.js seems to be not enougth.

    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      vistalba The drive does not store any data.

      It is important that the container always has the same hostname, because the hostname is part of the device ID (hash). I'm not sure if that is possible with kubernetes.

      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      @vistalba This is the default behavior of a neeo driver. But I think I can change that. I'll probably test it on the weekend.

      Reply Like
      • vistalba
      • vistalba
      • 1 yr ago
      • Reported - view

      Alexander Bauer aaaaaaaaahhhh.. nice hint.

      hostname: neeo-driver-kodi

      Reply Like
  • Hi Alexander Bauer

     

    You know if the resent firware update broke anything on you driver? maybe the NEEO REST-WebService? getting an error when starting:

    one@debianone:~/neeo-driver-kodi/src$ node index.js
    
    ---------------------------------------
    
     NEEO driver for KODI - Version: 0.4.2
    
    ---------------------------------------
    
    [NEEO] Connecting Brain ( 192.168.0.241 ) ...
    
    [NEEO] Starting API server and connect to Brain: 192.168.0.241 ...
    
    events.js:160
    
          throw er; // Unhandled 'error' event
    
          ^
    
    
    Error: listen EADDRINUSE 0.0.0.0:6336
    
        at Object.exports._errnoException (util.js:1020:11)
    
        at exports._exceptionWithHostPort (util.js:1043:20)
    
        at Server._listen2 (net.js:1277:14)
    
        at listen (net.js:1313:10)
    
        at net.js:1423:9
    
        at _combinedTickCallback (internal/process/next_tick.js:83:11)
    
        at process._tickCallback (internal/process/next_tick.js:104:9)
    
        at Module.runMain (module.js:613:11)
    
        at run (bootstrap_node.js:387:7)
    
        at startup (bootstrap_node.js:153:9)
    
        at bootstrap_node.js:500:3

     

    btw, you need to update the neeo-driver-kodi/src/index.js line 18 (driver version number :)

    Reply Like
  • Thank you for this driver, it is working almost perfect for my 2 kodi machines. 

    Only 1 question, i would like to have a shortcut for delete/subtitle time +/subtitle time -. Is it possible to add the 4 color buttons so I can keymap these buttons?

    Reply Like
    • Niels Feenstra I agree, if we can have subtitle time +/subtitle time - buttons it will be perfect :)

      Reply Like
  • When is Kodi integrated in a normal update. Not all people out there are Developers. I can’t understand why one of the most used media center is not integrated from the beginning.  

    Reply Like 1
  • I have seen all your efforts for Kodi. Great work ! As i am not really into programming, has any of you worked on a driver for foobar 2000? There is a http plugin available, an android app is also available . Any thoughts about a foobar driver for neeo ? https://planet.neeo.com/t/63fhaq/directxnative-support-of-foobar2000-would-be-great

    Reply Like
  • Hi, I just test this plugin, it works fine. But, when I start to power on, the script send WOL to Kodi and start a the same time the reciepe and changing input TV. The two actions executing at the same time, nothing is displaying with HDMI. If I start via WOL since I wait 2/3 seconds before changing the HDMI of my TV everything works. It is possible to add this pause some pars?

    THank's

    Arnault

    Reply Like
  • This weekend I finally came around installing Kodi (well, OSMC in my case). This driver is great!

    The "Skip seconds forward" and "Skip seconds backward" don't seem to have a specific handler and therefore fall into the "default" handler switch: https://github.com/alxbauer/neeo-driver-kodi/blob/b4bf6b1d1ffe8bd17e43f068a65ca8f24b3d6443/src/kodiDevice.js#L90 . Is this a restriction on the Kodi API or "just" not implemented? I'm happy to have a look at this myself later this week once I have time, figured somebody (maybe Alexander Bauer ;)) might know this already.

    Edit: REVERSE and FORWARD have the logic to check for an active player and then would call a "fastforward" or "rewind" which I assume would be the same thing? In any case, this doesn't seem to do anything on my installation here. Is that the behaviour I would suspect or are those actions used for something else I'm missing right now?

    Reply Like 1
  • First of all..Thank you for this driver and sorry for my english. For me as an absolutely Linuy noob it was a hard work to get 2 drivers (Enigma 2 from Markus Mahr ) and your Kodi driver to work.(i changed the port for your Kodi Driver)  but i still have a problem, power on does not work for me. i canceled the config.kodi.broadcastAddress, so it's empty, because i run the sdk on a raspberry.  I set the correct MAC and IP Address of my Intel Nuc. With Yatse ecverything works perfect, As i saw in Yatse WOL Port there is 5600 do i have to fill in this port somewhere? Shutdown and Navigation works perfect. 

    Reply Like
    • I'm sorry...today everything works fine, without any changes. I guess it was a confusion with my NUC profile, which just had a power toggle. So when the NUC shuts down because of the toggle and the Kodi Profile seems to be still powered on there is no power on in the NEEO receipe for kodi driver?..Thanks a lot for your work here,with the community drivers the NEEO starts now to get better..

      Reply Like
  • Hello Alex,

    Am about to embark on a mission impossible with this remote, I have a few nagging questions ====>

    What do you think about a multi room feature say if I had an x number of rooms with Kodi installation ====> Kitchen, Living............etc, Wouldn't be nice to have switching buttons (graphics) for if moved into a different room to continue with what you were watching? A bit like a follow me feature. Kodi already can sync libraries and was designed with that in mind.

    The other thing I should point out is that MQTT here is not taken seriously but that not a problem in trying to automate things and not overloading the BRAIN multi-tasking by including other dedicated automation servers to do the heavy lifting! ====>

    For KODI mqtt was taken care of so if you want to do lighting, no problem, look here : Kodi2Mqtt

    Now to have things happen "automagically" you throw in a system like HomeSeer 

    This is not to compete with the BRAIN but to do the hard labour /share the load  =====> You have to like these plugins : 

    mcsMQTT HomeSeer plugin and MQTT plugin for HomeSeer

    I not even mentioned security cameras and the all lot more.

    Going back to main topic, I would like the NEEO remote conservatively ====> SCENES! but not controlling individual lights or devices with the exception of TV charnels thus less work for the BRAIN because most of the hard work happens over the network!

    Opinions granted!

     

    Eman.

    Reply Like
  • Emmanuel Serebe said:
    Hello Alex,

    Am about to embark on a mission impossible with this remote, I have a few nagging questions ====>

    What do you think about a multi room feature say if I had an x number of rooms with Kodi installation ====> Kitchen, Living............etc, Wouldn't be nice to have switching buttons (graphics) for if moved into a different room to continue with what you were watching? A bit like a follow me feature. Kodi already can sync libraries and was designed with that in mind.

    The other thing I should point out is that MQTT here is not taken seriously but that not a problem in trying to automate things and not overloading the BRAIN multi-tasking by including other dedicated automation servers to do the heavy lifting! ====>

    For KODI mqtt was taken care of so if you want to do lighting, no problem, look here : Kodi2Mqtt

    Now to have things happen "automagically" you throw in a system like HomeSeer 

    This is not to compete with the BRAIN but to do the hard labour /share the load  =====> You have to like these plugins : 

    mcsMQTT HomeSeer plugin and MQTT plugin for HomeSeer

    I not even mentioned security cameras and the all lot more.

    Going back to main topic, I would like the NEEO remote conservatively ====> SCENES! but not controlling individual lights or devices with the exception of TV charnels thus less work for the BRAIN because most of the hard work happens over the network!

    Opinions granted!

    Eman.

     

    Hello all,

    Can you please disregard the above post now that I have my remote! After setting it up I found that what I was asking for was feasible through setting up ROOMS ====> Pure Nice!

    BUT! Although I installed the KODI driver for Neeo on my Node-RED/MQTT server I briefly was able to have it connect to the Neeo Brain! WHY? ====> Because in the absence of STATIC IP settings in the Neeo systems, they keep roaming from IP to IP =====> Now that's not good 😲

    But maybe all is not as bad as it seems at first sight? Say if I install the driver on every KODI system I want to use this driver on, the question is can the driver automatically pick up and connect to any KODI which goes on line provided that KODI also has auto IP set by DHCP? ===> This am going to test 👀 Why say this is unless the driver can auto find the NEEO Brain on the network to connect to it, the whole thing defeats the objective! Maybe more coding to the driver to achieve that would be an overkill ====> Now you see it 👀👎. 

    We should all scream and pull our hairs out ( I don't have any 😢)

    Please NEEO Team we need static IPs. And I think it's the reason why it's so hard to pair the NEEO Brain to the Remote!

     

    Eman.

    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Emmanuel Serebe You can run multiple instances of the driver on one central server.

      Clone the repository in different directories and adjust the config.json

      Important settings to run multiple instances are:

      // Set the local TCP port for the NEEO REST-WebService
      // Use a different port number for each instance
      config.neeo.port = 6336;
      

      and

      // Use different settings here to find the correct instance in the NEEO App
      config.neeo.driverName = 'MediaCenter';
      config.neeo.driverManufacturer = 'KODI';

      But I've never really tested it. You're the first one to try.

      Alex

      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Alexander Bauer I just noticed that the new SDK version 50.5 has support for multiple drivers. I will take a closer look in the next days, maybe the problem can be solved more easily with the new version.

      Reply Like
    • Alexander Bauer Nice one! Alex,

      That sounds incredible! Am going test and see it works.

      There is also one more thing, to start the drivers automatically? I have been using pm2 but caught it spiking the CPU at 100% and disabled it. It's known issue with pm2.

      I would like to use the Docker version but just trying to learn how to and noticed on my Qnap there a few versions of your driver listed so I believe 0.4.3 is the stable one and please advise on how to configure and run.

       

      Thank you.

      Reply Like
  • Hi.

     

    Can somebody help me. Trying to run the docker version but can get it to start.

    Attaching some images.

    Reply Like
  • Hi Nicalas,

    You have to be inside /neeo-driver-kodi/src folder when executing commands.

     

    Note : cp config.js.sample config.js

     

    Eman.

    Reply Like
    • Emmanuel Serebe Is it the Index.js I should execute?

      I attach an image of the settings I can do when I create the docker.

      Reply Like
    • Niclas Wallensäter 

      Start here : https://planet.neeo.com/t/k9tnlp/getting-started-with-node-js-code-and-the-neeo-sdk-v0-5

      I have not used docker before but provided it creates the driver automatically then true it's the 

      'node index.js' I wanted you see it the git version :( https://github.com/alxbauer/neeo-driver-kodi ) and compare notes.

      Now if you look again at your initial post, that problem is caused if you execute the commands outside the 'src' folder!

      So if already understand docker compare notes if were to be using the command line (Linux)

      How to install

      $  

      git clone https://github.com/alxbauer/neeo-driver-kodi.git

      if PI then 

      $ cd ~/neeo-driver-kodi/src

      Then

      npm install

      $ cp config.sample.js  config.js

      Then Edit the config.js file to adjust the settings

      Then Start the driver

      node index.js 

       

      Now all that assumes you are sudo and also have Node.js intalled

      Tip : All that is found here : https://github.com/alxbauer/neeo-driver-kodi

       

      I hope that helps.

       

      Eman.

      Reply Like
    • Emmanuel Serebe Thank you for your time. I will try again tomorrow but now I have an idea how to maybe solve it.

      Reply Like
  • Can you guys help with my log file?

    var/log/node.log is at 15gb.  My OS SSD is only 30gb.

    Can I reset the log, delete the log or move the log to free up the space??

    Any help would be great.

    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Mark Haywood  You can delete the log file ...

      rm /var/log/node.log
      Reply Like
  • Hi Alex,

    Can you please be more specific on how to run the driver on docker (how to). I know you are not obligated but it could help a lot of folks. I have tried it on the Qnap and RPI but I can't have the bloody thing run!. Is there a clear guide assuming one is using Docker for the first time?

    I have indeed been able to run the git version but docker boasts of cool tricks on utilizing resources and who wouldn't like that. 

    Please be nice and simplify the install process.

     

    Thank you. 

    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Emmanuel Serebe The docker image is for x86 architecture only! It will not work on ARM based hosts like RPi or Qnap. At the moment I don't have the time to build images for all platforms.

      Reply Like
    • Alexander Bauer 

      Now that explains everything! I tried days on end! I thought I was going nuts!

      And if so, does it auto-start? Can you share the basics?

      I found this guide : https://www.smarthomebeginner.com/docker-home-media-server-2018-basic/  am interested in and may be able to achieve that.

      Otherwise I appreciate your help.

       

      Eman.

      Reply Like
  • Trying to run in docker but keep getting this error. Anyone seen it?

     

    ⋊> ~ docker logs neeo-driver-kodi                                                            10:49:00
    ---------------------------------------
     NEEO driver for KODI - Version: 0.4.5
    ---------------------------------------
    [NEEO] Connecting Brain ( 10.0.0.83 ) ...
    [NEEO] Starting API server and connect to Brain: 10.0.0.83 ...
    [NEEO] Api is ready and running!
    
    [NEEO] ===> Use the NEEO app to search for "KODI" device. <===
    
    [KODI] Try connecting at 10.0.0.79:9090 ...
    [KODI] Successfully connected.
    401 - undefined
    401 - undefined
    [KODI] Active players = 0
    Reply Like
    • Christian Ek 

      That indicates that the driver is connected but nothing is playing in Kodi!

      Reply Like
      • Christian Ek
      • System developer
      • Christian_Ek
      • 1 yr ago
      • Reported - view

      Emmanuel Serebe Thanks for your fast reply, sadly the buttons are not working for me. the logs shows following:

       

      [KODI] Button FORWARD pressed
      401 - undefined
      [KODI] Button SUBTITLE pressed
      401 - undefined
      [KODI] Button PAUSE pressed
      401 - undefined
      [KODI] Button SKIP SECONDS FORWARD pressed
      401 - undefined

      What am i missing?

      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Christian Ek HTTP 401 means authentication error. Check user and password.

      Reply Like
      • Christian Ek
      • System developer
      • Christian_Ek
      • 1 yr ago
      • Reported - view

      Alexander Bauer thanks. That was it :) now working. Good job with the driver!

      Reply Like
  • Hello Alex,

    The new driver is not working because it's trying to connect to your NEEO but can't find it! log below : 


    - Start server
    ERROR! { Error: connect ETIMEDOUT 192.168.178.170:3000
        at Object.exports._errnoException (util.js:1020:11)
        at exports._exceptionWithHostPort (util.js:1043:20)
        at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)
      code: 'ETIMEDOUT',
      errno: 'ETIMEDOUT',
      syscall: 'connect',
      address: '192.168.178.170',
      port: 3000,
      config:
       { adapter: [Function: httpAdapter],
         transformRequest: { '0': [Function: transformRequest] },
         transformResponse: { '0': [Function: transformResponse] },
         timeout: 0,
         xsrfCookieName: 'XSRF-TOKEN',
         xsrfHeaderName: 'X-XSRF-TOKEN',
         maxContentLength: -1,
         validateStatus: [Function: validateStatus],
         headers:
          { Accept: 'application/json, text/plain, */*',
            'User-Agent': 'axios/0.17.1' },
         method: 'get',
         url: 'http://192.168.178.170:3000/systeminfo',
         data: undefined },
      request:
       Writable {
         _writableState:
          WritableState {
            objectMode: false,
            highWaterMark: 16384,
            needDrain: false,
            ending: false,
            ended: false,
            finished: false,
            decodeStrings: true,
            defaultEncoding: 'utf8',
            length: 0,
            writing: false,
            corked: 0,
            sync: true,
            bufferProcessing: false,
            onwrite: [Function],
            writecb: null,
            writelen: 0,
            bufferedRequest: null,
            lastBufferedRequest: null,
            pendingcb: 0,
            prefinished: false,
            errorEmitted: false,
            bufferedRequestCount: 0,
            corkedRequestsFree: [Object] },
         writable: true,
         domain: null,
         _events:
          { response: [Function: handleResponse],
            error: [Function: handleRequestError] },
         _eventsCount: 2,
         _maxListeners: undefined,
         _options:
          { protocol: 'http:',
            maxRedirects: 21,
            maxBodyLength: 10485760,
            hostname: '192.168.178.170',
            port: '3000',
            path: '/systeminfo',
            method: 'get',
            headers: [Object],
            agent: undefined,
            auth: undefined,
            nativeProtocols: [Object],
            pathname: '/systeminfo' },
         _redirectCount: 0,
         _redirects: [],
         _requestBodyLength: 0,
         _requestBodyBuffers: [],
         _onNativeResponse: [Function],
         _currentRequest:
          ClientRequest {
            domain: null,
            _events: [Object],
            _eventsCount: 6,
            _maxListeners: undefined,
            output: [],
            outputEncodings: [],
            outputCallbacks: [],
            outputSize: 0,
            writable: true,
            _last: true,
            upgrading: false,
            chunkedEncoding: false,
            shouldKeepAlive: false,
            useChunkedEncodingByDefault: false,
            sendDate: false,
            _removedHeader: {},
            _contentLength: 0,
            _hasBody: true,
            _trailer: '',
            finished: true,
            _headerSent: true,
            socket: [Object],
            connection: [Object],
            _header: 'GET /systeminfo HTTP/1.1\r\nAccept: application/json, text/plain, */*\r\nUser-Agent: axios/0.17.1\r\nHost: 192.168.178.170:3000\r\nConnection: close\r\n\r\n',
            _headers: [Object],
            _headerNames: [Object],
            _onPendingData: null,
            agent: [Object],
            socketPath: undefined,
            timeout: undefined,
            method: 'GET',
            path: '/systeminfo',
            _ended: false,
            _redirectable: [Circular],
            parser: null },
         _currentUrl: 'http://192.168.178.170:3000/systeminfo' },
      response: undefined }

    npm ERR! Linux 4.14.32v7-aufs
    npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
    npm ERR! node v6.14.2
    npm ERR! npm  v3.10.10
    npm ERR! code ELIFECYCLE
    npm ERR! neeo-driver-kodi@0.5.0 start: `neeo-sdk start`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the neeo-driver-kodi@0.5.0 start script 'neeo-sdk start'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the neeo-driver-kodi package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     neeo-sdk start
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs neeo-driver-kodi
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls neeo-driver-kodi
    npm ERR! There is likely additional logging output above.

    npm ERR! Please include the following file with any support request:
    npm ERR!     /home/pi/node_modules/neeo-driver-kodi/src/npm-debug.log
     

     

    Am I doing something wrong? Please advise because I can't see the settings for the NEEO brain in the config!

     

    Eman.

    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Mark Haywood Emmanuel Serebe 

      With Version 0.50.x of the NEEO-SDK the brain configuration is done in the package.json file.
      Look for the following section in the file:

      "neeoSdkOptions": {
          "brainHost": "192.168.178.170",
          "brainPort": 3000,
          "serverName": "default",
          "serverPort": 6636
      },
      

      These options are optional. If you do not specify the brainHost, then the driver will try to autodiscover your Neeo Brain.

      Also see: https://github.com/NEEOInc/neeo-sdk#neeo-sdk-cli for more information.

      Warning: The version 0.5.0 is *BETA*. It should work, but is less tested.
      Any feedback is welcome.

      Reply Like
    • Alexander Bauer Thank man for pointing that out. It was driving me nuts!😡

      Reply Like
  • I'm having the same issue, just installed 0.5.0 from 0.4.2 I have a fixed IP for my brain and it sure isnt 192.168.178.170!!

    Any one can advise?

    Reply Like
    • Mark Haywood You need to change the config file to fit your Kodi / Brain ip i guess. But i don't use this driver so i'm not 100% sure about it.

      Reply Like
    • Markus Mahr That was something you could do in the old version config, but this new one doesn’t have a line to change the brain IP, I too think that’s what I need

      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view
      Reply Like
    • Alexander Bauer  Works like a charm, just testing the WOL i had working earlier.  Thank you.

      Reply Like
  • How do I keep the driver running. Everything stops when I close the putty window to to Linux server. 

    Reply Like
    • Mark Haywood did you start teh server in the same instance with putty? if so, you also close the server. If you runt he code directly on the linux server (outside the putty session) it shouldn't stop when ending putty.

      Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Mark Haywood use tmux. might have to install it first

      Reply Like
  • I just released a new version. With version 0.6.0 a lot of code has been restructured to support the new neeo-cli utility. Also the installation of the driver has changed again. The driver can now be installed completely with NPM. Please follow the instructions: https://github.com/alxbauer/neeo-driver-kodi#how-to-install

    The driver now also supports browsing of videos, music, TV shows and PVR.
    There is still much to improve here, but basically it should work.

    To use the browsing functions, just add the shortcuts:

    • [DIRECTORY] Video
    • [DIRECTORY] Music
    • [DIRECTORY] TV Shows
    • [DIRECTORY] TV And Radio

    Have fun ...
    Alex

    Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Alexander Bauer please show me your package.json file. Im getting json parse errors left and right..

      Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Alexander Bauer yhea, i cant seem to append this code to the package.json file without getting parse errors.. 

      {
        [...]
        "neeoSdkOptions": {
          "serverName": "neeo-server",
          "serverPort": 6336,
          "brainHost": ""
        }
      }
      

      please show me how the complete file should look to see what i do wrong.

      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Remko

      Here is a sample of a complete file:

      {
        "name": "Neeo-Server",
        "version": "1.0.0",
        "description": "",
        "main": "index.js",
        "scripts": {
          "test": "echo \"Error: no test specified\" && exit 1"
        },
        "keywords": [],
        "author": "",
        "license": "ISC",
        "neeoSdkOptions": {
          "serverName": "neeo-server",
          "serverPort": 6336,
          "brainHost": "192.168.178.170"
        },
        "dependencies": {
          "neeo-driver-kodi": "^0.6.0"
        }
      }
      Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Alexander Bauer tnx, you should add that to the github install description. because users (non coders) dont know not to put [...] in or add a comma in the end, also "dependencies" are not mentioned, but maybe its not needed.. but by putting your complete list up it will help normal users..  :)

      Reply Like
  • 
    
    Any idea whats wrong here anyone?
    
    
    one@debianone:~/my-neeo-drivers$ npm install --save neeo-driver-kodi
    
    Neeo-Server@1.0.0 /home/one/my-neeo-drivers
    
    └── neeo-driver-kodi@0.6.0
    
    
    npm WARN Neeo-Server@1.0.0 No description
    
    npm WARN Neeo-Server@1.0.0 No repository field.
    
    one@debianone:~/my-neeo-drivers$ neeo-cli start
    
    /usr/lib/node_modules/@neeo/cli/lib/sdkoptions.js:22
    
      );
    
      ^
    
    
    SyntaxError: Unexpected token )
    
        at createScript (vm.js:56:10)
    
        at Object.runInThisContext (vm.js:97:10)
    
        at Module._compile (module.js:549:28)
    
        at Object.Module._extensions..js (module.js:586:10)
    
        at Module.load (module.js:494:32)
    
        at tryModuleLoad (module.js:453:12)
    
        at Function.Module._load (module.js:445:3)
    
        at Module.require (module.js:504:17)
    
        at require (internal/module.js:20:19)
    
        at Object.<anonymous> (/usr/lib/node_modules/@neeo/cli/lib/commands.js:4:20)
    
        at Module._compile (module.js:577:32)
    
        at Object.Module._extensions..js (module.js:586:10)
    
        at Module.load (module.js:494:32)
    
        at tryModuleLoad (module.js:453:12)
    
        at Function.Module._load (module.js:445:3)
    
        at Module.require (module.js:504:17)
    Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Remko Looks like a problem with neeo-cli. But i've no problems with it.🤔

      Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Alexander Bauer maybe this looks wrong aswel

      one@debianone:~$ npm list neeo-sdk
      
      /home/one
      
      ├─┬ neeo-driver-kodi@0.1.0
      
      │ └── neeo-sdk@0.45.7
      
      └── neeo-sdk@0.50.5 
      Reply Like
      • Alexander Bauer
      • Software Developer
      • Alexander_Bauer
      • 1 yr ago
      • Reported - view

      Remko Yeah, that looks very strange. Looks like you mixed different versions of neeo-sdk, as well as neeo-driver-kodi. You may try a new installation in an empty directory.

      Reply Like
      • Remko
      • Remko
      • 1 yr ago
      • Reported - view

      Alexander Bauer I managed to uninstall one of them, but cant seem to get rid of the other. any idea's?

      one@debianone:~$ sudo npm uninstall neeo-sdk
      
      npm WARN enoent ENOENT: no such file or directory, open '/home/one/package.json'
      
      npm WARN one No description
      
      npm WARN one No repository field.
      
      npm WARN one No README data
      
      npm WARN one No license field.
      
      one@debianone:~$ npm list neeo-sdk
      
      /home/one
      
      └─┬ neeo-driver-kodi@0.1.0
      
        └── neeo-sdk@0.45.7 
      Reply Like
Like21 Follow