Curate at the source, not in Tempo

A noisy timeline is almost always a sending problem, not a Tempo problem. The order of intervention, cheapest first:

1. Filter at the source. An event that is never sent costs nothing. In Home Assistant, label the handful of entities you actually want and forward only those. In UniFi Protect, scope the alarm to person detection on the cameras that matter, not every motion. In Uptime Kuma, enable the notification on your critical monitors first.
2. Narrow the score. If a source sends a bit more than you want, the score can drop or downplay what you do not care about.
3. Hide in Tempo. Last resort: the source panel can hide a source you have decided you never want to see.

Home Assistant is the example that matters most here, because it can fire on nearly every state change in the house, hundreds an hour. The wrong move is a blanket automation pointed at every entity; the right one is a curated forwarder. Tag the handful of entities worth an event (a label like tempo, or an explicit entity list), then write one automation that POSTs only those to Tempo. You decide at the source what deserves a place on the timeline, and everything else never leaves Home Assistant. Widening later is one line; digging out of a flood is not.

A related habit: when two sources see the same device (UniFi sees a TV as a network client, Home Assistant sees it as a media player), pick the one with the cleaner signal and let only that one report it.

New to a source? Start narrow and widen later. It is much easier to add what you are missing than to dig out from a flood.