Camera-based hive monitors mount a small lens above the landing board and run a lightweight object-detection model on every frame. Each bee that crosses the board is picked out as a bounding box, tracked frame-to-frame, and classified as moving inward (returning forager) or outward (departing forager). Counting these crossings over time builds an activity index — a proxy for foraging intensity that beekeepers use without opening the hive.
Because raw video is far too heavy to stream continuously from an apiary with no reliable internet, most production bee-counters run detection directly on cheap edge hardware (a Raspberry Pi or similar) and upload only the resulting counts — a few kilobytes per hour instead of gigabytes of footage.
A camera watches a hive's landing board, detecting each bee that crosses in or out, drawing a live bounding box, and rolling those detections into a running activity index — just like the small edge-computing devices real apiaries use.
Bees crossing the green detection zone trigger a simulated model pass: a confidence roll against your threshold decides whether the bee is flagged (green box) or missed (red dashed box), and every detection feeds a rolling activity chart on the monitor panel.
Raise the traffic rate to see busier crossings, lower the confidence threshold to see more false negatives, and flip on low-light / IR mode to see how poor lighting degrades detection — the same trade-off real hive-cam hardware has to manage.
Production bee-counters typically log only aggregate in/out counts from an edge device rather than streaming raw video, because a rural apiary rarely has the bandwidth to upload continuous footage.