You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is a feature request or a bug :)
The MQTT topic LOGtoMQTT seems to only log a single entry at startup/restart of the device detailing the reason for the startup, namely something like:
"reason": 6,
"uptime": 2490
Changing the Log Level in the GUI has no effect.
I (perhaps naively) expected changing the log level in the GUI to allow for more verbose logging to MQTT.
Would it make sense to allow for more verbose logging to MQTT so that you aren't restricted to logging via the serial interface which is a PITA when your receiver is distant from your PC work area.
The text was updated successfully, but these errors were encountered:
we used to have an MQTT logger a few years ago but the quantity of messages were generating instabilities.
It may not be the case anymore with the central queue implementation.
Not sure if this is a feature request or a bug :)
The MQTT topic
LOGtoMQTT
seems to only log a single entry at startup/restart of the device detailing the reason for the startup, namely something like:Changing the Log Level in the GUI has no effect.
I (perhaps naively) expected changing the log level in the GUI to allow for more verbose logging to MQTT.
Would it make sense to allow for more verbose logging to MQTT so that you aren't restricted to logging via the serial interface which is a PITA when your receiver is distant from your PC work area.
The text was updated successfully, but these errors were encountered: