Fixed
- Low-battery suggestions for different sensors no longer hide each other. When the model proposed a low-battery idea without citing a machine-readable entity — common when it names the device only in prose — every such proposal was filed under one identical internal label, regardless of which sensor it was about. The first one through claimed the slot and later ones for other sensors were silently discarded as duplicates, so a second device's dying battery could simply never reach you. Those proposals are now told apart by their own wording, so proposals that name their sensor stay separate. Two proposals worded identically still count as one, and re-proposals whose text carries a changing reading ("battery at 12%", then "11%") can still show up more than once — both are being tracked for a follow-up. Reported by @hruba202 (#571); fix contributed by @hruba202.
- A low-battery proposal for a lock, alarm panel, or door/window contact is no longer mistaken for an unrelated one. These devices report battery through a companion sensor the proposal does not always cite, and a fix for the case above initially stripped them of their "low battery" identity — which would have let any other unlabelled suggestion about the same device displace them, or them displace it. Whichever arrived first would win and the other would vanish. They keep their own identity, so a dead alarm-panel battery is never swallowed by an unrelated suggestion about the same panel.
Note: after upgrading, low-battery suggestions you had already dismissed may reappear once while their stored identifiers migrate to the new form; they settle after a single Sentinel run.