francop/HomeAssistantVS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

opencode/decisions.yaml, zigbee2mqtt/state.json

Browse Source
This commit is contained in:
Home Assistant Version Control
2026-10-15 17:46:23 +00:00
parent e9a0bb27cc
commit 5ebc38eac8
2 changed files with 57 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
opencode/decisions.yaml
+42 -4
View File
@@ -1053,10 +1053,10 @@ notes:
segment.
rationale: sensor.sparkx_i7_used_material_length is a per-job counter (resets to 0 at
completion), so derived templates read 0 when idle; the helpers keep the last job
across restarts. The latch automation (1791477238762) accumulates each colour segment
into input_number.sparkx_i7_slot_N_grams; the completion adds the final segment and
sums them. A split(' ') bug left helper_idx empty, so total and last-job equalled only
the last segment (12.02 g, not 59.4 g). Do not revert.
across restarts. The latch automation (1791477238762) accumulates each colour
segment into input_number.sparkx_i7_slot_N_grams; the completion adds the final
segment and sums them. A split(' ') bug left helper_idx empty, so total and last-job
equalled only the last segment (12.02 g, not 59.4 g). Do not revert.
entities:
- input_number.sparkx_i7_last_job_filament_weight
- input_number.sparkx_i7_last_job_cost
@@ -1072,3 +1072,41 @@ notes:
- spoolman
pin: true
status: active
- id: 2026-10-15-sparkx-i7-low-spool-alerts-use-a-4
date: 2026-10-15
title: SparkX i7 low-spool alerts use a 4-digit band dedupe
decision: The SparkX i7 low-spool alert (automation 1792076023718, every 15 min) stores a
4-digit band in input_text.sparkx_i7_low_spool_notified, slot 1->4, 0=ok / 1=<100 g
/ 2=<25 g, and notifies only when band > stored band and band > 0. The dashboard
tube cue mirrors the same bands. CFS Lite slots only.
rationale: Gives one notification per threshold crossing per slot; recovery updates the
stored band silently so no repeat. The tube cards compute the alert-identical band
from the same spool entity, so the card and the notification cannot disagree about a
slot's state. A spool sensor briefly going unavailable can reset its band to 0 and
re-notify once on recovery; that is known and accepted.
entities:
- input_text.sparkx_i7_low_spool_notified
- automation.sparkx_i7_low_spool_alert
files:
- automations.yaml
status: active
- id: 2026-10-15-cfs-lite-slot-matching-is-by-spoolman
date: 2026-10-15
title: CFS Lite slot matching is by Spoolman spool location, not colour
decision: SparkX i7 per-slot filament tracking matches purely on the Spoolman spool's
location field == 'CFS Lite <n>' (slots 1-4); the colour check and any fallback were
removed. When swapping a roll into a slot, set that spool's Location to 'CFS Lite
<n>' — a stale label is the only thing that can misroute a deduction.
rationale: Identical-colour rolls in different slots auto-rotate, so colour alone cannot
attribute usage. Only individual spool records (their location field) were changed;
no Spoolman setting or config was touched. Applies to automation 1791477238729
(completion), 1791477238762 (latch), 1791477238799 (sufficiency) and script
spoolman_set_spool_remaining.
entities:
- sensor.sparkx_i7_active_filament_slot
files:
- automations.yaml
- scripts.yaml
integrations:
- spoolman
status: active