Skip to content

feat(wui): Add extended fields to /api/v1/status#5229

Open
packerlschupfer wants to merge 1 commit intoprusa3d:masterfrom
packerlschupfer:pr/extended-status
Open

feat(wui): Add extended fields to /api/v1/status#5229
packerlschupfer wants to merge 1 commit intoprusa3d:masterfrom
packerlschupfer:pr/extended-status

Conversation

@packerlschupfer
Copy link
Copy Markdown

Summary

Add commonly needed telemetry fields to the /api/v1/status printer object that are already available in marlin_vars but missing from the local PrusaLink API.

New fields

Field Type Description
temp_heatbreak float Heatbreak temperature [°C]
target_heatbreak float Heatbreak target temperature [°C]
print_fan_speed int Print fan PWM value (0-255)
job_id int Current print job ID
print_duration int Print time [ms]
time_to_end int Estimated remaining time [s] (only during print)
progress int Print completion (0-100%)

Motivation

These fields are already exposed through Prusa Connect telemetry but missing from the local API, forcing local integrations (Home Assistant, custom dashboards) to either use the cloud API or poll multiple endpoints. This is a simple addition with no breaking changes.

Test plan

  • GET /api/v1/status returns new fields while idle
  • time_to_end appears only during active print
  • progress updates during print
  • No regressions on existing fields

Add commonly needed telemetry fields to the PrusaLink v1 status
endpoint, reducing the need for additional API calls:

- temp_heatbreak / target_heatbreak: heatbreak temperature and target
- print_fan_speed: print fan PWM value (0-255)
- job_id: current print job ID
- print_duration: print time in milliseconds
- time_to_end: estimated remaining time in seconds (only during print)
- progress: print completion percentage (0-100)

These fields are already available in marlin_vars and exposed through
the Connect telemetry, but were missing from the local PrusaLink API.
Adding them enables local dashboards and Home Assistant integrations
to display print progress without polling multiple endpoints.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant