In the following document you will find a step-by-step guide to troubleshooting the Blackbird IoT Hardware, Factbird.

Device appears offline

If your Factbird device is not online (see status light in Chapter 1), the following table explains the meaning of the different status light stages and will help you determine how to proceed.

Color Lamp Explanation Procedure
Yellow stable Temporary hardware status when
switching between other statuses.
This can last up to 10 minutes. Wait for the status LED to change color
(do not unplug!)
Red Blinking Offline 1. Check the general network availability (Network availability on your mobile phone / correct entry of the WIFI credentials)
  1. Restart the device (Unplug for approx. 1 min)
  2. If the status LED continues to flash red after this, contact the Blackbird support | | Green | Blinking | No GSM internet connection. The SIM card is connected to a network, but has no internet reception. | Contact Blackbird support and provide details on which country/region the device is located. | | Pink | Blinking | OTA ongoing. The firmware of the device is being updated over-the-air at the moment. | Wait for the status LED to change color (do not unplug!) | | Blue | Blinking | No Wifi internet connection. The Factbird device is connected to the router, but has no connection to the Internet. | Verify internally that for each device

WiFi not connecting

  1. Wifi SSID (Network name) and passwords are case sensitive. Please ensure that you have configured the Wifi credentials correctly in Blackbird. If the credentials have been misconfigured bring the Factbird Duo online via the cellular network and when fully connected configure the credentials again.
  2. Test with your phone that the WiFi network is reachable at the location of the Factbird.

WiFi credentials are wrong

  1. Bring the Factbird Duo online via cellular network.
  2. Once the Factbird Duo is online in Blackbird remove the faulty WiFi configuration and re-configure the WiFi settings.

WiFi is connected but has no internet

  1. Make sure your internal network and firewall have whitelisted the domains and ports listed here: Whitelist domains & Ports in Firewall