Row in Widget "Table" is not shown when String is 4 characters

Hello
I am new to Blynk. So far i like it very much but i have a really strange behaviour.

First off all:
I use an ESP32 Dev Board with Bluetooth Connection BLE
I use the IOS App

When i call:
table.addRow(rowCount,"name" ,"Float" );
it doesnt show up in the table in the app… but what is awkward… if i change the name… sometimes it gets shown and other times it doesnt… i tried a little bit and it seems to me, that it doesnt show up, if the name is exactly 4 characters… when i add a space after the name… example:
table.addRow(rowCount,"name " ,"Float" );
it is shown in the app…

Can someone check if it is the same issue with an Android app?

I made an example Scetch:

const String Names[5] ={"This", "is", "a","Test","Test2"};
float Time[5] = {0};

#define BLYNK_PRINT Serial

#define BLYNK_USE_DIRECT_CONNECT

#include <BlynkSimpleEsp32_BLE.h>
#include <BLEDevice.h>
#include <BLEServer.h>
char auth[] = "auth";

WidgetTable table;
BLYNK_ATTACH_WIDGET(table, V1);

  // Button on V10 adds new items
BLYNK_WRITE(V10) {
  if (param.asInt()) {
    for (int i=0;i<5; i++){
      table.addRow(i, Names[i], Time[i]);
      Blynk.virtualWrite(V1, "deselect", i);
    }
  }
}

// Button on V11 clears the table
BLYNK_WRITE(V11) {
  if (param.asInt()) {
    table.clear();
  }
}

void setup() {
  // put your setup code here, to run once:
  Blynk.begin(auth);
}
  
void loop() {
  // put your main code here, to run repeatedly:
  Blynk.run();
}

Looks like a bug of concatenating BLE message parts.

What happens if you increase the BLYNK_SEND_CHUNK value (in BlynkSimpleEsp32_BLE.h file)?

I increased the default of 20 to 25.
Now it works flawlesly… :slight_smile:

EDIT:
Nope it doesn’t I am filling Names in a table… and now the names with 4 characters work but another name disappeared… so not flawlesly at all…

@Eugene What does the BLYNK_SEND_CHUNG value change/affect? What happens when i increase or decrease the value?

1 Like

Right, this was an indicator if my assumption correct.

Please check the 2.26.1 (2) beta build with the fix. It is already available in TestFlight for testing.

I am not a beta tester…
My project isn’t this big… for me it is not a problem to wait for the official release.

Except you want me to check it for you.

Greetings

2 Likes