Ruuvi Innovations Oy
Buy Now

Troubles? RuuviTag

  • RuuviTag is not starting

    RuuviTag is not powered

    First run: remove a resist between battery and the battery clip. Indicator LED will blink on RuuviTag, when the beacon is powered. Change battery if no LED indicator is shown.

  • RuuviTag is not visible

    Check permissions

    Some applications (Ruuvi Station, IoTool, etc) require permissions in order to see RuuviTags. Check granted permissions in OS settings.

    Bluetooth is disabled

    RuuviTag uses Bluetooth (BLE) to broadcast data. Check that your Bluetooth connection is enabled. Notice, that RuuviTag will not show up in your mobile device Bluetooth settings because RuuviTags are not connectable Bluetooth devices, since they are only broadcasting.

    RuuviTag is not powered

    First run: remove a resist between battery and the battery clip. Indicator LED will blink on RuuviTag, when the beacon is powered. Change battery if no indicator is shown.

    RuuviTag firmware

    Check that you are using the correct firmware for your application (Ruuvi default firmware, Eddystone, Espruino). Refer to https://lab.ruuvi.com/dfu for more information regarding firmware.

    RuuviTag signal is out of range

    Bring RuuviTag closer to your mobile device. Make sure there are no structures between RuuviTag and your mobile device, that could prevent Bluetooth signal.

  • RuuviTag not visible in iOS Chrome

    Chrome physical web support

    Google has dropped support for Physical Web in iOS Chrome. This means, that iOS Chrome cannot see the RuuviTag physical web advertisements in the latest version of Chrome on iOS (version 62.0.3203.60 and newer).

  • RuuviTag not triggering Android Nearby notifications

    Android Nearby support

    Google has chosen to discontinue support for Android Nearby notifications. This means, that Android devices will not trigger Nearby notifications starting from December 6th 2018. This is why Ruuvi recommends only RAW data mode to be used, which is a format developed by Ruuvi and fully supported in Ruuvi Station.

  • Airpressure is different than reported on online weather services

    Altitude compensation

    RuuviTags report actual sensor values. This means, that values are not altitude compensated (many online weather services use sea level pressure values).

  • Acceleration data is not equal or close to zero

    Gravity component

    RuuviTag uses a gravity component (proper acceleration) when measuring acceleration, which means that your tag is accelerating roughly at 9.81 m/s^2 (or 1000 mG) towards the center of the Earth. The measurement result will slightly vary based on your altitude and geological location.

  • Readings are rounded to full values

    Firmware package

    This is the default behavior in old Ruuvi firmware version. High resolution RAW mode is on by default in firmware versions higher than 1.2. Download latest officially supported packages from https://lab.ruuvi.com/dfu.

  • Battery life is shorter than expected

    Humidity

    Using RuuviTag in high humidity may have created a leakage pathway that drains the battery prematurely. Remove the battery from RuuviTag. After the power is switched off, try to remove as much moisture as possible from the device. Grab a soft cloth and soak up all excess moisture. Use a cotton swab for the small parts. Blow dry the PCB gently with compressed air. Placing the PCB into silica gel to dry for a day or two can also help. Check the PCB for physical damages. Replace battery with a new one.

    Battery is low quality

    Make sure that you are using high quality batteries. CR2477 button-type batteries are recommended. If you are using the device in extreme temperatures, please use a battery suited for these operating conditions.

    Device damaged

    Damaged component in RuuviTag might cause the battery to drain faster than expected. Check terms to see if your device could be eligible for replacement under warranty.

  • Cannot enter bootloader or update the firmware

    Enable Bootloader mode

    Open RuuviTag enclosure, locate buttons B and R: keep button B pressed down and press reset button R. Red indicator LED will light on continuously. This means that RuuviTag is currently in Bootloader mode and ready for firmware update.

    Firmware package

    Check that the firmware package you are trying to update to your RuuviTag is correct and not corrupted. Download latest officially supported packages from https://lab.ruuvi.com/dfu.

     

  • Ruuvitag LED indicator is green and nRF Connect tries to initialise RuuviTag but it fails

    DFU connection

    Device Firmware Update (DFU) connection may be stuck. Disconnect battery from RuuviTag, restart Bluetooth on your mobile device and try running the update again.

    Other BLE programs running

    Quit all other Bluetooth LE applications running on your device and try running the update again.

  • RuuviTag disconnects before firmware update finished

    Other BLE programs running

    Quit all other Bluetooth LE applications running on your device and try running the update again.

    Random error during firmware update

    We have noticed that nRF Connect may in some cases disconnect during update process without any reason. This is possibly due to the amount of different types of Android phones available. Please try to run the update again.

  • Red LED indicator stays on after firmware update

    Firmware package

    RuuviTags which have been running Eddystone or Espruino firmware can have old configuration remaining which causes Ruuvi FW to crash. Please update to the latest Ruuvi firmware (1.2.11 or later). Download latest officially supported packages from https://lab.ruuvi.com/dfu.

  • Eddystone firmware cannot be configured

     

    Firmware package

    Check that you are using the correct firmware package. Download latest officially supported Eddystone package from https://lab.ruuvi.com/dfu.

    Unlock code

    Check that the correct unlock code was entered: 0x00112233445566778899aabbccddeeff. Notice! Web tool expects 0x prefix but not all Android apps expects this to be used.

  • Error 133 when configuring RuuviTag Eddystone using EID key

    Firmware package

    Check that you are using the latest firmware package for Eddystone. Download latest officially supported packages from https://lab.ruuvi.com/dfu.

  • Espruino firmware cannot be configured

    Firmware package

    Check that you are using the correct firmware package. Download latest officially supported Eddystone package from https://lab.ruuvi.com/dfu.

    Espruino support

    Espruino has its own active support forum where many topics are discussed. However, if your problem is clearly related to running Espruino on RuuviTag, please ask on our forum. This is mainly because we don't want to increase Espruino team's workload with questions related to third-party hardware platforms.

  • Uncaught Espruino Error: Module RuuviTag not found

    Espruino firmware version

    Check that you are using the latest firmware package for Espruino. Download latest officially supported packages from https://lab.ruuvi.com/dfu.

    Web IDE

    Check that you are using the latest Web IDE version.

    Connection to Espruino servers

    Confirm that your development computer is not behind a restrictive firewall.

  • RuuviTag MAC address

    How to find

    RuuviTag devices broadcast their MAC address via Bluetooth connection. Make sure your Bluetooth connection is enabled and RuuviTag is powered.

    Here are some examples to find RuuviTag MAC address:

    Android: Install Ruuvi Station app on your Android device, grant permissions and scan for nearby RuuviTags. All visible RuuviTags will be listed according to their signal strength. (Note! This method requires using the default Ruuvi firmware). You can also use nRF Connect app for finding MAC address.

    iOS: Unfortunately Apple has decided to hide MAC addresses from app developers. Therefore it's not possible to show Bluetooth device MAC addresses on mobile applications.

    Ruuvi firmware 1.2.12 or later supports scanning MAC address with NFC.

  • Operating limitations

    Limitations

    RuuviTag sensors are recommended to be used within -20°C to +65°C. Don’t place RuuviTag sensor in an environment, where maximum operating temperature limits (-40°C to +85°C) might exceed. This might damage the electronics. Default batteries delivered with the device are not suitable to be used in extreme conditions (under -40°C or +65°C).

    We recommend using RuuviTag with the included waterproof enclosure to prevent humidity, water or any other conductive element from getting in contact with the sensitive electronic components.