Zynetic
Talk to salesRequest a demo

Command Palette

Search for a command to run...

Inside the CPMS

OCPP — Open Charge Point Protocol. How your chargers connect to the CPMS.

Not a separate product. OCPP is the language your chargers and our CPMS share: 1.6, 2.0.1 and 2.1, spoken natively over secure WebSockets.

OCPP 1.6 · 2.0.1 · 2.1OCPI compliantDedicated microserviceWatchtower · KnightwatchAny compliant OEM · AC/DC

Outcomes, with names attached

What it does for your network.

Your chargers stay available.
Watchtower probes the quiet ones, Knightwatch pages you when a site drops, Flap Tracker flags the unstable, before a customer finds a dead connector.
WatchtowerKnightwatchFlap Tracker
Fix more from your office.
Restart, unlock, reconfigure and change availability remotely, one charger or your whole infrastructure. Send an engineer for hardware, not routine recoveries.
RemoteResetUnlockBulk ops
Buy chargers on merit.
This OCPP-compliant CPMS speaks OCPP 1.6, 2.0.1 and 2.1, so you mix manufacturers as price and performance change, never as a contract dictates.
1.62.0.12.1Multi-OEM
Proof, not opinions.
When a customer, host or partner disputes a session, you open the message trail: the exact Authorize, Start, MeterValues and Stop frames.
Live streamHistorical store

Connect · Control · Protect

Connect, control and protect your chargers.

One connection layer, three jobs: keeping every charger online, obedient and watched — OCPP charging software doing all three at once.

01

Connect.
Every charger, always on the line.
  • Always-on secure WebSocket sessions
  • Boot, heartbeat and registration handling
  • StatusNotification and MeterValues ingestion
  • Multi-tenant OCPP endpoints
  • OCPI for partner networks

02

Control.
Commands that arrive, and prove it.
  • RemoteStart and RemoteStop
  • Reset, unlock, change availability
  • Configuration get and set
  • Diagnostics and firmware instructions
  • Charging profiles for site power limits
  • Bulk actions across charge points

03

Protect.
Six monitors on duty, around the clock.
  • Watchtower
    Probes your silent chargers.
  • Knightwatch
    Pages you when a site drops.
  • Session Monitor
    Guards live sessions.
  • Overstay Monitor
    Clears held connectors.
  • Charger Error Monitor
    Acts on serious faults.
  • Flap Tracker
    Proves the network problem.

Why a separate service

The connection layer is isolated by design.

A thousand chargers reconnecting after a network blip should never be your team's problem too.

Scales independently.
Charger connections never compete with console load.
No one gets logged out.
A connection-layer restart never touches your team's session.
Isolated end to end.
Your organisation's endpoints are yours alone.
Runs in your region.
Deployable wherever your policy requires it.
Zynetic CPMSWhere your business runs.TariffsWalletsAppsAnalyticsReportsWatchtowerKnightwatchSessionOverstayErrorFlapCommandsLive data1Prices & commands go down.Tariff rules & remote actions leave the CPMS.4Truth comes back.Verified session + meter truth for billing.OCPP connection layerDedicated serviceMessage storeAlways-on WSSSpeaks OCPPSpeaks businessOCPIPartner networks2Translated to OCPP.1.6 / 2.0.1 / 2.1 over secure WebSockets.3Chargers report live.Status, heartbeats and metered energy, stored.Down the wire.Remote actions arrive asRemoteStart, Reset and profiles.Back with proof.Stored, searchable andsession-correlated for billing.AC · 7.4 kWAC · 11 kWAC · 22 kWDC · 60 kWDC · 120 kWDC · 150 kW240 kWHub · 240 kW

The specifics

The OCPP capability sheet.

OCPP 1.6, 2.0.1 charging software — versions, messages, commands and where it all runs, pinned down in one place.

Protocol and transport.
OCPP versions
1.6, 2.0.1 and 2.1 available; version negotiated per charge point.
Transport
Secure WebSocket (WSS) with TLS; per-charger credentials.
Messages and retention.
Core messages
BootNotification, Heartbeat, StatusNotification, Authorize, Start/StopTransaction, MeterValues.
Message retention
Live stream plus historical store, searchable and session-correlated.
Control and operations.
Remote commands
RemoteStart, RemoteStop, Reset, UnlockConnector, ChangeAvailability, Change/GetConfiguration, TriggerMessage.
Firmware and diagnostics
UpdateFirmware and GetDiagnostics where your hardware supports them.
Smart charging
Charging profiles and composite schedules for site-level power limits.
Bulk operations
Commands issued across a group of charge points in one action.
Deployment.
Deployment
Our cloud, a dedicated in-region environment, or your own infrastructure.

The platform

Explore the other modules.

The CPMS.
The console the whole business runs on.
Explore
Native Android and iOS app.
Your customers charge under your brand.
Explore
Host Portal.
Site owners see their numbers and set their price.
Explore
Fleet Portal.
Fleets run wallets, RFID caps and reports.
Explore
Maintenance.
Four journeys from fault to fixed.
Explore
Operations App.
The engineer app for the Maintenance module.
Explore
OCPI roaming.
Your chargers on partner apps.
Explore
Integrations.
Hardware, payments and your systems.
Explore

Questions

Frequently asked questions.

The OCPP protocol is the connection layer of the CPMS rather than a separate product. If you have an unusual architecture in mind, talk to us. We are honest about fit.

Next step

Send us one charger and a firmware version.

We will connect it, run a paid session end to end, and show you your own message trail.

  • Demo on your data, not ours
  • Honest answers, including when it is no
  • We reply within one business day

We reply within one business day · Singapore · Dubai · Abu Dhabi