Speaks OCPP 1.6J, which Flowion speaks too — so the compatibility question is answered by the protocol. What follows is the part that actually costs you an afternoon: how this box lets you change its CSMS URL, and exactly what is and is not established about it.
The charging station opens its own WebSocket to Flowion. You configure the CSMS URL on the device and it speaks OCPP to us with nothing in between.
Connects and runs. For OCPP-direct devices this follows from the protocol: the station speaks a version Flowion speaks. Check the evidence grade for who established that.
The manufacturer's own documentation states the OCPP support and provisioning path cited.
Set in the manufacturer's cloud portal. You cannot type a URL into the box; the vendor pushes the setting to it.
SetChargingProfile reaches this hardware on this path, so Flowion's load balancing can actuate it.
The station talks only to its manufacturer's cloud, which relays OCPP to us. Each vendor's relay has its own onboarding, authentication and capability rules, so every one of these needs an integration built before it works.
Not supported today. Either the vendor integration has not been built, or the device's own path to a third-party CSMS is unclear or being withdrawn.
The manufacturer's own documentation states the OCPP support and provisioning path cited.
Onboarded programmatically through the manufacturer's own API, usually with per-station credentials issued by them.
SetChargingProfile does not reach the hardware on this path, so Flowion cannot load-balance this charger. Anything sold as dynamic load balancing does not apply here.
Status: not started.
Researched 2026-08-12. This entry is a starting point, not a guarantee: confirm the exact SKU and firmware before you commit to a fleet of them.
No rip and replace. Point your existing chargers at your organization's URL — and when the hardware isn't in the room, the simulator is.
