I am trying to set up a rule in RM. In the morning when it is cool here I want to set my wife's fan on low (8am - 10) Med (10 - 11:59) Hi at 1:00 pm
Turn off at 12:00 - 12:59
Turn off at 5:00 pm
And the rule will only be in effect Mon - Fri
So I am trying to control the fan speed so my wife does not have to keep changing the speed is this possible? Is this the right way to go about this?
UPDATE
screenshot
I think you are overcomplicating things by thinking of "between" instead of things happening at a fixed time. Your rule as written is only going to trigger three times a day, and you should set the level at each of those three times at whatever is appropriate. As shown, the conditions for 1-4 PM and 5-5:05 PM will never happen anyway.
I would also use presence in the logic somewhere. If she is not in her office, running the fan does nothing but waste energy. Fans don't cool a room. In fact, in an insignificant way, they add heat to the room. The breeze generated by a fan causes sweat to evaporate from skin, making you more comfortable.
2 Likes
Agreed.
The Required condition is good, but as @HAL9000 suggests, I would add a condition that your wife must be present for it to start.
Unless there is a need for this to all happen in a single rule, I would consider making one rule per trigger. The rule would only contain the required action. You could make the first rule, then just copy it and make the small changes needed, or create each from scratch.
Alternatively, you could do a single rule that triggers in the morning, then waits for the other times to run the speed change actions.
There are many ways to do this, each with its advantages and inconvenients.
2 Likes
I agree, my fans are just part of my lighting scenes, triggered by presence. Each scene has a fan speed associated with it, if there is a ceiling fan in the room. Scenes change through the day based on time triggers and illuminance triggers, and the current scene is activated by someone walking into the room when it is inactive. Fans go off with the lights when room goes vacant.
Scene changes cause the room scene to refresh if the room is already active, so if the scene changes while room is active, the fan speed changes to the scene speed.
1 Like
I just copied the low setting rule for the fan for the Med & High. I do not have presence sensor for her yet. Please let me know if this will work for now.
Is there not a way to add to the High rule to turn OFF at 5:00 pm?
1 Like
You can do this is one very simple rule as shown below. Hope this helps!
1 Like
That is perfect! THANK YOU!
You're welcome!
FYI - Just noticed in your screenshot above that there is no time on your last WAIT action. 
I don't know the answer to this, so I'm not challenging. Just curious.
What happens if you reboot the hub at, say, 9 AM? I would think the fan would continue to run until 8 AM the next weekday.
As long the hub reboots before the active wait statement, I believe it will work without any issue whatsoever. That wait statement simply creates a scheduled task to wake up the rule at that particular time. If the hub is down through the active wait statement, I am not sure what will happen.
Give it a try and let us know! 
2 Likes
Anybody know what this error means?
That error means that the current device driver type that device 261 is using does not have a routine called doubleTap(). Has the driver type for device 261 been changed?
1 Like
the GE Fan switch - no it has not been touched.
I wish I could help more, but I don't use Z-Wave devices any longer. Thus, I have no experience with that particular device/driver. Not sure if an App is trying to subscribe to double tap button presses from that device and failing? Did you try to configure an app to react to a double tap event from that GE Fan Controller device? just a guess.
Perhaps @jtp10181 might be able to offer some insight, as I believe he uses Z-Wave quite a bit.
That error means that something is trying to run the doubleTap method on that device and it does not exist in the code. Usually those methods are only used for simulating button events from the commands on device page. That driver may have never implemented that function when the commands got added to the capabilities.
This is the first day to test this rule. Everything worked as hoped for until 1:00 pm the fan did not turn on.
any thoughts why?
According to your log, the rule sent the action to the fan at 1pm.
There’s potentially a few reasons why the fan didn’t get the message.
Could be an issue with your z-wave mesh, could be an issue with the device.
The exact answer why can’t be inferred from the log screenshot.
1 Like
I installed this new Enbrighten 14314 today Saturday. Having the same problem with RM. It turns on the fan and changes the fans speed fine. However I can not get it to turn off in RM. Right now for my wife's fan I make a basic rule to turn it off and that works fine. It would just be nice to do it all in one place if possible.
I know the description says 1:00 this is just for testing. On at 12:15 pm and Off at 12:30 pm - of course did not turn off at 12:30
never mind I figured it out. Come to find out it was really simple - 