commit dbd02b3f14330ecc018dd66f02a3ec5e6741b492 Author: Manuel Tack Date: Sun Nov 23 17:12:32 2025 +0100 Initial Commit diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/.vscode/extensions.json b/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/.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" + ] +} diff --git a/include/README b/include/README new file mode 100644 index 0000000..49819c0 --- /dev/null +++ b/include/README @@ -0,0 +1,37 @@ + +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 convention is to give header files names that end with `.h'. + +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 diff --git a/lib/README b/lib/README new file mode 100644 index 0000000..9379397 --- /dev/null +++ b/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 the executable file. + +The source code of each library should be placed in a separate directory +("lib/your_library_name/[Code]"). + +For example, see the structure of the following example libraries `Foo` and `Bar`: + +|--lib +| | +| |--Bar +| | |--docs +| | |--examples +| | |--src +| | |- Bar.c +| | |- Bar.h +| | |- library.json (optional. for 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 + +Example contents of `src/main.c` using Foo and Bar: +``` +#include +#include + +int main (void) +{ + ... +} + +``` + +The PlatformIO Library Dependency Finder will find automatically dependent +libraries by scanning project source files. + +More information about PlatformIO Library Dependency Finder +- https://docs.platformio.org/page/librarymanager/ldf.html diff --git a/platformio.ini b/platformio.ini new file mode 100644 index 0000000..39563d2 --- /dev/null +++ b/platformio.ini @@ -0,0 +1,17 @@ +; 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:d1_mini] +platform = espressif8266 +board = d1_mini +framework = arduino +lib_deps = + knolleary/PubSubClient@^2.8 + adafruit/DHT sensor library@^1.4.6 diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..21a00c0 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,78 @@ +#include "DHT.h" +#include +#include + +#define DHTTYPE DHT22 + +uint8_t DHTPin = 4; + +DHT dht(DHTPin, DHTTYPE); + +const char* WIFI_SSID = "Mi 10"; +const char* WIFI_PASS = "12345678"; + +unsigned long lastMqttAttemptMs = 0; +const unsigned long MQTT_RETRY_MS = 3000; + +const char* MQTT_HOST = "broker.hivemq.com"; +const uint16_t MQTT_PORT = 1883; +const char* MQTT_CLIENTID = "bbsgut-dht22-d1mini-01"; +const char* TOPIC_TEMP = "bbsgut/sensor/dht22/temperature"; +const char* TOPIC_HUM = "bbsgut/sensor/dht22/humidity"; +const char* TOPIC_STATUS = "bbsgut/sensor/dht22/status"; + +float Temperature; +float Humidity; + +WiFiClient espClient; +PubSubClient mqtt(espClient); + +bool ensureWifi() { + if (WiFi.status() == WL_CONNECTED) return true; + WiFi.mode(WIFI_STA); + WiFi.begin(WIFI_SSID, WIFI_PASS); + unsigned long t0 = millis(); + while (WiFi.status() != WL_CONNECTED && millis() - t0 < 15000) { + delay(120); + } + return WiFi.status() == WL_CONNECTED; +} + +bool ensureMqtt() { + if (mqtt.connected()) return true; + if (!ensureWifi()) return false; + + if (millis() - lastMqttAttemptMs < MQTT_RETRY_MS) return false; + lastMqttAttemptMs = millis(); + + if (mqtt.connect(MQTT_CLIENTID, nullptr, nullptr, TOPIC_STATUS, 0, true, "offline")) { + return true; + } + return false; +} + +void setup() { + Serial.begin(115200); + delay(100); + + WiFi.mode(WIFI_STA); + WiFi.begin(WIFI_SSID, WIFI_PASS); + + mqtt.setServer(MQTT_HOST, MQTT_PORT); + + pinMode(DHTPin, INPUT); + + dht.begin(); + delay(500); + ensureMqtt(); +} + +void loop() { + ensureMqtt(); + mqtt.loop(); + Temperature = dht.readTemperature(); + Humidity = dht.readHumidity(); + mqtt.publish(TOPIC_TEMP, String(Temperature, 1).c_str(), true); + mqtt.publish(TOPIC_HUM, String(Humidity, 1).c_str(), true); + delay(1000); +} \ No newline at end of file diff --git a/test/README b/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/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