Skip to content
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

nodejs v11 seems to break pigpio #1

Open
l8gravely opened this issue Oct 31, 2018 · 6 comments
Open

nodejs v11 seems to break pigpio #1

l8gravely opened this issue Oct 31, 2018 · 6 comments

Comments

@l8gravely
Copy link

Having a heck of a time installing nodejs according to the instructions, which seems to boil down to node v11.0.0 being installed, which causes pigpio to not get installed properly for some reason. Can you confirm on your setup which version of node you have installed?

Now trying to fall back to basic Raspbian, without any npm or node installed. Then will try to move up and get it all installed again.

@l8gravely
Copy link
Author

Well after a bunch of poking around, I finally got it to install. I had to do a whole bunch of stuff.

The real trick turned out to be:

sudo npm install node@v10
sudo npm install --unsafe-perm --verbose -g node-gyp
cd drawbot
npm install pigpio

I couldn't install it globally, etc. It was a total pain. Once I get another PI Zero, I'll try to actually document the steps I had to take. Also, the latest version of nodejs is now v11.0.0, so maybe updating the instructions to force the tested version for the install would be better?

Thanks for the software, it's now running and I'll be able to test my wiring better now.

@mcbriers
Copy link

Hi John

It has been ages, but have you found a working solution? I am somewhat stumped, although I am not surprised since I am a Pi-diot

@l8gravely
Copy link
Author

Sorry, I haven't touched this project in quite a while, been distracted with ATTiny85 hacking lately. Did you try my "npm install node@v10' trick? I'll have to see if I can fire up my PiZero again and see what the status really is these days. It might also be that newer versions of node have fixed this issue.

John

@mcbriers
Copy link

I doubt newer versions fixed it, as I ran into startup troubles using the documented step by step. It is then that I started looking around, and found your issue. Thanks anyway, it was worth a shot. Now I'll just fox-terrier it.

Stay safe!
Capture

@ronaldmyers4
Copy link

The Cannot read property 'botID' of undefined error is caused by an errant comma on line 36 of the config.json file. The code works when the comma is removed.

@mcbriers
Copy link

Yes! That was it! Now the code runs like a charm. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants