Simple Automation Rules issues after updating

[joseph1]

Already did. Post #5 on August 13. It still shows double, just like that.

[bravenel]

OK, sorry I missed that. One of them should work. Are you sure that neither does?

Would you try to open the top one, and give me a screenshot of what happens.

[joseph1]

[bravenel]

Could you do that with a Logs tab open, and post what, if anything, it logs.

[joseph1]

When checking logs:

[joseph1]

Same log when I have the live logs open. Anyway, here it is, you can see me uninstalling then installing again.

[bravenel]

Thanks...

[tedbalog]

I'm now on 2.3.0.116 and still having this issue. How can I resolve?

[bravenel]

@tedbalog

still having this issue

This is an old topic, and it's been months since I've looked at this. Please be specific about the issue you are having, and don't assume that I know anything about it for the past. Turn on logging in the rule and post a screenshot of those logs (not copy/paste) that show the problem occurring.

[tedbalog]

Sure - I was one of the original reporters back in September. I submitted a support ticket, with all of the relevant details and those details are all the same with the exception that I'm now on the version stated in my previous comment.

Simple Automation Rules, simply don't work. I have several rules set up to execute based on a specific time, or an offset of time from sunrise/sunset. Daily, these fail with NullPointerExceptions reported in the logs. These rules were working well for me until I updated my Hub's software back in September. They have been broken, consistently, ever since.

Attempting to access the App, it leads me to a blank page:

Thanks for the help.

[bravenel]

You will have to remove this app instance, and create a new one. Something happened to corrupt that instance.

[tedbalog]

When adding a built-in app, I have two choices:

The first brings up the same screen I saw before:

The second gives me an error when attempting to create a new rule:

[gopher.ny]

Could you please PM me your hub id? I can check the engineering logs on the hub for possible root causes.

[dkkohler]

I'm having the same issue. Is there any way to copy the rules from the "corrupted" instance, or do I need to recreate them all from scratch?

[cgmckeever]

@bravenel Same issue. I just started to setup my hub and give it a test drive. When playing with the different rule engines, I noticed the same issue as @tedbalog posted

• 2 Versions of Simple Automation Rules
• First one brings up a blank screen with GEAR icon
• Second one Has a Create/Remove Rule; Create takes you to the 404

Hubitat Elevation® Platform Version
2.3.0.120

Hardware Version
Rev C-5

[tedbalog]

@gopher.ny was able to resolve my issue, but it required modifying and restoring a backup from my hub. I also had to re-create all of my rules.

[ourmessages]

That doesn’t really sound like a good resolution in the scheme of things.

[agavenda]

@gopher.ny I'm having the same issue as @tedbalog. I recently updated my hub and noticed that a simple automation rule for a porch light stopped working. I see the same blank screen for the one app version and the same error message for setting up a new rule with the second app version.

Appreciate any help.

[cjtman.theriault]

Having the same issue. Simple Automation Rules presenting with the below message.

[cjtman.theriault]

This bug is kicking my butt. Attempted to bite the bullet and reinstall SAR, but now I'm getting three instances when I attempt to reinstall, none of which work.