Integrate qualified Zigbee fan modes and evidence

ALYT qualifies Zigbee fan controls from declared capability and observed device evidence, not from converter guesses or old retained values. A fan becomes usable when its declared type, actual reader and writer behavior, and matching cluster evidence line up in the full-acquisition home cohort. The fan view shows only the presets that are actually qualified, and each write is confirmed by a fresh reported fan preset rather than an acknowledgment or airflow estimate. Climate and fan controls stay separate, and a fan adapter does not replace thermostat control.

Qualification and scope

A library fan can be selected for association or interview through its declared type in the full-acquisition home cohort. Qualified fan controls use the existing bounded component map and fans family, with ordinary authorization and resident MG24/CPC hub owners. No converter catalogue enters hub RAM.

For the standard Fan Control profile, qualification requires all of the following:

• the actual frozen fromZigbee.fan reader
• the unambiguous toZigbee.fan_mode writer
• the observed 0x0202 input cluster
• matching declared modes and access

The enum codes 0–6 map to off, low, medium, high, on, auto, and smart.

Unknown or private converters do not receive the standard flag from a lookalike declaration. Climate and fan components keep separate identities, so a fan control does not displace thermostat controls.

What the fan view exposes

The shared fan descriptor projects only declared qualified presets. Manual settings, saved routines, and governed proposals reuse the current target, fence, and receiver owners. If an additional target is needed, current protocol2 owner evidence and an exact qualified receiver revision are required.

An old receiver that ignores unfamiliar flags cannot authorize the new operation. The existing finite job fields carry the preset and readback, and there is no new persistent native state or scalar slot.

The physical-result field is the freshly reported fan preset. It is not an ACK and not an airflow estimate. Typed attribute reports reject duplicate, invalid, or foreign-namespace values. Canonical per-field evidence keeps original source, time, and expiry, and retained or replayed values do not establish current completion.

Cohort withdrawal removes the new writable presentation without deleting inventory or replacing working legacy paths. The existing Zigbee knowledge, controls/readings, and owner-fence guides remain the scope and recovery references.

Device-specific behavior

Inovelli VZM35-SN and VZM36

The Inovelli VZM35-SN and VZM36 use separately observed fan endpoints and their exact original level-mode codec. Power is a separate On/Off report. Their original mode reader can show Low for a zero level and High for the On command’s maximum level. ALYT preserves those reports rather than inventing Off/On mode evidence.

A requested preset that cannot be matched or observed remains unconfirmed. Check the actual power and preset readings before trying another action. The VZM36 light remains a separate target.

IKEA STARKVIND E2007 and E2006 alias

The IKEA STARKVIND E2007 and its E2006 alias offer Off, Auto, and numbered presets 1–9. The reported speed is an index from 0–9, not a percentage. The speed reading is read-only; use an offered preset to change the setting. Reports keep the device’s original mode and manufacturer scope.

FanBee

FanBee uses its original raw speed scale 1–254 with a separate On/Off control. That scale is not a measured percentage of airflow.

Tuya _TZE284_z5jz7wpo

The Tuya _TZE284_z5jz7wpo module declares a raw control range of 0–254. Its original adapter snaps a request to one of five steps and reports 51, 102, 153, 204, or 255.

A requested value and its reported step can differ. ALYT preserves the actual report and keeps a nonmatching requested value unconfirmed rather than claiming exact completion. Do not treat speed zero as a power-off instruction; use the offered power control.

Working with evidence and access

Use the observed report as the proof of the current fan preset. Do not rely on a retained value, a repeated value, or a foreign-namespace value to mark completion. If a preset is not observable, it stays unconfirmed.

Access boundaries matter in the same way as for other Zigbee controls:

• household permissions are narrower than staff
• DEV credentials act in the developer sandbox
• LIVE credentials only apply to their own installed connector

Local functions can keep working during a cloud outage. Cloud-dependent connectors require the provider and network, so a cloud connector does not work when its cloud path is unavailable.