Marc Billow
36240b44e6
Both switches were shipped unconditionally (no exists_fn) as an unverified guess -- the module docstring already flagged them as "unproven." Every range/oven fixture in the corpus, including the new issue #183 dump, reports neither fastpreheat_* nor NaturalSteam_* in /mode/vs/0's options at all, so both were phantom controls: always read as off, and toggling them wrote a token the firmware never recognized in the first place. That matches the reporter's exact complaint ("doesn't appear to do anything"). Also bound two tokens confirmed present on this dump but never modeled at all: EnergySaving_On (the 120-hour energy-saving standby from the app) and BurnerOnAlert_Off (cooktop-on alert), following the same single-token options-merge pattern as the existing lamp/sound/fast_preheat switches. Child lock, the setpoint mismatch, and the missing cook-start control from this issue are not code bugs -- see the issue comment for what was verified and what still needs more information from the reporter.
44 lines
957 B
JSON
44 lines
957 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"burner_0_hot_surface",
|
|
"burner_0_pan_detected",
|
|
"burner_0_power_level",
|
|
"burner_0_state",
|
|
"burner_1_hot_surface",
|
|
"burner_1_pan_detected",
|
|
"burner_1_power_level",
|
|
"burner_1_state",
|
|
"burner_2_hot_surface",
|
|
"burner_2_pan_detected",
|
|
"burner_2_power_level",
|
|
"burner_2_state",
|
|
"burner_3_hot_surface",
|
|
"burner_3_pan_detected",
|
|
"burner_3_power_level",
|
|
"burner_3_state",
|
|
"child_lock",
|
|
"cloud_connected",
|
|
"cook_time",
|
|
"cooktop_child_lock",
|
|
"cooktop_power",
|
|
"cooktop_safety_shutoff_enabled",
|
|
"cooktop_state",
|
|
"current_temp_c",
|
|
"cycle_active",
|
|
"door_open",
|
|
"energy_saving",
|
|
"finish_time",
|
|
"firmware_update",
|
|
"lamp",
|
|
"machine_state",
|
|
"operation_time_minutes",
|
|
"oven_mode",
|
|
"oven_setpoint",
|
|
"oven_state",
|
|
"power_switch",
|
|
"progress_percentage",
|
|
"remote_control",
|
|
"sound"
|
|
]
|
|
} |