Skip to content
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

Open
puterboy opened this issue Aug 25, 2024 · 3 comments
Open

Add ability to log more data to MQTT #2022

puterboy opened this issue Aug 25, 2024 · 3 comments

Comments

@puterboy
Copy link
Contributor

puterboy commented Aug 25, 2024

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.

@1technophile
Copy link
Owner

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.

@puterboy
Copy link
Contributor Author

Perhaps instabilities were caused by the memory corruption bug in jsonQueue that is now fixed?

@1technophile
Copy link
Owner

It may be.
I'm currently improving the mqtt msg publish frequency. Still encountering issues, this work could be a prereq to an mqtt log publication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants