Why phone keypresses land these codes more reliably
The sequences fail for two mechanical reasons on a hardware remote. An infrared remote that has drifted off-aim drops a press silently, so a five-press count becomes a four-press count and nothing happens. And a sticky or worn button can double-register, which corrupts the sequence just as effectively.
Sending each key over the network removes both failure modes: every tap is one discrete command, delivered or not, with no aim to lose and no membrane to misfire. You still have to keep the rhythm up, because the timing constraint lives in the device rather than in the remote, but the presses themselves are clean.