> 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/on-premise/on-premise/how-to-guide/configuration/device-statuses.md). # Device statuses Adjust online, GPS-not-updated, and offline timeout thresholds for device status indicators in Navixy on-premise. Edit the tcp-server configuration file. Each device in the Navixy platform has a specific status that indicates its current condition. These statuses change based on the duration of time that elapses.


	N/A	Data is constantly being received from a device and contains valid coordinates
	5 minutes	No valid location data for more than 5 minutes or the device is transmitting data in a time zone other than UTC+0
	10 minutes	The device does not send any data packets for over set time period

### Adjusting Timeout Settings If needed, timeouts in On-Premise instances can be adjusted by modifying the "tcp-server" configuration file. The configuration file is located at the following path * on Linux: `/home/java/tcp-server/conf/config.properties` * on Windows: `C:\java\tcp-server\conf\config.properties` To adjust the timeouts, open the "tcp-server" configuration file for editing and add the following lines: ``` timers.idleTimeout=10m timers.offlineTimeout=15m ``` In the above example, the timeout value for "GPS not updated" status is set to 10 minutes, while the timeout value for "Offline" status is set to 15 minutes. You can specify any values you need, but make sure to set the first timeout value to be less than the second one. Also, note that it is mandatory to add the letter "m" after the specified timeout value, which means minutes. After specifying the timeout values, save the configuration file and restart the "tcp-server" to apply the changes. With these adjustments, the timeout settings can be customized to suit users' needs and ensure optimal device performance on the Navixy platform. --- # 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/on-premise/on-premise/how-to-guide/configuration/device-statuses.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.