ESP8266-I2C-Driver VS Arduino

I haven't seen anyone use that particular library with the ESP8266 yet. I've personally tried the core Wire library, the Enjoyneering library, and the brzo_i2c library. The only issue I see offhand with that Multi_Bitbang library is at line 185 in the source: it's only waiting a half bit-time for the ACK, which will fail (NACK) with any part that does clock stretching; it won't see the ACK. The I2C spec allows for slave clock stretching on any of the bits, although I've only seen stretches on the ACK bit myself with the parts I've used.

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