Error logging in

[PatrikPatrik2]

I just installed the node-red-contrib-bluelinky in my Node red (home assistant) installation, using the palette (I am not sure that this is the correct way). I have a migrated Kia account. I have tried to log out and log in on the Uvo app on my phone Still I get an error in node-red

what can be the problem?

[PierreLevres]

The ‘ stamps ‘ used in BlueLinky are invalid since a few days. we need to implement a new way of getting fresh stamps every week. so keep an eye out for new releases, hopefully soon.

On 7 Jun 2021, at 22:11, PatrikPatrik2 @.***> wrote:

I just installed the node-red-contrib-bluelinky in my Node red (home assistant) installation, using the palette (I am not sure that this is the correct way). I have a migrated Kia account. I have tried to log out and log in on the Uvo app on my phone Still I get an error in node-red

what can be the problem?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/55, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO7MCG3EYPFPW63HZYSTU33TRURYBANCNFSM46IMQYDA.

[happyjaxx]

They possibly moved things around lately... former UVO app has got an update a few days ago, and they pushed out a brand new UVO V2.0.0 at the same time. (which seems to add a breakdown of energy consumption sources on trips)

Eyes peeled for an update ;-)

[PierreLevres]

A new version of bluelinky (7.3.0) was released June 8th. The stamps are now available from an external location, thus eliminating the need for a weekly release of the app with fresh stamps. So you should be able to login and close this issue.

[happyjaxx]

Yep ! it does log in now :) By politeness, I'll let @PatrikPatrik2 close the issue

[raleeSheffield]

Hi Pierre,

I still can't log in on my Node Red app. What isCan you tell me what the latest NodeRed version is - I have 0.0.24 and no updates showing?

Rachel

On Mon, 14 Jun 2021 at 10:32, PierreLevres @.***> wrote:

A new version of bluelinky (7.3.0) was released June 8th. The stamps are now available from an external location, thus eliminating the need for a weekly release of the app with fresh stamps. So you should be able to login and close this issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/55#issuecomment-860542852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5LKHTKTAF44C62ZVC6RKDTSXEELANCNFSM46IMQYDA .

-- Regards

Rachel

[PierreLevres]

What underlying bluelinky version do you have? Change to your node-red directory to verify it. You may need to update that by issuing the npm i bluelinky command. If you cant issue the npm command, then let us know what platform you are running node-red from.

Example how i updates first bluelinky on my development pi and then the node-red addon of it:

pi@rpi:~/.node-red $ npm ls bluelinky
node-red-project@0.0.1 /home/pi/.node-red
├── bluelinky@7.2.2
└─┬ node-red-contrib-bluelinky@0.0.23
  └── bluelinky@7.2.2 deduped

pi@rpi:~/.node-red $ npm i bluelinky

changed 1 package, and audited 419 packages in 8s

26 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
pi@rpi:~/.node-red $ npm i node-red-contrib-bluelinky

changed 1 package, and audited 419 packages in 7s

26 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
pi@rpi:~/.node-red $ npm ls bluelinky
node-red-project@0.0.1 /home/pi/.node-red
├── bluelinky@7.3.0
└─┬ node-red-contrib-bluelinky@0.0.24
  └── bluelinky@7.3.0 deduped

pi@rpi:~/.node-red $ 

[raleeSheffield]

Hi Pierre,

I'm using an emonpi (open energy monitor) . I can run an NPm command, but it doesn;t work (and I've never been able to make it work!) . I'm no an expert in these things, so I'm fiddling about really. I've pasted some of the output from Putty so you can see what's there. At the bottom you can see that I get a bunch of error messages when I run "npm i bluelinky" - no write access even though I've just done rpi-rw and it can;t find the right directories - I suspect the config on by emonpi is not quite what should be, though I've never changed any of it. It's always worked fine if I download the nodes directly in Node Red.

Regards Rachel

@.(ro):~$ dir avrdude-rpi emonpi node_modules phpredis backup emonupload oem_node-red postprocess backup_php.ini huawei-hilink-status oem_openHab RFM2Pi data logrotate.conf.old package-lock.json sync emonhub logrotate.old php.ini usefulscripts @.(ro):~$ dir node_modules ajv got @protobufjs asn1 har-schema psl assert-plus har-validator pump async http-cache-semantics punycode asynckit http_ece push-receiver aws4 http-signature qs aws-sign2 inherits querystring bcrypt-pbkdf isarray readable-stream bluebird is-arrayish request cacheable-request isstream request-promise caseless is-stream request-promise-core clone-response is-typedarray responselike color jsbn safe-buffer color-convert json-buffer safer-buffer color-name json-schema simple-swizzle colors json-schema-traverse @sindresorhus colorspace json-stringify-safe sshpk color-string jsprim stack-trace combined-stream keyv stealthy-require core-util-is kuler string_decoder @dabh kuvork @szmarczak dashdash lodash text-hex decompress-response logform to-readable-stream defer-to-connect long tough-cookie delayed-stream lowercase-keys triple-beam duplexer3 mime-db tunnel-agent ecc-jsbn mime-types tweetnacl enabled mimic-response @types end-of-stream ms universalify extend node-red-contrib-kuvork uri-js extsprintf node-red-contrib-sun-position url fast-deep-equal normalize-url url-parse-lax fast-json-stable-stringify oauth-sign urlsafe-base64 fast-safe-stringify once util-deprecate fecha one-time uuid fn.name p-cancelable verror forever-agent performance-now winston form-data prepend-http winston-transport getpass process-nextick-args wrappy get-stream protobufjs @.***(ro):~$ rpi-rw Filesystem is unlocked - Write access type ' rpi-ro ' to lock

@.***(rw):~$ npm i bluelinky npm WARN checkPermissions Missing write access to /home/pi/node_modules/node-red-contrib-kuvork npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field.

npm ERR! code ELOOP npm ERR! syscall access npm ERR! path /home/pi/node_modules/node-red-contrib-kuvork npm ERR! errno -40 npm ERR! ELOOP: too many symbolic links encountered, access '/home/pi/node_modules/node-red-contrib-kuvork'

npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2021-06-14T15_18_59_762Z-debug.log

On Mon, 14 Jun 2021 at 11:59, PierreLevres @.***> wrote:

What underlying bluelinky version do you have? Change to your node-red directory to verify it. You may need to update that by issuing the npm i bluelinky command. If you cant issue the npm command, then let us know what platform you are running node-red from.

Example how i updates first bluelinky on my development pi and then the node-red addon of it:

@.:~/.node-red $ npm ls bluelinky @. /home/pi/.node-red ├── @. └─┬ @. └── @.*** deduped

@.***:~/.node-red $ npm i bluelinky

changed 1 package, and audited 419 packages in 8s

26 packages are looking for funding run npm fund for details

found 0 vulnerabilities @.***:~/.node-red $ npm i node-red-contrib-bluelinky

changed 1 package, and audited 419 packages in 7s

26 packages are looking for funding run npm fund for details

found 0 vulnerabilities @.:~/.node-red $ npm ls bluelinky @. /home/pi/.node-red ├── @. └─┬ @. └── @.*** deduped

@.***:~/.node-red $

On 14 Jun 2021, at 12:33, raleeSheffield @.***> wrote:

Hi Pierre,

I still can't log in on my Node Red app. What isCan you tell me what the latest NodeRed version is - I have 0.0.24 and no updates showing?

Rachel

On Mon, 14 Jun 2021 at 10:32, PierreLevres @.***> wrote:

A new version of bluelinky (7.3.0) was released June 8th. The stamps are now available from an external location, thus eliminating the need for a weekly release of the app with fresh stamps. So you should be able to login and close this issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/55#issuecomment-860542852 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AM5LKHTKTAF44C62ZVC6RKDTSXEELANCNFSM46IMQYDA

.

-- Regards

Rachel — You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/55#issuecomment-860580186>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AO7MCGYYBCDBSD5I763QRFTTSXLHRANCNFSM46IMQYDA .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/55#issuecomment-860594441, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5LKHQCF47KQXMBFUBSWNTTSXOJFANCNFSM46IMQYDA .

-- Regards

Rachel

[PierreLevres]

Hi Rachel, from the directory listing and command you seem to be using the deprecated KUVORK implementation for Kia. Which is kind of impossible given the fact that the latest version node-red-contrib-kuvork is 0.21 and you reported using version 0.24. So the directories you are looking at probable are not the directories where node-red is run from. I'd bet my money that you are running node-red from ~/data/node-red, from what I read about emon-pi on. eg. https://community.openenergymonitor.org/t/updating-node-red-in-emonpi/6662/2

Since your case seems to be unique, we could continue to discuss this one-on-one, eg on discord. You can find me on de bluelinky server https://discord.gg/j9GBVak9 as PierreLevres (case sensitive).

[PatrikPatrik2]

I run home assistant on a raspberry pi. I have found the directory, but when i run npm i bluelinky i get this error: zsh: command not found npm

[PierreLevres]

You running homeassistant os version, not supervisor i presume. In your node red config in home assistant add the following:

npm_packages:

• @.***

It should update to the latest version of bluelinky when starting node-red.

Op 22 jun. 2021 om 21:35 heeft PatrikPatrik2 @.***> het volgende geschreven:

 I run home assistant on a raspberry pi. I have found the directory, but when i run npm i bluelinky i get this error: zsh: command not found npm

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

[PatrikPatrik2]

I get an Invalid YAML error. If i remove the space between - and * I do not get the invalid YAML error, bur when I press save I get Failed to save add-on configuration, Invalid list for option 'npm_packages' in Node-RED

[PierreLevres]

mmm... sending an email with a code in it gives very strange result in GitHub. Please enter the following code in your configuration file

[Hacksore]

This is likely improved with the latest node-red-contrib-bluelinky plugin, closing for now.