VRM API stuck on ‘Connecting to VRM API’

Node-RED
, , ,
1

Hello,

I am trying to retrieve solar forecasts from VRM API and having the same issue as here:

  • Here is what I get (stuck forever):

image

image
image506×711 16.6 KB

  • The thing is, it can’t purely be my internet connection because I can easily retrieve the info via a python script from my PC using the same internet connection;
import requests
import json

url = f"https://vrmapi.victronenergy.com/v2/installations/..../stats?type=custom&attributeCodes%5B%5D=solar_yield_forecast&interval=hours"

headers = {
    'X-Authorization': f"Token xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    'Content-Type': 'application/json'
}

print(requests.get(url, headers=headers))

  • I am able to retrieve info via requests fine to other APIs (even SolCast)

  • I have tried a normal request node to the VRM API and get a “No response from server”

    image

image
image513×635 16.7 KB

Not sure where I am going wrong, or what to try next.

I have a workaround by using SolCast but then I have a severely limited number of requests per day and would much rather use the VRM info.

Many Thanks

2

I have only recently fixed this issue. I found that it worked when connected to starlink internet but not my home fiber. After hours of chat GPT (which wasn’t much help) I turned off PPPoE in my router. Internet still works and that fixed the connecting to vrm issue.

Edit: I have no idea why that fixed it and im not smart enough to know what to do if your ISP requires PPPoE

3

Thanks Josh,

My ISP uses VLAN ID, not PPPoE but I have a Starlink lying around so I thought why not…

Lo and behold, success

image
image1050×145 5.99 KB

But this seems bizarre, there must be something that the VRM API server doesn’t like about some internet connections?

Running it from a starlink won’t work long term for me, so I am still looking for a solution but this does narrow the problem down and confirms it isn’t a config issue in Node Red.

4

Bump. Perhaps someone like @dfaber can comment?

The fact that I can easily access the API elsewhere on my network from other machines would suggest there is an issue specific to the security or protocols on the Cerbo GX / Node-Red side and combination of some specific router configuration or internet policy.

Summary:

  • :cross_mark: Cannot access/connect to VRM API from Node-Red on my Cerbo GX using my standard Fibre internet (Spark New Zealand)
  • :white_check_mark: Can access/connect to VRM API from Node-Red on my Cerbo GX using Starlink (although this is not a viable fix for me)
  • :white_check_mark: Can access/connect to VRM API from any other machine (with Python HTTP requests) using my standard Fibre internet (Spark New Zealand)
  • My standard Fibre internet (Spark New Zealand) is not using PPPoE (thus the suggested fix by josh1 doesn’t apply to me)
  • I have tried opening up my router security as much as I can see (I may have missed something) but still no success.

Many thanks,

Lawrence

5

Well, I have found a workaround, but it again reinforces there is a problem with the VRM API Node.

So I have uploaded my python script and am just calling directly with an Exec node and it works totally fine:

image
image965×142 11.3 KB

image

So it does indeed run on the Cerbo GX (even with the same suspect internet connection), and something about the native Node-Red and/or VRM API node itself is causing the problem.

6

I am having the same issue with my VRM API nodes. Has been working fine since October 2025 when Victron tech assisted and forced IPv4 for my HTTP call.

Can Victron assist again Dirk @dfaber ??

Also in NZ, and have just updated Cerbo to lastest firmware, and selected the IPv4 check box on my VRM API config node.

VRM API node status message showing “Connecting to VRM API” and getting status: undefined in verbose message from node.

Addtional info, using curl from command prompt gives proper response, returning data.

7

Hi Larry, I’m also in NZ and having the same issue.

My VRM API nodes were working and I was using them to assist with scheduling charging and feedin based on VRM forecasts… The VRM API stays in the ‘connecting to VRM’ mode, but using the same HTTP string in command prompt using curl returns the data. Clearly not related to my connection per se, but some some combination of the VRM API node and my connection. I have looked into disabling PPPoE in my router, but it appears my wireless router (2-degrees) doesn’t have this. I have also tried through my phone hotspot with the same issue. Any more information you can provide would be helpful. Cheers, David

8

Hi David,

Nothing much else I can really add except for that it still isn’t working.

My python script to pull information via the API is behaving ok, but I really hope that someone from Victron can investigate why the API Node isn’t working.

It definitely points to a Venus/NodeRed software issue considering it works from a python script (but doesn’t work as a VRM API Node) running on the same hardware/network. I don’t have enough knowledge on networks or packets etc to talk at that level.

Cheers,

Larry