Finch on LoRaWAN

Real sensors on our wall measure things like distance, light, temperature, humidity, pressure and motion. Before sending, bitteiler compresses the data on each sensor's own microcontroller. This page decompresses it and shows you the readings and how many bytes were saved.

Live lossless compression is what is happening right now: the last 10 packets (Wi-Fi devices) or the latest batch (Finch on LoRaWAN) compared with their raw size. It reacts to what you do with the sensor. Data savings is the running total since the demo started: all bytes sent with bitteiler versus what the raw data would have been.

Our wall shows both ways bitteiler runs. Streaming compression (Finch on Wi‑Fi, Sparrow on Wi‑Fi): every reading is compressed and sent the moment it is taken, so the dashboard updates continuously. Batch compression (Finch on LoRaWAN): LoRaWAN devices may only send rarely, so the Finch collects several readings, compresses them together and sends them in one uplink about every 2 minutes. Both are 100% lossless; only the timing differs.

Every value you see is identical, bit for bit, to what the sensor measured. Nothing is rounded, sampled down or thrown away.

It depends on the data itself. Steady signals (temperature, a device sitting still) are predictable and shrink a lot. Sudden or noisy changes, like your hand over the sensor, carry more new information, so those packets shrink less. That's why we show a live number instead of promising a fixed percentage.

It depends on your sensors and your scenario. Every dataset has a hard limit: the amount of real information it contains (its entropy). No lossless compression, ours included, can go below that limit, and lossy methods only get past it by throwing data away. Because bitteiler is 100% lossless, it is built to get as close as possible to that limit, and our benchmarks against other compressors back this up. Ask us for the results, or test it on a sample from your devices.

Occasionally, when readings jump randomly, a packet barely shrinks at all. It's rare, and over a session the savings from predictable readings far outweigh it.

LoRaWAN devices are designed to send rarely to save battery and respect radio rules (in Europe, a 1% duty cycle). Want instant feedback? Try the Finch or Sparrow on Wi‑Fi, which stream every reading.

LoRaWAN payloads are capped (222 bytes at the fastest setting, as little as 51 bytes at long range). Smaller payloads mean fewer uplinks, less time on air, longer battery life and more devices per gateway. On the Finch on LoRaWAN page, the “Why fewer bytes matter on LoRaWAN” card shows how a raw batch compares with these limits.

No. Every reading is sent and recovered. Edge filters that send only “anomalies” throw data away and decide in advance what matters. bitteiler keeps the full history, so you can still analyse it later.

No. bitteiler is a software drop-in for the sensor's existing microcontroller. Your radio, protocol and network stay the same, and decoding happens wherever you receive the data.

Yes. Talk to us at the device wall, or book a call and send us a sample CSV. You can also estimate your savings with our calculator.