victron-vrm-api node - invalid API token (401) for DESS, works well for other API types

Question

question

falkon asked 3 hours ago

victron-vrm-api node - invalid API token (401) for DESS, works well for other API types

Hello,

I am not sure I hit some bug in the VRP API implementation, but I am experiencing some strange behavior.

I am using `victron-vrm-api` (https://flows.nodered.org/node/victron-vrm-api) implementation to access VRM API. I configured the API token successfully, which works for 3 out of 4 API types -- for API Type = "Dynamic ESS", the response returns: 401 / "Unauthorized" / "Invalid VRM token".

The configuration is the same for these 2 'clones' of flows:

API Type: "Installations" -- this works well

API Type: Dynamic ESS -- this returns "Unauthorized" / "Invalid VRM token" error:

I have tested the API calls both when DESS was enabled and also disabled on the VRM portal -- it always returned 401 "Unauthorized"

Am I doing something wrong, or is this a problem on the VRM side?

VRM DESS vrm-api

1721142721962.png (13.1 KiB)

1721142832396.png (27.9 KiB)

1721142908005.png (40.4 KiB)

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Modifications Space

Node Red Space

Answer 1 · 2024-07-16T15:34:49Z

falkon answered · 2 hours ago

OK, I found the quirk a minute after I submitted the question...

So, for anyone possibly hitting this same issue:

- the problem was that "Dynamic ESS" requires the "VRM Portal ID" (= string in the form of, e.g., "c06......b1b") labeled as "VRM id"; while the other API types ("Installations", "Widgets") require an "Installation id" labeled as "VRM site id" (= a number you see in the URL when you look at the Dashboard of your installation in the browser).

See:

vs.

1721144078627.png (14.3 KiB)

1721144083580.png (13.9 KiB)

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

question