It looks like a BLE based module, so pick any BLE supported device I guess. But it doesn’t matter what hardware type you pick if you use only virtual pins in the App. The App device type is only for determining the I/O pin types when using direct pin connection in the Widgets.
Even with BT/BLE, the App must communicate with the Server, and the Server stores and controls the project operation… thus all devices need a Auth token regardless of connection method…
With normal IoT connection methods (Wifi, Ethernet) it is like this…
APP ← networking → SERVER ← networking → DEVICE
With BT/BLE the server is still in command and the App is still the GUI, but now also acts as a sub-link to the server for the device…
DEVICE ← BT/BLE → APP ← networking → SERVER
So far, due the lack of direct connection between the device and the server, there are some widgets and commands that do NOT work properly with the current BT/BLE connection method: email, sync, notifications? webhook, etc.
Just forget about that … Blynk seems to use BT/BLE differently, basically as a simple link.
It should work as well… but there are some more things to consider with Blynk and BT/BLE… they are effectively still in beta it seems, and possibly lower priority in development then normal IoT networking methods like WiFi.
You need to have the latest BETA version of the App… I think they are still running… With Android, you scroll to the bottom of the Blynk Play Store page on your phone and somewhere you will see option to join Beta program.
This is the code, compiled to U-BLOX NINA B112, that uses a NRF52832 core!
I use the bleperipheral
#define BLYNK_USE_DIRECT_CONNECT
#define BLYNK_PRINT Serial
#include <BlynkSimpleBLEPeripheral.h>
#include <BLEPeripheral.h>
#include <SPI.h>
// You should get Auth Token in the Blynk App.
// Go to the Project Settings (nut icon).
char auth[] = "xxxxxxxxxxxxxxxxxxxxxxxxxxxx";
// define pins (varies per shield/board)
#define BLE_REQ 6
#define BLE_RDY 7
#define BLE_RST 4
// create ble serial instance, see pinouts above
BLESerial SerialBLE(BLE_REQ, BLE_RDY, BLE_RST);
void setup() {
Serial.begin(9600);
SerialBLE.setLocalName("Blynk");
SerialBLE.setDeviceName("Blynk");
SerialBLE.setAppearance(0x0080);
SerialBLE.begin();
Serial.println("Waiting for connections...");
Blynk.begin(SerialBLE, auth);
}
void loop() {
SerialBLE.poll();
if (SerialBLE) { // If BLE is connected...
Blynk.run();
}
}
Bleperipheral works very fine no NINA B112, i have done many BLE applications!
OK… as I said, forget that… it works differently and we all know it (BT/BLE) generally functions just fine with dedicated standalone Apps designed for it.
Blynk however, uses BT/BLE as just a peer to peer link for an optional method of connecting their non-standalone App and devices with their IoT based server infrastructure.
I still have a BLE device that sometimes works, but often not, and even the type of phone/tablet I use seems to affect that when using Blynk… I find it so unreliable that I basically avoid BT/BLE options with Blynk.
And quite honestly, my personal thoughts are that BT/BLE is a low priority in the developers overall scheme of commercial applications.
So, sorry, but I can’t think of anything more I can suggest for your issue.