Marc Billow
c72b5a988e
NE63B8411SS reports no oneUiVersion and no /information/vs/0 resource at all, so neither for_device nor for_device_by_model's modelNum tokens have anything to key off -- it fell through to the unknown-device fallback, which also mis-binds /temperatures/vs/0 against fridge.py's setpoint capability (a collision the oven family's own capabilities are normally excluded from the global registry specifically to avoid). Add a resources-based signature to for_device_by_resources(): 'Bake' in /mode/vs/0's supportedModes is oven/range-exclusive vocabulary, and paired with the /oven/vs/0 cavity resource it reliably identifies this family even with no model info at all. Route to 'range' when a cooktop-status resource is also present, else plain 'oven'. This board's cooktop half also doesn't expose the per-burner /cooktop/status/vs/0 array range.py already models -- only the coarser /cooktopmonitoring/vs/0 summary resource. Add a read-only COOKTOP_MONITORING capability for it (cooktop running state, warming center state) rather than leaving it unbound.
28 lines
501 B
JSON
28 lines
501 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"child_lock",
|
|
"cloud_connected",
|
|
"cook_time",
|
|
"cooktop_running_state",
|
|
"current_temp_c",
|
|
"cycle_active",
|
|
"door_open",
|
|
"fast_preheat",
|
|
"finish_time",
|
|
"firmware_update",
|
|
"lamp",
|
|
"machine_state",
|
|
"natural_steam",
|
|
"operation_time_minutes",
|
|
"oven_mode",
|
|
"oven_setpoint",
|
|
"oven_state",
|
|
"power_switch",
|
|
"progress_percentage",
|
|
"remote_control",
|
|
"sound",
|
|
"warming_center_state"
|
|
]
|
|
}
|