Ok set a Trigger of When Away Mode is enabled.
Set Action Turn on Zigbee Socket to power an internal Eufy Camera at the Front Door
How do I complete the rule?
I seem to have only one option Cancel this action.
Clicking around the window does not invoke the Done button.
Any other actions I can take to complete this rule or is it just crash out of, Delete it, and start all over again?
Since it's a pretty short rule I'd try deleting it and recreating it. If you need to, you can use the little gear in the upper right and delete it from there.
I recreated as a Legacy Rule no problem.
Reverted the 6 RM5 rules back to Legacy, will wait for a later update to stabilise before migrating/creating Rules in RM5.
RM5 brings a lot of benefits, so looking forward to it.
Ah ok. Was it happening on more than 1 rule? I have been using RM5 for a while and have not seen that issue.
Have you tried canceling? 
(And then seeing if it lets you re-add this action.) I can't see any reason they should have happened in the first place from your description, so this is just an attempt to answer the question. And I'd probably follow the recommendation above to just re-create the rule to see if that "fixes" it--both because it's usually not good when the RM UI gets confused and because if you've fond a reproducible problem (i.e., these exact steps make it happen again), staff should be able to use that information to identify and fix the problem.
I don't think this stems from a bug in the code (how many rules are out there that turn on switches?). More likely, this stems from a browser issue (clearing cache might help) or a bad element in the database. I've seen things like this happen from time to time that have no explanation. Cancel the action, make another one. If it happens again, delete the rule, and make another one. If it still happens after that it's time to look at Backup, Soft Reset, Restore to cleanup the database.
I've seen this happen with Rule-4.1 also -- it's not a characteristic of Rule 5.0. Every time I've seen it, it clears up right away through deleting the action and redoing it.
What browser are you using?
Safari
Safari is always a problem browser. Try Chrome...
This one stuck in a v4.x RM.
I think I am seeing where the issue is.
If I edit a Rule and say Insert a Simple Conditional, realise the Simple Conditional won't do what I need the Conditional is more complex so select the Cancel (or whatever the button is) the edit is now screwed - pressing the cancel button totally crews the pooch, I am then left in the cup de sac of another option where you cannot go back and you cannot go forward - the only option is to delete and start all over again.
Now if that is Safari messing it up I will try the same scenario with Chrome (albeit having its own issues)
What happens if you carry on and define a simple conditional and click done.
Can you then go back into the rule and then delete that action to get you back to where the rule is now editable?
I think, not sure, I've seen similar things but completing, albeit something that is not required, the process allows me then to delete it and carry on. (If that makes sense 
).
As for RM5.0 being 'unstable', I'm not seeing that. In fact I've moved all my RM4.1 rules to RM5. I class it as a refresher and an opportunity to rationalise my rules and, hopefully, make them more efficient.
Yeh repeated the issue of HE leaving Rule in a Cul de sac with exit on Chrome.
So Chrome is bad for HE as well which other browsers do you want me to test?
The issue I am seeing on both Safari, Chrome and RM4.1 and RM5.0 appears to be using the Cancel button, pretty sure it is the Cancel this Condition or could be Cancel this Action.
I have limited time to debug further, but as it is consistent across Browsers I do not think it is a Browser issue.
Certainly occurs more during Editing/ change mind during creation, so would suggest being VERY clear about what you are creating in a RULE BEFORE doing it or risk corrupted rules.
@bobbles That is a good point, and completing it - albeit wrong, is better than pressing the Cancel This Condition. Then return and delete it later.
I have about 50 Rules in RM, I migrated 7 of them, 2 corrupted (1 Broken Action, and one Cul de Sac), other issues around Paused not consistently showing in Apps View, and Variable management is more complex, unnecessarily so.
So have migrated 6 of them back to Rules 4.1, which I am assured will not be end of life, so no rush right now 
Will try again after next update because RM5 brings a lot of benefits
Seeing some mention of Safari, keep in mind that Apple requires (at least the last time I checked) browser vendors to use its core libraries for a large part of the undercover work when running on its devices which is why some browser features aren’t completely supported on their platform.
Well the issues are occurring on Chrome too.
So it looks like I have to find a way to run MS Explorer on my Mac to manage HE 
Once you start a Simple Conditional, you have to finish it. Give it any condition, and define any action, then you can delete the action. No doubt the ability to bail earlier would be nice, but it just isn't there.
Yeah, it annoys me too. There's some reason in the code about why it's hard to deal with... But, I will look at it again.
Sorry- I should not bait a developer .....
But explains where I have fallen over....
Will avoid using Cancel Buttons - check
The only reason I have run into issues this week is because I am adding new logic to handle vacation time while we are away from the house.
Many years ago, when I was working as software tester, I had one developer, Kevin, who whenever an issue occurred in his code would immediately declare the issue, while consistent and repeatable, was not occurring on his dev PC. So we priced up a special version of the software called the Kevin Release - which included a clone of Kevin's PC. A bit expensive and costly to ship, did actually work.
As far as I know, this is the only place in the UI with this problem.
Download the Hubitat app
