Renaming my Bluetooth beacon

badiu · March 8, 2019, 10:00am

Hello,
just want to ask,is that possible to i to rename my ruuvi name to something else?

my ruuvi name just now display Ruuvi62ca. and i want it to rname as ‘Ruuvi1’

so what should i have to do it (hardware & software)and if have tutorial on it can you just share with me

thank

otso · March 13, 2019, 8:58am

Hello, which fw version you’re running?

Name is generated in firmware, and it can be adjusted as needed.

badiu · March 13, 2019, 9:31am

right now im running on eddystone_dfu_2.3.0
which firmware should i go to adjust my ruuvi tag?

otso · March 13, 2019, 10:22am

github.com

ruuvi/ruuvitag_fw/blob/351b1eb5b6ff9b9bb6f6f1b99c29ebc915710a18/ruuvi_examples/eddystone/main.c#L168


uint8_t                 device_name[20] = { 0 };



BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);



snprintf((char*)postfix, 5, "%04x", (unsigned int)(mac0));



// ok to write trailing null, altough unnecessary if the base pointer includes it already

memcpy(device_name, device_name_base, strlen((const char *)device_name_base));

memcpy(device_name + strlen((const char *)device_name_base), postfix, sizeof(postfix));



err_code = sd_ble_gap_device_name_set(&sec_mode,

                                      device_name,

                                      strlen((const char *)device_name));

APP_ERROR_CHECK(err_code);



memset(&gap_conn_params, 0, sizeof(gap_conn_params));



gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;

gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;

gap_conn_params.slave_latency     = SLAVE_LATENCY;

gap_conn_params.conn_sup_timeout  = CONN_SUP_TIMEOUT;

dgerman · March 24, 2019, 4:29pm

badiu:
Why do you want to change the name?
The current code generates a unique name based on the MAC address of the device. This permits unique names for each ruuvi.

badiu · March 25, 2019, 1:18am

Right now im doing some project on ruuvi ,my company will buy several of Ruuvi and place them in several block and level. My idea to put Ruuvi name according to block and its level such RuuviB1L2(ruuvi at block 1 and at level 2)

otso · March 25, 2019, 10:30am

Making a separate firmware for each tag might not be the best approach. Have you considered using MAC addresses of RuuviTags to identify the beacon and name the beacons by MAC on your application or backend?

You can check lab.ruuvi.com live demo for an example on how to name tags on the backend side rather than renaming the tags themselves.