> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/vehicle-wait-time/troubleshoot-vehicle-wait-time.md). # Troubleshoot Vehicle Wait Time Refer to the table below for help troubleshooting Vehicle Wait Time. | **Issue** | **Cause(s)** | **Solution(s)** | | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Vehicle wait time motion zone is not saving when I select "done" | There is a limit of one non-regular motion zone per camera and 5 per device. | Verify "people motion" and/or "vehicle motion" is not already configured on the camera. [Please contact our Support team](/docs/get-started/introductory-guides/how-to-contact-our-team.md) if you require additional assistance. | | Vehicle Wait Time events are not being created, despite configuring a motion zone and vehicles are driving through the zone. | Motion zone may require reconfiguration (not optimal size). | Try the following:\* Wait a few minutes for at least two vehicles to pass through the motion zone so the AI can properly calibrate. \* Adjust the size of the motion zone to recalibrate. A smaller motion zone may be more effective than a larger one because it excludes irrelevant movement (e.g., background motion, waving hands… etc.). \* Clean the camera lens or adjust the camera placement to better detect cars. | | "Window time" is not being calculated/displaying for events. | The motion zone may not have saved correctly. | **Reset** the motion zone and draw the region of interest again. | | "Window time" is inaccurate, usually displaying "1 second". | The motion zone may be too large, causing irrelevant motion such as shadows, light changes, etc. to impact results. | Configure the motion zone to be smaller. | | Solink is picking up a shadow as a vehicle, which can cause issues with the vehicle detection AI. | Shadows can trick the vehicle detector; the silhouette has a strong resemblance to an actual vehicle. Sun position changes over the course of the day, sometimes introducing problematic shadows. | Move your motion zone(s) to an area without shadows present. | ## Camera Placement Troubleshooting Some issues with Vehicle Wait Time can be attributed to **camera placement** at your location. It is recommended to try the following troubleshooting actions to improve camera placement for Vehicle Wait Time if you are experiencing issues. ### Camera Angles Refer to the following table for an overview of ideal camera angles for optimal Vehicle Wait Time performance. If your camera angle is similar to the "Least Ideal Angle" in box 3 or 4, try to reposition the camera to an angle more reflective of box 1 or 2. **Note**: Cameras facing the rear of a vehicle are optimal. | **1. Best Angle** | **2. Acceptable Angle** | | ----------------------- | ---------------------------- | | | | | **3. Less Ideal Angle** | **4**. **Least Ideal Angle** | | | | ### Weather Effects on Cameras Keep in mind the effects of rain, snow and/or fog when using Vehicle Wait Time. Weather can impact camera clarity, which can impact the accuracy of metrics. ### Dirty Camera Lens Dirty or foggy camera lens can lead to visibility issues when capturing Vehicle Wait Time data. [Refer to this guide](/docs/install-connect-and-integrate/camera-guides/how-to-clean-camera-lens.md) for more information on how to clean your camera and lens. --- # 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://help.solink.com/docs/understand-your-business/vehicle-wait-time/troubleshoot-vehicle-wait-time.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.