Add device support for Samsung water purifiers (issue #90)
The TP2X_WATERPURIFIER_20K water purifier reports no oneUiVersion and its modelNum/description don't match any consumer-prefix or existing board-family token, so it fell into the unknown-device-type fallback with only common capabilities. Add a new water_purifier registry, routed via a 'WATERPURIFIER' modelNum/description fallback rule. Models dispense settings (type/temperature/capacity/pouring status), sterilize and filter status, favorite-capacity presets, and the three water/buzzer locks. Per the adding-device-support skill's "never hard-code the one dump's values" rule: dispense-capacity bounds and step come live from the device's own desiredCapacityRange/ capacityResolution fields (range_field/step_fn), not a hardcoded constant, and the hot-water-temperature control is a select over the live supportedHotTemperatures list rather than a number with invented bounds, since only a few discrete temperatures are selectable. /mode/vs/0 and /automation/waterpurifier/vs/0 are left unmodeled: the former carries an opaque wizard-workflow token with no coherent current-value contract, the latter is a static support-flags blob with no live setting to expose. Confirmed against the issue #90 diagnostics dump with zero unbound hrefs. Updates the README's supported-appliance-types table for the new device type.
This commit is contained in:
11 files changed
+715
-1
No files matched your search
@@ -31,6 +31,7 @@ Your state stays on your LAN: HA talks to the appliance over a direct DTLS sessi
|
||||
| Dishwasher | `by_type/dishwasher.py` |
|
||||
| Refrigerator | `by_type/refrigerator.py` |
|
||||
| Washer | `by_type/washer.py` |
|
||||
| Water purifier | `by_type/water_purifier.py` |
|
||||
|
||||
Each registry composes shared and family-specific `Capability` objects from `registry/capabilities/`; those modules document the individual resources/entities in more depth than a README table can stay current with.
|
||||
|
||||
|
||||
Reference in new issue
Block a user