Scan mode or similar feature

[Nebnenut]

It might be useful to introduce some kind of “scan mode”. This could include a switch that temporarily disables regular polling/queries.

Background: When searching for a specific value or analyzing something in detail, the log can currently grow very quickly because continuous entries are still being generated. A dedicated scan or pause mode would make it easier to inspect or search for specific values without the log filling up unnecessarily.

Potential benefits:

• clearer logs during analysis or troubleshooting
• easier identification of specific values
• fewer unnecessary log entries
• optional feature that doesn’t affect normal operation when disabled

What do you think — would such a mode be useful for future improvements?

[kr0ner]

So you mean disable logging but only print UNKNOWN hex ids and their raw values?

[Nebnenut]

That's right.

[kr0ner]

we could use logger.set_level and set it to WARN and also change UNKNOWNS from INFO to WARN

logger.set_level Action 
Set the log level at runtime. The level can only be set to a level that is no less severe than the global log level.

level (Required, string): The new log level to set.
tag (Optional, string): The tag to set the log level for. If not set, the global log level will be set.

on_...:
  then:
    - logger.set_level: INFO

    - logger.set_level:
        level: DEBUG
        tag: mqtt.client
ℹ️ Note

When using logger.set_level with a tag parameter, runtime per-tag log level support is automatically enabled. If you need to call set_log_level() directly from a lambda or external component, you must manually enable runtime_tag_levels: true in the logger configuration.