Troubleshooting Guide: WS1 Thermohygrometer, Cradlepoint IBR200, and Clean Claims BLE BLD2020

1. Wireless Thermohygrometer Model WS1

The Clean Claims WS1 wireless smart sensor, which monitors temperature, humidity, and ambient light. The WS1 is an all-in-one IoT thermohygrometer that measures temperature, humidity, and ambient light levels. It uses Wi-Fi (2.4 GHz only) to sync data to the Clean Claims cloud, allowing remote monitoring. The device features on-board memory for data logging (so it can store readings when offline) and runs on USB power or AA batteries for flexible deployment. It’s designed for quick setup and offers email/app alerts for threshold conditions.

Common Issues and Fixes (Connection Loss or Difficulty Connecting)

If the WS1 experiences Wi-Fi connection loss or has trouble connecting (especially to a Cradlepoint IBR200 router), use the following troubleshooting steps:

• Use 2.4 GHz Wi-Fi: Ensure the WS1 is connecting to a 2.4 GHz Wi-Fi network. It does not support 5 GHz Wi-Fi. If your router has both 5 GHz and 2.4 GHz under one SSID, temporarily separate them or ensure your mobile device is on 2.4 GHz during setup. The WS1 supports channels 1–13 on 2.4 GHz; avoid channels outside this range. Your Cradlepoints are preconfigured with these settings. If they have been adjusted, they will need to be reviewed and ensure it's set up properly. 
• Power Supply and Battery: Check the WS1’s power. Wi-Fi connectivity is power-intensive – if running on batteries, weak batteries can cause the device to boot but not maintain a Wi-Fi link. If you experience dropouts, try replacing the AA batteries or use a stable USB power source. On battery power, also ensure the device isn’t placed in a power-saving mode that disables Wi-Fi (WS1 is generally always-on, but low voltage could cause resets).
• Distance and Signal Strength: Keep the WS1 within a reasonable range of the IBR200 router. Barriers like concrete walls or electrical interference can weaken the Wi-Fi signal. If the WS1’s Wi-Fi indicator LED blinks red/green or shows connectivity issues, try moving it closer to the router. The IBR200’s external Wi-Fi antenna should be attached and oriented for best coverage.
• Interference: Reduce potential interference on the 2.4 GHz band. If multiple Wi-Fi networks are on the same channel in your area, log in to the Cradlepoint and change the Wi-Fi channel to one with less traffic (e.g. 1, 6, or 11) to improve reliability. Also keep the WS1 away from other electronics (microwaves, cordless phones, etc.) that could cause 2.4 GHz interference.
• Monitor Indicators: Observe the WS1’s LED status during connection attempts and also the Cradlepoint’s Wi-Fi client list in its admin console to see if the WS1 is associating. This can pinpoint whether it’s failing to join the Wi-Fi or failing to reach the internet.
• Data Logging Feature: Remember that if the WS1 temporarily cannot connect, it will continue logging sensor readings internally. Once the connection is restored, it will upload the stored data to the cloud. This means short-term outages won’t result in data loss – focus on restoring the Wi-Fi link and then allow time for the backlog to sync.

2. Cradlepoint IBR200 (IoT Router and Hub)

The Cradlepoint IBR200 is a compact, semi-rugged wireless router purpose-built for IoT and M2M applications. It provides an integrated Cat 1 LTE modem for cellular WAN connectivity, a 10/100 Ethernet LAN port, and 2.4 GHz Wi-Fi (802.11n) for connecting wireless devices (IBR200 Series Router | Ericsson). The IBR200 is designed to deliver reliable connectivity in diverse environments – it supports a wide operating temperature range and features GPS and GPIO ports for asset tracking and sensor integration. Managed through Cradlepoint’s NetCloud platform, it offers enterprise-grade security (VPN, firewall, VLANs) and cloud-based management for deployments of many devices.

Common Connectivity Issues with IoT Devices (e.g. WS1)

When wireless sensors like the WS1 have trouble connecting through the IBR200, or if the IBR200’s Wi-Fi network seems unstable, consider the following:

• Verify Wi-Fi is Enabled: The IBR200’s Wi-Fi radio must be on to accept connections. Check the device’s LEDs – the Wi-Fi LED should be solid green, indicating the 2.4 GHz WLAN is active. If it’s off or not lit, Wi-Fi may have been disabled in the router settings (or the router might be in a “Wi-Fi as WAN” mode that repurposes the radio). Log in to the IBR200’s web console (or NetCloud Manager) and ensure the Wireless LAN (AP) interface is enabled and broadcasting the SSID. Enable it or toggle it off/on if needed, and then retry connecting your device.
• Antenna and Placement: The IBR200 uses an external Wi-Fi antenna (usually a small detachable antenna). Make sure it is securely attached to the Wi-Fi port (labeled 2.4 GHz) and not loose. A missing or improperly connected antenna will severely limit range and could cause frequent disconnections. Also, place the IBR200 in a central location relative to your wireless sensors if possible, and away from large metal enclosures or sources of interference, to improve signal propagation.
• Device Connection Failing: If an IoT device fails to associate with the Wi-Fi:
  • Credentials: Confirm the SSID (network name) and passphrase in the IBR200 match what the device is configured to use. If you recently changed the Wi-Fi password or SSID on the IBR200, update the sensor’s settings accordingly (via its app or config interface).
  • Network Mode: The IBR200’s Wi-Fi is 2.4 GHz 802.11 b/g/n only – which is compatible with most IoT devices (like WS1). It does not support 5 GHz Wi-Fi, but this is usually not an issue since IoT sensors use 2.4 GHz. If the router is set to “802.11n-only” mode, try switching to mixed b/g/n mode, as some IoT devices with older Wi-Fi chips prefer b/g modes.
  • Security: Ensure the Wi-Fi security mode is one that the client supports (WPA2-Personal is recommended for IoT). The IBR200 supports WPA2 by default; avoid using WPA-Enterprise (RADIUS) unless your device supports 802.1X authentication. Also, the WS1 (for example) doesn’t support 
  • SSID Settings: If you’re using a hidden SSID, you will need to manually input the network name on the IoT device. Hidden SSIDs can also sometimes delay the connection process; as a test, you might broadcast the SSID temporarily to see if the device connects more readily.
• Intermittent Wi-Fi Drops: If devices connect but drop off frequently or show high latency:
  • Interference and Channels: Use the Cradlepoint’s interface to check what Wi-Fi channel it’s on. If the environment has many Wi-Fi networks, the default channel might be crowded. Change the Wi-Fi channel on the IBR200 (to 1, 6, or 11 in the US, for example) to find a cleaner spectrum. This can significantly improve stability if interference was the cause. Also, disable any unnecessary channel auto-scanning during critical operation hours – frequent channel hopping can cause momentary drops.
  • Transmit Power: The IBR200 allows adjustment of Wi-Fi transmit power. If you find the coverage area insufficient, ensure the transmit power is at 100% (or “Max”) in the settings. Conversely, if the device is very close and experiencing issues, excessive signal can saturate the receiver – but this is uncommon. Typically, you want maximum power for IoT coverage.
  • Max Clients: The IBR200 can handle multiple clients, but if you have a large number (dozens of sensors), ensure you haven’t set a low client limit in the Wi-Fi settings (some routers let you limit the number of connections). If a limit is set, it could be kicking devices off as new ones connect
• Using IBR200 with Other Networks: Some deployments use the IBR200 as Wi-Fi as WAN (using Wi-Fi as an internet source) or in bridge mode. In Wi-Fi as WAN mode, the device’s radio might connect to another AP instead of broadcasting your local Wi-Fi network, which would prevent your sensor connecting to it. Ensure the IBR200’s operational mode matches your use-case: for most IoT hubs, it should be in AP mode providing a Wi-Fi network to sensors. If you had experimented with Wi-Fi as WAN, revert to AP mode for the WS1 to connect, or use a second Cradlepoint radio (if available) to simultaneously support AP and client mode.

