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 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.
A curated public compatibility list or another CSMS operator reports it. Reliable enough to plan against, not a substitute for running it.
Requires the manufacturer to act — a firmware build, an account flag or a manual unlock. Not self-serve.
Nobody has established whether SetChargingProfile reaches this hardware. Treat it as work to be scoped, not as working.
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.
