This page covers which fields to surface for each device type and how to keep data fresh. All device data is returned from the standard GET endpoint — there is no separate state endpoint.
Four fields cover all energy movement in the system:
Field
Unit
Sign convention
Description
current_solar_production_w
W
Always positive
Solar panel output
household_consumption_w
W
Always positive
Total household power use
battery_charge_discharge_power_w
W
Positive = discharging, negative = charging
Battery power flow
current_power_to_grid_w
W
Positive = exporting, negative = importing
Grid exchange
Current battery level is in battery_charge_level_percent (0–100%).The solar_surplus_w field gives the same value pre-calculated, or derive it as current_solar_production_w - household_consumption_w.All inverter state is timestamped in current_state_last_updated_at.
Two fields indicate whether a device needs attention:is_authenticated — false means the manufacturer connection has lapsed. The user needs to reconnect their device. Check the actions array for a resolution_link URL to redirect them to.action_needed — true when the actions array contains one or more unresolved items. Inspect actions[].code to determine the type and actions[].resolution_link for how to resolve it.
Device state updates every 5–15 minutes depending on the manufacturer’s API. A 30-second stale time works well for device lists — refetch in the background when data becomes stale and provide a manual pull-to-refresh.For EV detail views, poll every ~3 seconds while boost_state === 'requested' to catch the transition to 'ongoing'. Return to standard background refetches once the boost is underway.
The Podero API does not provide a WebSocket or push mechanism. All state updates require polling.
