Walkie-Textie Wireless Communicator

Original Article ↗ Hacker News Discussion ↗

A DIY “walkie‑textie” built on LoRa radios sparks broader exploration of long‑range, low‑bandwidth texting without cellular service, from hardware choices like ATtiny microcontrollers to battery life and power‑saving strategies. Commenters contrast LoRa’s peer‑to‑peer use with its original IoT role, note strict duty‑cycle and band regulations across regions, and compare it with alternatives such as GMRS/FRS radios, Meshtastic devices, and private Wi‑Fi or GSM setups. The thread highlights how legal constraints, radio propagation limits, and human‑factors issues (like T9 vs numeric keypads) shape what’s realistically possible for off‑grid messaging tools.

Power use, duty cycle, and interactivity

  • 24 mA draw implies only ~10 hours on the suggested battery; several comments question whether LoRa devices can be made to last much longer.
  • Others note LoRa receive current is not “free”; continuous listening drains batteries significantly, so real low-power designs require long sleep periods and event-driven wakeups.
  • LoRaWAN-style devices work by letting battery nodes sleep most of the time and a mains‑powered gateway listen continuously; this tradeoff is harder in symmetric peer‑to‑peer chat.
  • Some propose beacon-and-sync schemes to reduce duty cycle, but these run into legal duty-cycle limits (e.g. 1 % on 868 MHz in EU) and complexity.

Range capabilities and technical limits

  • Reported real-world LoRa ranges vary from a few km in cities to 30–60 km line-of-sight, and over 100 km with a balloon.
  • Range depends strongly on line-of-sight, modulation settings, and legal duty-cycle constraints; robust settings give low data rate but excellent sensitivity.
  • LoRa is viewed as poor for heavily obstructed or underground use; through‑earth and bunker scenarios are better served by much lower frequencies and different modulations.

Regulation, licensing, and encryption

  • LoRa in ISM bands faces duty-cycle and sometimes message-count limits; human chat is seen as “pushing it to the limits” of what it was designed for.
  • GMRS/FRS and ham options are discussed extensively: licenses, type-acceptance, digital/data restrictions, time limits on digital bursts, and removable-antenna rules.
  • Encrypted mesh systems (e.g. Meshtastic on 900–930 MHz) are fine on unlicensed bands but not on amateur allocations; enforcement is perceived as lax on encryption but stricter on power.

Hardware, UX, and design choices

  • The choice of an ATtiny814 is debated: some praise its simplicity, robustness, peripherals, and adequacy for this narrow task; others argue modern ARM/RP microcontrollers offer far more capability for similar price.
  • Old-school multi-tap numeric input is criticized for RSI and slowness; some wish for T9‑style prediction or a QWERTY keyboard.
  • Confusion arises over power: one person complains about AAA-only and poor life, but others clarify this design supports LiPo via JST.

Alternatives, practicality, and use cases

  • Suggested alternatives include Meshtastic T‑Decks, RAK base stations, GMRS text-capable handhelds, simple FRS radios, Wi‑Fi + SIP/IRC/Mumble setups, and even private GSM with SDR (not legal in most places).
  • Some see Meshtastic and similar devices as solutions in search of a problem; others imagine strong use cases in camping, disaster backup, and youth “adventure” communication.
  • Users highlight protocol challenges (collision avoidance, time-slicing, synchronization) when scaling beyond simple two‑node links.