"Sensor not in Water" - WaterGuru SENSE
The WaterGuru SENSE has a Sensor that is suspended by a cable beneath the SENSE skimmer cover. This error "Sensor not in Water" is usually displayed if the Sensor is not immersed in the water.
Note: When you initiate a "Measure Now" through the WaterGuru App, the app will check to see if the SENSE is in water. If you initiate a "Measure Now" when the SENSE is not in water, you may have to wait several hours until the next scheduled measurement for the error to clear.
Perform the following troubleshooting:
- Lift up the SENSE from the skimmer and place the SENSE on a dry flat surface
- Clean the skimmer of any debris
- While placing the SENSE back over the Skimmer, check to ensure that the Flow Sensor (Metal rectangle) portion of the Sensor that is suspended by a cable is completely immersed in the water and that the metal triangle is facing the pool and not facing the back of the skimmer.
- Ensure the SENSE is over the Skimmer
- If the SENSE Sensor touches the bottom of the skimmer, you can adjust the cable.
- Turn on your pool pump to the highest speed
- Lift up the SENSE from the skimmer enough to see if the water level in the skimmer drops with the higher pool pump speed
- If this is the case, reduce the pool pump speed to a lower speed.
- Ensure that at the lower speed, the Flow Sensor is immersed in water.
- Note: If the water level in your pool has changed and is lower than normal preventing the Flow Sensor from being immersed in water, you will need to ensure that the water level is raised to a level where the Flow Sensor is immersed.
If you have completed the above troubleshooting steps, have waited at least 30 minutes and the WaterGuru app still shows "Sensor not in Water" and / or if the SENSE water temperature shows 34.1F, there may be a problem with your device, click here to submit a Support Request and we will respond.
You can also contact us by phone Monday to Friday from 9:00am - 6:00pm PST at 1-844-989-4878. WaterGuru Support can check your device remotely for further troubleshooting.
Comments
0 comments
Article is closed for comments.