github / NPM repositorys from every User developing with the SDK

Because NEEO offers a SDK for the Public development of Drivers to be Supported with itself. And not everybody whant to search the Web for a NEEO Supported Driver by themselves. I would like to start a listing of every SDK driver available.
Visit the following link to find a Overview of the current Available (and discovered Drivers). Please feel Free to enter new discovered ones or selfmade Drivers.

As new entries will follow i will edit this Post and add the new Devices. If possible make a short reply and Mention me about a new Device.
All Bugs and Errors should be discussed in an other Topic or (the better way) directly over at the GitHub Page.

You can find the SDK on GitHub over here: or go to the Examples over here: The SDK Documentation is available under the following link:

Also Helpfull Links to get started with the Drivers are the following Topics from Niels de Klerk :

Node.js Starter Guide:

API Examples:



To Run multiple Drivers it is required to Change the Port of each individual Driver used. This must be fixed from NEEO in the Main SDK Code. They are allready working on a better solution!

For a quick overview of the actual availability of developed Drivers here is a short list:


Lurton Electronics Cassata Wireless Devices
Enigma2 Receivers
Blustream HDBASET Matrix
Athom Homey
TP-Link Smart WiFi Plugs (HS100 & HS110)
LIFX Smart Bulbs
Onkyo AVRs
Sony Bravia TVs
Logitech Squeezebox
openHAB Binding and Transport
Denon AVR
Belkin WeMo Switch



To Keep this Topic clean and only add Drivers, please Open a Topic for the Discussion of one of the Drivers!

If you like to Setup such a driver and have no clue how to do it, maybe this guide help you:

If you have questions about the usage of drivers, just reply in the other Topic, please not within here!

75replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • New driver: myStrom WiFi Switch


  • Like 1
  • I've knocked up a simple Nanoleaf Aurora Driver - it's pretty basic at the moment but it works for me. Currently it only supports changing colour, changing brightness and switching the Aurora off and on. It's still a work in progress - more features to come!

  • Posted a driver interfacing the new NEEO SDK media player example to node-raumkernel for controlling and also browsing the mediaserver of Raumfeld / Teufel streaming devices. The main limitations that I'm currently aware of are listed in the Readme.

  • This is somewhat pointless now, but we published our driver for Yoctopuce devices:

  • Yet another attempt at a Kodi driver:

    Like 1
  • Hello, is there still an interest for new drivers? I am finalising one for yamaha receivers and in progress for Mi TVs. Please let me know if I should publish them. I never had the neeo with cloud working so don't know if they were part of neeo supported library. 

    Like 1
    • JeanArnaud , You may not be able to make an SDK for Roon. 😊

    • Tolga Aydogan indeed it is not my immediate priority. Later maybe... 

    •  JeanArnaud Hi,

      Ok thanks

  • By the way for those who could be interested I have also created a small driver to connect to a python library connecting to broadlink IR devices. The good thing is that broadlink is super cheap (less than 15 USD) and then you can control any device with IR, anywhere. So all the Air conditioning units of my home are under control... 

    Like 3
      • Bernard Cooper
      • Software Tester / Tech Enthusiast / Disenchanted KS NEEO backer
      • Bernard_Cooper
      • 3 yrs ago
      • Reported - view

      Sounds interesting.  The more drivers the better chance we have to keep our expensive purchases functional once the servers go dark.  I see that Broadlink devices have a cloud database AND can learn IR codes.  A trick we are told NEEO could do but the devs / Raphael refused to enable... for reasons.

      I haven't been paying an awful lot of attention to the drivers and I'm not 100% sure how they interface with NEEO.  Is it correct we need to have another device that is always on in order for the drivers to work, i.e. they aren't stored in the brain?  If so, how have people been implementing this?  Could it be done with a Raspberry Pi?

      • JeanArnaud
      • JeanArnaud
      • 3 yrs ago
      • 1
      • Reported - view

      Bernard Cooper yes Bernard, you are absolutely correct, you need to have a device always on. Obviously the best option is a raspberry pi, it is totally inexpensive and very power efficient. Plus you can find tons of extremely detailed and easy to follow tutorial to install it and have node.Js (the runtime used by the brain) working. After, installing the drivers is very easy. That means that I have my Pi always on somewhere hidden in a closet, I access it remotely from my computer (also, super easy to do) and deploy the drivers directly in it without manual interventions. 

      Like 1
    • JeanArnaud I would be interested too. I would really appreciate if you could share your work.

    • Andreas Coradi ok, no pb, I will look at it this weekend. Actually it is only a wrapper to a good python library I found. The library basically use the broadlink (mini 3 in my case) to learn an IR code and being able to repeat it on request. 

      You may ask how to learn code if you don't have the remote control anymore. The best way I found is to use an old android device with IR blaster and downloaded anymote app which has a huge IR codes database. I used it to configure my xbox one x for example. Of course for playing it is not suitable but for netflix over xbox, it is more or less OK.

      Very useful for switch on and switch off of not 'always on" devices for example. For my Mi TV driver, I first try an http request, if no answer, I switch on the TV automatically  through IR and take over the control with WiFi http calls. 

  • Other advantage is  that for broadlink I don't have to use the Web. I can control the device locally (not a fan of havingy data on the cloud). 

Like21 Follow