2024-09-14

.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 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,20 @@
+; 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:lolin32]
+platform = espressif32
+board = lolin32
+framework = arduino
+upload_port = /dev/ttyUSB0
+monitor_port = /dev/ttyUSB0
+monitor_speed = 115200
+monitor_filters = time;
+lib_deps =
+    knolleary/PubSubClient @ 2.8

src/main.cpp

@@ -0,0 +1,79 @@
+#include <Arduino.h>
+
+/*
+   ibeacon oder Beliebiger BLE Gerät Präsenz Überwachung mit Relais Anwesenheitserkennung 
+   
+   Michael Dworkin http://esp32-server.de/
+   Based on Neil Kolban example for IDF: https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/tests/BLE%20Tests/SampleScan.cpp
+   Ported to Arduino ESP32 by Evandro Copercini
+*/
+#include <BLEDevice.h>
+#include <BLEUtils.h>
+#include <BLEScan.h>
+#include <BLEAdvertisedDevice.h>
+#include <BLEAddress.h>
+#include <Ticker.h>
+#include <PubSubClient.h>
+ 
+String Adresse = "CF:D7:AB:1F:24:2C"; // Bluetooth Adresse die zu Anwesenheitserkennung überwacht wird
+const int RelaisPin = 22;             // Pin an dem Relais hängt
+int Verzoegerung = 15;                // Auschaltverzögerung wenn das Signal von BLE ibeacon fehlt
+ 
+int VerzoegerungZaeler = 0;
+Ticker Tic;
+static BLEAddress *pServerAddress;
+BLEScan* pBLEScan ;
+int scanTime = 30; //In seconds
+ 
+ 
+class MyAdvertisedDeviceCallbacks: public BLEAdvertisedDeviceCallbacks
+{
+    void onResult(BLEAdvertisedDevice advertisedDevice) // passiert wenn BLE Device ( beacon ) gefunden wurde
+    {
+      Serial.print(advertisedDevice.getAddress().toString().c_str()); // ibeacon Adresse anzeigen
+      if (advertisedDevice.getAddress().equals(*pServerAddress))      // ibeacon Adresse Vergleichen
+      {
+        Serial.print(" Ueberwachte Adresse");                         // wenn überwache Adresse gefunden wurde
+        if (advertisedDevice.haveName()) {
+          Serial.print(" Device name: ");
+          Serial.print(advertisedDevice.getName().c_str());
+        }
+        Serial.print(" RSSI: ");  
+        Serial.print(advertisedDevice.getRSSI());
+        Serial.print(" dB  ");  
+        Serial.print(advertisedDevice.getTXPower());
+        Serial.print(" ");  
+        digitalWrite (RelaisPin, LOW);                                  // Relais Einschalten
+        VerzoegerungZaeler = 0;                                       // Ausschaltverzögerung zurücksetzen
+        advertisedDevice.getScan()->stop();                           // Scanvorgang beenden
+      } // Found our server
+      Serial.println("");
+    }
+};
+ 
+void SekundenTic()  // Wird jede Sekunde ausgefüert
+{
+VerzoegerungZaeler++;  // Sekundenzähler
+if (VerzoegerungZaeler >= Verzoegerung) digitalWrite (RelaisPin, HIGH); // Wenn Verzögerungszeit erreicht wurde Auschalten
+}
+ 
+void setup() 
+{
+  pinMode (RelaisPin, OUTPUT);
+  digitalWrite (RelaisPin, HIGH);
+  Serial.begin(115200);
+  Serial.println("");
+  Serial.println("Starte BLE Scanner");
+  pServerAddress = new BLEAddress(Adresse.c_str());
+  BLEDevice::init("");
+  pBLEScan = BLEDevice::getScan(); //create new scan
+  pBLEScan->setAdvertisedDeviceCallbacks(new MyAdvertisedDeviceCallbacks());
+  pBLEScan->setActiveScan(true); //active scan uses more power, but get results faster
+  Tic.attach( 1,SekundenTic);
+}
+ 
+void loop()
+{
+  pBLEScan->start(scanTime);
+  delay(2000);      // Alle 2s nach ibeacon scannen
+}

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