Electronic Technical Report issued on: 08/01/2026
⚠️ SAFETY WARNING / ELECTRICAL RISK. This device is directly connected to the 230V/400V electrical grid. Before any physical inspection or removal of the charging module (Chargeberry), it is mandatory to disconnect the power supply by operating the dedicated miniature circuit breaker/residual current device in the main electrical panel. Any electrical work involves a serious risk of electric shock and must be performed exclusively by a qualified technician. ReeFix provides this diagnosis for informational purposes only.
For an effective diagnosis, especially in more advanced stages, the following are required:
This phase focuses on software and configuration issues, which account for most cases of smart charging failure or OCPP errors.
1.1. OCPP configuration error or invalid credentials (Probability: 45%)
Key signals: The Easee One does not start scheduled charging via app or external backend. The wallbox appears "Disconnected" or "Offline" in the Easee portal or CPO logs, even though manual charging works. This indicates a block in authenticated communication with the OCPP server.
Analysis: The OCPP protocol requires a secure "handshake" and authentication. If the endpoint URL, Charge Point ID, or authentication credentials are incorrect, the connection will not be established. This is a common error during initial setup or CPO change.
Quick checks (for experienced user/technician):
wss://ocpp.yourserver.com/) and the Charge Point ID.Preliminary operational decision: If the OCPP parameters are incorrect or the credentials are invalid, correcting this data via the Easee portal or Installer app is the first step. This operation requires specific technical skills and access to CPO credentials.
1.2. Firmware/software conflict or time synchronization issues (Probability: 15%)
Key signals: The wallbox is connected to the OCPP backend, but smart charging commands are rejected or not executed. CPO logs may show errors such as "CallError" or "Rejected" in response to SetChargingProfile commands. Smart scheduling via the native Easee app may conflict with a third-party service.
Analysis: Outdated or corrupted firmware can destabilize the wallbox's OCPP client. Time synchronization (NTP) is crucial for validating OCPP messages and TLS certificates; desynchronization can cause secure communication failures. Conflicts can also arise with HEMS systems or third-party services that send unsupported charging profiles or profiles that conflict with Easee settings.
Quick checks (for experienced user/technician):
Preliminary operational decision: If firmware issues or software conflicts are suspected, proceed with firmware updates and temporary deactivation of external services. This operation can be performed by an experienced user but requires attention to avoid further complications.
This phase addresses issues related to the quality and stability of the internet connection, often more complex to diagnose without specific tools.
2.1. Network connectivity instability (WiFi/Cellular) or firewall blocks (Probability: 35%)
Key signals: The Easee One disconnects and reconnects to the backend intermittently. Smart charging works sporadically or with significant delays. Sometimes the wallbox appears online, other times offline. This often happens when the radio signal is weak or the home network has restrictive configurations (firewall, DNS).
Analysis: The Easee One requires a stable internet connection (integrated eSIM or WiFi) to communicate via secure WebSockets (wss://). A weak signal (e.g., RSSI worse than -90 dBm for cellular or unstable WiFi) can cause TCP/IP socket interruptions, preventing the exchange of critical messages. Firewalls or routers with incorrectly configured DNS can also block traffic on ports 443 (HTTPS/WSS) or other CPO-specific ports.
Quick checks (for technician):
Safety notes: Any intervention on network configuration or firmware must be performed with caution. Errors can compromise the security and functionality of the device.
Preliminary operational decision: Network connectivity issues require in-depth diagnosis with specific tools and advanced skills. It is strongly recommended to contact a network specialist for resolution. Only in extremely rare cases, and after ruling out all other causes, should the replacement of a hardware component such as the Easee Chargeberry Control Unit be considered.
Operational decisions should be guided by the probability of causes and the complexity of the intervention.
If the Easee One is always "Disconnected" or does not connect to the OCPP backend at all (Cause 1.1, 45%):
If the Easee One connects and disconnects intermittently, or smart charging is unreliable (Cause 2.1, 35%):
If the Easee One is connected, but smart commands are rejected or there are conflicts (Cause 1.2, 15%):
Operational decision: If the Easee One does not connect to the CPO or smart charging is unstable, contact a technician for an in-depth analysis of the OCPP configuration and network connectivity. If the problem persists after basic software checks and firmware updates, consider a more in-depth analysis by Easee support.