Introducing the NEEO SDK

Developers: Here is your access to the official NEEO SDK. We share with you our development environment, which we use ourselves to create integrations, drivers, applications and more. With the power of the SDK, you will be able to unlock the full potential of NEEO and create new experiences for everyone. Here are the most important links:

Are there plans for a deeper level of integration with the Neeo remote itself? I'm still pursing the SDK source code, but exporting media collections that the remote can browse seems to be absent. Would be super nice to be able to push self-contained HTML5 widgets to the remote which could represent and control a device. Widgets could have internal navigation to browse media collections or do advanced things like provide rgb color or temperature picking for LED lights.

Any plans for a Neeo brain / remote simulator as well? Waiting for my remote, but would really like to get started with the SDK before then. :)

John Ehringer As you can see over on the NEEO-SDK Github Page, such features are allready requested. Since the first Publishment the SDK was also Updated a few times and brings new Features with each Update. So also i'm quite sure more and more features will come over time.

I think the Team is very Busy right know with the Launch of the Product and will be much busier, when the first 100 of people will hold the Remote in their Hands, so i assume, more features can take a few days, weeks or month, but there are definitly some new ones.

I am really happy that NEEO-SDK is available now and I hope that I will get my device soon. 2 questions :

The SDK gives me the possibility to implement drivers for special devices with node-js technology running on some external node-js host interacting with the NEEO brain. Will it be possible in future to install such drivers directly on the brain ?

The whole SDK is more or less a wrapper for REST based bidirectional HTTP communication. As I am a Microsoft .NET guy I think about implementation of a NEEO-SDK with .NET technology as it would better fit in my private SmartHome / Media environment. I would like to hear if somebody else is interested on a .NET based SDK.

Christian Riedl For the first question the answere can only be given from Patrick , Raphael or Sandro . MAybe one of these guys will answere.

For your second question: It is difficult to say, the official SDK is not finished, it will keep crowing over time. Therefor a "Translation" to an other Language can be a endless Job and in my eyes it would be bad to have a half done way. Therefor i'm normally against such thinks, when the original API is not finished.

I already wrote a version with C# and a version of java. The C# was just a test bed for some stuff I was doing - the java one if full featured and part of the openHAB implementation. Feel free to reach out to me if you have any questions when you are implementing yours...

Christian Riedl Concerning your first question: You are right, at the moment these drivers have to run somewhere else and can't be installed on the NEEO Brain. We are working on a solution for that, we are currently looking at different options. Stay tuned.

Christian Riedl C# / .Net guy reporting in. Working with node is ok even if javascript gives me a rash, but I would happily find a use for a .Net implementation if you were to make the effort. Of course. as Markus Mahr mentions, this would probably have to chase the official API a bit until it becomes stable.

Rune JacobsenRune Jacobsen I know for a fact from Bruno, the SDK will soon be available in TypeScript - I actually took a pass at it myself but the SDK progressed on without me while I was coverting it (see the src folder in the next branch at my github - https://github.com/amirburbea/neeo-sdk/tree/next ) . While obviously not C#, it's a huge help to have typed interfaces. I would also love to have the SDK in Kestrel/C#/.NET Core as well, but then 3rd party drivers are not compatible and would have to be rewritten.

Amir Burbea That is very interesting, thank you! TypeScript is a huge step in making javascript bearable for someone used to static typing. I have been through a major rebuild of a lot of the tech infrastructure here at home and will take a look at your repo once the dust literally settles!

Not sure how you use the SDK to code custom IR Codes for a device - I've looked over the examples but don't know how IR Codes are entered. Is there a doc you can point to about how the Brain uses IR Codes or what format they are entered in? Thanks.

Tom Berarducci the reason to use a SDK is to control your device over IP rather then IR. If you would like to include a driver then just ad a new topic requesting a driver and tag Andy . If you have IR codes then you can add them to the post. If not then the NEEO driver team will try to find them.

Ok so now I get it. IR codes cannot be added via SDK... that's unfortunate because it causes a bottleneck.

Also when you say "send the IR Codes" that implies all IR codes are in some standard format. Not sure that's the cause. I can use my Pronto to grab the IR codes sent by a remote - comes out as a big hex string - is that what you want? pls confirm.

Yes, Pronto HEX code would be one of them. There are other formats such as NEC, RC5, Sony,. It would not be necessary to convert them to Pronto HEX code. Andy can sure handle any of the formats you provide.