Cellular Network and Firmware Considerations

The IBR200’s primary WAN is often its cellular LTE connection. If your IoT device’s connectivity issues stem from the router losing internet, pay attention to the cellular link:

• Check Cellular Connection: The Modem LED on the IBR200 should be green when connected (blinking green means connecting, solid green means connected). If it’s flashing yellow or red, there is a data connection error or the modem is resetting. In such cases, the WS1 might be on Wi-Fi but unable to reach the cloud (hence appearing “offline”). Troubleshoot the cellular: ensure the SIM card is properly inserted (in the IBR200’s SIM slot) and activated with a data plan. Check that the APN settings in the IBR200 match your carrier’s requirements (via the router’s Local UI or NetCloud Manager).
• Signal Strength: Observe the signal strength LEDs (blue bars on the IBR200) or check the Web UI for RSSI/RSRP values. Poor cellular signal can cause intermittent internet. If signal is weak, reposition the router or its LTE antennas (e.g., near a window or higher location) or consider a higher-gain antenna. Cradlepoint’s documentation on optimizing modem signal is useful (Support - Always Connect Solutions). A stable internet connection is crucial for cloud-connected sensors.
• Failover Behavior: The IBR200 may be configured to fail over between networks (e.g., cellular to Ethernet WAN if present). During failover or failback, there could be a brief network interruption. If your WS1 reports intermittent loss on a schedule, check if it coincides with any failover events (the log in NetCloud Manager can show this). Adjust the failover settings or keep only one active WAN to simplify if constant connectivity is critical.
• Reboots and Resets: As a troubleshooting step, power-cycle the IBR200. A fresh reboot can clear any transient issues. If problems persist and you suspect a misconfiguration, you might back up the config and then perform a factory reset to baseline the router. Reconfigure minimally (just the WAN and Wi-Fi settings) and test the IoT device connection again. This can rule out any obscure setting causing trouble.

Best Practices: Maintain a stable environment for the IBR200 – stable power (avoid power dips), moderate temperature (within spec), and updated firmware. 

References & Resources: Consult the Cradlepoint IBR200 Quick Start Guide for installation basics (attaching antennas, LED meanings, initial setup). The Cradlepoint Knowledge Base has articles like “Troubleshooting No Internet or Connection Issues” and Wi-Fi Best Practices which cover interference reduction and optimal placement (Troubleshooting Wi-Fi). For in-depth troubleshooting, the IBR200 Local Admin Guide (available on the Cradlepoint website) provides guidance on using tools like Site Survey, ping tests from the router, and client logs. If the issue involves cellular connectivity, refer to Cradlepoint’s modem and signal troubleshooting guides (Support - Always Connect Solutions). Finally, Cradlepoint’s support can be contacted for persistent problems; having debug logs and firmware versions on hand will expedite the process.

3. Clean Claims BLE Model BLD2020 (Environmental Logger)

The Clean Claims BLE (e.g. models BLD2020/2025) is a battery-powered Bluetooth Low Energy (BLE) environmental data logger. It measures relative humidity, temperature, and moisture content in materials like wood or drywall. The device can store up to ~1,000 readings internally at user-defined intervals, and its data can be accessed wirelessly via the Clean Claims app. Key features include a replaceable CR2450 coin cell battery, an IP65-rated enclosure (dust-tight and water-resistant), and simple one-button Bluetooth pairing with the app. This makes it ideal for long-term monitoring of building environment conditions – it can log over time and then upload data when in range of a receiver.

Connecting via the Fanstel IoT Wireless Gateway

You will use a Fanstel IoT Gateway to collect data from the Clean Claims BLE and forward it to the Clean Claims app. Fanstel gateways are BLE-to-WiFi bridges – they scan for BLE devices and send their data over a Wi-Fi or Ethernet network. When setting up the Clean Claims BLE with a Fanstel (or similar) gateway, consider the following troubleshooting tips:

