[HOW TO] CLI install method

Firewall is now deactivated, Antivirus tool, too.
“Incorrect header check” - like yesterday

“Incorrect header check” suggests that either the archive file that is generated (and which contains the app code) is invalid, or there’s an issue with the HTTP response compression. Both issues are very strange (but I don’t use Windows so don’t know if it’s a generic Windows issue, or it has something to do with your specific setup).

My homey is Brand new and nearly blank. Only some Apps are installated, no flows are created…

So maybe, i think there is an incompatibility between Mapulo Devolo App - and homey firmware version. Github file is older…

Did anyone have a idea? Maybe i will ask Mapulo…

I think CLI installation issue is solved for the Moment.

Thanks for you help, Folks!

install homey failed :crazy_face:

did you try the examples as mentioned before in this tread?
see [HOW TO] CLI install method and before

I tryed that, and my npm version is 6.14.2,node is 12.16.1, but it still doesn`t work…

Hi!
I’m new in the command line and tried to install the devolo app from mapulu.

Can someone tell me, what I can do:

Also tried the examples above, but there’s always the same errors.

Edit: Homey node.js version is: 12.16.1 and I downloaded 12.18.3

Thanks!

Looks like you’re using a proxy or a firewall that’s blocking access to the NPM repository.

Thanks @robertklep it was my firewall. I had to uninstall…

Now it worked untill I want to install the devolo app:

I unpacked the files to the desktop. What could be wrong?? Do I have to rename the file, or type the name of the file in the cmd?

grafik

thanks!

… now i got it…

didn’t type cd cm.decolo-alpha…

Hi all,

I think something whent wrong somewhere. Getting this message.
What could be wrong?

Already installed it, but didn’t work so i removed it and installed it again.

Please follow the exact instructions from the first post. The correct command is:

npm install -g homey

Thanks, worked now!

Hi @robertklep,
I suppose you use a Mac, too, right?
The CLI method and also the use of the terminal is new to me, but according to the information here, it should not be a problem. It shouldn’t be a problem… But…

The installation of node.js (v. 14.8.0) worked without problems.
But when I execute the command npm install -g homey I get some error messages because I don’t have the necessary write permissions. But I am logged in as admin. What can I do?
I use macOS Catalina v. 10.15.6 (should this be relevant).

If you’re installing a module as admin, you need to add the --unsafe-perms flag:

npm install -g --unsafe-perms homey

Many thanks for the quick feedback.
I get the same error messages.

npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/local/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! [Error: EACCES: permission denied, access '/usr/local/lib/node_modules'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/local/lib/node_modules'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running

Oh wait, you wrote “But I am logged in as admin”, and I assumed that you ran the npm command with sudo, but I guess you’re running it as a regular user (that also happens to be an admin).

In that case, the best solution would be to change the ownership of the global node_modules directory to your user id:

sudo chown -R $USER /usr/local/lib/node_modules

After that, you should be install to install global modules as a regular (admin) user (and you don’t need --unsafe-perm).

At least that’s what I thought.

Something has changed, but I still don’t seem to have write access, at least not to the named files.

Dirks-MacBook-Pro:~ goebeldi$ npm install -g homey
npm ERR! code EACCES
npm ERR! syscall symlink
npm ERR! path ../lib/node_modules/homey/bin/homey.js
npm ERR! dest /usr/local/bin/homey
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, symlink '../lib/node_modules/homey/bin/homey.js' -> '/usr/local/bin/homey'
npm ERR!  [OperationalError: EACCES: permission denied, symlink '../lib/node_modules/homey/bin/homey.js' -> '/usr/local/bin/homey'] {
npm ERR!   cause: [Error: EACCES: permission denied, symlink '../lib/node_modules/homey/bin/homey.js' -> '/usr/local/bin/homey'] {
npm ERR!     errno: -13,
npm ERR!     code: 'EACCES',
npm ERR!     syscall: 'symlink',
npm ERR!     path: '../lib/node_modules/homey/bin/homey.js',
npm ERR!     dest: '/usr/local/bin/homey'
npm ERR!   },
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'symlink',
npm ERR!   path: '../lib/node_modules/homey/bin/homey.js',
npm ERR!   dest: '/usr/local/bin/homey'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/goebeldi/.npm/_logs/2020-08-19T08_30_29_752Z-debug.log

Do you use also Catalina v10.15 (or higher)?
I found this link on the official nodejs.org. If I understand it correctly, there are some problems with Catalina and node.js, right? However, the topics “programming” and “node.js” are a new world for me with lots of question marks. When you know what I mean.

Ah, you may have to change the ownership of /usr/local/bin as well:

sudo chown -R $USER /usr/local/bin

I don’t use Catalina because of all the “enhancements” that are making life for users and developers much worse.

1 Like