Is Victron intending to add OCPP 2.x protocol support to the EV chargers?

[langestefan (Stefan de Lange)]

@BartChampagne

You’re still missing the point.
Yes, OCPP is an Open protocol. So is Modbus.

No, I think you are. OCPP is a standard. Modbus is a communication protocol. My alfen also speaks modbus, yet it can’t communicate with the GX. Guess why? Because it’s not a standard!

@BartChampagne

You’re ranting at Victron for not implementing an OCPP server for your convenience, while they have no business case to do so but they offer you an equally open alternative - that you’re refusing.

Which I have already said multiple times does not meet my requirements. The end goal here is getting the charger into DESS. Which is impossible in the current situation.

@BartChampagne

Turning your charger into e-waste?
That’s just BS.

Nope. If I have to buy the victron charger to get my EV into DESS, then that turns my alfen into e-waste.

@BartChampagne

There’s the Node Red OCPP implementation and both Victron and Alfen support the open Modbus protocol so nothing and nobody is stopping you from integrating them.

Read this again:

@langestefan

@BartChampagne

With the Node Red OCPP solution, a lot can be done by the user.
If the Victron solution doesn’t fit your needs, you can always build your own interface - that’s how an open system works.

Yes, but not this. There is no virtual EV charger node and in another thread I read that victron has no interest in adding that either.

@BartChampagne

The solution to your problem is Modbus.

Modbus is nothing. It does not specify anything. It does not do anything. You might as well have said, the solution to your problem is HTTP. Great, so I have 4 wheels and no engine and no steering wheel. Let’s go!