Basic rule freaking out

Same here.

Well, it could be that it is the rule itself, waits, times/modes, or even the physical device itself causing this problem. Without narrowing it down to something, you are blaming Basic Rules (or waits) for what is happening. And maybe that is the case. There are certainly other bugs that have cropped up in nearly every app at one point or another.

It also could be that these devices have weak signal, and that is causing the problem. Or a very chatty device. I have seen that happen more than once. Sometimes Zwave will do this repeating thing if the mesh is weak.

So while it is frustrating, there may not be an answer if there is something unique to your hub, your devices, and so on. Maybe nobody else is seeing this?

So when you get time, do some testing and see if you can pinpoint the cause.

Well I created several very simple basic rules that do the same thing as my single basic rule did, and STILL the problem exists.
I have seen others with very similar problems whether it is the chatty device, or something happens with the hub.
The other posts I read are using other apps as well, and not basic rules, and they aren't using waits either.
Here is what happened tonight so far with my kitchen lights:
dev:4692021-06-03 19:58:27.695 infoKitchen NORTH light is 25% [digital]
dev:4692021-06-03 19:58:27.693 infoKitchen NORTH light is on [digital]
dev:4502021-06-03 19:58:27.673 infoKitchen SOUTH ceiling light is 40% [digital]
dev:4502021-06-03 19:58:27.670 infoKitchen SOUTH ceiling light is on [digital]
dev:4692021-06-03 19:58:21.811 infoKitchen NORTH light was set to 25% [physical]
dev:4692021-06-03 19:58:21.809 infoKitchen NORTH light was turned on [physical]
dev:4692021-06-03 19:58:21.793 infoKitchen NORTH light was set to 25% [digital]
dev:4692021-06-03 19:58:21.791 infoKitchen NORTH light was turned on [digital]
dev:4502021-06-03 19:58:21.781 infoKitchen SOUTH ceiling light is 40% [physical]
dev:4502021-06-03 19:58:21.779 infoKitchen SOUTH ceiling light is on [physical]
dev:4502021-06-03 19:58:21.665 infoKitchen SOUTH ceiling light was set to 40% [digital]
dev:4502021-06-03 19:58:21.663 infoKitchen SOUTH ceiling light is on [digital]
dev:4932021-06-03 19:58:20.564 infoKitchen under cabinet light was turned on [digital]
app:4912021-06-03 19:58:20.502 infoapp: When Side Yard motion illuminance is below 160 lux …
app:4912021-06-03 19:58:20.501 infoapp: finished
app:4912021-06-03 19:58:20.481 infoact: Set level Kitchen NORTH light 25
app:5522021-06-03 19:58:20.435 infoapp: When Side Yard motion illuminance is below 110 lux …
app:5522021-06-03 19:58:20.434 infoapp: finished
app:5522021-06-03 19:58:20.383 infoact: Turn on Kitchen under cabinet light
app:4912021-06-03 19:58:20.381 infoact: Set level Kitchen SOUTH ceiling light 40
app:5522021-06-03 19:58:20.379 infoevt: Side Yard motion illuminance 59
app:4912021-06-03 19:58:20.375 infoevt: Side Yard motion illuminance 59
dev:4272021-06-03 19:58:20.306 infoSide Yard motion illuminance is 59lux ****** trigger basic rule here ****
app:562021-06-03 19:58:00.276 infoMode set to Sunset from sunset -30 min

and here is the rule that triggered the lights:

I am not the only one experiencing this type of freakout with a device, and different devices as well.
Here is the thread:

Note the different devices/drivers/device control vs. a rule..... doesn't seem to be related to a specific hub/device/driver/etc., but the actual firmware the hub is running possibly.

Also note that it happened within the same minute! No wonder my hub becomes sluggish and non-responsive when this is happening!

Well I am now pretty much convinced that basic rules SUCKS!!!
I created a brand NEW rule:

And THIS rule acts NUTS also!
Here is the log for the change in time of day to 1700 hrs.:
app:6362021-06-12 17:00:01.261 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.260 infoapp: finished

app:6362021-06-12 17:00:01.246 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.246 infoapp: finished

app:6362021-06-12 17:00:01.245 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.243 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.229 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.208 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.206 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.205 infoapp: finished

app:6362021-06-12 17:00:01.188 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.185 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.129 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.128 infoapp: finished

app:6362021-06-12 17:00:01.099 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.097 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.080 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.078 infoapp: finished

app:6362021-06-12 17:00:01.064 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.061 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.052 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.051 infoapp: finished

app:6362021-06-12 17:00:01.038 infoact: Turn off Office printer light

app:6362021-06-12 17:00:01.035 infoevt: certain time , wait over

app:6362021-06-12 17:00:01.017 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:01.016 infoapp: finished

app:6362021-06-12 17:00:01.000 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.996 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.973 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.972 infoapp: finished

app:6362021-06-12 17:00:00.960 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.959 infoapp: finished

app:6362021-06-12 17:00:00.956 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.953 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.945 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.942 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.931 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.930 infoapp: finished

app:6362021-06-12 17:00:00.904 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.901 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.868 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.867 infoapp: finished

app:6362021-06-12 17:00:00.854 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.852 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.846 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.845 infoapp: finished

app:6362021-06-12 17:00:00.834 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.831 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.795 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.794 infoapp: finished

