Using WROOM 32 or NodeMCU32S but no Pin 15 in Blynk Digital Pin drop down list

[PeteKnight]

@trakidbob

Where do I change this?

You don’t.

In the legacy version of Blynk, you selected a board type and this gave you a list of digital pins that related to that board.
When Blynk IoT was released, no digital pins were available at all. Later, they did add digital pins, but this was done in a very strange way, and there is no relationship between the pins available on the board and those available in Blynk.

I raised this issue a few years ago, but it seems it still remains.

But, the good news is that you can forget using digital datastreams. I never used them in the Legacy version of Blynk, and I don’t really know why they were re-introduced in Blynk IoT, because they aren’t needed.
Instead, you should use virtual datastreams, and add a simple virtual pin handler function into your code for each virtual datastream you use.

This guide was written for the legacy version of Blynk, but the basic principals and the code examples apply equal well to Blynk IoT

Using Virtual Pins to control physical devices

I thought I’d write a guide about how to use virtual pins with app widgets such as buttons, to control physical devices such as relays, LEDs etc… Why use virtual pins anyway? I’d always recommend using virtual pins over physical pins when developing your code. There are a number of reasons, but here are what I consider to be the main ones: Virtual pins are hardware independent. This means that it’s far easier to port your code from one hardware platform to another in future (when you realise…

There’s also a good description of how to use virtual datastreams in the Blynk IoT documentation…

Virtual Pins | Blynk Documentation

Pete.