That wouldn’t work because the problem isn’t related to pins it’s related to pin labelling.
Check the pin map link I provided. It’s for the Mini because WeMos have removed the map for the full WeMos D1 from their site but I believe it’s the same general mapping.
WeMos did change at least 1 pin map between the original D1 and rev 2.
So to recap, the notes refer to GPIO numbers not WeMos pin labels, use the map.
It will get more confusing when you actually start coding for the WeMos because then there is a GPIO to pin label mapping system that can be used. I NEVER use D references for ESP’s, always GPIO references and a map.
Actually I have probably confused everyone, me included.
Blynk actually maps the WeMos pin labels to the relevant digital pins (GPIO).
So if you select a WeMos board in the app and then allocate a button to label D3 it will control GPIO 0.
In my defence, serious Blynkers hardly ever use digital pins as the virtual pins are so much more powerful.
Also for WeMos’ I normally select the generic ESP8266 board in the app as there are some features not available when you select WeMos.
Using a WeMos with Blynk is normally child’s play. Can’t undersand what your problem is.
Presumably you selected WeMos D1 device in the app, right?
You could try switching to the ESP8266 device and there you will see gp0, gp1, gp2 etc rather than “D” pins.
For the onboard LED you would want gp2. I think the LED is active LOW so the Blynk button will work in reverse i.e. ON will turn LED off etc. That’s another reason to use virtual pins but don’t consider that until you have completed this elementary step.
as per my last post, you will need to have the button in the off position to turn on the onboard LED.
You can change the labels in the app so OFF becomes ON etc but later you will move to virtual pins.
I understand, but have been toggling the buttons on and off so I agree the positions would be wrong but in one of the two I should see the LED come on right ?
Very, very, very occasionally when you select a device it appears not to recognise it. You can remove the device, refresh the token etc or switch to ESP8266 etc.
Just for your information. As I understand them… The device choices in the App determine:
How the App maps device layout to our visual reference. Things like Digital and Analog Pins with designations (A, D, or GPIO) and numbering; If only using Virtual Pins, then you could probably use any device choice for any project…
And limits the “available” number of Vpins, probably due to “processing power” of a device… but that can be adjusted with a single define in the sketch - #define BLYNK_USE_128_VPINS
You have to use Blynk Widget Digital D9 to control the onboard LED. Must be a mapping problem in the Blynk or Wemos drivers. Here’s what I’ve discerned by trial-and-error on my Wemos D1 mini: