> 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/user/guide/events-and-notifications/vehicle-efficiency/fuel-level-change.md). # Fuel level change Alert when the fuel sensor detects a significant level change, signaling refueling or potential fuel theft. Requires a configured fuel level sensor per device. Monitoring fuel levels is crucial for managing fuel consumption and detecting unauthorized usage. The Fuel Level Change rule is designed to provide real-time notifications whenever significant changes in fuel levels occur, such as sudden increases or decreases. These notifications can be delivered through the web user interface, SMS, or email, and can be consolidated into reports. This proactive monitoring helps users quickly respond to fuel level changes, potentially lowering fuel costs and resolving disputes among employees. {% hint style="info" %} Before setting up this rule, ensure that the fuel level sensor you intend to monitor is properly configured. For detailed instructions on setting up and configuring fuel level sensors, see the [Fuel level sensor section](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors/fuel-level-sensor.md). {% endhint %} ## Rule settings ### Sensor Specify the fuel level sensor that will be used as the source for notifications and analysis. The number of fuel changes indicated is regulated by the Accuracy parameter of the fuel level sensor, which is explained in the [Fuel level sensor section](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors/fuel-level-sensor.md). For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The Navixy platform smooths sensor data and compares the total change within a 10-minute window against the fuel sensor's Accuracy setting to determine if a notification should be triggered. For example, with an Accuracy setting of 5%, a fuel level change of 5 liters or more for a 100-liter tank within 10 minutes triggers an alert. If the cumulative change meets or exceeds this threshold, the platform sends a notification. * Fuel change volume estimation is not currently included in notifications but will be available soon. * The **Fuel level change** alert has a 15-minute reset timer, meaning the alert doesn't trigger more often than once every 15 minutes. If a fuel level change occurs while the rule is in its reset period, the platform omits the event, including in the reports. * This rule supports only one device per rule. This limitation is due to the complexities involved in cross-referencing multiple measurement sensors with different GPS devices, calibration tables, and other measurement and filtering aspects. --- # 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/user/guide/events-and-notifications/vehicle-efficiency/fuel-level-change.md?ask=&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.