@nygma2004 Did you manage to get RemoteStartTransaction working?
No, I did not. Honestly I was waiting for some suggestion on what I have done wrong, or what how should I try different.
And unfortunately I am not able to VPN into the place were it is installed, so can't test right now.
Thats what I use to schedule start/stop for charging my car.
Sorry I still haven't tidied up my flows (they are a working mess, intertwined with cron scheduling from 30 min block electrickery rates from octopus agile) - you are welcome to a copy of what I have (but only via DM - as they need tidy up work before being presented as usable to a passer-by on the forum)
3 Likes
Yes please Steve.
I'm not too bothered about the octopus agile stuff, but I'd like to see how you've structured your commands that interact with your charger.
As my charger is solar compatible, I'm wanting to divert exported solar power to the charger.
I'm using Monta at the moment, which works fine for normal charging, but it performs poorly when diverting solar. Monta tech support haven't been much use...
ok, since @Paul-Reed and @nygma2004 have asked, I took a little time to tidy up the flows.
Nodes used:
- "node-red-contrib-ocpp": "1.3.6" (or greater) (required)
- "node-red-contrib-cron-plus": "2.1.0" (or greater) (required for scheduling)
- "@sammachin/node-red-matter-bridge": "0.12.0" (or greater) (optional matter device - for "hey google/alexa/siri, turn the ev charger on"
- "@flowfuse/node-red-dashboard": "1.22.1" (or greater) (optional, for dashboard control)
The dashboard looks like this:
Flows: evse-demo.json (105.0 KB)
3 Likes
Thanks a lot, this is very helpful, although I think tried the same myself.
From your flow, I copied over these 3 nodes to test the simple GetDiagnostics request.
All I did is replaced the configuration on the CS request JSON node to my Charge Box ID. When I deploy the flow I see this:
I triggered the inject node, and I see this:
Why is this happening? This is why I got stuck with RemoteStartTransaction as well, because nothing seems to be executed.
And I am pretty sure the ID is correct, because I see that in the Heartbeat message in the debugger:
And the configuration is like this:
What am I missing here?
Hey! I’ve been looking into OCPP integration in Node-RED too, and yeah... it’s definitely not super straightforward out of the box.
I came across a few community nodes like node-red-contrib-ocpp but they seem either outdated or not actively maintained. What worked best for me was using a WebSocket client node in combination with some custom logic to handle the OCPP JSON messages manually. It’s a bit more hands-on, but you get more control that way.
You’ll probably need to mimic the heartbeat, boot notification, and other standard messages depending on if you're simulating a charge point or managing a backend.
If anyone’s got a more plug-and-play approach or a node that’s currently maintained, I’d love to hear about it too!
2 Likes
I will try to give the occp nodes a try, it worked for Steve so I am hopeful. I just started a holiday now, so this has to wait a bit.
