I have a very annoying problem, when i try to do a update request to the API on a specific PIN my whole NodeMCU sort of crashes (Diagnosed in the Serieal Monitor) very strange. When i try to trigger PIN in the app it just works fine without any problem. The update request that i make is just standard how it’s been documented in the API docs. I have tried so many things, can anyone help me?
I connected pin D8, after a API put request i see the device restarting so there is literally no error message just a reboot of the NodeMCU. That’s the weird thing.
D8 (GPIO 15 - the prefered way to reference pins in the IDE) is a semi special pin that needs to be set LOW during boot (it has a built in pulldown)… change it to one of the “safe” pins for general use…
Just the normal really plain Blynk code so nothing special, what i see in the serial is just the normal messages that the device is connected to the API. So what i replied to Gunner is no strange errors just a weird reboot of the nodeMCU after a API request.
Nope doesn’t work either It’s so strange because when i turn on PIN D2 (GPIO 4) what you said in the Blynk app i works flawless, but when i try to make a API request like: http://blynk-cloud.com/my_token/update/D2?value=1 it crashes the NodeMCU what i said earlier so strange.
@teumaas I hope you didn’t get confused in that last post… I know this and I still get tossed about by it (I always use vPins, so often forget this fact)…
Please note, the D in the API usage is a reference to “Digital”, not to be confused with the silkscreened Dx designation. The number used is still the sameGPIO number not the silkscreened one
Thanks for the response! but i already solved it by writing my own ExpressJS api, there i connected my NodeMCU with. So yeah thanks again for the help.