Upgrade Issues

[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.