Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart

[CatmanV2]

No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.

Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?

Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.

I guess it's something of an edge case so no huge issue.

TIA!

C

[gwp1]

@CatmanV2 in my (recent) experience, as soon as a ruleset or reaction attempts to run that's missing something it will alert and then mark it in the list of rulesets/reactions.

Then you go thru and correct it.

[tunnus]

@gwp1 this is also my experience, so maybe the enhancement here could be that MSR would check reactions for missing entities even before they are run. That way you could spot those faulty reactions earlier (catching also rarely run reactions).

[CatmanV2]

@gwp1 Yes, but by that point, the reaction has failed. And if it's something like 'turning the lights off because I'm in bed' I'm too lazy to want to get out of bed and find out why

@tunnus exactly that. Sort of like a 'dry run' option in SQL. Tells you what's not going to work in advance.

C

[therealdb]

I did a "replace script" that's parsing JSON files and replacing references. Every time I change a device (i.e.: I pair a new Zwave device or replace some Wi-Fi thing with ZigBee/Zwave), I run it with old device and new device as params. Back in the days I mostly did it manually.
Here's the todo list:

• Stop reactor
• Copy storage folder (and make a backup)
• Search for the old device ID and change accordingly
• Save files, copy to storage folder
• Start Reactor again

I agree a much needed feature will be the ability to filter rules by device. At least you'll easily spot the ones not used in code blocks and that will be useful when you don't remember the exact rule that is doing something with a particular device.