Trying to log in Node JS - Invalid Token


#1

When trying to log in to homey in Node JS I copy and paste the token i got from http://go.athom.com/cli-login , but it only replyes Invalid Token please try again.

Anyone who knows what to do?


#2

Same here. Both on Win and MacOS.


#3

Same here - to 1.5.13-rc.11 from Windows 10


#4

Athom is aware of the issue, and is going to look into it as soon as possible.


#5

The problem can be resolved by installing the newest version (2.1.83)


#6

I can not find 2.1.83


#7

The version with the fix is 2.1.38. typo by Jeroen :slight_smile:

Run npm i -g athom-cli to get the latest version.


#9

Trying to update it i get theese errors… I am not aware of any restrictions in filesystem…

828 verbose argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” “install” “athom-api”
829 verbose node v10.11.0
830 verbose npm v6.4.1
831 error path C:\Program Files\nodejs\node_modules.staging
832 error code EPERM
833 error errno -4048
834 error syscall mkdir
835 error Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs\node_modules.staging’
835 error { [Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs\node_modules.staging’]
835 error cause:
835 error { Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs\node_modules.staging’
835 error errno: -4048,
835 error code: ‘EPERM’,
835 error syscall: ‘mkdir’,
835 error path: ‘C:\Program Files\nodejs\node_modules\.staging’ },
835 error stack:
835 error ‘Error: EPERM: operation not permitted, mkdir ‘C:\Program Files\nodejs\node_modules\.staging’’,
835 error errno: -4048,
835 error code: ‘EPERM’,
835 error syscall: ‘mkdir’,
835 error path: ‘C:\Program Files\nodejs\node_modules\.staging’ }
836 error The operation was rejected by your operating system.
836 error It’s possible that the file was already in use (by a text editor or antivirus),
836 error or that you lack permissions to access it.
836 error
836 error If you believe this might be a permissions issue, please double-check the
836 error permissions of the file and its containing directories, or try running
836 error the command again as root/Administrator (though this is not recommended).


#10

That works. Thx.