Morning. I have two apps I am trying to run, but IF both apps are running, neither will work. This is the first app, it controls the washing machine, or tells me when the wash is complete.
If I am running both apps, it will not work on either app. Can you have two waits, on different apps, going at the same time?
Yes, each rule had its own timers (scheduled jobs). You also don't need those last three actions in this Rule at all. None of them do anything: Exit Rule as the very last action makes no difference since you're already at the end, and your cancelations won't do anything where written because nothing will still be scheduled by then.
That being said, neither should hurt--just not necessary. One guess: if you cloned the Rule, maybe that "Cancel Timed Actions" still points to the original Rule and causes the oddity you see. (I know there were some surprises in the early days of cloning regarding this, but I'm not sure if anything has changed.)You can edit or remove and recreate the action to be sure. But since you don't need it at all, just deleting it should work.
Thank you. No, neither were cloned. If I stop one app, and pause it, the other one works, but if both are running, neither will work.
Here is the Dryer one.
Hmm. Not sure why then--again, each Rule has its own app state, including scheduled jobs. But you could still get rid of the last three actions since they don't do anything (but by the time they are reached also shouldn't cause problems--your notification should already be done--so I really doubt this is it).
Turning on trigger and action logging for the Rules in question would be a good way to see what is each is actually doing when and would be my best advice for troubleshooting more.
Ok, thank you, I will keep trying. Also I am finding the power feedback from the Wemo Insight plugs are taking a long time to refresh their status.
Also for the last three lines, if not included, will not work for some reason.
The last three lines would not have any effect in your Rule, so there isn't any reason they should be needed. ("Exit Rule" just stops running additional Rule actions but does not cancel anything already set into place, but there are no additional actions, so leaving it out would be the same. Even if it did cancel anything, there's nothing left at that point. The only timed action in your rule is the Wait for Event: Elapased Time, which will already have expired by the time you get to Cancel Timed Actions. You don't have any delays or delayed actions, so Cancel Delayed Actions does nothing not only here but at any point in the Rule. And none of these would be reached at all if your first Wait for Event: Power didn't happen--or if a re-trigger happened, which would cancel all waits and, in this case, start over with that first one.)
I would recommend turning on logging to see what you find.
can you test a notification before the voice notification? i wonder if they might be conflicting by trying to go off at similar times and causing issues. i know if i try to send commands to my echos too fast, it'll cause an error, but that's on the amazon side, nothing we can do about that
Thank you. I think I found the issue, was with the Wemo plug not being refreshed for 45 minutes. I changed everything, and will see if this works now. Thank you for your help
Download the Hubitat app
