Introduction
This guide explains the EVSE communication status codes shown in the Communication section at EVSE level in Fuuse. These codes help you understand whether a charger connection was closed normally, dropped unexpectedly, or ended because of an error. Use this article to quickly identify whether action is needed or whether the code is harmless.
What the suffix letters mean
Some codes include a letter suffix that shows which side closed the connection:
C = the connection was closed by the charger
M = the connection was closed by the middleware, meaning the OCPP server or Fuuse side
Communication status codes
| Code | Meaning | Action needed |
|---|---|---|
| 4000-M | The charger opened a new connection, so the old one was closed. This is normal behaviour. | No action needed |
| 1000-M | Disconnected by an operator, or closed because there was no activity from the charger. | Usually no action needed unless it happens repeatedly |
| 1000-C | The charger closed the connection normally. | No action needed |
| 1001-C | The charger is going away, usually because it is rebooting or shutting down. | Check the charger if this was not expected |
| 1006-C | The connection dropped without a proper close, usually because of a network or power loss on the charger side. | Investigate charger power and network connectivity |
| 1009-M | The charger sent a message that is too large. | Check the charger configuration or contact support if it continues |
| 1002-M / 1007-M | The charger sent an invalid WebSocket frame. | Investigate charger firmware or communication settings |
| 1011-M | An internal error occurred on the Fuuse side while processing a message. | Contact Fuuse support |
When to take action
Some codes are part of normal charger behaviour and do not require any action. These include 4000-M, 1000-C, and usually 1000-M when it happens occasionally. In these cases, the connection ended cleanly or was replaced by a new one.
You should take action when the code suggests a problem with the charger, its network, or its power supply. Examples include 1001-C, 1006-C, 1009-M, and 1002-M / 1007-M. If these codes appear often, they may point to a recurring connectivity or device issue.
When to contact support
Contact Fuuse support if you see repeated disconnects, unexpected 1011-M errors, or any code that continues after you have checked the charger, network, and power supply. When you contact support, include the EVSE name, the code shown, and the time the issue occurred. This helps the support team investigate more quickly.