That is usually caused by aborted/improperly saved rules. You should be able to click on the rule from the 'In Use' list
And then remove it properly.
When on Wed? 12:00:01 AM? It has to be sometime, doesn't it?
In RM3, the restriction was just Wed, and the action would define when it would run.
If that is not possible in RM4 then fine, I was just curious
Thanks
Rick
Maybe I am not following. If I select a device, view the in use by, then select one of the rules, I don't see the device in question as being part of the current rule
For example, take this VS, Garage Door Open - At Sunset
Here is the Garage Door Open - At Sunset rule, no where is the VS to be found. Now, yes it was part of the rule at one time when I was using the VS to test. However once it was removed from the rule, IMO it should no longer be part of the In Use By.
My guess is, since its part of the Manage or Create Conditions, that is why its part of the In Use By, however I could be wrong
Rick
It was in use by that rule before, right? And you changed the rule? Deselecting a device doesn't "erase" it from where the device thought it was in use. Removing the rule would do that though.
That's my point Bruce, Was in use by is different than Is in use by
I don't recall this being the case in RM3, could be wrong however
Thank you for responding... even on a Sunday when most developers aren't working. You guys rock 
Rick
Edit: In one case with this VS, it was still associated to a Rule that no longer existed (not showing in the RM list). When I selected the rule from the in use by list, it did display the missing rule with a missing action, deleted it and now it's gone
This has always been the case in pretty much every app. Don't put so much energy into these little details, they will drive you crazy -- and by extension, the rest of us.
3 Likes
@bravenel Hey Bruce, we're getting close - but just observed an unexpected outcome.
Here's the current incarnation of my rule:
Here's the log from Master Bath Shower Light - it shows the light was turned on at 9:12. Off at 9:29. On again at 9:29.
Here's the log from the rule - it shows expected action at 9:12. At 9:29 it was triggered again, but at 9:32 the original 20 minute delay ended and turned everything off. So, seems "Cancel Delayed Actions" didn't cancel the original delay?
You didn't select Cancel for the Delay.
Trigger Events: Fan, Light, Hot Water any On
Actions:
On: Hot Water
Set BathHot to true
Cancel Delay
Delay Actions 20:00 Cancel
IF (DishHot = false) Off: Hot Water
Set BathHot to false
I figured it was something simple I missed. Thanks!
@bravenel So, given the power of RM, especially with 4.0 now, curious as to the thought of "doing everything" in RM versus doing some things in RM and other things in say - Simple Lighting, Notifications, and Motion Lighting (maybe others too).
Is there any benefit to using one app vs many? Or maybe a detriment from having more RM rules all running?
So, back to the original question... is it feasible to get all this logic into a single rule? I now have 3 rules and I believe they are working as desired now (will still monitor).
I looked at combining these using changed of the 4 devices as trigger, but then thought the cancel actions would mess each other up - maybe. Here's what I have:
My advice is to always use the simplest tool that solves the need. I have almost 30 instance of Motion Lighting, and wouldn't dream of doing those in RM. I have instances of Simple Lighting as well, and push those things that it supports there. There is no downside to having as many rules as you want, as many Motion Lighting instances as you want, etc. When you say "all running", you really mean that they have a live subscription in the database for events that trigger them. They only run now and then. Those subscriptions in the database consume no resources (well, a tiny amount of storage in the db, its caches, etc.).
1 Like
Why bother? Don't fix it if it isn't broken.
1 Like
The fact that you're typing rules that way, rather than providing screen shots, is an excellent example that it would be highly beneficial to users to provide a textual interface for writing & debugging complex rules.
If you had any idea how many rules I create on any given day you'd have more understanding for why sometimes its easier to just type something than to create a rule, take screenshots, etc. Besides, how do I get a users devices into my rule? Should I also create some virtual devices to set it all up? The idea is to give help to someone who needs it. Not disputing that there could be better user interfaces than what we have. That's a never ending possibility --> seeking an ever better way to define automations. You haven't been around to see the progress in the RM UI over the past several months.
Having said that, what you're asking for is not a small undertaking, in fact, it would be a rather large undertaking. There are UI projects of higher priority than more UI work on RM. Our focus has to be on helping people new to home automation, not on making things slicker for people able to deal with RM.
But thanks for the encouragement! 
5 Likes
Has anyone else noticed that you cannot select two different types of speakers for notifications for an RM4.0 action? Any time I combine Google Home and Echo devices on any single action, it completely fails. If I separate them into two different actions, then they play fine. This also seems to impact me if I try to use the "Follow Me" app/driver stuff. If this is a limitation in the core architecture, is it possible to have RM simply give you a drop-down of "what type of speaker?" then have that auto-populate a list of similar-class devices that will not break the automation? I have been fighting this for a bit, and feel silly now that I figured it out.
This the first I've heard of this. Will investigate...
Oddly enough, I just blew away all my speaker integrations and re-created them from scratch. Now they seem to be playing nicely. Very odd. Echo+Sonos+Google Home. If somehow logs on my end would help, I'd be glad to provide.
