[2.5.0.123 C8 Pro] SOLVED: Automations are misbehaving after migration from C7 to C8 Pro

This morning I (finally) migrated my main hub from a C7 to a C8 Pro. All my devices (150 Zigbee, 30 Z-wave) seem to be up and working just fine. I reconnected Alexa and Hub Mesh and everything seems to be working great...

EXCEPT a collection of Simple Automation Rules. I have about 25 of them because they are simple and just work. Right now, a whole bunch of them are activating to turn things on, but not turning them off.

E.g., when a garage door opens there is a rule to turn on a notification on an Inovelli Red Dimmer so that the LED flashes a pattern (to indicate the garage door is open). The SA rule works to turn on the notification device, but doesn't turn it off.

This is the log from when I last triggered this:

image

There is no "act: Turn off" happening.
The rule is acting just like "Turn off when closed" isn't selected.

The events on the garage door show the rule was invoked upon closing:

And (not surprisingly) the notification device only shows the "on" call:

I've tried updating the rule. I've unselected and reselected the devices and options. It still doesn't seem to be working.

This rule is at least 5 years old and was working perfectly on the C7.


UPDATES


I've shutdown and pulled power.
I've rebooted with DB rebuild.
I've shown the SA rule fails with just virutal devices.
I can create the same SA rule on my other C7 and it works.
I've reverted from 2.5.0.124 to 2.5.0.123.
It is also happening to Room Lighting and Motion and Mode Lighting rules.

It's a schedulerError (in Logs -> Hub Events). See Solution post!

Have you tried re-creating the rule from scratch?

I was just doing that after making this post. The new rule I just created has the same problem!

The test rule:

The log:

Just to be sure it wasn't the Inovelli notification child device, I swapped out a real dimmer for the device to turn on/off. The Simple Automation rule is only turning it on, and still not turning it off.

I know you just migrated, but how about a Reboot with Advanced Option b/u db checkbox selected? Can't hurt, I hope.
edit: Then there's the controlled shutdown/power cycle thing.

I did do a full shutdown / power cycle already. I'll try a DB rebuild.

Not surprisingly, if I ask Rule Machine to create a rule from the SA rule, it works just fine.

image

I just really don't want to do that for 25 (previously working) SA rules.

Nothing to lose, hopefully.
It cleared up some weird $hit for me a little while ago.

Lovely. lol.

Basic Rules is the heir apparent to (the no longer actively supported) Simple Automation Rules, so if you do decide to move on from SAR, hopefully Basic Rules would be a similar fit overall.

It made no difference in behavior. Simple Automation Rules are still broken.

I also have a bunch of SA rules, some a little complicated with virtual switches and the like, and also have no inclination to switch.

I just created a SA rule on my C8Pro with .123 and it worked.
Zooz contact sensor and switch.

1 Like

Ugh. I don't even have Basic Rules installed. At least RM gives me a one-click way to convert SA rules to RM rules.

Uncharted territory for me.
You can Export rules. Maybe you could export all the SA rules to a file. Remove the Simple Automation automation, (lol), reinstall it and then restore the rules from the file. All after making a backup of course, lol.

So I went to my other C7 (not the one I migrated from; that one is still powered off) and created a similar SA rule. It works. Also running 2.5.0.124.

Log:

image

Is ZWJS in play?

No ZWJS. I just migrated from the C7. Making those sorts of changes will happen later.
(but this is failing with virtual devices also)

wow

As far as triage goes, I'm like the nurse who takes your blood pressure in the little room. You need an actual doctor. :slight_smile:
Does Dr Bruce still make house calls?

I understand from @hydro311 that .124 is a beta. Is that what you have?
Maybe revert to .123?

The exact same SA rule on my C8 Pro doesn't trigger "act: anti-Turn On":

image

@support_team