Phaeton documentation
Troubleshooting
Common checks for web UI access, activation, charger communication, GX discovery, and Auto mode.
Cannot Reach The Web UI
- Confirm Phaeton is running.
- Use the correct device IP address.
- Check that port 8088 is reachable.
- On Venus OS, confirm /data/rc.local exists and modifications are enabled.
Charger Does Not Connect
- Confirm the charger IP and Modbus port.
- Confirm Modbus TCP is enabled on the charger.
- Confirm the selected charger profile matches the charger.
- Review Phaeton logs for connection or decoding errors.
Auto Mode Does Not Start
- Read the Dashboard status reason first; it names setup, activation, charger, EV, schedule, SoC, grid-threshold, or solar-surplus blocking states.
- Try Manual mode at 6 A. If Manual does not start charging, debug charger-side control before Auto thresholds.
- Confirm GX integration is enabled and the GX test succeeds.
- Confirm the EV is connected according to charger status.
- Review configured current limits and battery SoC rules.
- Check whether the site has enough PV excess for the selected phase mode.
- For Alfen, confirm EMS / Active Load Balancing allows Phaeton to write maximum-current setpoints.
- For Alfen, run Test Alfen Control and confirm the setpoint is accounted for.
Capture Logs For Support
- Open Logs.
- Set the level to DEBUG.
- Clear displayed logs.
- Reproduce the Manual 6 A test, then the Auto-mode attempt.
- Select Download full log.
Information For Support
- Phaeton version.
- Platform, charger model, and charger firmware.
- Selected charger profile.
- Whether onboarding and activation are complete.
- Relevant log excerpt from the Logs page.
- Install ID if the issue is licensing related.