Marc Billow
e49b61e01e
A follow-up dump confirmed these ride as plain BubbleSoak_On/Off, PreWashSetting_On/Off, and IntensiveSetting_On/Off tokens in the same /course/vs/0 options array as the cycle select, so they're exposed as self-gating config switches the same way other options-array fields are. Per-cycle availability (BubbleSoakSet/PreWashAvailableSet/IntensiveAvailableSet) lines up positionally with editCourseList but isn't used for gating, since exists_fn only runs once at setup against whatever course happened to be active then.
30 lines
544 B
JSON
30 lines
544 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"bubble_soak",
|
|
"child_lock",
|
|
"cycle",
|
|
"cycle_active",
|
|
"delay_start_hours",
|
|
"detergent_low",
|
|
"diagnosis_status",
|
|
"drum_clean_cycles_remaining",
|
|
"dry_level",
|
|
"energy_kwh",
|
|
"finish_time",
|
|
"firmware_update",
|
|
"intensive",
|
|
"job_beginning_status",
|
|
"machine_state",
|
|
"power_switch",
|
|
"pre_wash",
|
|
"progress",
|
|
"progress_percentage",
|
|
"remote_control",
|
|
"rinse_cycles",
|
|
"softener_low",
|
|
"spin_speed",
|
|
"wash_temperature"
|
|
]
|
|
}
|