2nd car with nod red

[olivierjag2]

Describe the bug
When I add the second car in node red, my first car stop working

1rd car Kia Canada
2nd car Hyundai Canada

• Region: CA
• Brand: kia, hyundai

[Hacksore]

@olivierjag2 Did you configure two bluelinky configs for each vehicle and use them accordingly in each node?

[NellicusLabs]

I also have the same issue. I have experienced similar behavior for about 2 months just haven't got around to submitting a PR until I saw this one flash through. I am in the US region though and each of my vehicles has a separate BlueLink account.

On the offending configuration I get the following error:
"Error: Vehicle not found: REDACTEDVIN!"

[Hacksore]

@justinoreilly is it possible the case bug was related here?

Depending on how the Hyundai server was storing the VIN it could have been trying to, for example, compare the following which would fail.

VINABCD1234567890 == vinabcd1234567890

[NellicusLabs]

@Hacksore I was able to confirm the case issue with the working vehicle. Setting the VIN to lowercase caused a fail. Upon changing it back to uppercase it worked.

I attempted to do the same with the vehicle that wasn't working and it produces the same error regardless of uppercase or lowercase VIN.

Also not sure if this is related but I am unable to rename the bluelinky config node. If I attempt to change it, It reverts back to Bluelinky

[Hacksore]

Yeah looks like it's kind of related - we need to refactor a bit to support multiple vehicles in the node-red addon.

Right now there is only a single instance of bluelinky globally which is the root cause of the problem.

Closing in favor of the ticket downstream SondreNjaastad/node-red-contrib-bluelinky#62