• Gateway Discovery & Network Setup: First, ensure the Fanstel gateway itself is properly connected to your network. Follow the gateway’s quick start instructions to join it to your Wi-Fi or LAN. Often, issues in this stage are due to the gateway not being powered or connected correctly.

• Power Supply to Gateway: A common issue is the gateway not being detected or functioning due to insufficient power. Use the recommended power adapter for the Fanstel gateway (typically 5V/2A DC) and the supplied USB cable. Using a lower-current adapter can prevent the gateway’s BLE and Wi-Fi modules from running properly. In fact, in one case, a user reported the gateway was not detected until the proper 5V/2A adapter was used. Ensure the gateway’s power LED is on; if not, swap the adapter or cable and try a different outlet.

• BLE Range and Placement: Bluetooth LE range is limited, generally around 10 meters (30+ feet) in open air, and less in indoor conditions. Place the Clean Claims BLE relatively close to the Fanstel gateway during setup – ideally in the same room or an adjacent room. Thick walls, metal structures, or interference in the 2.4 GHz spectrum (BLE operates at 2.4 GHz, like Wi-Fi) can reduce the effective range. If you notice intermittent readings or dropouts, try moving the sensor closer to the gateway to see if reliability improves. Also, avoid having the sensor inside metal enclosures or far inside wall cavities during initial connection – get a solid link first, then test the limits of placement.

• Pairing/Bonding: Many BLE sensors like the Clean Claims BLE do not require manual pairing; they advertise data for any authorized scanner. The Fanstel gateway likely operates as a BLE central device that can connect to the logger. Ensure the Clean Claims BLE isn’t already connected to another device (BLE typically only allows one central connection at a time).  The gateway might automatically bond with the device when it finds it – check the gateway’s device list or BLE devices page to see if the Protimeter is listed once discovered.

• Common Issues & Fixes:

  • Gateway not detecting BLE device: After ensuring proper power and proximity, if the gateway still doesn’t see the Protimeter, try restarting both devices. Power cycle the gateway, and turn the Clean Claims BLE off and on (if there’s no switch, you can pop the battery out for a few seconds to reset it). This can clear any stale state. Next, make sure the Protimeter is indeed advertising – you can verify by using a smartphone with a generic BLE scan app (like nRF Connect). If the phone scanner also doesn’t see the device, the Protimeter could be faulty or in need of a reset/battery. If the phone can see it but the gateway cannot, focus on the gateway (could be a firmware issue or a scan parameter mismatch).
  • Interference on BLE: If you have many BLE devices or beacons in the same area, the radio traffic might be high. Try temporarily turning off other BLE devices to give the gateway a chance to pick up the Clean Claims BLE. Also, ensure the Wi-Fi router (if very close to the gateway) is not set on channel 11, as the upper range of Wi-Fi overlaps with BLE frequencies – you could try Wi-Fi channel 1 or 6 to reduce interference on the BLE side.

• Setup Adjustments for Stability: Once the Clean Claims BLE is successfully connecting through the gateway, there are a few best practices to keep the connection stable:

  • Mounting: Mount the Clean Claims BLE and the gateway securely at their locations to avoid physical movement which could affect signal. For instance, do not place the Clean Claims BLE behind large obstacles or inside metal electrical boxes – its built-in antenna needs some clear airspace to broadcast.
  • Power Management: The Clean Claims BLE will likely go into a low-power advertisement mode when not actively connected. The Fanstel gateway may periodically wake it to fetch data. This is normal and helps battery life (which can exceed one year on a CR2450 if logging intervals are infrequent). Also, always have spare batteries on hand as a nearly depleted coin cell can cause erratic behavior – the device might power on but drop connection under load, similar to Wi-Fi devices on low batteries.
  • Multiple Sensors: If you plan to use multiple Clean Claims BLE devices, add them one at a time.