search

angeloxx / homebridge-vantage

Homebridge driver for Vantage Controls
3 stars 14 forks source link

Can't Install #1

Closed geofbuck closed 7 years ago

geofbuck commented 7 years ago

Tried to install from NPM but just kicks out error:

Darwin 13.4.0 npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge-vantage" npm ERR! node v6.9.4 npm ERR! npm v3.10.10 npm ERR! code E404

npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/sprint-fs npm ERR! 404 npm ERR! 404 'sprint-fs' is not in the npm registry.

Help?

angeloxx commented 7 years ago

I'm sorry, there're some mistakes that should be fixed. This week I plan to update the project and the package in the npm repository so please wait few days. I'll update this ticket when package installation works properly.

angeloxx commented 7 years ago

Last version of package (0.0.9) corrects that issue; in the next days I'll start again the development (currently paused to continue with homebridge-myhome project) and implement more functions.

geofbuck commented 7 years ago

Thanks so much! Can't wait to try it.

geofbuck commented 7 years ago

Hmm I can't find package 0.0.9. Where is it located?

angeloxx commented 7 years ago

npm will find it for you: https://www.npmjs.com/package/homebridge-vantage

elbugs commented 7 years ago

Hello I'm trying to install too but I got this error, can you help me to solve it? captura de pantalla 2017-05-04 a las 17 58 06 I'm using latest Mac OS X. Thanks.

angeloxx commented 7 years ago

Retry with the lastest version AND please don't use a closed issue.

elbugs commented 7 years ago

Thanks for the update. I did it and now installs without problem. Before your reply I just deleted the dependency of sleep module in index.js and I got one load showing in the terminal but never was shown in the home app. Now, I'm in the same step. The system stops when it loads the first load, a DMX load. Could this kind of load be an issue? I'll test tomorrow to delete the DMX loads I have and try to run the plugin again and post an update. If meanwhile you have any idea, you can check the issue I opened few hours ago.

El 5 may 2017, a las 21:34, angeloxx notifications@github.com escribió:

Retry with the lastest version AND please don't use a closed issue.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.