Rule Machine help with garage light automation

I have been trying to replicate the way my garage lights were setup in webcore over to Rule Machine, and can't seem to get it to work.

Z-wave Devices used in the automation:
Z-Wave switch that turns on the overhead lights
Quantity of 2 Besence ZWave overhead motion detectors
Quantity of 2 Monoprice recessed door contacts installed in both garage entry doors.

I am trying to get the lights to turn on as soon as one of the doors is opened, or when a motion is triggered, and turn off 1 minute after both doors are closed, and no motion is detected.

Currently the lights do turn on if the motions detect motion, but do not turn on when the door contacts change to open. What am I doing wrong. Any help would be appreciated.

Forgot to mention. In the rule I only have one of the door sensors setup to trigger. Once I get it to work I am planning on adding in the other door sensor.

I’m not sure why your rule is conditioned and defined by your lights being off. Is it possible that your two doors are reversed, and you’re trying to open the wrong one?

I use 2 rules to accomplish the exact same thing. One turns on the light whenever any of the doors or motion detector is opened/active. The other rule turns off the lights if all doors are closed and there is no motion for 10 minutes (use a delay with cancel).

Have you checked motion lighting controller for this? Seems like it’s more aligned to this task.

Yes, I actually started there. The problem I am having is that it is ignoring the door senor. Motion is working fine. I am starting to wonder if it has something to do with the device handler I am using for the Monoprice Recessed sensors. There doesn’t seem to be a direct match with any of them so I chose to use the “Dome Door/window Pro”, because at least with this DH, the open and close is reporting.

I looked at both Simple Lighting and Motion Lighting, but neither seem to be able to combine motion detectors and contact sensors, unless I am missing something.

I believe I have reduced my two rules down to one (as I have improved my RM skills over the past few weeks!). Here is what my new single garage overhead light rule looks like. I have not tested every condition, but I believe it works as desired.

Thank you. I am going to play with this this morning and hopefully get it to work!

1 Like

Even this very simple “Simple Lighting” app won’t turn on the garage lights when the door is opened. I can see that the contact is opening in the device handler screen. Maybe I need to uninstall simple lighting and RM and reinstall? Or maybe its because I don’t have a great match for DH. I am using the Dome contact pro DH, but am using a monoprice recessed sensor. I am using this DH because it correctly shows the open and close state changes.

Forgot to post this in the last reply.

I just found a new DH in this comunity that someone said works well with my recessed sensor called “Aeon Recessed Door Sensor”. I am now using this DH, and it seems to be perfectly compatible. It is reporting battery and correctly reporting contact as open or closed when I physically open and close the door.

In the device handler screen, in the “In use by” section, it does have the “Turn On Garage Lights when Office Garage Entry Opened” simple lighting rule listed.

The contact current state is changing to accurately reflect the door position.

Still does not turn on the lights using the above simple lighting app. Is this maybe a bug?

Try deleting and reinstalling the app, then building the automation again. Sometimes a setting gets stuck in the background somewhere and it’s hard to diagnose.

Got this figured out! After deleting and reinstalling Rule Machine, Simple Lighting, Button Controller, and motion Lighting apps and reinstalling, the issue did not go away. The door contact would still not turn on the lights.

What fixed it was excluding the contact and then re joining it to the ZWave network. After that it started working right away.

Also, for anyone else using these recessed Monoprice Zwave contacts, RBoy Apps has a great device handler that is super easy to convert to Hubitat. I would share the code, but he charges for admission to his software, so this knowledge transfer is all I can do. I only needed to do a find and replace from physicalgraph to Hubitat.

I think his apps also have a no alterations licence, so I’m not sure that usage on Hubitat is actually allowed.:confused:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.