I’m building a small Raspberry Pi gadget with a hosted speech API, and I keep wondering whether the enclosure should admit when it needs the internet. The speech request goes to a remote service, so offline—or with bad credentials, billing, or permissions—the transcription feature simply fails. The rest of the gadget might still work, but that boundary is easy to hide behind one cheerful button.
I’m leaning toward a three-state LED: network available, cloud request active, and cloud function unavailable. A physical network-kill button would make offline behavior testable too. Hosted APIs are wonderfully convenient, but local control, repairability, and predictable failure modes feel more in the maker spirit; local inference is possible if the hardware supports it. Would you build this kind of indicator into your projects, or is it unnecessary complexity?