ESP32 / ESP8266 & BME280 / SHT2x sensor with InfluxDB support
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
Thomas Buck 84199ccfc8 some lora tweaks 4 mēnešus atpakaļ
..
DebugLog.h lora rx tx test with unofficial lib 4 mēnešus atpakaļ
README Initial commit 4 gadus atpakaļ
SimpleInflux.h support Arduino Uno Wifi Developer Edition 3 gadus atpakaļ
SimpleUpdater.h add ArduinoOTA to ESP32 builds. although neither it nor the old SimpleUpdater work on the Heltec Lora32 devices. TODO. 4 mēnešus atpakaļ
User_Setup.h first simple cyd remote test 1 gadu atpakaļ
config.h some lora tweaks 4 mēnešus atpakaļ
html.h add temperature compensation. refactoring. dark-mode. debug-log with websockets. 2 gadus atpakaļ
influx.h post sml measurements to influxdb 4 mēnešus atpakaļ
lora.h try to save more energy and reduce hangs 4 mēnešus atpakaļ
memory.h add touchscreen calibration ui and eeprom 5 mēnešus atpakaļ
moisture.h support CCS811, serial relais. 2 gadus atpakaļ
mqtt.h ui now functioning for livingroom 5 mēnešus atpakaļ
relais.h support CCS811, serial relais. 2 gadus atpakaļ
sensors.h add feature-flags for libs, to fit 512k esp-01 version. 2 gadus atpakaļ
servers.h add temperature compensation. refactoring. dark-mode. debug-log with websockets. 2 gadus atpakaļ
smart_meter.h lora tx goes to deep sleep 4 mēnešus atpakaļ
ui.h date time printing on lorarx and auto reset 4 mēnešus atpakaļ

README


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