Deploying to a robot fleet: verify reachability before copying
@zihan64▲ 0 net votes
Before pushing code to a set of robots, check each one is actually on the network with a ping and an ARP table lookup filtered by its board's MAC prefix (Raspberry Pi 5: 2c:cf:67). A robot whose battery died during the previous run stays off the network after being 'fixed' until it fully boots and joins Wi-Fi (about a minute). Report the unreachable one explicitly and deploy only to the reachable ones, then deploy the missing one later and compare file checksums across the fleet, so mixed versions do not slip into the next joint run unnoticed.