A Bluetooth NVidia Shield driver is HERE
Few weeks ago i posted this sneak peak...
Since I just couldn't stand the fact that Shield Bluetooth support was promised, but never delivered. So I started a long... long... quest online and spend no less then 200 hours researching over the past few weeks, learning a lot about Bluetooth GATT profiles, services, characteristics etc. etc.
In the end i managed to make it work; and the driver is now on GitHub!
Christian Kalemkiewicz Canberk Demiroluk Jacob Wiqvist Jeff Bernard Cooper Markus Marbach Emmanuel Serebe Pepijn Chad L. Quint Stoffers Julien Luca Weil Niels de Klerk Daniel Jordi
The driver is now on Github https://github.com/Webunity/neeo-driver-nvidia-shield
Twitter link: https://twitter.com/GillesvdHoven/status/1118395927578988544Reply
Darren Greenberg Personally, I consider a Logitech hub to be the easiest way to realize this because the NEEO Brain itself cannot use Bluetooth because of discontinued development. The Logitech hub can be paired easily as a normal remote with the Amazon Fire TV via Bluetooth. The only thing you have to do then is to send the commands from NEEO via forward actions to a system that passes the command to the Logitech Hub. You can do this, for example, with a Raspberry with a PHP server or a home automation software that forwards the command from NEEO and passes it to the Logitech Hub. I myself use Symcon and IPSymconNEEO with IPSymconHarmony to remotely control a Fire TV in another room via a Logitech Hub via Bluetooth with an NEEO Remote.Reply
Hello Gilles van den Hoven Are you still there? Can you please advise on how to install the driver SDK?
I managed to pair up the the Shield with the PI but still stuck on getting the driver in the BRAIN.
Doing an "npm run index.js" doesn't yield anything but error. How far am I too off?
Or do I have to do it on the whole folder?Reply
Gilles van den Hoven ,
I guess you are busy and most likely forgot about my request. Am sorry about that.
But here goes : In the files hosted on Git hub miss the critical files and/ or folder namely "peripherals" as shown in your last video posted here : https://gopro.com/v/DbW4rZbP1NlQo which are of the NEEO driver side of things.
Of course I know you mentioned that you don't develop for NEEO anymore but what has one got to do to get hold of this driver before the NEEO dies? 😟
It's sad that no so many realized how amazing the all in one Nvidia SHEILD is and we all missed the plot!
Else, do I have to contact you privately about this?, because I didn't get a response at Git Hub. Pleas advise.Reply
Gilles van den Hoven ,
When I run npm i in the neeo-driver-nvidia-shield cloned folder. here is the log :
0 info it worked if it ends with ok
1 verbose cli [ '/home/pi/.nvm/versions/node/v6.14.4/bin/node',
1 verbose cli '/home/pi/.nvm/versions/node/v6.14.4/bin/npm',
1 verbose cli 'i' ]
2 info using firstname.lastname@example.org
3 info using email@example.com
4 verbose npm-session 9bb3fed6f3d399ee
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall firstname.lastname@example.org
7 info lifecycle email@example.com~preinstall: firstname.lastname@example.org
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 timing stage:loadCurrentTree Completed in 64ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 2ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 21ms
16 silly install loadAllDepsIntoIdealTree
17 http fetch GET 200 https://registry.npmjs.org/neeo-sdk 430ms (from cache)
18 http fetch GET 200 https://registry.npmjs.org/one-websocket 446ms (from cache)
19 http fetch GET 200 https://registry.npmjs.org/@neeo%2fcli 502ms (from cache)
20 silly fetchPackageMetaData error for one-websocket@^2.0.0 No valid versions available for one-websocket
21 silly pacote range manifest for neeo-sdk@^0.53.8 fetched in 498ms
22 silly pacote range manifest for @neeo/cli@^1.1.0 fetched in 585ms
23 http fetch GET 200 https://registry.npmjs.org/body-parser 367ms (from cache)
24 silly pacote range manifest for body-parser@^1.18.3 fetched in 477ms
25 http fetch GET 304 https://registry.npmjs.org/debug 1466ms (from cache)
26 http fetch GET 304 https://registry.npmjs.org/config 1479ms (from cache)
27 http fetch GET 304 https://registry.npmjs.org/bluebird 1552ms (from cache)
28 silly pacote range manifest for debug@^3.1.0 fetched in 1618ms
29 silly pacote range manifest for config@^1.28.1 fetched in 1634ms
30 http fetch GET 304 https://registry.npmjs.org/debug 1061ms (from cache)
31 silly pacote range manifest for bluebird@^3.5.2 fetched in 1696ms
32 http fetch GET 304 https://registry.npmjs.org/bluebird 1129ms (from cache)
33 http fetch GET 304 https://registry.npmjs.org/commander 1118ms (from cache)
34 http fetch GET 304 https://registry.npmjs.org/axios 1183ms (from cache)
35 http fetch GET 304 https://registry.npmjs.org/bonjour 1207ms (from cache)
36 silly pacote range manifest for debug@^4.1.0 fetched in 1199ms
37 silly pacote range manifest for bluebird@^3.5.3 fetched in 1267ms
38 silly pacote range manifest for commander@^2.19.0 fetched in 1246ms
39 http fetch GET 304 https://registry.npmjs.org/express 1241ms (from cache)
40 silly pacote range manifest for axios@^0.18.0 fetched in 1340ms
41 silly pacote range manifest for bonjour@^3.5.0 fetched in 1354ms
42 http fetch GET 304 https://registry.npmjs.org/fast-url-parser 904ms (from cache)
43 silly pacote range manifest for bluebird@^3.5.1 fetched in 118ms
44 silly pacote range manifest for express@^4.16.4 fetched in 1394ms
45 silly pacote range manifest for commander@^2.16.0 fetched in 167ms
46 silly pacote range manifest for fast-url-parser@^1.1.3 fetched in 1052ms
There is an error at line "20"