[SOLVED] Rule doesn't trigger on change randomly?

Setup, Configuration and Use Scripts & Rules
21

That would be another test then… does it hang with it ON?

That’s very odd. Maybe LSP wasn’t up to date for 2.3. I don’t see why you couldn’t use previousState.toString == "NULL" instead though.

How about the items definitions?

22

I think i figured out my problem

I was using the old syntax for the lambda expressions!

old syntax:

createTimer(now.plusMinutes(SA_dismissMinuets), [|
    logInfo("SA", "Timer up, no occupancy for X min")
    ...
    ])

new syntax:

createTimer(now.plusMinutes(SA_dismissMinuets)) [|
    logInfo("SA", "Timer up, no occupancy for X min")
    ... 
]

I must have picked that up from an old forum post, I’m not sure why but the effect of using the old syntax was that the code inside the lambda was run immediately and the rest of the function did not run at all.

I’m gonna let it run for a week and see if it happens again to see if this was the real issue or maybe a secondary mistake.

Note: As @vzorglub noted both syntax are supposed to be valid, and maybe this solution works for me for some other reason (my guess with no real proof is that I’m using openjdk). So your mileage may vary.

23

Both syntaxes are valid.
I use the first one.

24

If both are valid i’m not sure exactly what my problems was, maybe one syntax has problems with openjdk, or maybe switching to the new syntax i accidentally fixed another syntax problem I had.

Either way this has been working for me for the passed week and I consider that enough for me for now.