datawebotSensibo product data: models, sensors and compatibility
Compare Sensibo devices by AC compatibility, sensors, accessories, kit quantity, warranty and shipping; separate public catalog facts from account-based API data.
Compare the current controller models by their source labels
Sensibo's comparison guide distinguishes Sky, Air and Air PRO. The Air PRO product page says it was formerly AirQ, so that alias belongs with the current model rather than as a second current product. The source lists HomeKit for Air while its FAQ says Sky does not support it; preserve these model-specific claims.
Scroll to compare →
| Product record | Useful public fields | Keep distinct from |
|---|---|---|
| Sensibo Sky | Product URL; model name; color or kit choice where offered; source-listed integrations | Air or Air PRO, even where the supported AC categories overlap. |
| Sensibo Air | Product URL; remote-control model; built-in temperature/humidity fields; compatible accessories | An included Room Sensor or a multi-unit bundle. |
| Sensibo Air PRO | Product URL; current model name; former AirQ alias; source-listed air-quality fields | A separate current AirQ model record or a direct CO2 reading inferred from a CO2-equivalent label. |
Separate built-in readings from accessory sensors
The Air PRO specification labels a field “CO2 equivalent (using TVOC).” Keep that exact qualification with the source-reported value instead of treating it as a generic CO2 field. Sensibo's Room Sensor is a separate accessory: its page lists temperature, humidity and motion, and says it works with Air but not Sky.
Scroll to compare →
| Source item | Record separately | Relationship to preserve |
|---|---|---|
| Air PRO built-in sensors | Temperature, humidity, TVOC and the source's CO2-equivalent label; product URL and observation date | Do not collapse unlike sensor readings into one air-quality score or remove the equivalent qualifier. |
| Air built-in sensors | Product-level temperature and humidity specifications | Keep internal sensors distinct from data provided by a paired Room Sensor. |
| Room Sensor accessory | Accessory model; its listed temperature, humidity and motion fields | The source says it requires Sensibo Air and is not compatible with Sky; it is not a standalone AC controller. |
| Air + Room Sensor bundle | Bundle URL; included Air controller and Room Sensor quantity | Link the accessory and controller records without changing the sensor into a controller variant. |
Treat AC compatibility as a remote-control condition
Sensibo lists window, portable, split, cassette, high-wall and some central systems, but its compatibility guide requires a working infrared remote for each supported AC. The list is described as non-exhaustive. For some window and portable units, relative button commands can leave the app and physical controls out of sync.
Scroll to compare →
| Compatibility evidence | Useful equipment fields | What it does not establish |
|---|---|---|
| AC type and model | Manufacturer and model as stated; equipment category; source compatibility result and review date | That every unit in the category works or that an unlisted model is incompatible. |
| Remote-control requirement | Whether a working infrared remote is available; remote model where known; selected Sensibo controller | Compatibility from a wired thermostat alone. |
| Window or portable control behavior | Whether physical buttons or relative commands affect state synchronization, when documented for that model | A guaranteed match between app state and the AC's physical state. |
| System relationship | One controller-to-AC association, if the source or setup record specifies it | A second controlled unit just because two AC products share a room or account. |
Keep multi-unit kits and sensor bundles at their own grain
Store the selected kit as a package with an included-device count, then link its component models. A multi-unit controller kit and a controller-plus-sensor bundle answer different quantity questions; neither should be flattened into a controller color or model variant.
Scroll to compare →
| Retail grouping | Fields to retain | Keep separate from |
|---|---|---|
| Multi-unit controller kit | Kit URL or option; controller model; included unit count; displayed per-unit amount and currency only when useful | The count of product options or accessories. |
| Air + Room Sensor bundle | Bundle identity; Air controller count; Room Sensor count; included components | A single Air controller's selectable model or color. |
| Air PRO + Door/Window Sensor bundle | Bundle URL; Air PRO count; sensor type and count; included component relationship | The Air PRO model's built-in sensor fields. |
| Store offer | Market/currency, displayed price, offer label and observation date if captured | A durable list price, current availability, or price guaranteed across destinations. |
Attach warranty and delivery statements to their conditions
Sensibo product pages state a one-year limited warranty, and its refund policy describes a 30-day return period for delivered purchases in original packaging with proof of purchase. The Terms describe plan-based extended coverage for only one eligible device under specified eligibility and timing conditions. Territory and checkout affect shipping, customs and taxes.
Scroll to compare →
| Policy or order field | Source context to keep | Do not infer |
|---|---|---|
| Standard warranty | Product model; one-year limited-warranty wording; source page and review date | Coverage for every accessory, bundle component or use case beyond the stated terms. |
| Extended warranty | Eligible device; qualifying plan; activation or timing conditions stated by the Terms | That every purchased unit or Room Sensor receives extended coverage. |
| Return period | Official-store purchase context; delivery date; original package and proof-of-purchase conditions | A universal return right for purchases from other sellers. |
| Shipping and duties | Destination and checkout observation; displayed estimates, customs or tax context | A fixed delivery date, shipping price or destination eligibility based only on the product page. |
Separate the public store catalog from authenticated device data
Sensibo's API documentation describes account-authenticated operations for a customer's connected devices, including device state, historical measurements and events. Personal API use relies on account-generated keys; the documentation says commercial OAuth2 is available by request, while some Airbend organization actions require membership or administrator access. These endpoints describe account/device data, not a public product catalog.
Scroll to compare →
| Source area | Useful access and data context | Boundary for a public product record |
|---|---|---|
| Public store | Model pages, product options, bundles, stated warranty and checkout-specific offers | Do not claim that public product pages expose a customer's connected-device readings. |
| Personal API | Account-created credentials; connected devices; states, history and events listed by the API docs | No API key, device ID, event history, reading or location tied to an account belongs in this article. |
| Commercial and Airbend APIs | OAuth2 access is available to commercial users by request; organization endpoints have membership and role conditions | Do not imply open or anonymous access to organization data. |
| Terms context | §1 names crawler restrictions for specified competitive, model-training and service-disruption purposes; §14 states personal-use and API limits, including up to 15 devices for non-commercial customers | Attribute the stated scope and date; API documentation and terms do not establish that private device data is public. |
Content reviewed 2026-10-07.