New Records

[mrrickau]

I have a alarm on the "New Record" tag, but that doesn't tell me which record has been triggered, apart from going through the "Records" page and looking for anything that has changed recently,is there a way of finding out which record has been trigged?

[mcrossley]

Ah, no you can't. Teh email messages look something like this (I forced a new record!)...

A Cumulus MX alarm has been triggered.
A new all-time record has been set.
Last message: High humidity = 101.000

I can add a ToDo item for a new web tag to show that "last message" which is stored in the alarm.

[mrrickau]

Thanks Mark, that would be great

[mcrossley]

There are of course all the existing web tags for TempRecordSet, WindRecordSet etc.

[mrrickau]

I have email on New All time record with Latch unticked, however I do not seem to be getting ALL of the emails when there is a new record..

Maybe I am not understanding how things work, this is the last entries in alltimelog.txt:

Code: Select all

New all-time record: New time = 2024-02-09 09:00, new value =  12.000 "Longest dry period" prev time = 2024-02-08 09:00, prev value =  11.000
New all-time record: New time = 2024-02-10 00:44, new value =  25.500 "Highest minimum temp" prev time = 2024-02-01 00:06, prev value =  25.000
*New all-time record: New time = 2024-02-11 06:52, new value =  78.000 "High humidity" prev time = 2024-01-29 23:51, prev value =  77.000
New all-time record: New time = 2024-02-10 09:00, new value =  13.000 "Longest dry period" prev time = 2024-02-09 09:00, prev value =  12.000
New all-time record: New time = 2024-02-11 22:18, new value =  79.000 "High humidity" prev time = 2024-02-11 06:52, prev value =  78.000
New all-time record: New time = 2024-02-11 22:35, new value =  80.000 "High humidity" prev time = 2024-02-11 22:18, prev value =  79.000
New all-time record: New time = 2024-02-11 22:54, new value =  81.000 "High humidity" prev time = 2024-02-11 22:35, prev value =  80.000
New all-time record: New time = 2024-02-11 23:10, new value =  82.000 "High humidity" prev time = 2024-02-11 22:54, prev value =  81.000
New all-time record: New time = 2024-02-11 23:20, new value =  83.000 "High humidity" prev time = 2024-02-11 23:10, prev value =  82.000
New all-time record: New time = 2024-02-11 23:41, new value =  84.000 "High humidity" prev time = 2024-02-11 23:20, prev value =  83.000
New all-time record: New time = 2024-02-11 23:52, new value =  85.000 "High humidity" prev time = 2024-02-11 23:41, prev value =  84.000
New all-time record: New time = 2024-02-12 00:11, new value =  86.000 "High humidity" prev time = 2024-02-11 23:52, prev value =  85.000
New all-time record: New time = 2024-02-12 00:13, new value =  87.000 "High humidity" prev time = 2024-02-12 00:11, prev value =  86.000
New all-time record: New time = 2024-02-12 00:24, new value =  88.000 "High humidity" prev time = 2024-02-12 00:13, prev value =  87.000
New all-time record: New time = 2024-02-12 01:10, new value =  89.000 "High humidity" prev time = 2024-02-12 00:24, prev value =  88.000

Out of all of those, only the one with the '*' at the beginning of the line I received a email for ...

[mcrossley]

The attached log starts at 2024-02-11 17:30 so I cannot see the previous messages.

But the first entry in your all-time log after that is at 22:18 for High Humidity. For which an email is sent...

Code: Select all

2024-02-11 22:19:12.285 SendEmail: Sending email, to [rick@rra.au], subject [Cumulus MX Alarm - Girrawheen], body ["A Cumulus MX alarm has been triggered.\r\nNew Record"]...

The next at 22:35 - another High Humidity and no email is sent.

All-time record alarms should clear every 10 minutes, so if triggered you will not get another until a round ten minutes of clock time has passed and then another record is broken. This is to avoid flooding of alarms/emails on new installs where records are broken continuously.

The logged messages are not in the format I expected though. Which version of MX are you running?

[mrrickau]

Thanks Mark, the 10 mins accounts for them, I'm running version v 3.28.3 (b3280)

The alarm that you noted below doesn;t say what its for though, the body is just "A Cumulus MX alarm has been triggered. New Record "

Whereas the one at 11/2 06:52 says "A Cumulus MX alarm has been triggered. A new all-time record has been set. Last message: High humidity = 78.000"

As the second one is the same record, but more than 10 mins later should it not of said it was for high humidity?

Which also means I would of expected to get emails for all of these as well as they are more than 10 mins apart

