I’m using a few shelly switches in my setup, and the MQTT events they send flood my HABapp logs. Stopping to listen is not the best solution because I want write a few MQTT based rules.
Is there a way to seperate the events in two logfile sinks?
For the record, I’m using HABapp 24.11.1 productive and 25.02.0-DEV-1 for experimenting.
Yes - you can moddify the existing logging config.
Just copy paste the existing event logging config but use the mqtt event logger for the second file.
Sorry, I might be a bit thick, and my Python-Fu is failing me…
in logging.yaml, I can see “HABApp.EventBus:” in the loggers section. What would I need to reference the mentioned mqtt event logger in this case?
My bad - I thought you had the DEBUG log enabled and were seeing the raw events from the mqtt connection. There it’s a specific mqtt logger.
If you want to limit the INFO event log the only way to achieve this is by creating a logging filter and attaching it to the event bus logger.
You can identify the mqtt messages by the forward slashes which occur before the colon.