BootNotification Rejected or Pending: what it means and what to do
After every boot a charger sends BootNotification and waits for Accepted. Pending means the management system is not ready to accept it yet. Rejected means it is not accepted, for example because its identity is unknown (OCPP 1.6, §4.2, §7.38).
What it means
Until the answer is Accepted or Pending, the charger sends no other request, not even messages it cached earlier (OCPP 1.6, §4.2).
Rejected: the charger sends no OCPP message until the retry interval has passed and may close its connection. While Rejected it does not respond to the server, and the server should not send it anything (OCPP 1.6, §4.2).
Pending: neither side should close the connection. The server may read or change the charger's configuration, but RemoteStartTransaction and RemoteStopTransaction are not allowed (OCPP 1.6, §4.2).
The interval in the answer is the minimum wait before the next BootNotification. If it is 0, the charger picks its own interval, without flooding the server (OCPP 1.6, §4.2).
In OCPP 2.0.1
While Pending, the station may only send requests the server asks for with TriggerMessage, GetBaseReport or GetReport (OCPP 2.0.1, B02).
While Rejected, any message other than BootNotification gets the error SecurityError from the server (OCPP 2.0.1, B03).
Why it looks offline
The charger reaches the server, but while Pending it sends no requests unless the server asks for them with TriggerMessage, and while Rejected it sends no OCPP message at all (OCPP 1.6, §4.2).
A dashboard that counts OCPP messages therefore shows it offline.
A charger can be set to accept transactions before it is accepted. The specification warns that those transactions may never reach the server, and advises denying charging on a charger that has never been Accepted with its current settings (OCPP 1.6, §4.2.1).
Likely causes
Rejected: the server does not know the charger's identity (OCPP 1.6, §7.38), for example because the charger has not been registered yet or its ID was entered differently.
Pending: the server still wants to read or set information on the charger before it accepts it (OCPP 1.6, §4.2, §7.38).
First three checks
1.
Find the last BootNotification and the status your system returned.
2.
Compare the charger identity in the request with the one registered on your side, character by character.
3.
Pending for a long time? Check what your system still needs from the charger before it accepts it.
What to do
What to tell the customer
"Your charger is reaching us, but our system hasn't accepted it yet.
We're fixing its registration now; you don't need to do anything."
A detection rule to start from
A charger that has sent BootNotification but is still not Accepted after a time you choose: open a registration ticket with the identity, vendor and model it sent.
Sources
- Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §4.2 Boot Notification, §4.2.1 Transactions before being accepted, §5.17 Trigger Message, §7.38 RegistrationStatus; accessed 2026-10-22.
- Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). B02 Cold Boot Charging Station – Pending (B02.FR.02), B03 Cold Boot Charging Station – Rejected (B03.FR.07); accessed 2026-10-22.
Talk to us about your chargers
- Tell us about your network.
- Meet a Kinethra specialist.
- Get your chargers live on Kinethra.
- 40,000+ chargers onlineOn the Kinethra platform.
- OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
- No commission on charging revenueKinethra takes none.
We use your details to answer your request. See our Privacy Policy for details.