-
-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting
bolagnaise edited this page May 6, 2026
·
12 revisions
| Issue | Solution |
|---|---|
| No sensors appearing | Check that the integration is enabled in Settings > Devices & Services |
| Invalid API token | Verify tokens at Amber and Tesla provider (PowerSync/Teslemetry/Fleet) |
| TOU sync failing | Check Home Assistant logs for detailed error messages |
| Issue | Solution |
|---|---|
| No Tesla sites found (PowerSync) | Sign in again at https://api.powersync.cc/auth/start and paste a fresh psync_ token |
| No Tesla sites found (Fleet) | Ensure the Tesla Fleet integration is loaded and working |
| No Tesla sites found (Teslemetry) | Ensure your Tesla account is linked in Teslemetry |
| HA prompts to re-authenticate | Token was revoked or invalidated. Visit https://api.powersync.cc/auth/start, sign in again, and paste the new token into the reauth form |
psync_ token rejected as invalid |
Tokens start with psync_ followed by 43 characters. Make sure you copied the whole token from the success page |
| Live status returns wrong values | If you've moved between regions, revoking and re-authenticating will refresh the cached region |
| Issue | Solution |
|---|---|
| Cannot connect via TCP | Verify IP address — H3 Smart appears as "espressif" on your network |
| Connection test fails | Ensure inverter firmware is up to date; check port 502 is accessible |
| Model detection failed | No response from inverter — check network connectivity and slave ID (default: 247) |
| Wrong model detected | You can override the model during setup (H3-Pro vs H3 Smart) |
| Issue | Solution |
|---|---|
| Connection refused | Local Modbus access must be enabled by your installer |
| Auth fails without Device ID | Try leaving Device ID blank first — it's usually not needed. If auth fails, find it via browser dev tools (see Battery System Setup) |
| Issue | Solution |
|---|---|
| Cannot connect (UDP) | Verify IP address and that port 8899 is accessible. Ensure the WiFi dongle is online |
| Cannot connect (TCP) | Verify IP address and that port 502 is accessible. Requires a LAN dongle |
| "No battery support" error | Your inverter is a grid-only model (DT/MS/XS series) — these don't have battery control |
| Model detection failed | Check network connectivity and ensure the inverter is powered on |
| Timeout errors | WiFi dongles can be unreliable — consider a LAN dongle for more stable connections |
| Issue | Solution |
|---|---|
| Cannot connect | Check IP, port 502, slave ID. Ensure Modbus is enabled on inverter |
| Modbus conflict | Sungrow battery and AC inverter can't use the same slave ID |
| Issue | Solution |
|---|---|
| Cannot connect via Modbus | Verify IP address and port 502. Ensure Modbus TCP is enabled on the inverter |
| Curtailment not restoring | Verify Modbus write permissions are enabled on the inverter |
| Using HA entity fallback | Ensure the homeassistant-solax-modbus integration is installed and entities are available |
| Issue | Solution |
|---|---|
| Setup aborts with missing entities | Confirm the Neovolt Modbus integration is installed and exposes dispatch mode, dispatch power, dispatch duration, charge target SOC, discharge cutoff SOC, battery power, battery SOC, grid power, load, and solar sensors |
| Force charge/discharge fails | Check that the Neovolt dispatch_mode select accepts Force Charge, Force Discharge, and Normal, and that the dispatch number entities are writable |
| Backup reserve write fails | The upstream Neovolt integration must expose discharging_cutoff_soc_default or discharging_cutoff_soc; otherwise PowerSync logs the call as unsupported |
| Issue | Solution |
|---|---|
| Charger not responding | Verify the OCPP HA integration is connected and the charger is online |
| Start charging fails | Check charger state — some chargers require a specific connection state before starting |
| Repeated start/stop failures | A circuit breaker activates after 3 consecutive failures with a 5-minute cooldown |
| Issue | Solution |
|---|---|
| Prices not loading | Verify GSP region code (A-P) matches your Octopus bill |
| Wrong product | Ensure product code matches your actual tariff |
| Limited price data | Octopus publishes next-day prices after 4pm UK time |
| Saving Sessions not appearing | Check whether Direct API mode has an Octopus API key/account number, or whether the BottlecapDave entity source is selected and the source entity is updating |
| Issue | Solution |
|---|---|
| Prices are shifted or missing | Confirm the selected bidding zone matches your market and that the EPEX Predictor API has published data for the day |
| Import prices look too low | Check surcharge and tax percentage in the provider settings; both are applied on top of the day-ahead wholesale price |
| Export value is wrong | Set a fixed export rate if your feed-in tariff is fixed; leave it at 0 only if you want wholesale export valuation |
| Issue | Solution |
|---|---|
| "Missing forecast data" | Ensure price data is configured and Solcast is set up for solar forecasts |
| Schedule not updating | Tap Refresh Now in the mobile app; check logs for errors |
| Optimizer not starting | Try restarting Home Assistant; check logs for dependency errors |
| Incorrect cost during force mode | Expected — force modes use temporary rate overrides; costs recalculate when mode ends |
| Issue | Solution |
|---|---|
| Connection failed | Ensure your HA URL is correct and accessible from your phone |
| Connection timeout | Check that your phone can reach HA (same network for local URLs) |
| Invalid token | Generate a new Long-Lived Access Token and try again |
Add to your configuration.yaml:
logger:
logs:
custom_components.power_sync: debugThis enables detailed logging for all PowerSync components including optimization, battery control, and price coordination.