Get details about a user's specific heat pump
Get the heat pump related to a specific user under a specific organization.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID of the user's organization
The user ID of the user whom the heat pump belongs to
The ID of the specified heat pump
Query Parameters
If true, includes soft-deleted
Response
OK
ok, warning, error, unknown ok, warning, error, unknown ok, warning, error, unknown The device's console health tone, and the only verdict a client should render: action_required when a partner-resolvable action is pending, else the worst of connection and monitoring, with not_steered for a healthy device nobody optimizes. Do not re-derive it from connection_status/monitoring_status/steering_status — those three are cue-blind and would report a device asking for reauthentication as healthy. The status filter on GET /org/{org_id}/devices and the tone counts on …/devices/summary grade the three statuses only, so a device with a pending action reads action_required here while being counted and filtered under its status tone.
good, warning, critical, not_steered Why actual_steering_state reads the way it does, from a closed set. unknown covers both a pump no evaluation has judged yet and one whose internal reason is outside the published set; no manufacturer error text is ever carried here.
no_schedule, missing_price_data, coverage_not_price_backed, no_commands, too_few_commands, retries_in_progress, no_critical_calls, commands_failed, commands_successful, physical_compliance_degraded, physical_compliance_low, physical_compliance_healthy, steering_permission_not_granted, subscription_required, non_steerable, no_blocker, unknown When the current pair of desired and observed steering states started — whichever of the two changed last. Null until at least one of them has been recorded. It is a start time, not a last-checked time: an evaluation that finds nothing changed leaves it where it was.
How many mode changes this pump's schedule called for over the last 24 hours. Zero means the plan asked for nothing, which is what tells an idle pump apart from one that was asked to act and did not.
Where this device sits in the same eight-value vocabulary the customer status uses, so a device and its owner read in one language. Unlike tone it keeps the communication and steering bands apart and separates an open ticket from an action the partner must take.
disabled, communication-error, steering-error, actions-required, troubleshooting, communication-warning, steering-warning, normal Whether the platform is doing what it should for this pump, component by component, and where the problem starts when it is not. Every cell is a reading of state the evaluators already recorded, so a cell nothing has observed reads not_measured rather than a guess.
Deprecated — use GET /org/{org_id}/notifications/status for per-device-type counts, or GET /org/{org_id}/notifications/actions?device_id=… for the specifics. True when at least one action is pending against this device and the partner must take that action before the device can resume normal operation.
AT, AT_HOURLY, BE, CH, EE, DE_LU, HR, HU, IE_SEM, IT_CNOR, IT_CSUD, IT_NORD, IT_PUN, IT_SARD, IT_SICI, IT_SUD, PT, RO, SE_1, SE_2, SE_3, SE_4, UK 20When set, the device is considered deleted.
25530010010010Overrides the temperature change amount when steering the device for slight changes. For example, from MIN to LOW. Disclaimer: this depends on the integration support for overrides.
Overrides the temperature change amount when steering the device for significant changes. For example, from MIN to MAX. Disclaimer: this depends on the integration support for overrides.
URL to embeddable onboarding form
Base URL for authorizing with the Podero server
Deprecated — use GET /org/{org_id}/notifications/status or GET /org/{org_id}/notifications/information?device_id=…. True when the device has at least one unread information notification for the owner.
Deprecated — use GET /org/{org_id}/notifications/actions?device_id=… instead. Pending actions the partner can take on this device. Each item carries a code discriminator that determines its remaining fields — different action codes can use different resolution mechanisms (URL flow, webhook, in-band command, ...). Empty when nothing is pending.
Action requiring the partner to reauthenticate the user against an upstream provider.
Once more action codes are introduced, expose them as sibling classes (e.g.
FooAction with code: Literal["foo"]) and combine them into a discriminated
union (Annotated[ReauthenticateAction | FooAction, Field(discriminator="code")])
so OpenAPI consumers can branch on code to select the right shape.
- ReauthenticateProjection
- InformationActionProjection
- SocInputRequestedProjection
