NODE MCU v3.4 does not load the sketch with Arduino IOT

Hello,
I have a NODE MCU v 3.4 (ESP8266) that I am trying to use with Arduino IoT.
When I try to load the sketch it gives me this error and I don't understand why:

/usr/local/bin/arduino-cli compile --fqbn esp8266:esp8266:nodemcuv2:baud=921600,dbg=Disabled,eesz=16M14M,exception=disabled,ip=lm2f,lvl=None____,vt=flash,wipe=none,xtal=80 --build-cache-path /tmp --output-dir /tmp/1722228377/build --build-path /tmp/arduino-build-3B486220E5927B2A72B2FB82FCB54A77 /tmp/1722228377/Untitled_oct18a
Error during build: Invalid FQBN: getting build properties for board esp8266:esp8266:nodemcuv2: invalid value '16M14M' for option 'eesz'

Do you have any suggestions.

EzioGi

Hi @eziogi. It seems like maybe something is wrong with the configuration of the Device you have associated with your Thing. I wasn't able to reproduce the problem even when using a Thing with a "NodeMCU 1.0 (ESP-12E Module)" device as you have done. So I think it should be possible to fix the problem by creating a new Device and then associating your Thing with the newly created Device.

Please try this:

  1. Click the following link to open the Arduino IoT Cloud "Devices" page in your browser:
    https://create.arduino.cc/iot/devices
  2. Click the "ADD" button.
    The "Setup Device" dialog will open.
  3. Click on the "Third party device" area of the dialog.
  4. Select "NodeMCU 1.0 (ESP-12E Module)" from the "Select model" menu in the dialog.
  5. Click the "CONTINUE" button.
  6. Adjust the name in the "Device Name" field of the dialog.
  7. Take careful note of the name of the Device (it might get a bit confusing since now you see two different "NodeMCU 1.0 (ESP-12E Module)" Devices in your Arduino IoT Cloud account).
  8. Click the "NEXT" button.
    The dialog will now show the "Device ID" and "Secret Key" for the newly created Device.
  9. Save the "Device ID" and "Secret Key" to a safe place.
  10. Check the box next to "☐ I saved my device ID and Secret Key".
  11. Click the "CONTINUE" button.
  12. Click the following link to open the Arduino IoT Cloud "Things" page in your browser:
    https://create.arduino.cc/iot/things
  13. Select the Thing you are working on from the list on the "Things" page.
    The Thing page will open.
  14. Click the "Change" button under the "Associated Device" section of the Thing page.
    The "Associate Device" dialog will open.
  15. Select the Device you created during the first part of these instructions.
  16. Click the "Configure" button under the "Network" section of the Thing page.
    The "Configure network" dialog will open.
  17. Enter your network credentials in the "Wi-Fi Name" and "Password" fields of the "Configure network" dialog.
  18. Enter the "Secret Key" of the new Device in the "Secret Key" field of the dialog.
  19. Click the "SAVE" button.

Now try loading the Thing sketch again. Hopefully this time the "Error during build: Invalid FQBN: getting build properties for board esp8266:esp8266:nodemcuv2: invalid value '16M14M' for option 'eesz'" will not occur.


Please let me know if you have any questions or problems while following those instructions.

Okay, thank you for your help.
I will try to follow your instructions.

EzioGi

1 Like

Hi,
I used the procedure you wrote down.
But even though it sees the NODE MCU in the full editor it gives me the error that it should not appear anymore.
It also tells me Type error: a.exe as indefined.
EzioGi

Please provide the full and exact text of the error message.

Please provide the full and exact text of the error message.

The mistake is this:

/usr/local/bin/arduino-cli compile --fqbn esp8266:esp8266:nodemcuv2:baud=921600,dbg=Disabled,eesz=16M14M,exception=disabled,ip=lm2f,lvl=None____,vt=flash,wipe=none,xtal=80 --build-cache-path /tmp --output-dir /tmp/662315579/build --build-path /tmp/arduino-build-D6EA10D942757CB6883FAA3DF8E7A7E5 /tmp/662315579/Fontana_v1_oct23a

Error during build: Invalid FQBN: getting build properties for board esp8266:esp8266:nodemcuv2: invalid value '16M14M' for option 'eesz'

EzioGi

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.