datawebotFlair HVAC product data: vents, Pucks and hubs
Map Flair Smart Vents, Pucks and Bridges by model, sensor role, IR compatibility and system dependency; keep size labels and setup caveats distinct.
Flair's catalog separates central HVAC, ductless control and Pro equipment
Flair (flair.co) sells HVAC controls for central ducted systems and ductless units. Its catalog also names accessories, software and professional-only hardware. Keep product, configuration, compatibility and service records at distinct levels.
Scroll to compare →
| Catalog family | Examples shown by Flair | Useful fields to keep separate |
|---|---|---|
| Central HVAC zoning | Smart Vents, a temperature-reading device and a Bridge-family hub | Store vent option and size separately from the room sensor, hub model and documented system requirement. |
| Ductless controls | Pucks for supported mini splits, window air conditioners and portable air conditioners | Record one Puck per ductless indoor head or supported window/portable unit; keep generation, remote model and signal method with the compatibility statement. |
| Professional solutions | Puck 2 Pro, Bridge Pro and Static Pressure Kit are marked for Flair Pros in the catalog | Preserve the professional-audience label; do not present these as ordinary consumer variants. |
| Software and integrations | Flair names hvacOS and lists thermostat and smart-home integrations | Store the named integration and source separately; a brand appearing on a compatibility list does not establish support for every model or feature. |
| Accessories | Smart Vent Covers, power and electrical accessories | Keep the accessory SKU, compatible host device and sold-separately status distinct from the main product. |
Smart Vent size refers to the duct opening
Checked October 4, 2026: Flair lists the 4x10 Smart Vent as SKU FLAIRVENT410 and defines the size by the duct opening. Its sizing article says the exterior cover is typically 1.5–2 inches larger in each dimension, so the option label and visible face are different measurements.
Scroll to compare →
| Smart Vent field | Published example or value | How to preserve it |
|---|---|---|
| Selected option and SKU | 4x10 / FLAIRVENT410 | Keep the variant label and exact SKU together; do not infer a different opening from the cover. |
| Measurement basis | Nominal duct-opening dimensions | Store opening size separately from exterior cover dimensions. |
| Radio and power | The product listing specifies 915 MHz device-to-device radio, two included C-cell batteries and an optional 24 VAC port. | Attribute power and radio details to this model listing and observation date. |
| Box contents | One Smart Vent, two C-cell batteries and two mounting screws | Separate included parts from optional accessories and system hubs. |
| System relationship | Flair's support guide says Smart Vents do not connect directly to home Wi-Fi; Bridge guidance depends on the configuration. | Keep the device fact here and record the exact Bridge context from the linked support material. |
Puck generation determines gateway, power and remote-control details
Flair uses Pucks as room sensors in some central HVAC setups and as controllers for ductless equipment. Generation and operating mode change the role: record the exact Puck and the equipment it controls rather than joining all Puck records together.
Scroll to compare →
| Device or compatibility field | Flair-published distinction | What a useful record retains |
|---|---|---|
| First-generation Puck | Flair support identifies Gateway mode as a feature of the first-generation Puck. | Attach Gateway capability to that generation only. |
| Puck 2 | Used as a room sensor in Smart Vent systems or as a ductless controller; Flair says Puck 2 cannot act as a Gateway. | Keep sensor role, controller role and no-Gateway distinction tied to Puck 2. |
| Puck 2 Solo | Can connect to 2.4 GHz Wi-Fi without a Bridge and control its own room; it must remain connected to USB-C power in this mode. | Store Solo mode, room scope, Wi-Fi band and continuous USB-C power as one configuration. |
| Ductless remote | A Puck uses infrared codes. Flair says the remote must be compatible and show current settings; control depends on an infrared signal and line of sight. RF-only remotes are unsupported. | Retain indoor-unit model, remote model/code, signal type and line-of-sight condition; a brand match alone is insufficient. |
| Third-party temperature sensors | Flair lists Nest thermostats, but says Google Nest room sensors are unsupported. Its support guide names ecobee SmartSensors and Honeywell Smart Room Sensors when paired with the same-brand thermostat. | Distinguish thermostat compatibility from separate room-sensor compatibility and preserve the named pairing. |
Bridge requirements vary by HVAC setup and Flair source
Flair describes Bridge requirements in product, catalog and support contexts. The published statements distinguish Entry Level and Pro systems, Smart Vent setups and wired or battery-powered Pucks. Keep the source and setup with each requirement instead of turning them into one universal compatibility flag.
Scroll to compare →
| Setup and source | What Flair says | Record the distinction |
|---|---|---|
| Smart Vent systems — device requirements support article | The article, updated September 16, 2026, says Smart Vent systems need Bridge or Bridge Pro; Smart Vents do not connect directly to Wi-Fi. | Attach this requirement to the documented Smart Vent system and cite the support article. |
| Entry Level and Pro — Flair catalog | The catalog says Bridge is required for Entry Level zoning and air balancing, and optional for Pro solutions. | Retain the solution tier and the catalog wording; do not erase the Pro exception. |
| Puck 2 Solo — support guide | A single Puck 2 can control its own room without Bridge while connected to USB-C power. Flair says Bridge is needed for the described wireless or battery-powered arrangement. | Store Puck 2 Solo, room scope and power method with the Bridge status. |
| Wired Pucks and multi-head ductless setups — Bridge listing | Flair says wired Pucks can operate without Bridge and recommends Bridge for some multiple-head configurations. | Keep a recommendation distinct from a requirement and record the number of indoor heads. |
| Bridge package | The product listing names a Bridge, power adapter, USB-A-to-USB-C cable and Ethernet cable. | Treat these contents as listing-specific; do not assume they apply to Bridge Pro or every bundle. |
Accessories, software and household configuration are separate data scopes
Flair lists physical accessories alongside software and its System Builder, but they describe different records. Public product research can describe catalog items and published compatibility; household layouts and account-specific setup answers belong to an individual customer context.
Scroll to compare →
| Record type | Source-supported example | Boundary |
|---|---|---|
| Vent accessory | Smart Vent Covers have separate 4x10, 4x12 and 4x14 size options and named colors; Flair says the Smart Vent is sold separately. | Keep cover size/color and compatible vent separate from a Smart Vent SKU. |
| Professional accessory | Flair lists a 24 VAC transformer for Flair Pros. | Preserve its stated audience restriction. |
| Software and service | Flair names hvacOS and a mobile/web application as parts of its ecosystem. | Do not treat a software feature or service label as a physical device variant. |
| Customer-specific information | Home layout, room names, HVAC settings, sensor readings, account details and individual System Builder answers. | Keep private household and account data out of public catalog records. |
The 2023 EULA applies to licensed Flair software
Flair's End User License Agreement displays a February 27, 2023 update date and covers software embedded in Flair devices and its application. It describes a personal, non-commercial license to operate a device and restricts use or access to licensed software for benchmarking, competitive analysis or building a competing product or service, as well as copying or reproducing that software. This is a scoped summary of the posted software-license text, not a legal determination.
Scroll to compare →
| EULA detail | Published scope | Record boundary |
|---|---|---|
| Date and coverage | Last updated February 27, 2023; applies to software embedded in Flair devices and the Flair application. | Keep the date and source with this agreement, not with catalog items. |
| License purpose | Personal, non-commercial use to operate a device. | Preserve the limited software-license context. |
| Named restrictions | The agreement names benchmarking, competitive analysis, building a competing product or service, and copying or reproducing licensed software. | Do not extend these clauses beyond the licensed software they govern. |
Content reviewed 2026-10-04.