Register an app at developer.tesla.com.
Set the redirect URI to /api/auth/callback.
Required scopes: energy_device_data energy_cmds offline_access.
After saving credentials, register this app with Tesla’s API (one-time, server-wide). Required before any user can discover their Powerwall sites.
These settings apply server-wide. Social sign-in IDs are updated in-memory immediately but the source of truth is Azure App Settings — set them there too for persistence across restarts.
📊 Application Insights
The connection string is normally set as the Azure App Setting
APPINSIGHTS_CONNECTION_STRING and picked up automatically.
Use this field only to override with a different resource.
🔑 Social Sign-In Client IDs
Changes here take effect immediately in-memory. To persist across app restarts, also set
the corresponding Azure App Setting: GOOGLE_CLIENT_ID, GOOGLE_IOS_CLIENT_ID,
MICROSOFT_CLIENT_ID, APPLE_CLIENT_ID.
These tools fix up historical IOG kWh figures for days where the automation wasn’t running. Tesla import (for solar/grid/battery history) is available to each user directly in their Settings page.
Copy each day’s EV kWh into IOG kWh for historical days where IOG data is missing.
Only days with iog_kwh = 0 and ev_kwh > 0 are updated — existing IOG data is never overwritten.
Use this if EV kWh history is unavailable. Enter how many kWh you typically charge per IOG session
(e.g. 30 kWh for a 7.4 kW charger over ~4 h). Sets iog_kwh for every historical day where it is currently 0.
Existing IOG data is never overwritten.