Ruuvi Tag - Ready To Go

The Ruuvi Tag is distributed ready to transmit environment data packets periodically in either URL or highres (raw) mode.
The (very) faint blinking of the green LED indicates URL mode while the red LED indicates raw mode.
The mode is toggled by pressing the B button on the tag.

Be sure to enable Blue tooth in settings on the Phone.

  • When the tag is in URL mode packets can be received by a smart phone which uses an app or widget (for example nRFconnect) or
    Phy By BKON Connect
    to retrieve the web page which intreprets the packet and dislays the data, For example.
    Swipe up and click $ . Then swipe left to Add Widgets and select nRFconnect. After a few seconds a link will be presented. Tap it to display the Temperature, Humidity and Atmospheric pressure data.

    There are also android apps that can display the data directly.

    See the getting started video.

    for example: ¿¿ NordicSemi

    There are also applications which issue a notification whenever a new beacon is detected.
    for example: ¿¿

  • When the tag is in highres(raw) mode packets can be processed by an android phone running the ruuvi app.
    Another option is to establish another device such as a raspberry pi to receive the packets and run a progran to intrepret the data.

    The other Ruuvi packets are embedded within an Eddystone URL frame.

    Frame Specification (summary):

    byte
    offset
     range of
      values
    0   x10   Frame Type
    1  -100..+20   TX Power Calibrated Tx power at 0 meters. This allows for estimating the distance to the tag.
     Max for nordic nRF5832 is 4
    200..03
    ¤
    Encoded Scheme Prefix
    ¤ codes:
    00 http://www. , 01 https://www., 02 http://, 03 https://
    URL (17 bytes)
    3..ia-z and - Domain Name (case insensitive, ie translated to lower) (Choose the shortest possible since the total length is restriceted)
    i+1..j
    or
    .c…
    Top Level Domain
    codes:
    00 .com  01.org   02.edu   03 .net  04 .info  05 .biz  06 .gov 
    07 .com/ 08 .org/ 09 .edu/ 0a .net/ 0b .info/ 0c .biz/ 0d .gov/

         or
    a..zz text characters to specify other (case insensitive) TLD, for example .fi,.us,.edu,.vi,.io,.tv,.news …  
    j+1..20c…Beacon Data Characters (Application dependent)

    ruuvi Beacon Data Formats for sample Application: Environment Station

    (doesn't really tell [let alone predict] weather [rain,sunlight…)

    The web server address is nearly minimal ¤ruu.vi/ Where the ¤ is the protocol code x'03' for https:// This allows only 10 characters for the beacon data which must be printable and cannot contain most special characters (an address of the form XYZ.com/ or XYZ.info/ would allow 12 characters since a code could be used for the TLD and slash).

    The beacon data is encoded using a base 64 scheme* is used. This causes 3 bytes to expand to 4 characters; 6 bytes expands to 8 characters. When viewing the packet with a diagnostic tool or the URL in the address bar of a browser it is this string of characters which is visible.

    Formats 1-7 are prefixed with the fragment identifier introducer (#) allowing only 9 actual beacon data characters. The # appears to immediately follow the / from the web page viewpoint. For example: ruu.vi/#BnALAMNQr
    This allows the default web page, index.html, to provide the decoding algorithim and page formatting.
    The data from the beacon is specified as the fragment identifier. Since the fragment is NOT transmitted, the web site cannot process any information other than the time and IP address.