Arduino VS nodemcu-devkit-v1.0

The result is that the WiFiSecureClient doesn't work when used in the bot declaration, so I changed the variable to WiFiClient but I can't use the certificate, so I comment it out and ESP8266.h gives me a thousand errors due to lack of dependencies in its libraries. I should point out that I downloaded the entire project from the Arduino ESP8266, I don't know how to link all the libraries, so I simply took those from the ESP8266WiFi.

#include #include "time.h" #include "sntp.h" char* ssid = "WIFI"; char* password = "w1fi"; const char* ntpServer1 = "pool.ntp.org"; const char* ntpServer2 = "time.nist.gov"; const long gmtOffset_sec = 3600; const int daylightOffset_sec = 3600; const char* time_zone = "CET-1CEST,M3.5.0,M10.5.0/3"; // TimeZone rule for Europe/Rome including daylight adjustment rules (optional) void printLocalTime() { struct tm timeinfo; if(!getLocalTime(&timeinfo)){ Serial.println("No time available (yet)"); return; } Serial.println(&timeinfo, "%A, %B %d %Y %H:%M:%S"); } // Callback function (get's called when time adjusts via NTP) void timeavailable(struct timeval *t) { Serial.println("Got time adjustment from NTP!"); printLocalTime(); } void setup() { Serial.begin(115200); // set notification call-back function sntp_set_time_sync_notification_cb( timeavailable ); /** * NTP server address could be aquired via DHCP, * * NOTE: This call should be made BEFORE esp32 aquires IP address via DHCP, * otherwise SNTP option 42 would be rejected by default. * NOTE: configTime() function call if made AFTER DHCP-client run * will OVERRIDE aquired NTP server address */ //sntp_servermode_dhcp(1); // (optional) /** * This will set configured ntp servers and constant TimeZone/daylightOffset * should be OK if your time zone does not need to adjust daylightOffset twice a year, * in such a case time adjustment won't be handled automagicaly. */ configTime(gmtOffset_sec, daylightOffset_sec, ntpServer1, ntpServer2); /** * A more convenient approach to handle TimeZones with daylightOffset * would be to specify a environmnet variable with TimeZone definition including daylight adjustmnet rules. * A list of rules for your zone could be obtained from https://github.com/esp8266/Arduino/blob/master/cores/esp8266/TZ.h */ //configTzTime(time_zone, ntpServer1, ntpServer2); //connect to WiFi Serial.printf("Connecting to %s ", ssid); WiFi.begin(ssid, password); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println(" CONNECTED"); } void loop() { delay(5000); printLocalTime(); // it will take some time to sync time :) }

https://github.com/esp8266/Arduino http://arduino.esp8266.com/stable/package\_esp8266com\_index.json https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads

He meant the Arduino framework. There is an Arduino core for the ESP8266 so you can use Arduino’s IDE and libraries for the ESP with this core here

According to this link(https://github.com/esp8266/Arduino/issues/6174) WeMos can't receive broadcasts on SDK 2.2.1.

There are 2 ways to minimize power consumption while maintaining an active WiFi connection, but it's not a large power reduction for either mode. Look at Automatic Modem Sleep and Automatic Light Sleep here: https://github.com/esp8266/Arduino/tree/master/libraries/esp8266/examples/LowPowerDemo

That's the Arduino (Uno) library. If you've correctly installed the ESP8266 package then it should be 3.(something-ish) for the ESP8266 version of the WiFi library. Current is 3.1.1 for the core files, and the WiFi is part of the core libraries. If you have your compile options set for verbose then you should see it doesn't access that old Arduino WiFi library.

Seems it's expected https://github.com/esp8266/Arduino/issues/721

This appears to be a NodeMCU, which is an open source dev board: you can just look up the schematics

ESP8266 boards out there, such as the NodeMCU (see here, under ESP-12 Core), normally have a 100uF SMD Tantalum capacitor for this purpose.

It should be fine. The Vin pin is indeed normally Voltage IN but on the nodemcu board as per the schematics it should work given that the 5V supply is powerful enough. I've done it myself multiple times. What type of relay module do you have? Have you connected the grounds together if using separate power supplies?

Board: NodeMcu 1.0 (I de-soldered the LEDs and serial chip to save power once programmed)

The NodeMCU v1.0 is based on the CP2102. Doesn't get much eachier than that.

Guess my only solution would be having to wire it to the USB input somehow. If I could somehow find the VU pin it would allow me to perhaps solder that pin directly to the Vin pin? Unfortunately this version did not populate VU on the board. From what I can see in schematics,(This is V1 so it may not be true) VU has a Schottky Barrier Plastic Rectifier Diode (Schematic) between it and Vdd (VIn) Perhaps tapping into that port could work? (This is V1 so it may not be true) VU has a Schottky Barrier Plastic Rectifier Diode (Diagram) between it and Vdd (VIn)

I don't see VIN max mentioned there but https://github.com/nodemcu/nodemcu-devkit-v1.0/blob/master/Documents/NCP1117ST33T3G.PDF says 10V if yours has the 1117. Either way 12V is pushing it, and as I mentioned lead is greater than 12V when charged, just like other chemistries like Lithiums say ~3.7V but charged are actually around 4.2V

It has the same pinout as a NodeMCU except for that ADC pin where the NodeMCU has a reserved pin. The ADC pin might differ from the A0 pin by including a voltage divider to match a D1 mini, but I'm just speculating and I'd recommend not using it. It looks different because they put the parts of the ESP-12 module directly on the PCB, which is going to same some money on the build. You should be fine treating it like a NodeMCU.

Yes. If you look at the schematic and prints (that's 1.0, but not much has changed), that's R10. Connects GPIO16 (aka XPD_DCDC) to /RST (aka EXT_RSTB). From the ESP8266 datasheet: