👻👻👻👻👻👻👻👻👻👻

Another release about false positives, which I would like to call the last one in that run, except I said that last week too.

A dashboard card that refers to its own row as config.entity was being told that entity does not exist. RFLink drives a doorbell with device_id: ev1527_0ddf80_0e, a protocol address, and Spook reported it as a device that had gone missing. Areas that exist purely so a robot vacuum can be sent round them were offered up for deletion, because they sit in a repeat and are therefore the target of nothing. That last one was in the empty floors and unused labels checks as well, so all three changed: being named counts now, not only being targeted.

Two things arrived. An action to change a label without deleting it first, which until now was the only way and took the label off everything it was on. And a repair that notices the same dashboard resource listed twice, usually because a custom card was updated by adding a second line instead of editing the first. The browser loads both, the card tries to register itself twice, and the second attempt throws. What you see is a broken card, so you go and look at the card rather than at the resource list.

Developer Tools is Settings > Tools now, and Spook was still saying the old thing everywhere. That is corrected, along with a handful of screenshots that described the wrong action entirely and one page that was missing altogether.

There was also some work on what the tests actually prove. Several of them checked themselves against the same list they were guarding, so taking an entry out of it took it out of the yardstick too and everything stayed green. Nothing you can see from the outside, but it is the reason some of the above lasted as long as it did.

Thanks to everyone who reported something this week. Four of these fixes exist only because somebody took the time to paste in their configuration, and in two cases the thing that cracked it was not the part the reporter was pointing at.

../Frenck