Initial version - basis works

.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

.vscode/extensions.json

@@ -0,0 +1,10 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ],
+    "unwantedRecommendations": [
+        "ms-vscode.cpptools-extension-pack"
+    ]
+}

include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

platformio.ini

@@ -0,0 +1,18 @@
+; PlatformIO Project Configuration File
+;
+;   Build options: build flags, source filter
+;   Upload options: custom upload port, speed and extra flags
+;   Library options: dependencies, extra library storages
+;   Advanced options: extra scripting
+;
+; Please visit documentation for the other options and examples
+; https://docs.platformio.org/page/projectconf.html
+
+[env:esp32doit-devkit-v1]
+platform = espressif32
+board = esp32doit-devkit-v1
+framework = arduino
+lib_deps = 
+	ayushsharma82/AsyncElegantOTA@^2.2.7
+	#me-no-dev/ESP Async WebServer@^1.2.3
+    https://github.com/me-no-dev/ESPAsyncWebServer.git

src/main.cpp

@@ -0,0 +1,78 @@
+#include <Arduino.h>
+#if defined(ESP8266)
+#include <ESP8266WiFi.h>
+#include <ESPAsyncTCP.h>
+#elif defined(ESP32)
+#include <AsyncTCP.h>
+#include <WiFi.h>
+#endif
+
+#include <AsyncElegantOTA.h>
+#include <ESPAsyncWebServer.h>
+
+const char* ssid = "JoNelsDarlings";
+const char* password = "Paris2016";
+const int BUBBLE_GPIO = 4;
+boolean isBubbleFirstContact = true;
+unsigned long bubbleFreqSec = 0;
+unsigned long lastMillis = millis();
+
+AsyncWebServer server(80);
+
+void setup(void) {
+  pinMode(LED_BUILTIN, OUTPUT);
+  digitalWrite(LED_BUILTIN, LOW);
+  Serial.begin(115200);
+  WiFi.mode(WIFI_STA);
+  WiFi.begin(ssid, password);
+  Serial.println("");
+
+  // Wait for connection
+  while (WiFi.status() != WL_CONNECTED) {
+    delay(500);
+    Serial.print(".");
+  }
+  Serial.println("");
+  Serial.print("Connected to ");
+  Serial.println(ssid);
+  Serial.print("IP address: ");
+  Serial.println(WiFi.localIP());
+
+  server.on("/", HTTP_GET, [](AsyncWebServerRequest* request) {
+    request->send(
+        200, "text/html",
+        "Hi! This is the Wine-Sensor. Last bubble frequency: every <b>" +
+            String(bubbleFreqSec) + "</b> Seconds. [" + String(millis()) + "/" +
+            String(lastMillis) + "/" + String(isBubbleFirstContact) + "/" +
+            String(digitalRead(BUBBLE_GPIO)) +
+            "]"
+            "<script>window.setTimeout(_=>{window.location.reload();}"
+            ",1000)</script>");
+  });
+
+  AsyncElegantOTA.begin(&server);  // Start AsyncElegantOTA
+  server.begin();
+  Serial.println("HTTP server started");
+
+  pinMode(BUBBLE_GPIO, INPUT_PULLDOWN);
+  digitalWrite(LED_BUILTIN, HIGH);
+}
+
+void loop(void) {
+  // digitalWrite(LED_BUILTIN, digitalRead(BUBBLE_GPIO));
+
+  // This runs real fast, so make sure that only the "first contact" is measured
+  if ((digitalRead(BUBBLE_GPIO) == HIGH) && isBubbleFirstContact) {
+    digitalWrite(LED_BUILTIN, LOW);
+    if (millis() > lastMillis) {  // don't measure if we had an overflow...
+      bubbleFreqSec = (millis() - lastMillis) / 1000;
+    }
+    lastMillis = millis();
+    isBubbleFirstContact = false;
+  } else if ((digitalRead(BUBBLE_GPIO) == LOW)) {
+    isBubbleFirstContact = true;
+  }
+
+  // need to slow it down a bit to prevent fluctuating state cahange
+  delay(100);
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner and project tests.
+
+Unit Testing is a software testing method by which individual units of
+source code, sets of one or more MCU program modules together with associated
+control data, usage procedures, and operating procedures, are tested to
+determine whether they are fit for use. Unit testing finds problems early
+in the development cycle.
+
+More information about PlatformIO Unit Testing:
+- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html