A DIY beacon tag for your key ring: finding lost keys in a forest
Contents 11
A small tag for your key ring that transmits a signal now and then, so that lost keys can be found in a forest or in grass. Your own, with no accounts and no one else's network. In this article:
- why build your own tag when ready-made ones exist, and where it falls short;
- two approaches: Bluetooth (search with a phone) and 433 MHz (heard further away, search with a receiver);
- which radio module to buy (CC1101 or RFM69), how many, and which lasts longer on a battery;
- a battery calculation for both;
- ready-made tags on Apple's and Google's networks: can you build your own for these networks, and is there a tag for every phone;
- how to search on the ground: "warmer, colder", a directional antenna and a signal strength map with GPS;
- what you are allowed to transmit;
- the case, the colour, and what to check once it is built.
First part: can you find a lost car key with a 433 MHz receiver.
draft — written before building; places for our results are marked [TO ADD]
In short
| Question | Answer |
|---|---|
| What the tag does | once a second (Bluetooth) or every 5–10 s (433 MHz) it sends a short packet with its ID; nothing else |
| Bluetooth or 433 MHz? | Bluetooth: search with any phone, heard at 10–30 m; 433 MHz: heard further, but you need your own receiver |
| How long the battery lasts | Bluetooth on a CR2032: one to two years; 433 MHz on a CR2032: a few months, with a bigger cell a year or more |
| How to search | walk and watch the signal strength: it grows as you get closer; a directional antenna shows the direction |
| Ready-made Apple and Google tags | other people's phones find them, but each tag is on one network only; your own tag on these networks only unofficially; no tag works with every phone |
| A "warm / cold" map | a program records signal strength with GPS and shows on a map where the signal is strongest |
| Is it legal to transmit like this | yes, in licence-free bands (2.4 GHz, 433.05–434.79 MHz) at low power; check your country's rules |
| Where to start | a ready-made nRF52 Bluetooth beacon board: cheap, and you already have a phone |
Why build your own tag
Ready-made tags (AirTag, Galaxy SmartTag, Tile) are good, but for searching in a forest they have weak points:
- the tag's location on the map is updated by other people's phones passing by; there are few of them in a forest, so the last known location may be old or inaccurate;
- nearby, you look for the tag over Bluetooth, whose range is a few tens of metres at most;
- you need an account and a phone of a particular brand.
A tag of your own needs no account, but it cannot fix the rest on its own. What it does have: it is yours, it transmits as often as you decide, on the frequency you choose, and you can find it with your own receiver without any network. The honest downside: it has no network of other people's phones (except unofficially and with risks, see below), so you will have to search for it yourself, in the area where you lost it.
What the tag must do
| Requirement | Why |
|---|---|
| key ring size | otherwise nobody will carry it on their keys |
| battery life of at least a year | a tag that needs frequent charging will be flat on the day you need it |
| heard at tens of metres in a forest | first you have to get within range; after that it is "warmer, colder" |
| water resistance | the key may lie in wet leaves for a week |
| a bright colour | once the signal has brought you to the spot, the last metre is found by eye |
| a random tag ID | the packet must not identify the owner; we never publish the ID |
⚠ Even a random ID, if it never changes and is on air every second, lets anyone with a scanner recognise the tag, and so the person carrying it. That is why the packet carries no human-readable name, and the ID can be changed from time to time, or the tag switched off at home.
Two approaches: Bluetooth or 433 MHz
| Comparison | Bluetooth LE (2.4 GHz) | 433 MHz |
|---|---|---|
| what you search with | any phone with a Bluetooth scanner app | your own receiver: an RTL-SDR with a laptop, or a DIY handheld finder |
| range in a forest, roughly | 10–30 m; less on the ground under leaves | from a few tens to hundreds of metres at 10 mW, depending on the receiver and how the tag lies |
| through leaves and grass | worse: water in leaves absorbs 2.4 GHz well | better: the longer wavelength is attenuated less by leaves and grass |
| CR2032 battery | one to two years | a few months; a year or more with a bigger cell |
| complexity | a ready-made beacon board plus firmware | a microcontroller, a radio module and a receiver to search with |
| direction | with a phone, only by signal strength (and your body as a shield) | a directional antenna shows the direction |
🔑 Our plan: start with Bluetooth: it is the cheapest, and you search with the phone you always carry. Build the 433 MHz tag second, for range, and compare both in the field.
Ready-made tags that other people's phones find
A ready-made tag sends the same kind of short Bluetooth packet as ours, but millions of other people's phones can hear it. A phone passing nearby sends the tag's encrypted location to the network in the background, without its owner noticing, and you see it on a map. There are several networks, and each works only with its own tags:
| Network | Tags | Which phones report the tag's location |
|---|---|---|
| Apple Find My | AirTag; compatible tags marked "Works with Apple Find My": Chipolo ONE Spot, Pebblebee, Eufy SmartTrack Link and others | iPhone, iPad, Mac; you can only see the tag on an Apple device |
| Google Find Hub (Find My Device until 2025) | Find Hub tags: Chipolo ONE Point, Pebblebee for Android, Moto Tag, Eufy SmartTrack for Android and others | Android phones with Google services, unless the owner has opted out |
| Samsung SmartThings Find | Galaxy SmartTag2 | Samsung Galaxy phones only |
| Tile (Life360) | Tile tags | phones with the Tile or Life360 app — far fewer of them |
For searching in a forest they have the same limits as described above:
- there are few other phones in a forest, so the location is rarely updated. By default, Android reports other people's tags only in high-traffic areas, so in a forest Google's network is of little help;
- the point on the map is where someone else's phone was when it heard the tag, with that phone's GPS error plus the distance at which it heard the tag, so up to a few tens of metres;
- close up, you search for the tag over Bluetooth, just like ours. AirTag, SmartTag2 and Moto Tag (since 2025) also have ultra-wideband radio (UWB): on a compatible phone they show a direction arrow for the last few metres.
Can you build or reflash a tag for Apple's or Google's network?
Officially, no. Tags for Find My and Find Hub are certified by Apple or Google, and their firmware is closed. You can't change how often a bought AirTag or Chipolo transmits or at what power, or add anything of your own, and still have it work on the network and in the official app.
Unofficially, yes. There are open research projects for this:
- OpenHaystack (researchers at the Technical University of Darmstadt, 2021) and Macless-Haystack, which is based on it. A tag on an ESP32 or nRF51 / nRF52 sends packets in the Apple network format, and other people's iPhones report its location. You see it in your own program through your own Apple account, not in Find My.
- GoogleFindMyTools (2024–2025) does the same for Google's network: firmware for ESP32 and nRF52, with a Python script reading the location through your Google account.
- For Samsung's network we found no working open-source project.
What this means:
- plus: the firmware is yours. You choose how often and at what power the tag transmits, and you can add your own packet for finding it with a phone up close;
- minus: the interfaces are unofficial. Apple or Google can change them at any time, and the tag quietly drops off the network. You might not find out until the day you need it;
- minus: you can only see the location in your own program, not in Find My or Find Hub;
- minus: a tag on an ESP32 draws a lot of power (see why not ESP32), so the battery lasts weeks rather than years: the authors quote 2–3 weeks;
- minus: it uses someone else's network outside its rules, and your account may be restricted.
⚠ A home-made tag on someone else's network may not trigger the "unknown tag travelling with you" alert that iPhones and Android phones show. So it is for your own belongings only. A tag on someone else's things or car is stalking, and it can carry legal penalties.
Is there a tag that works with every phone?
No. There is no tag that both iPhones and Android phones look for at the same time and report to a network. Some tags are sold as "universal" (Chipolo POP, Pebblebee Clip 5 / Clip Universal), but they work either with Apple Find My or with Google Find Hub. You choose the network during setup, and to switch to the other one you reset the tag. According to the makers, Apple and Google don't allow both networks at once. If your family has both iPhones and Android phones, put two tags on the keys.
What really is shared between them is the warning about someone else's tag. Apple and Google agreed on a common standard, and since 2024 both iPhones and Android phones warn about an unknown tag moving with you, whichever network it belongs to, as long as the tag supports the standard. But the tag's location is reported only to its own network.
One more thing they share is Bluetooth itself: the packets of any tag, yours or a ready-made one, show up in a scanner app on an Android phone, together with the signal strength (an iPhone hides some of these packets). But ready-made tags change their Bluetooth address regularly, so picking out your own in the list is harder than with our tag and its fixed name. That is enough for searching up close, and for a map see the section on the "warm / cold" map.
Option A: a Bluetooth beacon on nRF52
The nRF52 microcontrollers (nRF52810, nRF52832, nRF52840) have built-in Bluetooth and are designed precisely to run from a coin cell: between transmissions they sleep, drawing a few microamps. Coin-sized ready-made beacon boards with a CR2032 holder are inexpensive, and some of them can be reflashed through their SWD pads.
Why not ESP32: it has Bluetooth too, but most of its models draw noticeably more and have large peak currents that a coin cell handles poorly. For a tag that should last for years, nRF52 is the better fit.
What the tag sends: a Bluetooth LE advertising packet once a second at 0 or +4 dBm. It contains a short tag name (not the owner's name) and a random ID. There is no need to connect to the tag: the phone sees the packet and shows the signal strength (RSSI) in dBm.
Searching: a Bluetooth scanner app on the phone (for example nRF Connect) shows our tag in the list together with the signal strength, which updates with every packet.
[TO ADD: which board we used, how we flashed it, at what distance the phone sees the tag in a forest and in grass]
Option B: a 433 MHz tag
Parts: a low-power microcontroller and a 433 MHz radio module that can send packets with frequency-shift keying (FSK), such as an RFM69 or a CC1101. The microcontroller sleeps, wakes the module every 5–10 s, the module sends a short packet with the tag's ID, and both go back to sleep.
What to search with:
- An RTL-SDR with a laptop or phone. The same receiver as in the article about the tyre pressure sensor. The packet is visible on the frequency waterfall, and the software shows the signal strength.
- A DIY handheld finder: the same radio module receiving, an ESP32, a small screen and a buzzer that beeps faster as the signal gets stronger. That is a separate project, but in a forest it is handier than a laptop.
⚠ A coin cell struggles to deliver tens of milliamps, and a 433 MHz module draws exactly that while transmitting. The voltage sags and the microcontroller may reset. A 100–220 µF capacitor across the battery smooths only short peaks; it will not carry a 20 ms packet. You need a battery that handles pulses (CR123A, AAA), or lower power or a shorter packet.
[TO ADD: which module and microcontroller we used, the power, at what distance it is heard in a forest]
Which radio module to buy: CC1101 or RFM69
Both are cheap 433 MHz radio modules that can transmit as well as receive frequency-shift keyed (FSK) packets. For our three jobs, receiving tyre pressure sensors, a beacon tag and an alarm with its own transmitter, we're going with the CC1101. The reason is simple: the ready-made ESP32 library that decodes tyre sensors and other 433 MHz devices (rtl_433_ESP) works with the CC1101 but not with the RFM69 (it also supports SX1276 / SX1278, found on some LoRa boards). One module type for every job means less confusion, and the firmware and radio settings are written once for every device. A caveat: the module receives only one modulation at a time, and tyre sensors transmit in FSK, so the library has to be built with the FSK decoders. Whether the CC1101 really decodes our sensor, we will check with our own measurement: forums have complaints about FSK reception.
| Comparison | CC1101 (Texas Instruments) | RFM69CW / RFM69W (HopeRF) |
|---|---|---|
| frequencies | 300–348, 387–464, 779–928 MHz, but the board is tuned for one | 315, 433, 868 or 915 MHz, each module for its own |
| sleep current | ≈ 0.2 µA | ≈ 0.1 µA |
| transmit current | ≈ 30 mA at +10 dBm | ≈ 45 mA at +13 dBm; ≈ 33 mA at +10 dBm |
| receive current | ≈ 15–16 mA | ≈ 16 mA |
| listening without the microcontroller | yes: the module wakes up and listens by itself (Wake-On-Radio) | yes, simpler: Listen mode (alternates sleep and receive by itself) |
| decoding tyre sensors on an ESP32 | yes (rtl_433_ESP) | no |
| libraries | RadioLib, ELECHOUSE_CC1101 and others | RadioLib, the LowPowerLab library |
| supply | 3.3 V only | 3.3 V only |
| price | $3–5 | $3–6 |
⚠ RFM69HW / RFM69HCW are the high-power versions, up to +20 dBm, and draw up to ≈ 130 mA. They are no good for a battery-powered tag: even a CR123A copes poorly with such pulses. If you go for the RFM69, take the RFM69CW or RFM69W.
How many you need:
| Experiment | Modules | Why |
|---|---|---|
| receiving tyre pressure sensors | 1 | the sensors transmit by themselves; the module only listens, together with an ESP32 |
| beacon tag + handheld finder | 2 | one in the tag transmits, the other in the finder receives (you can also search with an RTL-SDR, then one is enough) |
| an alarm with its own transmitter | 1 + 1 per sensor | one in the base receives, one in each sensor (door, motion) transmits |
Buy two or three more than you need: the modules are cheap, and it is easy to kill one with 5 V or while soldering. Five or six cover all three experiments together.
Which lasts longer on a battery. There is hardly any difference between the modules: both draw a fraction of a microamp asleep, and at the same power they transmit at almost the same current. Whether the battery lasts months or years depends on three things:
- how often the module transmits. A packet every 10 s is ≈ 60 µA on average (see the calculation). once a minute, about a sixth of that;
- which battery. CR123A, AAA or lithium AA cells handle 30–45 mA pulses better than coin cells;
- who listens all the time. A receiver that listens non-stop draws ≈ 15–16 mA: an AA cell goes flat in about a week, and in hours with an ESP32. So the alarm base and the finder run from mains, a power bank or a rechargeable battery. Alarm sensors and the tag only transmit, so they run for years on a CR123A or two AAA cells. If a sensor also needs to listen for commands, both modules can wake up and listen in short windows by themselves (the CC1101 with Wake-On-Radio, the RFM69 with Listen mode): that stretches battery life to months, depending on how often the module listens.
What to search for on AliExpress:
- CC1101: search for
CC1101 433MHz module SMAorE07-M1101D 433. The board should have a square chip marked CC1101, a crystal and an antenna connector (SMA or a spring), and the listing should say 433 MHz. An 868 or 915 MHz module works poorly at 433: its matching coils and capacitors are chosen for its own band. - RFM69: search for
RFM69CW 433orRFM69W 433MHz. It is a 16 × 16 mm square module, usually under a metal shield, with a frequency sticker or mark. The contacts have a 2 mm pitch, so you need an adapter board to use it on a breadboard. - Check the pin pitch: 2.54 mm fits a breadboard; 2 mm or 1.27 mm only by soldering wires or on an adapter board.
- Don't confuse them with the "FS1000A + XY-MK-5V" pair for a dollar: it only switches the carrier on and off (OOK), its receiver is weak and needs 5 V. Fine for a doorbell, not for our jobs.
⚠ Both modules run on 3.3 V only, and their inputs do not tolerate 5 V. With an ESP32 (3.3 V), connect directly; with a 5 V Arduino, only through a level shifter.
Starter equipment: what to buy first
You do not need a separate device for each project. For the first check — whether it all works at all, what the range is, and whether we can decode our tyre sensors — two identical 433 MHz CC1101 modules with an antenna connector, two antennas and two ESP32 boards are enough. One module becomes the receiver ("base"), the other a prototype tag, and with this pair we test the link. In the first experiment the tag prototype carries a whip antenna and runs from a power bank: what matters here is range, not size or battery life. The spring or wire and a low-power microcontroller come later. We will buy the rest once the first experiments show the idea works.
| What | How many | Why |
|---|---|---|
| 433 MHz CC1101 module with an SMA socket | 2 | the base with an ESP32 and the tag prototype; together they test the link and range |
| 433 MHz whip antenna with an SMA plug | 2 | without an antenna the module is heard only a few metres away |
| ESP32 board | 2 | one for the base (tyre sensors, rtl_433_ESP) and the finder, one to drive the tag prototype; not for the finished tag — it draws too much |
Which versions are on sale. The same CC1101 chip is sold on different boards: some give more range, others are smaller. Below are the Ebyte E07 modules sold by the maker's own store (CDSENET on AliExpress); the specifications come from Ebyte's datasheets. Before buying, check the frequency (433 MHz exactly) and the connector in the listing.
Photo: CDSENET (Ebyte) store on AliExpress.
| Module | Antenna | Package and pins | Power; maker's range | Current: transmit / receive / sleep | Supply | What for |
|---|---|---|---|---|---|---|
| E07-M1101D-SMA | detachable, in an SMA socket | 15 × 28 mm board, two rows of 2.54 mm pins ² | 10 mW; 0.6 km ³ | 29 mA ¹ / 20 mA / 2 µA | 1.8–3.6 V | the base, the finder, first experiments |
| E07-M1101D-TH | a spring soldered onto the board | 15 × 28 mm board, two rows of 2.54 mm pins ² | 10 mW; 0.6 km ³ | 29 mA / 18 mA / 0.6 µA | 1.8–3.6 V | a tag prototype |
| E07-400M10S | IPEX socket or a pad for our own antenna | 14 × 20 mm, solders onto a board, 1.27 mm pitch | 10 mW; 1.5 km | 35 mA / 18 mA / 0.6 µA | 2.5–3.6 V ⁴ | a tag on our own board, antenna on an IPEX lead |
| E07-400MM10S | only a pad for our own antenna | 10 × 10 mm, solders onto a board, 1.27 mm pitch | 10 mW; 1.5 km | 32 mA / 18 mA / not stated | 1.8–3.6 V | the smallest finished tag |
| E07-433M20S | IPEX socket or a pad for our own antenna | 18 × 32 mm, solders onto a board, 1.27 mm pitch | 100 mW; 2 km | 100 mA / 20 mA / 2 µA | 2.1–3.6 V | a base or finder with more range; a tag only with a Li-ion cell and a 3.3 V regulator |
| E07-400MBL-01 | whip antenna in the kit | 53 × 27 mm USB board with an E07-400M10S on it | same as E07-400M10S | — | from USB | trying the module from a computer; not needed for our experiments |
¹ The E07-M1101D-SMA datasheet gives 100 mA for transmitting — most likely carried over from the E07-433M20S together with the receive and sleep currents (20 mA and 2 µA, exactly as there): the store photo for this same module says 29 mA, and so does the E07-M1101D-TH datasheet, with the same chip and power (receive 18 mA, sleep 0.6 µA there).
² Two rows of pins will not go into an ordinary breadboard: both rows land in the same strips and short in pairs. The module is wired with female-to-male jumper leads or put on an adapter.
³ The E07-M1101D datasheets contradict themselves here: 0.6 km in one place, 1 km in another. The maker's module pages and the store photos say 0.6 km; we take the lower figure.
⁴ This is the E07-400M10S's own datasheet; the shared series datasheet and the store say 1.8–3.6 V. We take the narrower range.
How to read the table:
- range in the datasheets is measured in an open field, with a 5 dBi antenna 2.5 m up, at 1.2 kbps. In a forest, with a spring antenna and from a pocket it will be several times shorter — which is why we check range by measuring it ourselves;
- "solders onto a board" means castellated (half-hole) pads along the edge at a 1.27 mm pitch: such a module will not go into a breadboard, so it needs our own board or an adapter;
- E07-433M20S has transmit and receive amplifiers (PA and LNA), so it both receives and transmits over a longer range. The cost is current draw: 100 mA while transmitting, three times that of the 10 mW modules. Even a CR123A handles such pulses poorly, so a tag with this module needs a rechargeable cell;
- the currents in the table are for the whole board, not the chip alone, so they are a little higher than in the CC1101 vs RFM69 comparison above (those are chip datasheet figures);
- E07-400MBL-01 is a development board: the module, a USB converter and its own microcontroller, with the pins brought out to headers. It is for testing the module from a computer; we work with an ESP32 anyway, so we can do without it.
Kits with an antenna. The same module is also sold with an antenna: "FPC" adds a 2 dBi flexible film antenna with an IPEX connector, "Rubber" adds a 3 dBi whip on an IPEX lead, and for the E07-M1101D-SMA a 4 dBi whip with an SMA plug. The film antenna is easy to stick inside a tag case; the whip gives more range. IPEX is a tiny connector rated for only a few dozen matings, so connect the antenna once and leave it alone.
⚠ Modules with "900" in the name (E07-900M10S, E07-900MM10S, E07-900MBL-01) are the same boards for 868–915 MHz; we don't use them — see above for why. Cheap unbranded green "CC1101" boards work too, but some of them are tuned for 868 MHz even when the listing says 433.
Detachable or soldered-in antenna. An SMA socket gives more range and freedom: you can fit a longer or directional antenna, or move the antenna out on a cable. The price is size: a module with its antenna is a palm-length whip that won't fit in a pocket. A soldered-in spring or trace keeps the tag small, but the spring is shorter than a quarter wave and is heard at a shorter distance. So for the base and the finder we take SMA, for the tag a compact variant, and we check the range by measurement.
Which 433 MHz antennas:
| Where | Antenna | Why |
|---|---|---|
| the base, the tyre sensor receiver | a 433 MHz rubber whip, SMA plug, 2–3 dBi, ≈ 15–20 cm | omnidirectional: picks up signals from every direction |
| the finder in the forest | the same whip at first; later a handheld 433 MHz directional (Yagi) antenna with 3–5 elements | the signal is strongest when the antenna points at the tag, which gives the direction |
| the tag (prototype) | a 433 MHz spring or a 17.3 cm wire | a quarter-wave wire (300 / 433 / 4 ≈ 0.173 m) is the simplest antenna, and a good one |
| the finished tag | a spring or a trace antenna on the board | compactness matters more than range |
⚠ Connector: Ebyte modules have an SMA socket (SMA-K), so the antenna needs an SMA plug (SMA-J). WiFi antennas won't do: they are for a different frequency, and their connector is often RP-SMA.
[ВПИСАТИ: which modules and antennas we bought, and at what distance the spring and the whip are heard]
Battery calculation
Average current = sleep current + transmit current × packet duration ÷ interval between packets. Divide the capacity by the average current and you get the running time in hours. The figures below are rough, from typical chip data. We will measure the real ones on the built tags.
| Tag | Transmission | Average current | Battery | Roughly |
|---|---|---|---|---|
| Bluetooth, nRF52, once a second, 0 dBm | ~7 mA for ~1–2 ms | ~10 µA | CR2032, 220 mAh | ~2 years |
| Bluetooth, every 0.1 s | the same, 10 times as often | ~70–140 µA | CR2032 | ~2–4 months |
| 433 MHz, every 10 s, 10 mW | ~30 mA for ~20 ms | ~60 µA | CR2032 | ~5 months |
| 433 MHz, every 10 s, 10 mW | the same | ~60 µA | CR2477, ~1000 mAh | ~1.5–2 years |
In practice you get somewhat less: a battery loses capacity in the cold and under large current pulses. That is why the tag should report a weak battery itself, by sending its voltage in every packet.
A CR2477 is a coin cell too: it handles 30 mA pulses just as poorly as a CR2032, so its real capacity will be lower than rated. For a 433 MHz tag, a battery that handles pulses is better: a CR123A (~1500 mAh) or two AAA cells.
[TO ADD: the measured average current of both tags]
How to search on the ground
- Get within range of the tag. Walk the route where you lost the key with the receiver or phone. As soon as the tag shows up, you are within its range.
- "Warmer, colder". The signal strength rises as you get closer. For a Bluetooth tag at 0 dBm, a phone typically shows about −60 dBm at a metre and −80 to −90 dBm at 10–20 m. An RTL-SDR shows relative signal strength: there, only watch whether it rises or falls. The signal jumps by a few dB with every step, so look at the average over several packets, not at a single number.
- Your body as a shield. Hold the phone or receiver against your chest and turn slowly on the spot: when the tag is behind you, your body blocks the signal and it is weakest. It is strongest when you face the tag.
- A directional antenna (433 MHz). A three-element Yagi for 433 MHz, about 35 cm wide, shows the direction much more clearly.
- Very close. Within a few metres the signal is so strong that it stops growing. Then lower the receiver gain, remove the antenna, or step back and approach from different sides. The last metre is done with your eyes and hands.
A "warm / cold" map: a program that records signal strength and GPS
Walking around watching a signal strength number is awkward: it jumps about, and after a few minutes you forget where it was higher. It's better to let a program remember. It records every packet it hears together with where you were standing, and draws points on a map: a strong signal is "warm" (red), a weak one is "cold" (blue). Once you have walked the area in strips, the warmest patch on the map is where to search.
What to record for each packet:
| Field | Why |
|---|---|
| time | to match the packet to the location and drop old records |
| latitude and longitude | where you were when you heard the tag |
| GPS accuracy, m | ignore points with poor accuracy (in a forest it can be 15 m or worse) |
| signal strength | in dBm (Bluetooth) or relative (RTL-SDR); this is what gives "warm / cold" |
| tag ID | record only your own tag, not every device around |
How to turn this into a map:
- Divide the area into cells of about 3 × 3 m and take the average or median signal strength in each. A single reading jumps by a few dB, but the average of several packets is steady.
- Colour the cells from blue to red. Leave cells where no packets were heard empty rather than "cold": nobody was listening there.
- Mark the warmest cell and walk around it again, slowly and in different directions.
What gets in the way:
- GPS in a forest is off by 5–15 m or more, so the map shows a zone, not a point. The last few metres are still "warmer, colder" and your eyes;
- your body blocks the signal. Hold the phone the same way every time, in front of your chest, and walk each strip in both directions so the effect of your body averages out;
- the phone scans for Bluetooth in bursts, not continuously. Walk slowly, or each cell will get too few packets.
What to build it with:
- for a Bluetooth tag, a phone app that listens for Bluetooth, takes the location from the phone's GPS and writes the result to a CSV file. A web page with a mapping library (for example, Leaflet) then draws the map. We'll write this app ourselves;
- for a 433 MHz tag, a laptop with an RTL-SDR and a USB GPS receiver, or an ESP32 handheld finder with a GPS module writing the same CSV to a memory card.
The records contain the places you walked, and if recording started at home or by your car, those addresses too. Keep them to yourself; before showing anyone the map or a screenshot, trim the start and end of the track.
[TO ADD: which program we wrote, what the map from the first search looked like]
What you are allowed to transmit
| Band | What is allowed, in general |
|---|---|
| 2.4 GHz (Bluetooth) | certified off-the-shelf Bluetooth modules need no separate licence |
| 433.05–434.79 MHz | in Europe, short-range devices, up to 10 mW e.r.p. (effective radiated power), transmitting up to 10 % of the time |
| other frequencies | not for home-made devices: other services use them |
Our 433 MHz tag sends a 20 ms packet every 10 s. That is 0.2 % of the time, well within the limits. Rules differ from country to country, so check them with your national regulator (in Ukraine, the NCEC).
⚠ The tag is for your own things. Secretly attaching a beacon to someone else's belongings or car to follow a person is stalking, and in most countries it is an offence.
The case
- Colour. Bright orange or lime green: the last metre is found by eye.
- Water resistance. A small box with a gasket, or a board potted in epoxy, leaving access to the battery.
- Attachment. A sturdy ring: a tag that has come off the keys will not help find them.
- Antenna. For 433 MHz, a piece of wire about 17 cm long, or a helical antenna if the wire gets in the way. Metal keys next to it detune the antenna a little; we will check how much.
- Display. The tag itself does not need one, but the finder and a fob from the same series will. Which displays draw almost nothing from a battery is covered in the article on displays.
Our experiment plan
| Experiment | What it will show | Result |
|---|---|---|
| Bluetooth tag: average current | how long the battery will really last | [TO ADD] |
| Bluetooth tag: range in a forest, in grass | at what distance the phone sees it | [TO ADD] |
| 433 MHz tag: average current, voltage sag | whether the battery copes with transmit pulses | [TO ADD] |
| 433 MHz tag: range in a forest, in grass | how much further it is heard than Bluetooth | [TO ADD] |
| a "warm / cold" map: signal strength + GPS | whether the map shows where the tag is, and how accurately | [TO ADD] |
| a "blind" search: someone hides keys with a tag | how many minutes a search takes with each tag | [TO ADD] |