app:6362021-06-12 17:00:00.778 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.774 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.747 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.747 infoapp: finished

app:6362021-06-12 17:00:00.733 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.730 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.699 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.698 infoapp: finished

app:6362021-06-12 17:00:00.684 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.681 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.664 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.663 infoapp: finished

app:6362021-06-12 17:00:00.651 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.648 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.582 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.581 infoapp: finished

app:6362021-06-12 17:00:00.569 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.566 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.512 infoapp: When time is 10:00 …

app:6362021-06-12 17:00:00.511 infoapp: finished

app:6362021-06-12 17:00:00.499 infoact: Turn off Office printer light

app:6362021-06-12 17:00:00.496 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.331 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.318 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.317 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.314 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.303 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.300 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.279 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.273 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.253 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.254 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.250 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.244 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.241 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.238 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.236 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.220 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.204 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.195 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.191 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.189 infoact: Wait Until time is 00:00

app:6362021-06-12 17:00:00.166 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.163 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.144 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.142 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.124 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.121 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.118 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.116 infoact: Turn on Office printer light

app:6362021-06-12 17:00:00.110 infoevt: certain time , wait over

app:6362021-06-12 17:00:00.110 infoevt: certain time , wait over

app:6362021-06-12 12:00:00.368 infoact: Wait Until time is 17:00

You can't tell me that this is a problem with my rule!
It is a PROBLEM with HE and waits!!! and NO ONE seems to have any ideas as to what is causing this!

I was better off with X10! but wanted to "upgrade" to something that was supposed to be much better, and in theory, should have been, but is turning into a BIG fiasco and problem!

Tagging @bravenel

1 Like

Thank you. i didn't know how to do that and I hope he can shed some light on this strange problem.

Please post your logs as screenshot, not copy paste.

1 Like

There is something very odd going on with your hub, and I don't know what it is. I created a similar rule, and it works as expected. It seems as though you have multiple copies of the same rule running at the same time.

My suggestion is to follow these steps. Download a backup of your database. Perform a Soft Reset of your hub, using your MAC address as a password at hub-ip-address:8081. Following that, restore the hub from that backup.

Also, please post your Apps list for Basic Rule, and also the App Status page for this rule (gear icon).

3 Likes

basic rules part 1:


part 2

application status 1:


status part 2:

status part 3:

Thing is that this rule is brand new, never had anything similar or like it before.
I did the backup/soft reset/restore and the hub is up now.

I am getting very similar multiple log entries for a completely different rule.

and

This is the rule:

This is after I did the soft reset and restore backup that you asked for.

Sorry for the incorrect method to post log entries. I can see that it is difficult to read and takes alot of space and a screenshot is much easier to read.

1 Like

OK, we have identified the cause of this, and it is a bug. The bug has already been addressed for the next release. In the meantime, you may be able to work around it by breaking the rule up into pieces.

2 Likes

Thank You Bruce for looking into this!
I am happy that this was found as I was going NUTS trying to figure out why this was happening, as it affected alot of basic rules that I had originally used waits in.
I did alot of searching for this problem, but it didn't seem like my particular problem had been addressed, but there were a few SIMILAR problems.

I can break up my rules to eliminate my problem children.

Question... is it the "wait" that is failing, and is it only in Basic Rules with "waits" that are affected?
If so, does a "wait" in rule machine and/or Simple Rules have the same problem?
How did you find the bug? Just asking for my own troubleshooting knowledge in HE.

Once again, thank you for finding this and I will be awaiting the next release! It sounds like it has some nice features!

Bill

This only affects Basic Rule, and only Wait for Certain Time. This bug had actually been found and corrected a couple of weeks ago, and the fix will be in 2.2.8. The nature of the bug is that it was not cancelling the scheduled time for the Wait, so they would build up in the scheduler.

1 Like

AHHA! Well good that it was found as it is a nice feature (for me at least), and makes sense as to where all the "waits" were coming from within the same second sometimes.
It looked like it was random as to whether or not the repeating would happen, and how many times it would "loop".

This also seemed to really bog down the hub for doing other things while the loop was happening, but is difficult to see because of the randomness, but I did notice that response time for other basic rules, and operation in general, seemed to be affected when this happened.

Anyway, like I said, it will be interesting to see how the next release works!
Thank You again for your help!
Bill

Well it seems like the latest update did not fix the basic rules wait problem.
Here is the rule:


and here are pages of the log:




Houston, do we still have a problem?
Running 2.2.7.128 on a C7

well seems like the birds air filter zigbee plug was not responding!
I couldn't even control it with it's device page.
The log, when I tried to control it, didn't have any response from the plug, just "on()".
I unplugged it, waited about 10 seconds, then plugged it back in and it came to life.

I had another plug do the same thing tonight... although there weren't multiple entries in the log, but I noticed that it was off, and tried the same thing.
Unplugging and plugging back in "reset" it.

Another thing I noticed is that before I "reset" the birds air filter plug, I had a ghost device in my zigbee listing, and afterwards, the ghost was gone!
Strange!

I will see what happens tomorrow night with the birds air filter...

Question...
Why are these listed this way in the log?


The latest entry after finished is the app name.
Shouldn't that be at the start of the log entry?

I think it is. The time stamps are in reverse order.

Bruce mentioned fix is coming in 2.2.8 which is still in beta

2 Likes