Device Troubleshooting

I just noticed that my Device Status LED has switched from blinking green and blue (or magenta) to blinking yellow and blue (or magenta).

The battery status LED is designed to show the following colors (for scale, approximately 8 hour usage time on a fully charged device):

  • 5 hrs = Green (Over 65% battery level)
  • 2.5 hrs = Yellow (between 35% and 65% battery level)
  • 0.5 hrs = Red (Under 35% battery level)

The Device Status LED is informing you the IDBLUE device battery is low on power and may require charging and has approximately 3 hours of usage time left.


I just noticed that my Device Status LED has switched from blinking yellow and blue (or magenta) to blinking red and blue (or magenta).

The battery status LED is designed to show the following colors (for scale, approximately 8 hour usage time on a fully charged device):

  • 5 hrs = Green (Over 65% battery level)
  • 2.5 hrs = Yellow (between 35% and 65% battery level)
  • 0.5 hrs = Red (Under 35% battery level)

The Device Status LED light is informing you that the IDBLUE device is now very low on power and will shut down shortly. Charge the IDBLUE device via a dedicated USB wall charger as soon as possible.


I plugged in my IDBLUE device for charging over a wall unit, but the Device Status LED does not indicate charging.

The charging circuitry is not receiving power or is defective.

  • Ensure that the wall electrical outlet has power. To confirm, switch to another wall outlet.
  • You may have a defective/non-compliant USB wall charger. To confirm, switch with a compliant USB 2.0+ dedicated wall charger.
  • You may have a defective USB cable. To confirm, switch the USB cable with a known good cable.
  • Try connecting the device to a computer using a USB cable to charge the device from the computer’s USB port.

If all else fails, you may have a device with defective charging circuitry. Please contact IDBLUE support for additional help as the device may be defective and should be returned to be repaired.


I am able to search my IDBLUE device from the application, but cannot connect using Bluetooth.

Your PDA or computer may be looking to exchange passkeys. If you are not noticing a prompt asking you to enter a passkey, please access the Bluetooth module of your PDA or computer and add the device first before attempting a connection over an application.

An IDBLUE device is a Bluetooth slave and therefore, cannot connect to more than 1 other Bluetooth device. Please ensure that no other PDA or computer is connected to your IDBLUE device.


I am trying to search/connect to the IDBLUE device via Bluetooth but the operation continues to fail.

Please make sure the device is put in Bluetooth Discoverable mode when searching.

Also, IDBLUE devices come with a Bluetooth Timeout device setting that turns off  Bluetooth on the IDBLUE device if the device does not have an active Bluetooth connection. If this is the case, press and release the Power button to re-enable  Bluetooth on the IDBLUE device.


My IDBLUE device disconnects from my application without any warning.

The IDBLUE device can disconnect from the application under any of these circumstances:

  • The IDBLUE device is not within range of the PDA or computer hosting the application. Move the IDBLUE device within Bluetooth range to re-establish the connection.
  • The Device Idle Timeout expires if the specified period of time elapses without the user pressing a button on the IDBLUE device or the application communicating with the IDBLUE device. The IDBLUE device must be turned back on such that the connection can be re-established.
  • The IDBLUE device runs out of battery power. Charge the IDBLUE device to re-establish the connection.


I have established connection to the device and having successful reads. However, the information of my reads is not being communicated back to my host application.

For Developers:

When developing this can happen for a few reasons:

  • The IDBLUE device sends the information back to the host application asynchronously via the established Bluetooth connection. Ensure that the connection is active and that the application is properly processing the asynchronous information from the IDBLUE device. Refer to the IDBLUE Firmware Interface Guide on our IDBLUE Documentation page for more information.
  • The IDBLUE device must be configured in a Connected Mode to retrieve the asynchronous tag information. Refer to the section Connected Operating Mode in our IDBLUE Users Guide on our IDBLUE Documentation page for more information.

For End Users:

This can happen due to improper device configuration settings. Please try power cycling your device and retry. If that doesn’t work, please try a Factory Reset which can be done from our IDBLUE RFID app. This will reset all configurable device properties back to their default settings.


If my IDBLUE HF device has an onboard memory, why is it that my tag scans are not getting saved?

IDBLUE HF’s on-board memory only saves information when set in Tag Store Disconnected Mode (not in Tag Verify Disconnected Mode or when it is connected to an application). Refer to the IDBLUE Device operating mode FAQ Question or the Operating Modes section in the IDBLUE User’s Guide on the IDBLUE Documentation page for more information.

This feature is not available for IDBLUE UHF devices.


I am trying to read a tag but keep seeing a red Action LED indicating an unsuccessful scan.

This could happen for a number of reasons:

The device could not energize a tag for communication

