No joy. Same error:
8 Apr 18:48:11 - [error] [http request:A random name] no response from server
No joy. Same error:
8 Apr 18:48:11 - [error] [http request:A random name] no response from server
most odd.
Everything looks normal (node-red installation / setup wise).
And I dont see the same rst
- this suggests something else (external to node-red) is going on.
One last check: what does npm ls -g got
reveal?
/usr/lib
└─┬ node-red@4.0.9
└─┬ @node-red/nodes@4.0.9
└── got@12.6.1
Do you have another SD card that you can install RPiOS & Node-red on to see if it works with a fresh installation?
Does it make any difference if you use the existing Pi on a different network (eg phone hotspot)?
I have tested the flow on another Raspberry Pi which is running Victron's Venus OS. It works. Here is the system info:
{
"report": "diagnostics",
"scope": "basic",
"time": {
"utc": "Tue, 08 Apr 2025 20:39:29 GMT",
"local": "4/9/2025, 8:39:29 AM"
},
"intl": {
"locale": "en-US",
"timeZone": "Pacific/Auckland"
},
"nodejs": {
"version": "v18.20.3",
"arch": "arm",
"platform": "linux",
"memoryUsage": {
"rss": 115806208,
"heapTotal": 50757632,
"heapUsed": 35713452,
"external": 4747760,
"arrayBuffers": 635613
}
},
"os": {
"wsl": false,
"totalmem": 1961508864,
"freemem": 1605591040,
"arch": "arm",
"loadavg": [
0.2,
0.2,
0.24
],
"platform": "linux",
"release": "5.10.110-rpi-venus-4",
"type": "Linux",
"uptime": 759370.35,
"version": "#1 SMP Tue Jan 28 14:19:25 UTC 2025"
},
"runtime": {
"version": "3.1.10",
"isStarted": true,
"flows": {
"state": "start",
"started": true
},
"modules": {
"node-red": "3.1.10",
"@victronenergy/node-red-contrib-victron": "1.5.23",
"node-red-dashboard": "3.6.5",
"victron-vrm-api": "0.2.10"
},
"settings": {
"available": true,
"apiMaxLength": "UNSET",
"disableEditor": false,
"contextStorage": {},
"debugMaxLength": 1000,
"editorTheme": {
"palette": {},
"projects": {
"enabled": false,
"workflow": {
"mode": "manual"
}
},
"codeEditor": {
"lib": "ace",
"options": {
"theme": "vs"
}
}
},
"flowFile": "flows.json",
"mqttReconnectTime": 15000,
"serialReconnectTime": 15000,
"socketReconnectTime": "UNSET",
"socketTimeout": "UNSET",
"tcpMsgQueueSize": "UNSET",
"inboundWebSocketTimeout": "UNSET",
"runtimeState": "UNSET",
"adminAuth": "SET",
"httpAdminRoot": "/",
"httpAdminCors": "UNSET",
"httpNodeAuth": "UNSET",
"httpNodeRoot": "/",
"httpNodeCors": "UNSET",
"httpStatic": "UNSET",
"httpStaticRoot": "UNSET",
"httpStaticCors": "UNSET",
"uiHost": "SET",
"uiPort": "SET",
"userDir": "SET",
"nodesDir": "UNSET"
}
}
}
This machine is on the same network but is running different versions of nodejs, node red and OS. So maybe I will try different versions of nodejs and/or node red on the problematic machine.
Downgraded nodejs to version v18.20.8. Node red version still v4.0.9. Flow now works.