-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install failure #11
Comments
Were you ever able to make any progress on this? I'm running in to a similar situation, I've been trying off & on for weeks to get this working on a fresh RPi install. No combination has worked as of yet on my end. |
No I haven't worked on it, unfortunately this looks like abandonware so we'll have to fix it ourselves, interested @the1snm ? |
I'm definately interested in seeing this up and working, I'm starting to think some of the trouble could be related to a bad GB module. I saw a post on Firstbuilds site here: https://cocreate.firstbuild.com/u/mylescaley/greenbeanmakermodule?d=gxcvxkp3rrycrmv5df54mfgvi where someone had trouble connecting and the lights would just flash alternating on the GB module. A replacement module fixed this for him, mine do the same thing. I actually have a 2nd GB module I could test but after hours messing with my RPi image last night I'm gonna wipe and start again. I don't trust the integrity of the software at this point. I'll let you know if I make some headway. |
Well good news, I've been able to get my RPi to finally connect after 4-5 hours working on it today. More good news, I documented every step I did along the way. The bad news I don't know for sure which are the critical steps needed and it's a bit inefficient I'm sure. I'll post the steps below so if you want to at least replicate my steps and we can work on streamlining later. The first thing I did was wipe and refresh my RPi with Noobs, made sure my wifi worked and updated the default password. Then in terminal (not root unless specified)
Hope this helps and I'll update as I learn more. |
Great news! Thanks for the work Steve, I'll give it a shot and let you know. Maybe we can formalize the changes in a new repo |
I haven't had a chance to go back and test some things the last couple days but I suspect the most crucial step is 21 to 26. Many people using the GreenBean online seem to be using a mac or pc box to connect where the node-hid is supported. Thats my next test is to start fresh, install node and compile node-hid then install GE & GreenBean packages. I suspect that might do it. I won't be able to test though for several more days as my evenings are full most of this week. Good luck on your end and let me know how you turn out. |
Thanks all, and particularly Steve, for your contributions to getting this running on a Raspberry PI. I will be watching with interest and hop to test in the near future. |
I was running into the same issues, RasPi B+ Arm6 Rasbian Stretch, however I'm connecting to a GE fridge. Had some issues with node and npm versions. Ended up doing the below first then following steps 21 - 28 of Steve's awesome step by step. Install Node
Make sure Greenbean is connected and bingo! I am able to communicate with the fridge. Guessing it would be the same for any of the supported GE devices. Had some USB issues as well (cheap cable missing or broken data pair) But if its helps anyone here and the devices you should see in /dev/ hidraw0 , usb. Hope this helps someone. Dustin`` As a bit of a side note as well, i did not want to deal with having the greenbean nor the raspi sitting somewhere near the appliance, fridge in the case. As such i ran about 20' of Cat6 terminated on B both ends. Seems to work great so far. |
Tried install on a ARM Pi and Intel laptop - same result. I dug in and manually installed a bunch of dependencies (libhid and such) to see if I could get it to complete but it still petered out. At the moment there's no way to use this library, and my new green-bean is sitting there lonely.
npm install green-bean
[email protected] install /home/auser/node_modules/node-hid
prebuild-install || node-gyp rebuild
/usr/bin/env: ‘node’: No such file or directory
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:354:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-92-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/auser/node_modules/node-hid
gyp ERR! node -v v4.2.6
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open '/home/auser/package.json'
npm WARN auser No description
npm WARN auser No repository field.
npm WARN auser No README data
npm WARN auser No license field.
npm ERR! Linux 4.4.0-92-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "green-bean"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: prebuild-install || node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'prebuild-install || node-gyp rebuild'.
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 node-hid package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! prebuild-install || node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-hid
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-hid
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/auser/npm-debug.log
The text was updated successfully, but these errors were encountered: