I went to create a rule with a condition (sunrise/sunset - not a specific time of day). The condition was "false", and when I went to create a Trigger I could not - I had to go and make sure the condition was "true", then I could create the trigger. This is not what I would expect - I should be able to create a rule whether the conditions are true or false.
It might be best to show a screen capture of your rule, which includes any error message you are receiving.
From your description, you are trying to do something similar to the following screen capture. And as you can see, this is certainly not a problem.
I cannot create a new trigger (second screen).
Once the expression is "true", I can.
No error, just no ability to add a trigger.
Possibly a sunrise/sunset issue? I did not think to try that.
Seems to only happen on a sunrise/sunset conditional. I updated the original post to reflect this.
I am not experiencing the same thing.
It's odd that your "actions" window says disabled across the top. It doesn't really resemble my screen.
Edit Sorry I was looking at actions and not triggers.
When I exited the rule and went back into it I saw the triggers were dimmed out as your image shows. Then I realized that it was still in the trigger entry mode.
When I clicked on "cancel this trigger event" I was able to create a new trigger.
Perhaps it's possible that when you returned to the rule after adding the first trigger you were still in the data entry mode.
1 Like
Nope. I could not even enter the first trigger without changing the conditional.
I had a similar experience a few days ago. Had to fiddle with it before I could edit and change. I do not recall the details but something with editing and adding an additional trigger has changed in the last couple of hub versions.
Same here. Above describes same thing a few days ago with me.
Same but different for me (but still trigger related)....
I recently needed to replace a couple of rules that occasionally ended up stuck with Private Boolean in the wrong state (just a badly written rule). On the new rules I needed to make use of conditional triggers and I could not get them to save...
Each time I clicked the conditional trigger switch, picked the condition type and device etc, the UI just keep on deleting what I'd entered and I was back at square one. Similarly, if I created the trigger first then clicked the conditional trigger switch prior to leaving the screen, the trigger would get deleted. The only way I can manage to complete writing a rule with a conditional trigger is to:
- Create new trigger, select capability and device etc, click done
- Repeat for additional triggers
- Click done with trigger events to get back to the main rule screen
- Go back into triggers, click on the individual trigger
- Turn on conditional trigger and set capability, device etc as required
The above is the only way I can create a rule with conditional triggers. I have to first create the trigger and come back out to the main rule screen, then go back in again to complete it.
I hope that in Bruce's absence Rule Machine doesn't begin to self destruct/go awry with each platform update....
2 Likes
I've run into similar problems when creating a conditional trigger that requires a new condition to be defined. The whole trigger editing process resets once I finish defining the new condition (but the new condition is now part of the list, so not exactly back to square one).
I've been working around it by first creating new condition(s) in "Manage Conditions" in the Actions page. Too bad it's not directly available in the Trigger setup page, as this adds a bunch of extra clicks.
Any word on when/if he'll be back?
I just did a new rule again with a required expression and ran into it again. Don"t know enough to be able to tell you exactly what happens but I"m certain it will be easy to recreate as I have only made 2 rules with an RE recently and it happened both times.
Usually if you mention "Rule Machine" and "possible bug" it's a surefire way to get a response....
1 Like
