Gradually turn on lights.

[toggledbits]

The status tab is starting to come together, and is supported in part by a new Alerts mechanism.

This is the place for discussion about that. Please don't open PRs at this point, as I'm not finished with the work. I estimate I'm about half done with what I know I have to do so far, and I imagine more to come later. If you have bugs to report, I'll take them here in this thread.

[LibraSun]

It's lookin' mighty good. Props to you, sir!

[PerH]

Nice! is a "Changed by" (rule/expression) column in that lower table in the works as well?

[toggledbits]

In the Entities? Probably not. How would I know what changed it?

[Matohl]

Nice, good work! I wait with my suggestions until I see what you have in mind.

[LibraSun]

The ALARM BELL already saved my bacon. A couple of otherwise "proven good" Rules evidently went rogue after I switched from detecting House Mode with Reactor (which yielded numbers 1, 2, 3, 4) to MSR's Vera > HouseMode feature (which yields strings "home", "away", "night" and "vacation"). This meant rewiring my logic flow, which got a bit out of kilter.

Anyway, MSR's "Status" report caught some unexpected "NULL" evaluations in the Trigger conditions, which led me down the proper rabbit hole to fix those and get both Rules back on track.

TIP: To account for the "NULL" condition (coming from a failed lookup in a "table" object I created -- see the ecobee plug-in is notorious for throwing an empty value back for Thermostat Mode in certain not-so-rare circumstances), I simply moved from:

[ Expression Value ] [ modesMatch ] [ is FALSE ]  // was bombing when NULL

to

[ Expression Value ] [ modesMatch ] [ <> ] [ TRUE ]  // works when FALSE or NULL

P.S. Oddly, the "Alarm Bell" icon remains %(#cc0000)[red] even after resolving the alerted conditions. (Solved with browser refresh)

[cw-kid]

The new version with alert bell seems to have messed up the menu when viewing on my phone, even in desktop mode. I can't get to the top of the menu and rule sets etc.

EDIT: MSR version 21091 fixes this issue

[cw-kid]

I also have this alert and cannot get rid of it when pressing the X

[cw-kid]

Vera "Rooms" are appearing in Recently Changed Entities for some reason ?

EDIT: MSR version 21091 fixes this issue

[PerH]

@toggledbits i'm thinking if some rule in reactor changed the state of the entity, it could be a column to identify that rule. changes done by others could simply state "other" or similar.

This is related to the other inquiry i had about entity change history..

[toggledbits]

Yeah, but there's no way to determine that.

[Matohl]

@cw-kid Same here. It is flooded by changes from the rooms

[LibraSun]

One of my Alerts says "
Unable to resolve global expression "timeStamp"
Last 22:23:06; this alert has repeated 3 times." ... yet I have no such variable. Perhaps I once did but not now that I can tell.

[toggledbits]

Something is referring to it...

...and yes I realize I need to make finding that something easier but, steps... one thing at a time...

[LibraSun]

Just as:

Reaction task "66" failed due to an exception
TypeError: Cannot read property 'length' of undefined
Last 09:21:10

must point to /something/ but I stand to be educated on where to look. The reactor Log, perhaps?

EDIT: Found line by searching for "length" in reactor.log.1 (downloaded from Synology NAS). Doesn't specify exactly what component the problem is with, but it did name the affected Rule. I suspect it's to do with a long JSON string in one of its variables that happened to contain an empty array as a 'value'.

[toggledbits]

Yes, log. All kids love log.

[LibraSun]

Do we really want disabled rules to appear among the list of Set Rules in status?

[cw-kid]

Can confirm the new Alert notification is working in a Reaction and puts an alert right on to this Status page under Current Alerts.

[LibraSun]

Neat! Will "clicking the red bell" eventually take us directly to the Alerts panel?

[LibraSun]

Also, so as to minimize the number of "SET" (but otherwise inactive) Rules, I decided to change all of my

[ Entity Attribute ]  [ X ]  [ is FALSE] // remains true indefinitely when OFF

to

[ Entity Attribute ]  [ X ]  [ changes ]  [ (any) ] to  [ FALSE ] // only true briefly when turned OFF

Dunno if I'm OCD or just didn't want Status implying that something was "going on" when it's not.