Stereo Thermostat and Control Wiring Data

It is first-person video of a person mounting a thermostat and wiring its controls, recorded from the worker’s own point of view with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: thermostat installation robot training data, stereo control wiring video, an egocentric HVAC thermostat dataset or custom trade service data collection. They describe one request from different angles. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on this row. The catalog lists a head-mounted phone or a multiview rig as its capture setup, so a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors, not robot or teleoperation data, so using it for a specific robot still needs your own retargeting step. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

One, listed in lib/commercial-catalog-data.ts, in the Trade Service Calls (Plumbing / HVAC / Electrical) environment of the Construction & Trades sector. "Thermostat & Control Wiring" is described as "Mount the thermostat, connect control wires to terminals and test the heating and cooling calls." It is rated Hard. The environment examples read "Plumber, electrician or HVAC crew on service calls at client sites", which are kinds of crew, not named firms, and this page names none.

The row is listed as Ready to deploy. The site states no delivered hours and no delivered stereo footage for it, so this page claims none. The first table below reproduces the row as the catalog states it, with three neighbouring rows from the same environment shown for comparison. Those three are different jobs and are not counted as thermostat work.

This page is the stereo and MCAP treatment of one row: thermostat mounting, control-wire termination and heating and cooling call testing on trade service calls. The egocentric thermostat and control wiring page covers the same row first-person and is not stereo as its subject. Where that page lists capture, it points to the instrumented tier; this page is the one that starts from a calibrated stereo pair and an MCAP file.

The stereo HVAC installation and service page covers five HVAC-related rows, and the thermostat row is one of them, so equipment mounting, ducting, filters and a home service call share its space. The stereo electrical installation page covers outlet, switch and fixture wiring and does not count this row. The stereo water heater replacement page covers a different Trade Service Calls row. The second table below sets the pages side by side with each status as the site lists it.

The catalog lists "Phone (head-mounted) / multiview rig" for the row, and the trade service calls environment page lists the same capture setup. The site does not state a head-mounted stereo setup for it. Stereo applies through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot.

The site describes two stereo setups and does not say which one an order for this row uses. The hard-environments stack is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output. A multiview rig adds synchronized third-person angles when the spec asks for them. Whether a stereo pair is worn, mounted or combined with a multiview rig is Not stated. The site also states that Firsthand does not capture at a customer’s own facility, so the setting is agreed in the spec.

Thermostat work is about placement and connection: where the thermostat sits, how a wire end approaches a terminal and which hand holds which part. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the geometry sits in the same capture that shows the hands working. The site gives no depth accuracy figure for this row, so what a buyer does with that depth is their pipeline’s question.

A stereo pair adds depth, not a verdict. The site states that metric depth on sub-centimetre parts is flagged rather than interpolated, and does not say whether a terminal or a wire end counts as such a part. Dataset 06 is stated at 1080p per eye, and whether that resolves a wire end at working distance is Not stated, so a spec should check it on a Spec Pilot. The egocentric thermostat page already supplies the first-person view; stereo is the addition for a buyer who wants the depth and the MCAP file.

The row gives a natural three-way cut: mount the thermostat, connect control wires to terminals, and test the heating and cooling calls. The order is the catalog’s own. A spec that says "wire the thermostat" gives one long action segment. A spec that names the steps gives a sequence you can slice by step, and the site does not set an episode length or say how many thermostats make up an episode.

The test step belongs in the same episode as the wiring, because the row ends with it and the job is not finished when the wires are connected. What the video shows is the contributor performing the test. Contact events can mark when a hand meets the thermostat, a wire or a terminal, where the spec asks for them, and the spec decides what counts as the object.

A wire end, a thumb and a terminal can all sit between the lens and the work. The site states that fingers disappear behind objects, which is why each hand joint carries a visibility flag, and that reach and grasp frames are where blur and occlusion show up. The site also says small parts can be hidden by fingers. The head camera is global-shutter, which avoids rolling-shutter skew.

The site gives no figure for how often a finger is hidden on this job, and no wire gauge, terminal size or placement tolerance, so a spec can ask for wrist views or a second angle and check it on a Spec Pilot. The site states no force, torque, tool-pose or electrical-signal stream for this row, and this page does not claim one. Hand tools are not named in the row either, so none is named here.

The row describes connecting wires and testing calls, and a stereo pair can show the thermostat, the terminals and the hands in three dimensions. The site lists no connection-correct, terminal-secure or test-passed label for this row, so none is claimed. Whether a connection counts as correct is a judgement a buyer’s pipeline or spec has to define.

The site also does not state a temperature, voltage, current or controller-signal stream, so none is claimed. An episode is rejected when the manipulated object is out of frame for more than 15 percent of it, and for this job the spec decides what that object is: the thermostat, a wire or a terminal. Thermostat brands or models, wire colours, gauges, voltages, terminal designations and cycle times are Not stated.

Safety procedures for this row are Not stated, and this page makes no safety, code, licensing or compliance claim. One neighbouring row, "Outlet & Fixture Wiring", says to test with a voltage tester with power off. The thermostat row does not state a power state, and this page says no more than the row does.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, that a reviewer confirms the result before anything ships, and that footage that cannot be de-identified is discarded. That matters on a service call at a client site, and access to a client’s home or site is a condition the spec sets. The anonymization record ships with the data, an undocumented bystander is a stated reject criterion, and every episode links to a signed contributor release. This is not legal advice, and the executed agreement controls.

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For this row the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The fourth table below sets each stream beside what the site states about it.

Hand and wire occlusion is the first risk, under the visibility flag above. Weak depth is the second: the site notes that glare-heavy and low-texture scenes make single-frame depth worse, and that depth degrades on wet and reflective surfaces while confidence maps mask low-confidence regions. An episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid. Lighting, enclosed-space and dust handling for this row are Not stated.

Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for an undocumented bystander or for a mismatch against the named skill spec. A reject log ships with every batch, and rejected items are recaptured at the provider’s cost. The fifth table below lists the failure modes beside what the site states.

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. The site names no thermostat or trade-service dataset among them, so this work is custom collection, not an off-the-shelf purchase. The off-the-shelf stereo and hand-tracking video can still show the format before you write a spec.

It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which speed applies to this row, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe the steps and where each starts and ends: mounting the thermostat, connecting control wires to terminals, and testing the heating and cooling calls. Say whether an episode covers one thermostat or one step, what counts as the object and what counts as a completed step, and name the variation your pipeline is missing. Then name the streams you want in the file, the topic naming and message encoding your reader expects, whether calibration ships inside the file or beside it, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The sixth table below shows what each spec element decides.