github / NPM repositorys from every User developing with the SDK

Carl Vannest As Markus said, the SDK drivers are very much optional extras.

Most devices are supported out of the box with IR drivers and you will have your Neeo setup very quickly to control your devices.

If you want to get network control of your devices then at the moment you will have to delve into the the SDK and run a raspberry pi or similar.

in time, some of these drivers will be migrated into the core Neeo code and will run on the brain.

hope that makes sense.

Bruce Hartley, thanks for making this driver available. Would this be compatible with Marantz AVRs such as the NR-1604? Denon and Marantz seem to be using a similar TCP command set. 

Cheers 

Markus Marbach I don't know. 

I guess you could try it. 

Maybe tweak it I requires ?

Awesome mate, will give it a go whenever my combo arrives and wife approves my man cave hours. :)

Markus Mahr Bruce Hartley has anyone if you had time to look into the Marantz AVR IP driver? I've received my combo this week and will be spending some time to set up a nodejs server on my Synology NAS. Hopefully I get the time approved by my wife so I can have a go at this. I might get a copy of Bruce's Denon AVR driver as a starting point. Any thoughts or gotchas I need to be aware of?

Justin Feinman I don't have either system just the Caseta system, but I think Neeo natively supports RA devices,  per the https://neeo.com/works-with-neeo/. 

Nick H Thanks Nick! I'm going to try and build a driver for the LG OLED TVs. Will post back if I have success. 

Humayun Hasan you might want to have a look at this node module: https://www.npmjs.com/package/lgtv2

Tom Schneider thanks! This will help get me started. Looks like I may not have to develop the communication functions. Just need to define the buttons and commands to map to this package. 

Nick H BTW, I was able to connnect to my C7 TV and have it respond to commands as documented in the E6 manual. I also looked at the E7 manual and the IP commands don't seem to have changed. But this was all done from telnet. Still have to create the NEEO driver. 

Nick H It shouldn't be a problem to include all known commands once I get comfortable with the NEEO SDK and getting the drivers to run. It looks like there are two ways to communicate with the the LG OLEDS. One is with using the LG Web OS API and the other is using telnet commands that are documented in the TV manuals. I don't know if there are advantages for using one approach over the other. I will start a separate thread for LG OLED IP Control and document progress there though it may be slow in the beginning.

Humayun Hasan I can not give you a definitive guide since I have my notes on my desktop at home about 9000km away, but I did that by adding a new service. I hope I can recall enough to give you some hints to get that going. 

So let's say the service is called example, first you need to create that service file:

sudo nano /etc/init.d/example

I then copied the contents from here. You need to edit the first lines, especially the variables, dir, cmd, user. Should look something like this:

#!/bin/sh
### BEGIN INIT INFO
# Provides: EXAMPLE
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start daemon at boot time
# Description:       Enable service provided by daemon.
### END INIT INFO

dir="="/home/pi/example"
cmd="node app.js"
user="root"

Save that, and then change the rights so you can execute it:

sudo chmod 755 /etc/init.d/example

You can then activate the service with that command:

sudo update-rc.d example defaults

You should now be able to start and stop the service with these commands:

sudo service example start
sudo service example stop
sudo service example restart

EDIT: I guess the guide  Markus Mahr posted would work fine too.

Markus Mahr Patrick  Thanks for the helpful tips! I'm actually using systemd on my Raspberry Pi instead of init.d but the information you provided pointed me in the right direction. I was able to get the Lutron driver running as a background process (executable command is 'node index.js' with absolute paths defined for both the node binary and the driver index.js) but the driver itself has an issue connecting to the Lutron hub as a system daemon.  I'll check with the driver's author. One step forward!

Humayun Hasan Try http://pm2.keymetrics.io , we use it all the time at work to start node projects.

Markus Mahr Awesome, thanks! Is there a how to set up the SDK for dummies guide anywhere? I'm still a n00b but would love to learn :)

Markus Mahr I run it on a raspberry pi 2 and 3, the 3 also runs openmediavault.  Load is under 25 % on the 2 and 35 % on the 3.  Still, it taxes the system more than it would only running NEEO SDK.  I really like Openhab though and the NEEO transport is working quite well for me.  I like how flexible this remote is and will become even more in the future.

Frederik Vancoillie Markus Mahr Jonas Olofsson

Just to add to the discussion.  The CPU usage really depends on how many things you have defined in openHAB (and mapped to NEEO) and how noisy those things are (ie how often they update state).  The latest version has reduced the transport CPU usage by quite a bit, has support for the newest firmware changes (power state, timings) and is much more stable (survives IP address changes, power outages, etc) - soon it will support older OH1 bindings and virtual things/items.  The development has been ongoing and the community support has been very active/awesome (even got one of the OH admins to purchase a NEEO based on how well it controls openHAB).

Morgan Fromentin 

really nice. i made yesterday a similar remote for firetv also by adb. Didn´t see your driver at this time. You can add decription for all android devices wich support network adb mode

Morgan Fromentin  Björn Müsing  hi, I had a question for you. coding is only a hobby of mine so my knowledge is minimal. In your shieldcontroller, your code:

if (-1 !== stdout.indexOf(config.shield.ip)) {
                exec('sudo adb shell '+config.shield.mapping[actionName], (err, stdout, stderr) => {
                    if (err) {
                        console.log(err);
                        return;

I understand how this works... I think... If no "ip" is connected to the adb it would return an index of -1. My question is would there have been a way to check if the stdout string == my ip constant (declared earlier in the code)? This was the direction I was taking and was running into errors. I eventually stumbled across your code which solved this issue, but was wondering if there was a solution with the direction I was headed.

Sorry if I am not very clear....

Morgan Fromentin 

Thank you for the great driver. I notice a small delay when pressing a button.

Is it possible add 2 different Shields?

Aaron Ranson The thing is that the "sudo adb devices" command actually returns more than just the ip of the connected devices. So, to be sure the IP is effectively in the list, I just test its presence in the list, in the returned string. Clear enough ?

Niels Feenstra Sadly yes, there is a delay, that is because I use the "adb" solution to communicate with the shield. This is a debug tool provided from NVIDIA to developers just to test and debug their app, but in our cas, this is the only way to comunicate with the Shield without buying any extra stuff - like a FLICIRC -. Still waiting for the bluetooth support from NEEO.

And no, for now, it's not possible to add 2 shields, sorry.

Morgan Fromentin thanks for the reply. Yeah, I kind of figured that out after playing around with the code a bit. Despite my fire TV being the only listed connected device, I was returning an array index value of 26 or something. I assumed there was more to it than I could see that was being returned. Playing around with it more, I could see it wasn't strictly ip returning. 

I just stuck with your solution and it works great now.

Https://github.com/amr024/fireapps1