New all-time record: New time = 2024-02-10 09:00, new value = 13.000 "Longest dry period" prev time = 2024-02-09 09:00, prev value = 12.000
New all-time record: New time = 2024-02-11 22:18, new value = 79.000 "High humidity" prev time = 2024-02-11 06:52, prev value = 78.000
New all-time record: New time = 2024-02-11 22:35, new value = 80.000 "High humidity" prev time = 2024-02-11 22:18, prev value = 79.000
New all-time record: New time = 2024-02-11 22:54, new value = 81.000 "High humidity" prev time = 2024-02-11 22:35, prev value = 80.000
New all-time record: New time = 2024-02-11 23:10, new value = 82.000 "High humidity" prev time = 2024-02-11 22:54, prev value = 81.000
New all-time record: New time = 2024-02-11 23:20, new value = 83.000 "High humidity" prev time = 2024-02-11 23:10, prev value = 82.000
New all-time record: New time = 2024-02-11 23:41, new value = 84.000 "High humidity" prev time = 2024-02-11 23:20, prev value = 83.000
New all-time record: New time = 2024-02-11 23:52, new value = 85.000 "High humidity" prev time = 2024-02-11 23:41, prev value = 84.000
New all-time record: New time = 2024-02-12 00:11, new value = 86.000 "High humidity" prev time = 2024-02-11 23:52, prev value = 85.000
New all-time record: New time = 2024-02-12 00:13, new value = 87.000 "High humidity" prev time = 2024-02-12 00:11, prev value = 86.000
New all-time record: New time = 2024-02-12 00:24, new value = 88.000 "High humidity" prev time = 2024-02-12 00:13, prev value = 87.000
New all-time record: New time = 2024-02-12 01:10, new value = 89.000 "High humidity" prev time = 2024-02-12 00:24, prev value = 88.000
New all-time record: New time = 2024-02-11 09:00, new value = 14.000 "Longest dry period" prev time = 2024-02-10 09:00, prev value = 13.000

I'll attached some more logs

The attached log starts at 2024-02-11 17:30 so I cannot see the previous messages.

But the first entry in your all-time log after that is at 22:18 for High Humidity. For which an email is sent...

Code: Select all

2024-02-11 22:19:12.285 SendEmail: Sending email, to [rick@rra.au], subject [Cumulus MX Alarm - Girrawheen], body ["A Cumulus MX alarm has been triggered.\r\nNew Record"]...

The next at 22:35 - another High Humidity and no email is sent.

All-time record alarms should clear every 10 minutes, so if triggered you will not get another until a round ten minutes of clock time has passed and then another record is broken. This is to avoid flooding of alarms/emails on new installs where records are broken continuously.

The logged messages are not in the format I expected though. Which version of MX are you running?

[mcrossley]

Thanks Mark, the 10 mins accounts for them, I'm running version v 3.28.3 (b3280)

The alarm that you noted below doesn;t say what its for though, the body is just "A Cumulus MX alarm has been triggered. New Record "

Whereas the one at 11/2 06:52 says "A Cumulus MX alarm has been triggered. A new all-time record has been set. Last message: High humidity = 78.000"

As the second one is the same record, but more than 10 mins later should it not of said it was for high humidity?

That message is from the email sender, whereas the full message is from the alarm code.

I think the messages are getting severely delayed.

Look in the 024000 log.

At 06:52:30 a new all-time for humidity is triggered.
Also at the same time the email request is generated.
Then at 06:53:12 (42 seconds later), the actual attempt to send the email happens.

On my system the send happens immediately after the request.

In the log file 114242, a number of emails are triggered when MX starts up, they all seem to attempt to send immediately as I would expect.

It may be worth switching on the email logging and see if the smtp.log file shows anything.

[mrrickau]

Hi Mark,

Checked the smtp.log (it was already turned on) and no errors in there...

I can see the sending of the emails for the 06:52:30 happenning immediately:

Code: Select all

2024-02-11 06:52:30.725 New all-time record: New time = 2024-02-11 06:52, new value =  78.000 "High humidity" prev time = 2024-01-29 23:51, prev value =  77.000
2024-02-11 06:52:30.725 Alarm (New Record): Triggered, value = True, threshold = 0, Message = High humidity =  78.000
2024-02-11 06:52:30.725 Alarm (New Record): Sending email - attempt 1
2024-02-11 06:52:30.726 SendEmail: Sending email, to [rick@rra.au], subject [Cumulus MX Alarm - Girrawheen], body ["A Cumulus MX alarm has been triggered.\r\nA new all-time record has been set.\r\nLast" +
    " message: High humidity =  78.000"]...

and the one for 06:53:12 also going immediately?

Code: Select all

2024-02-11 06:53:12.428 User Alarm (New Record): Triggered, value = 1
2024-02-11 06:53:12.428 User Alarm (New Record): Sending email - attempt 1
2024-02-11 06:53:12.428 SendEmail: Sending email, to [rick@rra.au], subject [Cumulus MX Alarm - Girrawheen], body ["A Cumulus MX alarm has been triggered.\r\nNew Record"]...

and I received both emails..

Maybe we target one specific record..

New all-time record: New time = 2024-02-12 00:13, new value = 87.000 "High humidity" prev time = 2024-02-12 00:11, prev value = 86.000
New all-time record: New time = 2024-02-12 00:24, new value = 88.000 "High humidity" prev time = 2024-02-12 00:13, prev value = 87.000
New all-time record: New time = 2024-02-12 01:10, new value = 89.000 "High humidity" prev time = 2024-02-12 00:24, prev value = 88.000

the 89 record should of been emailed as its more than 10 mins since the previous record?

[mcrossley]

Do you have a "latch" configured for the new record alarm?

[mrrickau]

Nah:

[mcrossley]

It's not record specific, the alarm is triggered by any new record.

I have found the problem though, you should be able to work around the issue by enabling latching for that alarm and set the hours to the period you only want one alarm raised. The hours can be a decimal value.

Then every 10 minutes the alarm will be checked to see if the latched hours have expired and clear the alrm ready to trigger again.

Meanwhile I'll fix the clearing of the alarm for the next release.

[mrrickau]

Thanks, thats fixed the issue until the fix comes out

I have found the problem though, you should be able to work around the issue by enabling latching for that alarm and set the hours to the period you only want one alarm raised. The hours can be a decimal value.