-
-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting
bolagnaise edited this page May 30, 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 |
| Globird tariff schedule shows the wrong period/rate | Set the correct Globird/TOU tariff in the Tesla app, remove any stale PowerSync custom tariff fallback if present, then restart Home Assistant or reload PowerSync |
| Globird exports outside the ZEROHERO/Super Export window | Set export/feed-in rates outside the Super Export window to 0c in the Tesla or PowerSync tariff, then reload PowerSync. Keep only the boosted Super Export window positive unless you deliberately want low-rate battery export |
| 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 says SolarEdge host is required | Enter the inverter IP address, or enter an HA entity prefix for entity fallback |
| Setup cannot connect | Enable Modbus TCP and active-power control in SetApp or the LCD menu. Also check port 502, slave ID, firmware support, and grid profile permissions |
| Entity fallback is not found | Confirm the SolarEdge Modbus HA integration exposes a writable active power limit number entity, then enter the prefix used by that entity |
| Battery level or live-flow data is unavailable | Confirm Home Assistant exposes SolarEdge battery/site telemetry entities such as battery state of energy/charge, battery power, grid power, and solar power. PowerSync reads these from HA entities; direct Modbus curtailment alone is not enough to create battery telemetry |
| Force charge/discharge fails with missing control entities | Confirm Home Assistant exposes writable SolarEdge storage-control entities for control mode, command mode, charge power limit, and discharge power limit. Telemetry can work without these entities, but dispatch cannot |
| Backup reserve or Hold SOC fails | Confirm the SolarEdge integration exposes a writable backup reserve or minimum SOC number. Without it, Hold SOC falls back to best-effort command idle only when the dispatch controls are present |
| Curtailment triggers but export continues | Some SolarEdge firmware/grid profiles reject power-control writes. Check Home Assistant logs for write failures and confirm installer permissions |
| 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 |
One stack stays at 0% SOC or unavailable
|
The upstream Neovolt integration has lost that inverter's Modbus session. Recover the EW11A/Modbus connection or reload the Neovolt entry before expecting PowerSync to balance the stacks |
Higher-SOC stack is set to No Battery Charge
|
Expected on independent stacks without BMS coordination. PowerSync parks the higher-SOC stack while force-charging the lower-SOC stack until the SOC gap is inside the configured tolerance |
| 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 a supported solar forecast source is available, such as Solcast or Open-Meteo Solar Forecast |
| 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 |
| Globird optimizer plans grid charge during a known peak window | Check sensor.power_sync_tariff_schedule. If it does not match the Tesla app tariff for the current time, reload PowerSync or restart Home Assistant so the Tesla tariff baseline is refreshed |
| Profit Max has little effect on Globird | Check the export price forecast. Profit Max needs a positive Super Export window and 0c export outside it; a flat low FiT across the day gives the LP no clear special window to target |
| 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.