MQTT-Display-LaserCutter/include
MaPaLo76 ae3e40f98d feat(mqtt): FR-012 Home Assistant MQTT Discovery (v1.5.0)
- MQTT_TOPIC_AVAILABILITY + MQTT_DISCOVERY_PREFIX in config.h
- LWT auf lasercutter/availability (online/offline, retained)
- publishDiscovery(): 8 retained Entities nach jedem (Re-)Connect
    binary_sensor: laser_active (device_class: running)
    sensor: session_sum (min), session_sec (s)
    sensor: total_time (hh:mm via Jinja2 value_template)
    sensor: firmware (diagnostic)
    switch: display (state aus status.display_on, cmd -> lasercutter/cmd)
    button: reset_session, reboot (entity_category: config)
- Heartbeat: neue Felder laser_active, session_minutes_sum,
    session_seconds, total_minutes fuer HA value_templates
- PubSubClient Buffer: 512 -> 1024 (Discovery-Nachrichten ~640 Bytes)
2026-03-04 19:40:54 +01:00
..
config.h feat(mqtt): FR-012 Home Assistant MQTT Discovery (v1.5.0) 2026-03-04 19:40:54 +01:00
display_manager.h feat(web+mqtt): FR-010 Webinterface-Redesign + MQTT-Steuerung 2026-03-01 17:28:47 +01:00
laser_tracker.h feat(tracker): resetSessionSum + MQTT reset_session + UI-Verbesserungen 2026-02-23 22:49:30 +01:00
mqtt_client.h feat(mqtt): FR-012 Home Assistant MQTT Discovery (v1.5.0) 2026-03-04 19:40:54 +01:00
README Initial Version of README.md 2026-02-22 10:34:37 +01:00
settings.h fix(auth): HTTP Basic Auth funktioniert korrekt 2026-02-23 22:09:28 +01:00
web_server.h feat(FR-002): Web Console via HTTP-Polling (/log + /log-data) -- v1.1.0 2026-02-28 17:24:56 +01:00
wifi_connector.h refactor(wifi): non-blocking WiFi-Architektur (Proposal B+D) 2026-02-26 21:05:22 +01:00

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