-
-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting
bolagnaise edited this page Feb 13, 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 Teslemetry/Tesla Fleet |
| TOU sync failing | Check Home Assistant logs for detailed error messages |
| Issue | Solution |
|---|---|
| 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 |
| 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 | 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 |
|---|---|
| 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.