Our devices are designed to be low powered near-field mobile RFID devices with scan ranges of 2-4 cm. IDBLUE.HF uses a directional HF RFID antenna at the tip of the reader for scanning while IDBLUE.UHF uses an omni-directional UHF RFID antenna for scanning near the front of the device but not at the tip specifically – it is on the bottom and close to the 2 screws towards the front of the device. As the UHF antenna is omni-directional, it is focused towards the front as much as possible and as much power as possible without impacting battery usage expectations – scan UHF tags under the front LED for best performance. You can also notice IDBLUE.UHF can also detect UHF tags under the bottom of the reader (closer to the lanyard loop) occasionally due to the omni-directional antenna signal.

For IDBLUE.HF and IDBLUE.UHF devices, you may also notice greater readability range based on the reader/tag orientation which maximizes the power picked up by the tag inlay.

Additionally, because of the power requirements for mini-tags (tags very small in diameter as small as 10mm or less), there may be readability issues as the energy required is more than what our devices can send.

The device was attempting to read an On Metal tag

RFID tags near metal will have difficulty energizing as metal absorbs more of the signal. To improve IDBLUE.HF performance with tags near metal, we do offer an “On Metal” tip configuration that replaces the capacitive tip with a flat tip to minimize the distance between the antenna and tag. Please refer to the IDBLUE Sales Order form for the tip customization. Because of the design of the UHF omni-directional antenna, this tip will have no performance improvements for our UHF devices.

Devices can only read compatible tags

IDBLUE.HF communicates via the ISO15693 protocol and IDBLUE.UHF communicates via the ISO18000-6C protocol. Our devices don’t support MIFARE and ISO14443 protocols specifically or tags with encryption or very small inlay due to either no support for proprietary encrypted card security or power requirements for energizing the tag. We are looking into future limited support for ISO14443/NFC protocol tags based on increased demand – please contact IDBLUE Support for more information.

If the tags support the protocols above, our device may not support that tag manufacturer identifier.

Our Sales Team has a catalog of known compatible/incompatible tags for reference to our customers – please contact our Sales Team for more detailed information.


I am trying to read/write the user memory of the tag. I am in proximity to the tag but the Reading Status LED remains blue.

A read/write operation to/from a tag’s user memory is a longer operation than a simple tag ID read/write. Depending on the amount of information stored on the tag, it can take much longer to read/write. Please ensure that you keep the IDBLUE device in the specified range until the Action Status LED indicates a successful (green) or unsuccessful (red) read/write.


My IDBLUE device isn’t powering on or charging. Help!

For more information, please see our IDBLUE User’s Guide on the IDBLUE Documentation page.

Diagnosing Battery Issues:

A good battery should be able to charge up to 100% battery level and maintain 90%+ for over 30 minutes. You can check battery level by:

  • using the IDBLUE RFID app on Android or iOS,
  • IDBLUE Manager Dashboard tab,
  • doing a Get_Status API call.

Our devices are not fully charged when shipped to maintain battery performance. Once a device is received from IDBLUE, it should be charged fully before using for the first time to maintain battery integrity. The device is not designed for long term storage and should be checked and charged approximately every 2 months to check battery level.

The battery status visual indicator on the Device Status LED is designed to show the following colors (for scale, approximately 8 hour usage time on a fully charged device):

  • 5 hrs = Green (Over 65% battery level)
  • 2.5 hrs = Yellow (between 35% and 65% battery level)
  • 0.5 hrs = Red (Under 35% battery level)

When getting an accurate battery level reading, it’s best to read it via a Bluetooth connection as when plugged in via USB, it boosts the battery voltage reading due to charging. Once the device stops charging after reaching 100%, it will not show any Device Status LED (when powered off and plugged in) or it won’t hold the battery status color (when powered on). If the Device Status LED ever shows red when powered on or not able to power on itself, the battery is low enough to require charging asap.

Optimally charging our device with a Windows OS USB port will require the device to be able to turn on and enumerate. If the device cannot turn on and cannot enumerate, Windows restricts the charge rate to 20% of it’s capacity. A suspected bad battery (or a critically low battery level) device should be tested/charged with a dedicated USB charger as soon as possible.

The batteries inside our devices are not user-serviceable. If you have a device with a compromised battery, you can contact IDBLUE Support to inquire about our battery replacement services.


I am trying to switch on my IDBLUE device but the device is not responding.

The device may become unresponsive for a number of reasons…

Battery level is too low to turn on. Please ensure that the device is fully charged and that you are pressing the Power Button for at least 2 seconds. To make sure the battery is charged, when plugged into a USB wall charger, it should display a Device Status LED color to indicate battery level:

  • Red – Battery is critically low and would not be able to turn on for long if at all. Please charge as soon as possible.
  • Yellow – Battery is low
  • Green – Battery is acceptable
  • Off – Battery is at 100%

For more information, please refer to the IDBLUE User’s Guide (User Feedback Section) on the IDBLUE Documentation page.

The device is in an unknown state. If the device gets into an unknown state and the power button has no effect, you can do a “Double Button Reset” – hold down rear and front buttons at the same time. You should see both front and rear LEDs light up for 2 seconds and then turn off. Release the buttons and the device should restart and power up as if it was power cycled.


If any of these questions doesn’t seem to apply, please try to contact IDBLUE Support and we can walk you through any issues you might be encountering.