Digital pin datasteams have only just been added to the web console in the past day or so, and I think this may be for testing. Blynk have made no announcement about them, and the available pins seem odd to me.
More info here:
I’ve not tested them yet (I never used them in Legacy Blynk anyway, so that are of no interest to me) and I’d stick with virtual pins for now at least.
As the onboard LED (if there is one on your board) is used to indicate that the device is in provisioning mode, I’d steer clear of trying to use that for anything else at this stage.
No, it means that the following settings in the Settings.h tab will be used…
#if defined(USE_WROVER_BOARD)
#define BOARD_BUTTON_PIN 15
#define BOARD_BUTTON_ACTIVE_LOW true
#define BOARD_LED_PIN_R 0
#define BOARD_LED_PIN_G 2
#define BOARD_LED_PIN_B 4
#define BOARD_LED_INVERSE false
#define BOARD_LED_BRIGHTNESS 128
If your particular ESP32 has a button attached to GPIO15 and an RGB LED attached to GPIOs 0,2 & 4 then that’s the correct setting to use for your board.
Personally, I’ve never seen an ESP32 with this configuration, which is why I said:
These aren’t macros, they are conditional inclusions, where the code is only compiled if the condition is met.
A you’ll see when you look at the Settings.h tab that if nether #define USE_WROVER_BOARD or #define USE_TTGO_T7 are un-commented then the custom board definition will be used, and a compiler warning will be displayed.
It’s up to you to either edit one of these three definitions existing, or add your own for your particular board.
Pete.