Setting Counter Causes System Reset

[Jeff]

Following Rules are causing ElkM1 to Reset:

WHENEVER EVERY 1 MINUTE

AND NoMotion_B (Counter 10) IS GREATER THAN 0

THEN SUBTRACT 1 FROM NoMotion_B (Counter 10)

 

WHENEVER NoMotion_B (Counter 10) CHANGES TO )

THEN SET TestCntr (Counter 12) TO 0

The M1 resets whent the 2 rule executes. If the 2nd rule is disabled, no issue. I’ve tried varations of this rule, such as setting to TestCntr to 1 and adding to TestCntr but reset still occurs.

[Jeff]

Correction due to typo above:

WHENEVER NoMotion_B (Counter 10) CHANGES TO 0

THEN SET TestCntr (Counter 12) TO 0

 

Variations of the above that I have tried, all result in Elk resetting:

WHENEVER NoMotion_B (Counter 10) CHANGES TO 0

THEN SET TestCntr (Counter 12) TO 1

 

WHENEVER NoMotion_B (Counter 10) CHANGES TO 0

THEN SET TestCntr (Counter 12) TO 1

 

WHENEVER NoMotion_B (Counter 10) CHANGES TO 0

THEN ADD 1 TO TestCntr (Counter 12)

 

WHENEVER NoMotion_B (Counter 10) CHANGES TO A VALUE LESS THAN 1

THEN SET TestCntr (Counter 12) TO 0

 

[Jeff]

Also tried:

WHENEVER NoMotion_B (Counter 10) CHANGES TO A VALUE LESS THAN 1

THEN SET TestCntr (Counter 12) TO 60

The reason I did this, is becuase I have a similar rule elsewhere that works just fine?!? Thought maybe the set-to value might be the issue. Still, it cause the Elk to reset.

Here’s the other weird thing: Even if I don’t change the programming, when I connect or do a “check for conflicts” ElkRP reports there are conflicts in the Rules & Texts. There nothing in the Texts. If Select All, and Send checked items to system it behaves as expected. But, on re-connection, ElkRP reports a conflict Rules & Texts (even though there were no changes. “View Difference for selected Items” reports “[Selected Item] cannot be compared.”

I then tried to Receive All, but that scrambled my new rules with some old rules that I had deleted. Cleared all rules and counters, Sent All. Then, Sent All from a back-up of my account but that results in same issues above.

 

 

[Jeff]

Any idea what might be causing this behavior?

[Jarek Bicki]

I would only suggest changing the Whenever statement to 60s instead of 1 min in rule 1

[Brad Weeks]

Are you running M1 Firmware 5.3.18?

[Author]

Posts