Good day,
I am trying to create a rule that will turn on all lights in the house, if the back pation motion sensor detects motion between 11:02 pm (I turn off most outside lights at 11pm) and sunset.
I've tried creating this in both Rules Machine app and the Motion and Mode Lighting app.
Based on the log file, the motion sensor detects motion and triggers the Motion and Mode Lighting rule:
But the lights do not come on.
Below is a screen shot of the rule:
Would appreciate any insights that anyone has.
Thanks
Paul
PS Grandchildren are here today until Sunday so I am not sure how responsive I will be.
What is app:204? I'm guessing the Motion Ligthing app? (You can filter Logs to just specific apps or devices to make their entries easier to find.) If so, it looks like it's sending the "on" command to the device, so you probably don't have a problem with the app. More likely, you have a problem with the device. Leave the app out of the picture for a second and just try to turn on the devices directly from their device detail page. Does that work? If not, no app is going to work either -- any of them just run the same command.
This will help you figure out where to start troubleshooting, but if it's the device, knowing more about them would be helpful (manufacturer, model, or at least protocol, etc.).
Yes App:204 is the rule created in the Motion and Mode Lighting App.
All the lights turn on at Sunset and off at 11pm based on a rules I have created in Rules Machine. So I think the devices are working properly. Based on the device details page, i can trigger on/off of any of the switches or smart plugs. They are all ZWAVE
The Motion sensor is a Hue Motiion Sensor and is Zigbee.
While I was trying to figure out the issue, I created a test rule to to turn on 1 light of motion is detected. That works fine:
It seems to have something to do with the condition I have set that I only want it to trigger between 1102pm and Sunrise.
Thanks,
Paul
I don't think so. The app logs say the app is trying to turn them on. And you said you had a problems with another app, too. Is it possible that the devices are just working inconsistently? Any problems with other Z-Wave devices ever? Any "ghosts" or other concerns (How to Troubleshoot Z-Wave | Hubitat Documentation)?
I can't get it working with a Rules Machine app rule (which i have Paused) or in a Motion and Mode Light app rule.
Not ghosts...
Occasionally when my Rules Machine app to turn on lights a Sunset is triggered, not all lights come on. I either get Alexa to do it or go into the Hubitat app and turn it on from Device page or the dashboard.
I erased the "Options for Activate, Disable and Enable Light-On" section. I triggered motion and all the selected lights came on:
Not sure if I have configured the settings within the section I erased properly.
I really don't think you have an app problem, as all the app logs you've provided suggest that the app is working as expected. This leaves us back with the device as the most likely culprit, unless you can find other suspects.
However, this:
Seems to answer this question:
It's possible you just have good luck when you run the commands manually and the app has bad luck when it does. If you tried more times, it's possible you'd run into the same.
But there's no reason to guess: go to the device detail page again, then go to the "Events" tab. Look for entries with "command" under the "Type" column. This will tell you what command was sent (e.g., command-on or command-off), what app did it (your Motion Lighting instance, for example), and when. You have app logs that already suggest everything is fine with the app, but if you wanted one more way to verify, you can check that the driver actually got the request to send the command by checking this way. (It's also a good trick to know if you happen to have logging not enabled when you need to know this information.)
I'm guessing you'll see everything was good there. If not, app logs at that particular time should provide more clues (Motion Lighting won't say it's turning something on if it's not, but it might say why). And if it's the device that's the culprit, we're back to device troubleshooting. If these are all Z-Wave, the doc I linked to above would be a good place to start.
