Repository navigation
Troubleshooting
This page covers the most common problems and their solutions. If your issue is not listed here, please open a GitHub issue.
- Ensure your charger is on the same network/VLAN as Home Assistant. Zeroconf/mDNS discovery does not work across VLANs without an mDNS repeater.
- Try adding the integration manually via Settings → Devices & Services → + Add Integration → OpenEVSE and entering the charger's IP address directly.
- Confirm the charger is powered on and its WiFi LED is stable (not flashing).
- Verify the IP address or hostname is correct. Try opening
http://openevse.local(or the IP) in a browser. - If the charger has HTTP authentication enabled, make sure you've entered the correct username and password.
- Check if the charger is reachable via
ping openevse.localfrom the Home Assistant host. - If using HTTPS, ensure your SSL certificate is installed on the charger first.
- Check that the integration shows a device in Settings → Devices & Services → OpenEVSE.
- Check Home Assistant logs for errors: Settings → System → Logs, filter by
openevse.
Entities with a firmware version requirement will show as Unavailable (not just hidden) if the charger firmware is too old. Check the Controller Firmware sensor to see your current version and compare it against the firmware requirements table.
- Certain sensors (e.g., solar/shaper diagnostics) only have values when the relevant feature is active.
- The charger may not have reported a value yet — wait for the next coordinator poll or trigger a manual refresh.
- Check Home Assistant logs for
Non-numeric statewarnings which may indicate a configuration mismatch.
- The GitHub API may be rate-limiting requests (60/hour unauthenticated). Add a GitHub Personal Access Token to increase the limit to 5,000/hour.
- Trigger a manual check with
homeassistant.update_entity.
Services such as set_rfid_user, delete_rfid_user, and get_rfid_users require specific firmware versions. The service will log a warning if the firmware version check fails. Upgrade the charger firmware to the required version.
These limit types require a Vehicle SoC sensor or Vehicle Range sensor to be configured in the integration options. The charger needs to receive current vehicle data to enforce these limits.
Go to Settings → Devices & Services → OpenEVSE → Configure and set the appropriate external sensor.
- Ensure you are targeting the correct entity or device ID in your service call.
- Another claim with higher priority may be overriding yours. Use
openevse.list_claimsto inspect all active claims.
- Verify the Grid Sensor or Solar Sensor is configured and reporting valid values.
- The integration pushes sensor data to the charger on state changes. If your power sensor updates infrequently, data pushed to the charger may be stale.
- Confirm the charger's Min Amps setting allows the divert algorithm enough headroom to operate.
- Ensure firmware is 4.0.0+ (check the Controller Firmware sensor).
- The pairing mode has a timeout — scan your card immediately after pressing the button.
- Confirm the RFID Access switch is ON.
- The tag must be registered on the charger. Use
openevse.get_rfid_usersto check registered tags.
Firmware 5.1.0+ introduces advisory notifications on the charger. The integration automatically surfaces these in Home Assistant:
- Repairs Dashboard: When an active advisory notification is detected, an issue is automatically created under Settings → System → Repairs.
-
Acknowledging Notifications: You can click into the repair issue and acknowledge (mute) the notification directly within Home Assistant, or call the
openevse.acknowledge_notificationservice with the notification ID. -
Notification Sensors: You can track total active advisories and overall severity with
sensor.openevse_notification_countandsensor.openevse_notification_severity.
When filing a bug report, please include:
- Integration version (from HACS or the GitHub release tag)
- Home Assistant version
- OpenEVSE firmware version (from the Controller Firmware sensor)
-
Home Assistant logs filtered to
openevse - Diagnostics download from Settings → Devices & Services → OpenEVSE → Download Diagnostics