I wondered why my (old) rule was no longer running then I noticed there is no trigger (there used to be). I tried to enter a trigger but can't because the trigger field is disabled. No idea how this happened nor can I figure out to re-enable it
(UPDATE: Just noticed that all my conditions are also disabled)
Hardware VersionC-8
Platform Version2.5.2.139
Can you share a screenshot of the entire page? Chances are it thinks you're in the middle of something, like creating a new trigger, that it wants you to finish first (if that specifically is the case, you'll see "Cancel Trigger Event" that will get you out, but it depends on what you really see, which is why I think the whole page may give more clues).
What about the "Select Trigger Events" page itself? (The whole page -- don't cut off any buttons at the bottom as in the one above, though I don't think there's going to be anything interesting on that one, so no big deal there.)
Disabling actions won't have any effect on this, by the way.
Well, that's a weird one. 
Nothing concerning there...
I might check other pages (actions, conditions, required expression and required expression conditions, etc.) for something similar -- something you may have been in the process of doing that isn't completed yet and can be cancelled or completed and might fix this problem, like creating a condition, editing a local variable, or something similar.
The conditions are all disabled as well. I found that after my 1st post. Actions, variables, etc are fine.
I ended up copying all the actions to the clipboard, created a new rule, added all the variables then imported the clipboard. That "fixed: the problem for this rule but..... what about next time.
UPDATE: While I could not edit any condition I could add a new one. Once I did everything was fine. I can now edit/add a trigger
THANKS EVERYONE FOR YOUR HELP
I was more asking if you saw a similar option to complete, cancel, etc. on those other pages (since there is nothing here but can be) that might help.
If you wanted to PM me an export of the rule (keep in mind it may have some hub-specific data visible that isn't in the UI, like other device names or previous selections you made), I can see what I can figure out. Otherwise, problems like these are rare and usually the result of something odd, like failing to complete some step in the UI (yours suggests you might have been adding a new trigger, possibly some time way in the past and possibly with some device or trigger/device type that no longer exists, for example -- or possibly something with a condition based on what fixed it for you), but it's possible something could be done to better recover from this if the problem is identified.
In any case, glad you figured out something for this one!
