opencode/decisions.yaml
This commit is contained in:
@@ -332,4 +332,25 @@ notes:
|
|||||||
- sensor.octoprint_filament_monthly
|
- sensor.octoprint_filament_monthly
|
||||||
integrations:
|
integrations:
|
||||||
- octoprint
|
- octoprint
|
||||||
|
status: superseded
|
||||||
|
superseded_by: 2026-08-14-octoprint-printjobhistory-set-to-2
|
||||||
|
- id: 2026-08-14-octoprint-printjobhistory-set-to-2
|
||||||
|
date: 2026-08-14
|
||||||
|
title: OctoPrint PrintJobHistory set to capture all jobs (not just successful)
|
||||||
|
decision: OctoPrint's PrintJobHistory plugin is set to capture ALL jobs (success +
|
||||||
|
failed/cancelled), not "success jobs only". Failed/cancelled prints are now recorded
|
||||||
|
so their filament usage flows into sensor.octoprint_filament_used_total and the
|
||||||
|
daily/weekly/monthly filament meters. Do not revert to success-only.
|
||||||
|
rationale: With "capture successful jobs only", cancelled/failed prints (e.g. 2026-08-14
|
||||||
|
11:09 and 16:32) never entered OctoPrint's history, so no filament usage reached HA
|
||||||
|
at all — the gap was OctoPrint-side, not an HA integration issue.
|
||||||
|
Sensor.octoprint_filament_used_total only updates on prints OctoPrint records.
|
||||||
|
entities:
|
||||||
|
- sensor.octoprint_filament_used_total
|
||||||
|
- sensor.octoprint_filament_daily
|
||||||
|
- sensor.octoprint_filament_weekly
|
||||||
|
- sensor.octoprint_filament_monthly
|
||||||
|
integrations:
|
||||||
|
- octoprint
|
||||||
|
pin: true
|
||||||
status: active
|
status: active
|
||||||
|
|||||||
Reference in New Issue
Block a user