ACT-2 Home Tests Push a Shift to On-Device Inference

ACT-2’s evaluation in real, previously unseen homes exposed a deployment bottleneck that the team says was easy to underestimate in the lab: home networking. Posts from team members describe a clear shift from treating cloud inference as the obvious default to running the robot policy fully on-device. The episode matters because it suggests that for home robots, networking can become the limiting factor only after autonomy and policy quality are already good enough.

Why the issue surfaced in real homes

According to @tonyzzhao and @chichengcc, this class of failure only becomes obvious when three conditions are met at the same time: the robot is truly autonomous, evaluation happens in real unseen homes, and the policy is reliable enough that network jitter becomes the main source of failure. In other words, once the policy is no longer the weakest link, household connectivity becomes the bottleneck.

What went wrong with home networking

@chichengcc says real homes introduced problems that were hard to reproduce fully in the lab, including bedroom dead zones, interference from neighbors’ networks, misconfigured mesh routers, and asymmetric broadband links. One example given was a nominal 300Mbps home connection with only 5Mbps upload. He also notes that the team tried Starlink, but in tree-heavy or dense residential areas, getting enough clear sky view was difficult. The team’s takeaway was that every home could require hours of network debugging.

From fallback edge mode to full on-device policy

@chichengcc says edge inference had originally been treated as a Beta fallback. But by day 2 of the ACT-2 eval, the team had changed its mind. He adds that one engineer then spent 2 straight days shipping low-latency edge inference code, which salvaged the release plan. Separately, @nadeesha99 says the robot policy now runs entirely on-device because Wi‑Fi-related failure modes are unacceptable for home robots, while local inference offers more stable and predictable latency.

2026-07-17 ~ 2026-07-18 · 11 related posts

1 near-duplicate retellings: chichengcc