I also had some of these broken conditions and tiggers this AM on .119. I had done a swap apps device this AM after adding a replacement Zigbee device (replacing an existing device of the same type) and after the swap found both broken tiggers and conditions. No idea if the swap triggered them, or if they were already there. I deleted the broken triggers and conditions and things appear to be fine.
BTW - any update on my remaining broken rule? No rush, it's the weekend, but since you are here...
Put all of the actions in that rule in the Clipboard using Copy column, and select Export Clipboard. Create a new rule, open its Actions, and import that clipboard, paste into the Actions. See if that one says Broken or not.
Interesting. Perhaps the label on the rule itself should provide more information. It used to be that the only thing detected were actions that had devices ripped out. Now it includes conditions used in actions and Required Expression, and triggers and waits.
There's nothing wrong with 119. The Broken designation on rules is going to pick up some things it didn't before. But if a rule worked before, it will still work. @danabw's rule is an oddball -- but it still works. Only one I know of where it isn't obvious why it says Broken.
To the extent a rule ends up showing Broken Triggers or Broken Conditions that were invisible before those can simply be removed.
It has a broken trigger that doesn't show on the main page. Open Triggers, you'll see it. Just remove it.
I will try to figure out why it didn't show on main page.
It used to have a trigger for 8:00 PM, but evidently that was partially removed. In next release a case like this would show this below, but not Broken in the rule name. Then opening the Trigger page you'd see the broken trigger.
Thanks very much. You are correct - before Required Expressions were available in RM the rule had a time-based trigger which I had removed. Updated UI sounds good.
Actually, on thinking about it further, that was really some weird abandoned trigger that RM didn't remove properly. There is some code that cleans out things like that, and this one should be cleaned out. Since I have your rule, it's easy for me to test this.
I am only adding it as a data point because on occasion when I have clicked on conditions to edit one, I only have the option to Select capability for new Condition, not to edit or delete until I select a capability and then Cancel the condition.
That last was most likely the result of some previous insult to the rule, such as only partially defining a condition and leaving the page mid-stream. Chasing down these sorts of anomalies is most likely a fool's errand.
