Repository navigation
fix(homeassistant): recover missing K1 SE layer totals - #761
Closed
alex-mextner wants to merge 1 commit into
Closed
alex-mextner wants to merge 1 commit into
alex-mextner wants to merge 1 commit into
Conversation
Use filename- and status-revision-bound Moonraker metadata when stock firmware reports no total. Keep bounded event-driven retries and discard obsolete requests without losing a newer pending job. Add actual-template regressions and declare their test dependencies. Task: UB-216 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
alex-mextner
added a commit
that referenced
this pull request
Nov 18, 2026
* fix(ha): recover printer cards and current-file layer counts (UB-217) Register loading shells after Home Assistant initializes its element registry, then load the pinned camera, inspector and sharing implementations with bounded recovery. Preserve their configuration, state updates, events and lifecycle. Use current-file Moonraker metadata when K1 SE firmware reports no total layer count, with filename and status-revision guards against stale replies. Add focused regressions and a Chromium/WebKit recovery fixture using the real Home Assistant frontend components. Extract existing HA vision helpers to keep the required whole-file complexity gate clean (Refs #707). Release 0.81.1. Primary task: UB-217 Related task: UB-216 Supersedes the source repair in PR #761 after this combined change is merged. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> * fix(ci): pin printer-card browsers to Ubuntu 24.04 (UB-217) The ubuntu-latest runner moved to Ubuntu 26.04, which the pinned Playwright 1.56.1 runtime does not support. Use its supported Ubuntu 24.04 runner for the printer-card browser job while preserving the locked dependencies, the browser cases, and all runtime assets. Refs UB-217 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> * fix(ci): use pinned Playwright image for printer card checks Avoid repeated APT setup timeouts by using the official Playwright image with matching browser binaries and dependencies. Set up Python explicitly for the existing fixture builder and retain Node 22, both browser cases, artifacts and the existing 15-minute budget. Refs UB-217 --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
This was referenced Nov 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
K1 SE firmware can report zero total layers while a real print is already advancing through layers. Moonraker has the correct layer count for the same G-code, so the dashboard currently shows a misleading zero despite available metadata.
Task: UB-216.
Changes
Verification
Deployment scope
The exact final change was deployed at 22:30 UTC on 2026-11-17. All three affected source/runtime YAML slices match byte for byte, preserving the older runtime checkout outside this change. A native full configuration check passed; template-only reload and independent live API readback confirmed total_layers=104, metadata=104, attempts=1 and matching filename/revision. Preimage, patch and receipt are retained for rollback. No Home Assistant restart or printer control commands were used.
This PR covers layer-count metadata. The separate custom-card rendering errors shown on the user's iPhone are outside this diff and are not claimed fixed here.