Authorization error

[nnoally]

Got an error when connecting to EU server (hyndai brand): error: @EuropeController.login: sign in with EuropeanBrandAuthStrategy failed with error Error: @EuropeanBrandAuthStrategy.login: Cannot find the argument userId in https://prd.eu-ccapi.hyundai.com:8080/web/v1/user/integration/auth

Relates to : https://github.com/Hacksore/bluelinky/issues/199 Seems to be fixed with latest bluelinky version.

[HanschDennis]

Hi, did you try to reinstall the bluelinky (not node-red-contrib-bluelinky!) node module (e.g. npm uninstall bluelinky)? My Hyundai is also in europe and it's working at the moment.

[Boxana]

Hi there, "node-red-contrib-bluelinky" doesn't work for me anymore. I can no longer log in (erro). Already removed it from NOde Red and re-added it again with no success. Can someone please help me? It went well for weeks. I use version 0.27.

[HanschDennis]

@Boxana did you remove the bluelinky module as well? I had to do it manually, it is not enough to only reinstall "node-red-contrib-bluelinky"

[Boxana]

Hi there, it's working again. Did it as written above with "npm uninstall bluelinky" then reinstalled with "npm install bluelinky". then removed "node-red-contrib-bluelinky" and set it up again. finally restarted and now it works again. I'm using an Openhabian as (how do you say that) patform. When installing came the following. "openhabian@openhab:~ $ sudo npm install bluelinky npm WARN saveError ENOENT: no such file or directory, open '/home/openhabian/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/openhabian/package.json' npm WARN openhabian No description npm WARN openhabian No repository field. npm WARN openhabian No README data npm WARN openhabian No license field.

• bluelinky@7.6.4 added 1 package from 1 contributor and audited 187 packages in 5,013s

4 packages are looking for funding run npm fund for details

found 0 vulnerabilities " Unfortunately I don't know exactly what I'm doing there. Can someone please take a look? Greeting Christian

[PierreLevres]

Hi there, it's working again. Did it as written above with "npm uninstall bluelinky" then reinstalled with "npm install bluelinky". ...... sudo npm install bluelinky.... Unfortunately I don't know exactly what I'm doing there. Can someone please take a look? Greeting Christian

What do you mean you don't know what you are doing? I see you issuing an npm install, and issuing a sudo npm install Generally sudo-ing "npm install" is a bad idea, since it installs in a directory only alterable for the root user.

[hessijames79]

After having the same problem and reinstalling node-red-contrib-bluelinky which updated bluelinky to 7.6.4 it worked again but failed after about 20 minutes. After some hours it worked again.

In 7.6.3 the stamp interval was set to 15 minutes, in 7.6.4 to 4 hours.

[Boxana]

it takes about 13 minutes for me, then the registration fails. if node red is restarted it works again for the same time. can it be the same thing?

[PierreLevres]

Same here 12 minutes... and it starts to fail..

[Boxana]

After having the same problem and reinstalling node-red-contrib-bluelinky which updated bluelinky to 7.6.4 it worked again but failed after about 20 minutes. After some hours it worked again.

In 7.6.3 the stamp interval was set to 15 minutes, in 7.6.4 to 4 hours.

that matches mine. After about 12 minutes, the registration is canceled. restarting node red fixes it for about 12 minutes. Also a full deploy fixes it for about 12 min. if you wait 4 hours then it automatically goes back about 12 minutes without doing anything. do you already have a solution?

[HanschDennis]

@Boxana Did you try updating to bluelinky 7.6.5?

[PierreLevres]

@Boxana Did you try updating to bluelinky 7.6.5?

I did, and indeed, seems fixed. Running well for two hours now ...

[nnoally]

@Boxana Did you try updating to bluelinky 7.6.5?

I did, and indeed, seems fixed. Running well for two hours now ...

Yes same for me.

[Boxana]

Thanks for this hint, I've overlooked :-(). It looks like it's working now. I have a completely different, unusual question. Since I'm not familiar with github at all. I am very grateful that there are people here who spend their free time with projects like this. I have set up a donation there and wonder if you can also increase the 1€. I can't find an option to do that. I don't take it for granted that you get such support. A hint would be nice.

[Helavi]

Hello, I really read all your comments carefully but still can't recognize what's the final solution is for the problem. What is meant with updating to 7.6.5? What do I have to do exactly? The version of node-red-contrib-bluelinky is 0.0.27, what's the other version 7.6.5 about?

[Boxana]

I uninstalled bluelinky in node red and then added it back. then the installation will automatically get the current version on Bluelinky. I did it this way because the directory structure in Openhabian is different than an installation with a standalone node red. everything is working again at the moment.

node-red-contrib-bluelinky has not changed but the program Bluelinky. node-red-contrib-bluelinky accesses it. I hope I explained that correctly 😅

[Helavi]

Thanks for the explanation, I did the same and first it seems to work, I got all the status information out of the car. But only some minutes later nothing happened any more, there is still the status "ready" shown beneath the "Get full status" node, but injection doesn't cause any output in the debug node. I am running node-red on a raspberry.

[Helavi]

After node-red-restart it is not possible to get a connection, message below bluelinky nodes say since minutes: "Logging in....."

[Boxana]

I have the same problem since I wrote you how I did it. Before that it ran about 3 hours.

[PierreLevres]

Same here. "Logging in” message for a long long time. Has been running perfectly a long time. Restart of node-red does not help. Logon node does not help. Stamps generated: "2022-02-10T16:03:59.510Z” ==> 17:03 my time…. So 24 minutes old. Still puzzled.

Bluelinky 7.6.5.

On 10 Feb 2022, at 17:14, Boxana @.***> wrote:

I have the same problem since I wrote you how I did it. Before that it ran about 3 hours.

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

[raleeSheffield]

I've had same issue for a few days now...

On Thu, 10 Feb 2022, 16:28 PierreLevres, @.***> wrote:

Same here. "Logging in” message for a long long time. Has been running perfectly a long time. Restart of node-red does not help. Logon node does not help. Stamps generated: "2022-02-10T16:03:59.510Z” ==> 17:03 my time…. So 24 minutes old. Still puzzled.

Bluelinky 7.6.5.

On 10 Feb 2022, at 17:14, Boxana @.***> wrote:

I have the same problem since I wrote you how I did it. Before that it ran about 3 hours.

— Reply to this email directly, view it on GitHub < https://github.com/SondreNjaastad/node-red-contrib-bluelinky/issues/64#issuecomment-1035111026>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AO7MCGY6AMAWE5LLX55CPYTU2PQAFANCNFSM5N3ZB3DA . 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/64#issuecomment-1035127508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5LKHTM5D6RLWCX4UXCHFLU2PRSJANCNFSM5N3ZB3DA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.*** .com>

[Helavi]

Hi, mine is running for more than 1 day stable, don't know why, I've change nothing, but in's nice!

[Vitani]

How do you uninstall a node that is in-use? The pallete manager won't let me (I'm using Node-RED in Home Assistant, if that makes any difference)

[PierreLevres]

How do you uninstall a node that is in-use? The pallete manager won't let me (I'm using Node-RED in Home Assistant, if that makes any difference)

Export the flows that contains the nodes (or export all of them) Delete the flows Delete the configuration node Remove the palette node-red-contrib-bluelinky Restart node-red Install the palette node-red-contrib-bluelinky, it will then install latest version of bluelinky as well Import the exported flows Redeploy

[Vitani]

I had to restart Node-RED between removing & installing the node, but otherwise that worked perfectly, thank-you @PierreLevres !

[PierreLevres]

I had to restart Node-RED between removing & installing the node, but otherwise that worked perfectly, thank-you @PierreLevres !

I updated the procedure, and submitted a PR for the readme

[binderth]

Since a few days I get an "error" for all my (previous functioning) flows:

You all are posting those logfiles - how can I reach them?

[Hacksore]

I have not following this issue much but if there is a continuing issue please raise a new one.