A-VSKR-TP1-22-VS9500AL connects successfully but its dump shows no vacuum-body state at all -- no suction level, no battery, no cleaning mode -- only the clean/auto-empty station's own dustbag, dustbin auto-empty settings, and UV-C sanitizing-cycle status. This strongly suggests the WiFi/DTLS module lives in the station, not the handheld stick, so the station is the only "device" this integration's local API can reach at all. New vacuum_station device type (these hrefs share nothing with any existing family, so there's no shared-href ambiguity to resolve against another type) routed via a new '-VSKR-' modelNum fallback. Binds with zero unbound hrefs: dust-bag full/usage sensors, auto-empty and dustbin auto-close switches, a discharging-time select, and clean-station status including UV-C intensive mode, operation time, and finished/emitted timestamps. A couple of fields with unconfirmed exact semantics (stick_status, dustbag_usage's unit) are exposed as plain diagnostic values rather than an asserted binary/percentage meaning.
19 lines
372 B
JSON
19 lines
372 B
JSON
{
|
|
"state_keys": [
|
|
"alarm_code",
|
|
"auto_empty",
|
|
"cleanstation_status",
|
|
"discharging_time",
|
|
"dustbag_full",
|
|
"dustbag_usage",
|
|
"dustbin_auto_close",
|
|
"energy_kwh",
|
|
"firmware_update",
|
|
"stick_status",
|
|
"uvc_emitted_time",
|
|
"uvc_finished_time",
|
|
"uvc_intensive_mode",
|
|
"uvc_operation_time",
|
|
"uvc_total_operation_time"
|
|
]
|
|
} |