-
-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting
bolagnaise edited this page Apr 10, 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 base64url characters. Make sure you copied the whole token from the success page |
| Live status returns wrong values for one Powerwall | The PowerSync proxy auto-detects your Tesla region (NA / EU). 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 registers responded — 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 (Modbus) | Modbus TCP Server 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 DT/MS/XS series (grid-only) — 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 | Check register 0xB5 (factory limit) is readable. Verify Modbus write permissions |
| Using HA entity fallback | Ensure the homeassistant-solax-modbus integration is installed and entities are available |
| 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 state (e.g. connected_waiting) 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 |
| 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 |
| scipy not available | The greedy fallback still works; try restarting HA to trigger scipy install |
| Incorrect cost during force mode | Expected — force modes use fake tariff rates; 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.