Marc Billow
5e2c23a62d
This board (NE63T8751SG/AA-class) reports no /information/vs/0 at all -- the modelNum-based routing fallback has nothing to read -- so it fell back to 'unknown' and lost the whole range registry (oven mode/setpoint/ door/connected, cooktop monitoring). /oic/d does carry oic.d.range, though, so this is a routing fix, not a new capability: adds 'oic.d.range' to _OIC_TYPE_TO_KEY. The second oven cavity is a genuine Pattern A indexed subdevice at /device/1 (issue #177's mechanism) -- once routing resolves the master to the range registry, the same registry already applies to the subdevice's canonical view and every href on both binds with zero gaps. _discover_full gains an optional device_types param (default (), every other fixture unaffected) so a fixture that can only route via /oic/d can exercise the same subdevice-aware pipeline the other composite fixtures already do.
39 lines
884 B
JSON
39 lines
884 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"child_lock",
|
|
"cloud_connected",
|
|
"cook_time",
|
|
"cooktop_on_alert",
|
|
"cooktop_running_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",
|
|
"subdevice1_cloud_connected",
|
|
"subdevice1_cook_time",
|
|
"subdevice1_current_temp_c",
|
|
"subdevice1_cycle_active",
|
|
"subdevice1_finish_time",
|
|
"subdevice1_machine_state",
|
|
"subdevice1_operation_time_minutes",
|
|
"subdevice1_oven_mode",
|
|
"subdevice1_oven_setpoint",
|
|
"subdevice1_oven_state",
|
|
"subdevice1_progress_percentage",
|
|
"subdevice1_sound",
|
|
"warming_center_state"
|
|
]
|
|
} |