llms.txt
Compare with other sites' llms.txt files →# TOMMY
> Wi-Fi sensing for Home Assistant, Homey and Matter
TOMMY is a Copenhagen-based startup developing privacy-focused Wi-Fi sensing for smart homes. TOMMY detects people by measuring how they change Wi-Fi signals, so its sensors work without a view of the room and can stay hidden.
TOMMY has two products. Both use Wi-Fi sensing and both work with your smart home. The difference is the hardware.
- **TOMMY One** is a sensor you plug in and hide. It is coming in 2027 and not for sale yet.
- **TOMMY Zero** is software that turns ESP32 boards you bring yourself into presence sensors. It is available today.
All documentation under https://www.tommysense.com/docs is for TOMMY Zero.
## Products
- [TOMMY One](https://www.tommysense.com/one): Upcoming presence sensor you plug in and hide, coming in 2027. Turns into a multi-room presence sensor by pairing with Wi-Fi devices already in the home as passive devices. Detects movement and breathing, works completely offline with no hub, server, or cloud, integrates with Home Assistant and Homey. Sign up for updates and early access on the page
- [TOMMY Zero](https://www.tommysense.com/zero): Available today. Turns your own ESP32 boards into presence sensors. The server runs as a Home Assistant App or a Docker container, integrates with Home Assistant and Matter
## TOMMY One
TOMMY One is a sensor that you plug in and hide, for example in a cupboard, a desk drawer, or under a sofa. It turns into a multi-room presence sensor by pairing with Wi-Fi devices already in the home, called passive devices. Like TOMMY Zero, it works with zones that cover the space between their devices, from a single room to the whole house. Nothing is installed on a passive device, and the extra traffic is light enough that the device keeps working as usual. There is no hub or server, and no flashing with TOMMY Flasher or ESPHome.
- **Status**: Coming in 2027, not for sale yet
- **Detection**: Presence, from movement and breathing, so it keeps detecting people who sit still. Based on the ESP32-C5, so there is no separate motion mode
- **Zones**: Each zone covers the space between TOMMY One and its passive devices, through walls and floors. Each zone has a TOMMY One, which can be shared between zones, plus at least one passive device. No proximity sensing, so a TOMMY One without passive devices is not a zone
- **Passive devices**: Any stationary Wi-Fi device that can be kept awake, like a TV, speaker, game console, oven, or washing machine. Battery-powered devices, phones, and laptops are a poor fit. Added by IP address in the TOMMY One dashboard. Each zone runs on either 2.4 GHz or 5 GHz and can use passive devices on that band
- **Performance mode, network impact, and algorithms**: The same as TOMMY Zero
- **Home Assistant**: TOMMY integration via HACS or as a custom component, connecting to TOMMY One directly on the local network. One `binary_sensor` per zone
- **Homey**: Homey app. Each zone can start Homey Flows
- **Privacy**: Fully local and offline. Needs no internet access, no hub, no server, and no cloud. The license is stored on the device. Updates can be installed over the internet or manually from a file
- **Relation to mmWave sensors**: TOMMY One contains no mmWave radar and senses with Wi-Fi only. It can be combined with separate mmWave sensors. TOMMY One covers large areas through walls while hidden, and a separate mmWave sensor can be added where very subtle breathing is expected, like in bed, since its much higher frequency picks up more subtle breathing but is mostly blocked by walls
## TOMMY Zero
TOMMY Zero uses Channel State Information (CSI) from Wi-Fi packets to turn ESP32 devices into presence sensors. Two or more ESP32 devices in a zone continuously exchange packets. When a person enters the path between devices, the CSI shifts in characteristic ways (direct-path obstruction, multipath changes, Doppler effects, and scattering). The TOMMY Zero server interprets these shifts as presence for the zone as a whole.
TOMMY Zero integrates with Home Assistant (via MQTT) and any Matter-compatible platform (Apple Home, Google Home, SmartThings).
## TOMMY Zero: Getting Started
- [Introduction](https://www.tommysense.com/docs): Overview and key features
- [Quick Start](https://www.tommysense.com/docs/quick-start): What the free Trial Mode includes, the one-time Pro license, and the setup steps in order
- [How It Works](https://www.tommysense.com/docs/how-it-works): Full explanation of Wi-Fi CSI sensing, the sensing network devices form, and how zones map to smart home entities
- [System Requirements](https://www.tommysense.com/docs/system-requirements): Supported ESP32 variants, host requirements, mesh network notes
- [Before you buy](https://www.tommysense.com/docs/before-you-buy): The two biggest weaknesses of TOMMY Zero. It is closed source and needs an internet connection for license verification. Why it works this way, how the risks are kept small (traffic inspection, Network Bounty Program, offline activation if TOMMY shuts down), and TOMMY One as a fully offline alternative
## TOMMY Zero: Installation
- [Home Assistant Installation](https://www.tommysense.com/docs/installation/homeassistant): Install as a Home Assistant App (recommended) by adding the TOMMY repository via the App Store
- [Docker Installation](https://www.tommysense.com/docs/installation/docker): Run TOMMY Zero as a Docker container on a Linux host, with Docker Compose and docker run examples
## TOMMY Zero: Flashing Devices
- [TOMMY Flasher](https://www.tommysense.com/docs/flashing-devices/tommy-flasher): Browser-based USB flasher built into the dashboard. Handles firmware, Wi-Fi provisioning, and OTA
- [ESPHome](https://www.tommysense.com/docs/flashing-devices/esphome): Add the `sensor_tommy` external component to your ESPHome YAML. Compatible with all ESP32 variants
## TOMMY Zero: Configuration
- [Zone](https://www.tommysense.com/docs/creating-zones/zone): A zone covers the space between its own devices and becomes one motion sensor entity
- [Group](https://www.tommysense.com/docs/creating-zones/group): Several zones share one sensor, so each zone only needs one device of its own
- [Signal Stabilization](https://www.tommysense.com/docs/signal-stabilization): On adds stabilization to the signal for fewer false positives at the cost of detecting less. Recommended off for zones with only ESP32-C5 devices (presence detection needs it off), on otherwise. On by default
- [Performance Mode](https://www.tommysense.com/docs/performance-mode): Minimal (least network impact), Conservative, Performance, High Performance (catches fast movements like running or typing most reliably)
- [Detection Mode](https://www.tommysense.com/docs/detection-mode): Motion mode (all devices) vs. Presence mode (detects stationary occupancy via breathing, requires ESP32-C5)
- [Algorithms](https://www.tommysense.com/docs/algorithms): Choose a detection algorithm that fits your use case - Contained, Standard, or Radar
- [Network Impact](https://www.tommysense.com/docs/network-impact): What TOMMY Zero sends and how much airtime it uses, with example figures per zone size and how to minimize interference
- [Device Placement](https://www.tommysense.com/docs/device-placement): The dashboard recommends where to place the devices based on how many a zone has
## TOMMY Zero: Device Discovery
- [Automatic - Online Coordination](https://www.tommysense.com/docs/device-discovery/automatic-coordination-service): Uses TOMMY's coordination service for the device to look up the TOMMY Zero server's local address by pairing code and establish a direct local connection. Requires internet access on devices
- [Automatic - mDNS](https://www.tommysense.com/docs/device-discovery/automatic-mdns): Devices discover the server via mDNS (`_tommy._tcp.local`) on the local network
- [Manual](https://www.tommysense.com/docs/device-discovery/manual): Specify the TOMMY Zero server IP directly during flashing. Use when automatic discovery methods aren't available
## TOMMY Zero: Integrations
- [Home Assistant Integration](https://www.tommysense.com/docs/integration/homeassistant): Install via HACS or manually. Each zone auto-appears as a `binary_sensor` (motion) entity over MQTT
- [Matter Integration](https://www.tommysense.com/docs/integration/matter): Expose zones as Matter Occupancy Sensors and pair with Apple Home, Google Home, SmartThings, or Home Assistant via QR code
## TOMMY Zero: Licensing
- [License Activation](https://www.tommysense.com/docs/license-activation): How to activate a Pro license key, multiple zone key consolidation, troubleshooting
**Trial** - Free. 1 zone, up to 4 devices. Detection pauses 1 minute every 2 minutes.
**Pro** - One-time purchase. Unlimited zones, unlimited devices. 30-day money-back guarantee.
Commercial use requires a separate license - contact info@tommysense.com.
## TOMMY Zero: Comparisons
- [Comparisons Overview](https://www.tommysense.com/docs/comparisons): Side-by-side table of TOMMY Zero, Philips Hue MotionAware, and ESPectre
- [TOMMY vs Philips Hue MotionAware](https://www.tommysense.com/docs/comparisons/motionaware-comparison): Wi-Fi CSI vs. Zigbee signal fluctuation. TOMMY Zero adds stationary presence, MotionAware requires Hue Bridge Pro
- [TOMMY vs ESPectre](https://www.tommysense.com/docs/comparisons/espectre-comparison): Both use Wi-Fi CSI on ESP32. TOMMY Zero measures device-to-device signals for arbitrary zones, ESPectre measures the router-to-device link so zones are tied to router placement. TOMMY Zero is closed-source and paid, ESPectre is open-source and free
## Learn
- [mmWave vs Wi-Fi sensing](https://www.tommysense.com/learn/mmwave-vs-wifi-sensing): How mmWave sensors and Wi-Fi sensing compare on small movements, zones, walls, range, hardware, and cost, and when to use each
## TOMMY Zero: Roadmap & Community
- [Roadmap](https://www.tommysense.com/docs/roadmap): 2026-2027 - human vs. non-human filtering. Future - activity recognition, human identification, fall detection
- [Release Notes](https://www.tommysense.com/docs/release-notes): Links to full changelog on GitHub
- [Discord Community](https://www.tommysense.com/docs/community): Announcements, feature requests, support, roadmap discussions
- [Support](https://www.tommysense.com/docs/support): Community support via Discord, with tips for effective questions
## Key Facts for LLMs: TOMMY Zero
- **Technology**: Wi-Fi Channel State Information (CSI) extracted per OFDM subcarrier from 802.11 packets
- **Supported hardware**: ESP32, ESP32-C3, ESP32-C5, ESP32-C6, ESP32-S2, ESP32-S3
- **Minimum devices per zone**: 2 (diminishing returns after 4, minimum 1 m apart)
- **Bands**: 2.4 GHz (all variants), 5 GHz (ESP32-C5 only)
- **Network impact**: On a 5 GHz HE20 channel in minimal mode, a 2-device zone uses 0.77% of the Wi-Fi channel. A 4-device zone uses 1.62%. The dashboard shows a live estimate (https://www.tommysense.com/docs/network-impact)
- **Processing**: On-device CSI extraction, server-side sensing algorithm, fully local
- **Presence detection**: Detects breathing and micromovements. Requires ESP32-C5
- **Through-wall sensing**: Yes, devices can be hidden in closets or behind walls
- **Does not filter pets/objects**: All presence detected (filtering planned Q2 2026)
- **Privacy**: TOMMY Zero runs on your own hardware and all sensing data stays on your local network. It needs an internet connection for license verification and the optional Online Coordination service. If TOMMY ever shuts down, offline activation is released for every purchased license. The Network Bounty Program (https://www.tommysense.com/docs/network-bounty-program) pays €250 to the first person who finds an undocumented external connection in a release
- **Source**: Closed-source (https://www.tommysense.com/docs/before-you-buy)
- **Released**: 17 August 2025
## Links
- **Website**: https://www.tommysense.com
- **Company**: TOMMY Technologies ApS, Vesterbrogade 208, 1800 Frederiksberg C, Denmark. CVR 46902572
- **Contact**: info@tommysense.com
- **Full TOMMY Zero docs as plain text**: https://www.tommysense.com/llms-full.txt