-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to log more data to MQTT #2022
Comments
we used to have an MQTT logger a few years ago but the quantity of messages were generating instabilities. |
Perhaps instabilities were caused by the memory corruption bug in jsonQueue that is now fixed? |
It may be. |
This issue is stale because it has been open for 90 days with no activity. |
Would still be good to get a way to get more verbose logging via MQTT. |
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: