Worked once... about node-red-contrib-bluelinky

[PierreLevres]

'Ready' merely means that a valid connection with the underlying bluelinky is active.
Tips:

1. You might want to try the 'login' node when the node doest not return anything. If it works well after a login or restart of node red, problem could be in the stamps used.
2. You might want to try the 'car-fullstatus' node
3. You can debug with only the bluelinky ts code thus pinpointing the problem to bluelinky or node-red

Could you check the versions of node-red-contrib-bluelinky and bluelinky in your node-red/node_modules folders.
Latest should be:
node-red-contrib-bluelinky = 0.0.28
bluelinky = 7.6.6

What are your versions? What car brand, car type and region ? Does your app work fine with the same credentials?

[wabiloo]

Hi @PierreLevres, I'll try your tips, but in the meantime:

node-red-contrib-bluelinky = 0.0.27 (installed from within Node-Red palette management; I don't se a 0.0.28 in the tags here either)
bluelinky = 7.6.6

Car brand = Kia e-Niro EV
Region = Europe
App (Kia Connect) works with same credentials = True

Regarding the login node, is it meant to be used in the workflow? If so, how? The status node does not seem to timeout, so I am not quite sure how I could have a logic of the sort "if timeout then login and try again"...

[Hacksore]

You can enable LOG_LEVEL=debug in your node-red settings.js file when using home assistant and the node-red addon.

hassio-addons/addon-node-red#879
https://github.com/hassio-addons/addon-node-red/blob/main/node-red/DOCS.md#time-zone-configuration

Otherwise, start node-red with the env var set like this LOG_LEVEL=debug node-red if not using HA.

[wabiloo]

I've not really done anything, but it seems to be working now. I've set the frequency of polling to 30 minutes.
Is there maybe something in the bluelinky code that "protects" against flooding? (although my initial tests were still minutes apart)

[Hacksore]

Probably related to rate limiting, gonna close this for now.