LED Indicator Colors

Modified on Tue, 05 Oct 2021 at 10:18 AM


Estimated reading time4 minutes, 20 seconds


The indicator LED on your bluebot is located next to your power button. During setup you will be prompted to pay attention to the color of the device indicator LED as you connect and install your device. If a problem occurs you may also use the status of the device to troubleshoot and potentially come to a resolution.

If you're experiencing an issue use the behavior patterns below to locate your issue and find the solution.


Yellow lights are all about connection, you will see a yellow light when connecting your bluebot to your home network before it eventually turns blue and connects to the cloud or fails and shows a different behavior pattern.

 Blinking Yellow: attempting to connect to the last known Wi-Fi network SSID (Name) and Password that was input by the user via the app.

Weak Wi-Fi Signal Strength At Install Location

Behavior patterns:

Attempting to connect to the access point, connection successful, repeat.


Solution: You may need to install a quality Wi-Fi repeater to increase the strength at the install location, especially if you're in a basement or detached garage or attempting to install the bluebot on your well head etc. Read more here about Wi-Fi Troubleshooting.
Tip: It can be helpful if you have a mesh system with an app to create a dedicated network for your iOT devices like bluebot.

Incorrect Credentials or Too Far From The Access Point

Behavior pattern:

Attempting to connect to the access point, connection failed.


Solution: Ensure your network name (SSID) and password are correct, this is a very common issue. You may also be too far from your router to test plug the bluebot device in near your router to rule out a wrong password. Read more about Wi-Fi Troubleshooting.



Blinking Green: initializing “access point” (AP) mode. 

Solid Green: AP mode active, now ready to connect to phone’s Wi-Fi network via the app.

Environmental Interference 

Common culprits causing connection problems for all smart home devices are RF (radio frequency) Interference that can interfere with the 2.4ghz channel that the bluebot uses to connect and transmit data to the cloud.  Microwave ovens, cordless phone systems, bluetooth systems and other Wi-Fi networks can all be responsible for interference as well.

Behavior pattern:

Cycling between flashing green and solid green indicates environmental interference.

FlashingSolidFlashingSolidRepeats Infinitely

Solution: Troubleshooting RF / Wi-fi Interference can be done by using a tool like NetSpot to reduce interference by identifying what is causing the issue in the first place. You may also attempt to connect the bluebot to the network outside of the home or area of interference and then take it to the install location and see if it will maintain a connection.



Solid blue, blinking blue: device is online and connected to the cloud. The bluebot device LED blinks to indicate active flow rate. Faster blinking shows that more water is flowing through the pipe. After installation, this is the expected behavior for your bluebot device.

False Flow

If you see in your app very low flow from 0.1 gpm to 0.4gpm flowing consistently it could be considered "signal noise" or also known as false flow.  It is possible for bluebot to read a false flow and calibrate it out using the Re-Zero tool.  Learn more...

Behavior pattern:

Flashing one time very regularly (every 30 seconds or every minute)

FlashingSolidrepeats every 30 - 60 seconds

Tip: FYI, please know the blue LED flashes to indicate live flow is present. If your bluebot is flashing blue at different rates and even flashing very slowly, this can be used as a manual indicator of water flowing. If you know NO water is flowing and the light is flashing you may need to Set the Zero Point for the device in the Sensor Details in the Device Profile.



Blinking purple: device is connected to your Wi-Fi network, but cannot establish connection to the bluebot cloud.

Firewall Blocking

This is generally a firewall setting on your Wi-Fi network most common in commercial network environments. 

Behavior pattern:

Flashing one time very regularly (every 30 seconds or every minute)


Solution: We recommend consulting your IT/ISP professional and/or contacting us.



Solid red indicator LED normally tells us that the bluebot is unable to connect to a Wi-Fi network because it is too far away from the router or the credentials (SSID / Password) are either no longer valid or incorrect.

Failed Connection

This is generally a firewall setting on your Wi-Fi network most common in commercial network environments. 

Behavior pattern:

Solid red 


Solution: Restart the connection process if you're experiencing this during initial setup of the device. If the LED indicator is red after you have had the device operational, make sure the Wi-Fi network is working properly and that the password has not been changed. In rare cases, where customers have dropped and damaged the bluebot or it has been improperly installed, the red status can indicate total failure which would require a replacement of the device itself.



Blinking pink: poor ultrasonic signal quality. 

Poor Ultrasonic Signal Quality

Possible cause: device adjustment, empty pipe during last rescan, dirt/debris interfering with device. 

Behavior pattern:

Flashing Pink


Solution: Perform a rescan when you are sure your pipe is pressurized/full. If that does not resolve your issue, check on your device installation status. Remove from the pipe, check the ultrasonic pads for dirt/debris, and ensure the bluebot is placed centered onto the pipe as shown in the illustration. 

Read all about signal quality HERE

If you have any questions or would like to speak to a member of the bluebot team, contact us directly at hello@bluebot.com or call/text (831) 275-2715 M-F 10 AM - 6 PM PST.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article