The Logger type and numeric mapping actually used at runtime
The Logger enum is defined in src/libelvutils/Logger.h:
typedef enum { LOG_ALL, LOG_DEBUG, LOG_INFO, LOG_NOTICE, LOG_WARNING, LOG_ERROR, LOG_FATAL_ERROR } LogLevel;
This means numeric values correspond to:
0 = LOG_ALL
1 = LOG_DEBUG
2 = LOG_INFO
3 = LOG_NOTICE
4 = LOG_WARNING
5 = LOG_ERROR
6 = LOG_FATAL_ERROR
See: https://github.com/OpenCCU/OpenCCU-Base/blob/main/src/libelvutils/Logger.h
The rfd.conf comment you pointed at (line shown) is inconsistent with this enum. The comment reads: "# Log Level: 1=DEBUG, 2=WARNING, 3=INFO, 4=NOTICE, 5=WARNING, 6=ERROR"
That mapping is incorrect relative to the code: the code casts the integer directly to the enum, so the actual runtime mapping is the enum order above (1=DEBUG, 2=INFO, 3=NOTICE, 4=WARNING, 5=ERROR, 6=FATAL_ERROR). Also note CONFIG_DEFAULTS in rfd.cpp sets the default "Log Level" to "3" — that corresponds to LOG_NOTICE in the enum, even though the rfd.conf comment says "Default is Info". So there are two mismatches in the comment: the ordering and the stated default.
https://github.com/OpenCCU/OpenCCU-Base/blame/5e9d5a4f59aeea8f951dacd1ba29edc60fc314b6/src/rfd/rfd.conf#L14
sorry fuer den "AI-slop" unten.
LEvel 2 und LEvel 5 sind als "WARNING" kommentiert.
Es ist unklar wie die Abstufung der loglevel tatsaechlicht ist, die Kommentarzeile sollte jemand der die Details kennt mal klarstellen.
(ab hier AI code Analyse, falls es jemand interessiert)
Direct answer — it's a comment that documents how the rfd daemon's numeric "log level" setting maps to human-readable severity names.
What the line means
Notes / observations
[...]