Last Alert Codes, Definitions and Action | Nayax Energy
The Last Alerts report in Nayax Energy Core displays the alerts related to EV chargers and Nayax devices. Learn how to efficiently manage EV Last Alerts to understand and identify the cause of a malfunction.
General
While electric vehicle charging technology is remarkably reliable, occasional alerts and error messages are a normal part of ownership and most issues can be resolved in minutes without calling support.
What causes EV charger error codes?
Electric vehicle chargers monitor dozens of safety parameters in real-time, from ground faults and temperature spikes to communication errors and power supply issues. When something falls outside normal operating range, your charger generates an alert code to protect both your vehicle and the charging equipment.
Most charging problems stem from just a handful of causes: tripped breakers, loose connections, ground fault issues, or temporary communication glitches. With the right knowledge, you can diagnose and resolve up to 80% of charger errors yourself saving time, money, and the frustration.
CONNECTIVITY & COMMUNICATION
|
Code |
Event Name |
Description |
Recommended Action |
|
991014 |
MQTT Connected |
The device is successfully receiving data from the server. |
No action required. |
|
991013 |
MQTT Not Connected |
The device is unable to receive data from the server. |
Check connectivity and network configuration. |
|
96 |
IP/DNS Connection Established |
Connection to IP/DNS was successfully established. |
No action required. |
|
22 |
No Charge Point Communication |
Internet communication with the charge point was lost. |
|
|
10 |
Charger Communication Error |
Communication between charger and device was lost. |
Restart the charge point. If the issue persists, contact support. |
|
23 |
Vehicle Communication Failure |
Communication between the charger and the vehicle was lost. |
Restart the charge point and ensure the cable is fully inserted. Contact support if unresolved. |
|
21 |
BLE Device Connected |
Communication between AMIT and BLE device established. |
No action required. |
|
22 |
BLE Device Disconnected |
Communication between AMIT and BLE device was lost. |
|
|
109 |
Low RSSI Signal |
Signal strength below threshold (RSSI < 10). |
Contact support. |
OCPP PROTOCOL
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
30
|
Boot Notification
|
Charge point was reset.
|
No action required.
|
|
38
|
Boot Notification Failed
|
Charger boot notification failed to reach the backend.
|
Contact support.
|
|
36
|
OCPP Authorize
|
OCPP authorization request processed.
|
No action required.
|
|
40
|
OCPP Server Error
|
An error was received from a third-party OCPP server.
|
Contact support.
|
|
501
|
WebSocket Closed (Heartbeat Missing)
|
OCPP connection closed due to missing heartbeat.
|
Perform a hard reset.
|
|
502
|
WebSocket Lost
|
OCPP server connection lost.
|
Perform a hard reset.
|
|
503
|
WebSocket Exit
|
WebSocket session exited unexpectedly.
|
Perform a hard reset.
|
|
504
|
WebSocket Error
|
Error detected in OCPP WebSocket connection.
|
Contact support.
|
|
510
|
Undefined Serial Number
|
WebSocket opened with undefined charger serial number.
|
Verify charger configuration.
|
|
511
|
WebSocket Connected
|
OCPP server connection established successfully.
|
No action required.
|
|
701
|
Remote Start Transaction
|
Remote command to start charging executed.
|
No action required.
|
|
702
|
Remote Stop Transaction
|
Remote command to stop charging executed.
|
No action required.
|
|
703
|
Reset Charge Station
|
Remote reset command executed.
|
No action required.
|
|
704
|
Change Availability
|
Charger availability status updated remotely.
|
No action required.
|
|
705
|
Unlock Connector
|
Connector unlock command executed.
|
No action required.
|
|
711
|
Get Configuration
|
Full configuration data retrieved from the charge point.
|
No action required.
|
|
712
|
Trigger Message
|
OCPP trigger message sent.
|
No action required.
|
|
714
|
Change Configuration
|
Charger configuration updated.
|
No action required.
|
|
715
|
Data Transfer
|
OCPP data transfer message processed.
|
No action required.
|
CHARGING SESSION MANAGEMENT
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
33
|
Start Transaction
|
Charging session started successfully.
|
No action required.
|
|
34
|
Stop Transaction
|
Charging session stopped.
|
No action required.
|
|
4081
|
Start Charging Failed
|
Charger failed to initiate charging.
|
Contact support.
|
|
31
|
Charger Status Update
|
Charger operational state update (Available, Preparing, Charging, Suspended EV, Suspended EVSE, Finishing, Reserved, Unavailable, Faulted).
|
If status is Faulted, contact support.
|
|
720
|
Set Current (Active Session)
|
Charging current adjusted for active session.
|
No action required.
|
|
721
|
Set Charging Profile
|
Charging profile applied to the charger.
|
No action required.
|
|
890
|
Charging Station Stop
|
Session Stopped as Authorization Amount Reached
|
No action required.
|
|
13
|
EV Telemetry
|
EV telemetry event recorded.
|
No action required.
|
CONNECTOR STATUS
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
14
|
Connector 1 Plugged In
|
Connector 1 (left) was plugged in.
|
No action required.
|
|
17
|
Connector 1 Unplugged
|
Connector 1 (left) was unplugged.
|
No action required.
|
|
15
|
Connector 2 Plugged In
|
Connector 2 (right) was plugged in.
|
No action required.
|
|
18
|
Connector 2 Unplugged
|
Connector 2 (right) was unplugged.
|
No action required.
|
|
16
|
Connector Plug In
|
Connector was plugged into the vehicle.
|
No action required.
|
|
19
|
Connector Plug Out
|
Connector was unplugged from the vehicle.
|
No action required.
|
PAYMENT & AUTHORIZATION
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
770
|
Card Type Not Supported
|
The device is not allowed to bill this type of card.
|
Verify that both the operator and the charge point support this payment method.
|
|
996
|
EMV Not Supported
|
The billing provider does not support EMV transactions.
|
Contact support.
|
|
18
|
Transaction Cancelled
|
Transaction was cancelled for an unknown reason.
|
Contact support.
|
|
29
|
Negative Prepaid Card Balance
|
The prepaid card balance is negative.
|
Go to Cards > Select Card > Change Credit, add credit, and confirm.
|
|
1
|
RFID Card Not Recognized
|
RFID card is not registered in the system.
|
Register the card using the decimal number shown in the event data.
|
|
2
|
RFID Card Blocked
|
RFID card is expired or inactive.
|
Go to Consumers > Cards and update the card status.
|
|
842
|
Card Not Allowed (Group Restriction)
|
Card usage restricted by charge point group configuration.
|
Go to Consumers > Cards and enable the relevant charge point group under limits.
|
|
1
|
AAC Report – Pre Authorization
|
Card reader failed to properly read the card.
|
Resend the Card Readers configuration to the charging station.
|
|
520
|
Account Billing Failed
|
Billing attempt failed for the account.
|
Add or update credit card details under the EV account.
|
|
521
|
Add Credit Card Failed
|
Failed to add a credit card to the account.
|
Retry or contact support.
|
ELECTRICAL & SAFETY
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
7
|
Leakage Current (RCD) Detected
|
Leakage current detected. Charging stopped. The EVSE will retry after 1 minute, up to 5 times.
|
Contact support.
|
|
4
|
High Temperature
|
Internal EVSE temperature exceeded 85°C. Charging will resume once temperature drops below 85°C.
|
Contact support.
|
|
6
|
High Voltage / Improper Grounding
|
Voltage exceeded ~270V (15% over nominal). Charging pauses until voltage normalizes.
|
Contact support.
|
|
12
|
Low Voltage
|
Low voltage detected, commonly during single-phase connection or charging.
|
Monitor power supply conditions.
|
|
11
|
Missing Phase
|
One electrical phase is missing.
|
Inspect power supply if persistent.
|
|
20
|
Ground Failure
|
Protective Earth (PE) wire is not connected.
|
Requires a qualified electrician to inspect PE wiring.
|
|
24
|
Relay B Failure – Single Phase Mode
|
Relay connecting phases 2 and 3 failed. Charging continues on one phase only.
|
Contact support.
|
|
8
|
Relay Malfunction
|
Internal relay malfunction detected (may be stuck open or closed).
|
Contact support.
|
SYSTEM & DEVICE MANAGEMENT
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
1
|
Application Restarted
|
Android application was restarted.
|
No action required.
|
|
31
|
Reboot
|
Device rebooted. If firmware was sent, it will be downloaded after boot.
|
Monitor device status post-reboot.
|
|
5
|
Remote Restart
|
Remote restart command executed.
|
No action required.
|
|
24
|
Charge Point Power Up
|
Charge point powered up.
|
No action required.
|
|
2
|
Door Open Event
|
EV meter back board was opened.
|
Inspect for unauthorized access if unexpected.
|
|
26
|
Reader State Error
|
Card reader fault detected; reset often resolves the issue.
|
1. Reset the charge point. 2. Contact support if unresolved.
|
|
135
|
POS Unexpected Failure
|
POS failure detected; device will reset automatically.
|
1. Reset the charge point. 2. Contact support if unresolved.
|
|
9
|
General Alert
|
General system alert reported.
|
Contact support for investigation.
|
FIRMWARE & CONFIGURATION
|
Code
|
Event Name
|
Description
|
Recommended Action
|
|
750
|
Firmware Version Mismatch
|
Main firmware version does not match the POS version.
|
Resend the firmware update to the device.
|
|
110
|
Firmware Update Successful
|
Firmware update completed successfully.
|
No action required.
|
|
713
|
Update Firmware
|
Firmware update command sent to the charger.
|
Monitor update progress.
|
|
803
|
FTP Download Completed
|
File download from the FTP server to the device completed successfully.
|
No action required.
|
|
601
|
DLM Configuration Missing
|
Board limitation configuration missing for Dynamic Load Management.
|
Verify DLM configuration.
|
Did you find this article helpful?