Would like to add the option in the current Change Trigger: When sensor changes, perform...

To: When sensor [does | does not] change, perform ....

to handle values that may or may not change. This would be helpful to easily identify files that do not change - but should.

For example, a JSON file has a time-stamp inside assigned to a XML Node (and optional property): msg_time. The file should be updated every 5 mins.

If we scan the file using the XML/REST sensor every 10 minutes, and this field does NOT change, trigger a Change Notification. However, this is hard-coded for "does change" and we are unable to easily perform this check with stock sensors/alerts.

I'm open to work-arounds also for this in the meantime. Any creative examples most appreciated.

Thank you!

Article Comments

Hi cvadmin,

Thanks for providing the feature request. To be able to vote for the rating, I'd like to ask you to change the format and tags as described here.

In the meantime, the workaround would be a custom script which sends out the queries to monitor the file age / hash of files to evaluate if the files changed or not.

Kind regards,
Felix Saure, Tech Support Team


Feb, 2021 - Permalink