Unable to install about ring HOT 17 CLOSED

I'm also getting errors:

pi@raspberrypi:~ $ sudo npm i homebridge-ring-alarm
npm ERR! code 128
npm ERR! Command failed: git clone --mirror -q git://github.com/dgreif/ring-api.git /root/.npm/_cacache/tmp/git-clone-49d34a63/.git
npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-49d34a63/.git'
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-01-27T05_51_01_159Z-debug.log

appreciate any help or advice

from ring.

from ring.

Much appreciated. Will be patient in the meantime!

from ring.

@dgreif - turns out I had a pretty old version of node installed - updating to the latest seemed to solved the install issue for me.

@gadgetfreak98 maybe give that a try?

from ring.

Can you tell me what version of node you installed? When I installed an updated one yesterday, it killed everything else for me, so I went back to 8.15.0. But maybe I'm missing the steps necessary to bring all the plugins in line with an updated version? Thanks

from ring.

I just installed the latest - v11.8.0

I'm on a clean slate with just Homebridge and homebridge-ring-alarm installed.

from ring.

did you have to do anything in particular after upgrading to re-enable homebridge and the plugin, or you did it all after node upgrade?

from ring.

I removed everything using npm uninstall and then uninstall node. Installed the latest and then homebridge

from ring.

ok, yeah, that may be the way to go... unfortunately as I've messed around quite a bit. But it seems like it makes sense to have the latest greatest node...

from ring.

do i need to uninstall all the existing plugins too?

from ring.

I don't know why you would have to but I can't say for certain.

from ring.

@gadgetfreak98 any updates?

from ring.

I ended up not doing the Node update from the 8.30 version since it was indicated as being sufficiently high a version and as I was afraid to mess up all the things I had done across half a dozen plugins. Plus I had basically run out of time.

Are you still planning to look into potential issues on your end?

from ring.

I think it's specific to your setup so I'm not sure there is much for me to do at this point. Seems like there are a lot of npm install issues, but they are almost always dependent on the node/npm environment in which you are trying to install it. Sorry I can't be of more help!

from ring.

Understood. I think this will be my next weekend project. Might just start from scratch since I know much more than I did this time last week. And I have my config.json file figured out, my Nest dev account set up, etc. Hopefully would be reasonably smooth — although it’s always hard to keep track of what random bit of advice I found not the web fixed whatever little thing wasn’t quite working right...

from ring.

I started anew. Used a v11 variant of Node, but got the same error code 128. Rolled back to 10.15 of Node and still got the error. So no luck. Any ideas?

from ring.

Going to close this since I am unable to reproduce

from ring.