I only have a few simple automation rules - all based on time of day, they stopped working a day or two ago. I've restarted the C7 hub - am using 2.4.3.176.
Where do I start with troubleshooting?
I would suggest also doing a reboot with advanced options -> rebuild database.
Afterwards, if they still donβt work, see if you have errors in the logs.
Do your actions take place when you click on the Run Actions button?
Have you checked that the time on the Hub is current and updating?
It's possible that your rules don't seem to be working because you no longer have access to the devices. Can you still control the devices manually from the device page?
I don't see a "Run Actions" button ![]()
date and time are correct
The devices can be controlled manually.
I'm trying that today - I'll need to deal with it later since I am painting our living room while stuck home in the snow!
I think the Run Actions button show in the Basic Rules app but not the Simple Automation Rules app...
You are correct. Simple Automation pre-date that feature.
Click the i icon on one of your rules and scroll to the bottom to confirm you have scheduled job at the time of day it is supposed to activate. If not this would be why they aren't firing and you can get those corrected by opening each rule and clicking Done.
Sorry about the confusion. When I received my Hub I immediately started using Rule Machine. The only other option I saw was Basic Rules which I thought were too "Simple" to be of any use.
Imagine my surprise when I learned today that there were rules even more Simple than the Basic rulesπ
So far you have determined that the clock is running accurately, so the rules should trigger at the expected times, and you know that you still have communication with the devices.
Have you done any Hub updates recently that coincide with the onset of this problem? I don't think many people use Simple Rules so a problem in a recent update might go unnoticed. If the other suggestions don't help, you might want to try and create a basic rule to eliminate the possibility that a bug was introduced in an update, causing the issue.
(newer) Basic Rules is the heir apparent to (older) Simple Automation Rules (SAR).
Although SAR is still available to be use, the staff does intend to provide any additional enhancements or fixes to it anymore (IIRC). Same story for (older) Motion & Mode Lighting app and (newer) Room Lighting app.
Does anyone know if any utility that can "migrate" the room lighting app entries into Rule Machine entries? I committed to that approach because I liked the compartmentalization of all lights in one place...Hum, maybe have a sub-category selection list option in a rule?
This selection list would allow you to select one option from the list (list managed by hub owner) to control sort order of rules). That way the rules could be sorted under Rule Machine in addition to just the title
as it is today. You could then see all the rules grouped by its target (switches, leak sensors, name (default as it is now), by trigger event, or any way hub owner would like their rules sorted, based on the items in the list they create. Right now the only way I know to do this is to prefix the title names with how you want them to sort. For me it is location. That is what drove me isolate the lights into one "group" using lighting app...so that all light related "rules" could be quickly identified.
Having the ability to quickly sort rules by their target action may be something others may find helpful?
Anyway, not that big of a deal to slowly re-create the lighting "rules" lol back in RM. Would like to avoid the manual effort if a conversion utility or other approach is already there.
Thanks,
Don
After reading your reply (and more about SAR and Basic Rules) I decided to migrate my SAR entries to Basic Rules - I only have 7 so it will be easy.
I created a test Basic Rule - simply turning on a bulb at a specific time - and it failed as well ![]()
I did test it with the Run Action button and it worked.
I triple checked the date/time since that seemed related.
I do not believe a hub update was done when this started, but I'll be doing a hub update this morning - to most recent 2.4.3.177 - just to see if that helps...
**update **
The update did not fix the issue of Basic Rules not working...
In that case I suspect that the scheduler is not working. Have you followed @ritchierich suggestions in post #8?
I agree that it appears the scheduler is not working.
The rule looks like it is scheduled but never runs...
update
I also now see that the OpenWeatherMap device that is supposed to update every 30 minutes is not - a manual refresh updates the weather but otherwise it does not update...
Are any of your schedule based automations working? Go to Logs \ Scheduled Jobs tab and see if anything looks off. Next Run should all be in the future.
Might need to have @support_team look at your engineering logs.
None of my schedule based automations are working ![]()
Have you gone to Settings \ Hub Details to make sure that the "Hub Time" is correct?
Yes - date and time are correct
my simple rules are working fine. have u tried rebooting the hub or re-saving the rule
yes - I've restarted a few times and re-saved the rule.
It looks like I'm having an issue with all/most of scheduled tasks - not just simple or basic rules...


