The room that joins the meeting in one tap.

Bill of materials per Google's setup resources for the Large kit and Logitech's kit datasheets; weights from Logitech's Rally specification sheet. The 715663 UPC prefix is not Logitech's; the kits were assembled by CTL, which is consistent and on the record.

Neither claim clears adjudication: same source tier, no agreement within tolerance, no third-party measurement on file to break the tie. Contested is a respectable end state; a quiet 55% upgrade in marketing copy is not.

Conflict ticket open: acoustic.pickup_range within gpd:family:logitech.rally. Six further conflicts in the register; see Provenance. No independent lab measurement exists for this family; when one lands, it gets its own row and its own color.

Epistemic note: no independent lab has measured this family; every technical value above is a manufacturer claim and says so. The aggregated row carries integrator guidance at confidence 0.5. Statements missing a required qualifier are stored incomplete and never shown as canonical; three such rows exist in the full dossier.

Sources: Logitech kit datasheet Sept 2021; MeetUp datasheet; Chrome Unboxed launch pricing 2020-06-02; Google Workspace Series One announcement 2020-09-15.

Ask the graph directly: GET /v1/products/…/compatibility?with=gpd:variant:logitech.rally_mic_pod returns the verdict, the path, and the hub condition.

Asset presence is itself filterable: filter[assets.install_diagram][exists]=true. All links verified 2026-06-10; archived addresses say so.

1. 2019-02-04Tap unveiled at ISE. Logitech positions the controller against “the complex and costly status quo”; the launch film later takes a Red Dot award.
2. 2020-06-02The Google Meet kits ship. Small, Medium, Large at $2,800 / $4,150 / $4,900, assembled with CTL compute. This composition enters the graph.
3. 2020-09-15Google announces Series One. The platform owner's own room kits with Lenovo arrive at $3,999 for the large room; the records link as competing successors.
4. 2021-09Cat5e revision documented. The /2 kits replace the 10 m optical USB tether with a 40 m category-cable link; this page describes that revision.
5. 2024-01-08Compute refresh. CTL's GQE20C (Core i5-1335U, 16 GB, update horizon 2030) replaces the original Chromebox in revision 4 kits.
6. 2025-06Auto-update expiration, revision 1 compute. The original Chromebox leaves Google's update window; the graph flags affected units, not the family.
7. 2026-06-10End of partner sale observed. Sold out or delisted at CTL, Bechtle, and the reference partner. A formal end-of-sale notice is not on file; the absence is recorded too.

Time travel: GET /v1/products/gpd:composition:logitech.room_google_large?at=2021-01-01 returns the Strong-USB revision, priced as it was.

Can this kit run Zoom or Teams instead of Google Meet?

Not this composition; the compute boots ChromeOS in Meet kiosk mode. The same AV hardware ships as separate Zoom Rooms and Teams Rooms kits with different compute; the same_hardware_as edges above name them.

How far can the Tap sit from the display wall?

Up to 40 meters on the Cat5e revision, with data and power on one run; 10 meters of cable are in the box. The original revision used a 10 meter optical USB tether, 25 meters at most.

How many people does the room really seat?

Logitech recommends 16 with the included two pods and supports 46 with seven; one integrator pegs practical use at 12 to 20. All three figures are on the record with their sources.

Are the displays included?

No. The kit drives one or two displays over HDMI and includes everything else; the wiring diagram under Documents shows both layouts.

Is it still being sold?

As of 2026-06-10 it is sold out or delisted at the major partners on record, and Logitech's Google Meet line-up leads with the Rally Bar generation. The record stays resolvable either way.

Why does the pickup range row show two values?

Because the manufacturer published two: 4.5 meters in the 2018 datasheet, 7 meters on the 2026 product page. Neither claim outranks the other, so the group is contested with a ticket open.

What happens after the compute's update horizon?

Revision 1 units left Google's update window in June 2025; they keep working but stop receiving features and security patches. Revision 4 compute carries the horizon to September 2030.

Where do these answers come from?

Every sentence above traces to a claim with source, locator, and retrieval date; the Provenance section counts them. If a rights holder disputes one, the correction loop ships a webhook, not a quiet edit.

$ curl "https://api.getproductdata.com/v1/products/gpd:composition:logitech.room_google_large\
?depth=full&expand=composition.components,context,assets,claims" \
  -H "Authorization: Bearer gpd_live_51Hx…"

# one request; this entire page renders from the response

{
  "object": "product", "entity": "composition", "authority": "manufacturer_defined",
  "id": "gpd:composition:logitech.room_google_large",
  "schema_release": "2026-06-08",
  "attributes": { "acoustic.pickup_range": { "statements": [
    { "value": 4.5, "unit": "m", "epistemic": "claimed", "status": "contested",
      "claims": [{ "source": "gpd:src:mfr.logitech.datasheet", "observed_at": "2018-10" }] },
    { "value": 7.0, "unit": "m", "epistemic": "claimed", "status": "contested",
      "claims": [{ "source": "gpd:src:mfr.logitech.product_page", "observed_at": "2026-06-10" }] }
  ] } },
  "context": { "percentiles": { "application.max_seats": 0.98, "optical.field_of_view": 0.34 } },
  "quality": { "completeness_vs_type_profile": 0.94, "overall_confidence": 0.91, "conflicts_open": 7 }
}

Source mix for this family: manufacturer 14 · platform owner 5 · retailer_major 6 · press and integrator 6. Population statistics and quality scores are a recorded demo snapshot; the product facts, identifiers, conflicts, prices, and documents are real and dated. No independent lab measurement is on file; the first one to land gets the blue.