A DV6800N (DA_WM_A51_20_COMMON) reports the same /st/dryercourse/vs/0 courseTable 'Table_00' as issue #357's DVE45R6300W/A3 -- also DA_WM_A51_20_COMMON -- and its reporter listed 14 selectable courses read straight off the appliance's own menu, in the same order /course/vs/0's supportedOptions enumerates them. Initially treated this as a second, incompatible Table_00 code family and added a device-model-keyed disambiguation layer to laundry.cycle_select. That was an unproven assumption: the two reporters' confirmed sets are mostly non-overlapping subsets (11 vs 14 codes), which is exactly what you'd expect from two models on a shared board exposing different subsets of one course table via their own /course/vs/0 supportedOptions -- not evidence of two different code dictionaries. The one code both reporters confirmed, 'a5', means Bedding on both, which is corroborating, not neutral. No confirmed code conflicts between the two sets, so this folds #394's 14 codes straight into the existing dryer_cycle_table_00 catalog entry (mirrored to all shipped languages), same shape as #357's original translations-only change. Adds a scrubbed fixture + golden for the DV6800N dump and tests confirming zero unbound hrefs and that its course codes resolve through the shared, now-larger dryer_cycle_table_00 catalog.
24 lines
407 B
JSON
24 lines
407 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"child_lock",
|
|
"completion_minutes",
|
|
"cycle",
|
|
"cycle_active",
|
|
"delay_start_hours",
|
|
"diagnosis",
|
|
"dry_level",
|
|
"dry_time",
|
|
"dryer_type",
|
|
"energy_kwh",
|
|
"finish_time",
|
|
"job_beginning_status",
|
|
"machine_state",
|
|
"power_switch",
|
|
"progress",
|
|
"progress_percentage",
|
|
"remote_control",
|
|
"wrinkle_prevent"
|
|
]
|
|
}
|