> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/measurement-sensor-alerts-trigger-later-than-expected.md).

# Measurement sensor alerts trigger later than expected

Switch measurement sensors to virtual sensors to prevent data thinning from delaying alert triggers; thinned data skips intermediate values

## Question

Why does the feature related to measurement sensors provide inaccurate results? The **Parameter in range** alert triggers later than it should.

## Answer

In some cases, the **Parameter in range** alert notifications may appear with a delay or trigger later than expected. It may happen in cases where the rule is tied to a measurement sensor as a source for values.

The reason why this may happen is that all measurement sensors are optimised in terms of data thinning. To resolve the data thinning situation, you can use Virtual sensors, which are not optimised the same way and will be triggered by a 'State field value' rule right away.

1. Create a virtual sensor and specify the same source parameter for data as in your old measurement sensor. Select 'Calculation method' as Value in range.

   ![](https://296077121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5dyjvbUVXEbs60EnxnDz%2Fuploads%2Fgit-blob-a279f9a0802bc7fd5b01cb949db69bfc96e7af61%2FUnknown%20image?alt=media)
2. Create a 'State field value' rule and specify the virtual sensor for state source data:

   ![](https://296077121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5dyjvbUVXEbs60EnxnDz%2Fuploads%2Fgit-blob-6e1d9d8657cf88f42732297f5d105916f7c7b3a4%2FUnknown%20image%20\(113\)?alt=media)

## Links

* [Measurement sensors](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md)
* [Virtual sensors](/docs/user/guide/devices-and-settings/vehicle-sensors/virtual-sensors.md)
* [State field value](/docs/user/guide/events-and-notifications/inputs-and-outputs/state-field-value.md)
* [Parameter in range](/docs/user/guide/events-and-notifications/inputs-and-outputs/parameter-in-range.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/qna/using-navixy/measurement-sensor-alerts-trigger-later-than-expected.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.