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

Sensor logger verbosity #481

Closed
thkrmr opened this issue Jan 5, 2024 · 2 comments
Closed

Sensor logger verbosity #481

thkrmr opened this issue Jan 5, 2024 · 2 comments
Labels
enhancement New feature or request no-stale

Comments

@thkrmr
Copy link

thkrmr commented Jan 5, 2024

Hi!

My HA logs are full of entires like:

2024-01-05 16:18:06.668 INFO (MainThread) [custom_components.meross_cloud.sensor] Refreshing instant metrics for device TV (mss310) power W - Main channel
2024-01-05 16:18:06.671 INFO (MainThread) [custom_components.meross_cloud.sensor] Refreshing instant metrics for device TV (mss310) voltage V - Main channel
2024-01-05 16:18:07.765 INFO (MainThread) [custom_components.meross_cloud.sensor] Refreshing instant metrics for device TV (mss310) energy kWh - Main channel

I see in sensor.py:
One instance it's a debug log _LOGGER.debug(f"Refreshing instant metrics for device {self.name}"), but int 3 other places it's _LOGGER.info(f"Refreshing instant metrics for device {self.name}") at info level logger.

Is the level of verbosity at INFO necessary for the refreshing? Should it be debug instead?

@albertogeniola albertogeniola added enhancement New feature or request no-stale labels Feb 12, 2024
@albertogeniola
Copy link
Owner

Hi @thkrmr ,

that seems reasonable to me. I'll see if I can change this behaviour in the next releases.

Thanks!

@albertogeniola
Copy link
Owner

Hi @thkrmr ,

this has been just implemented in v1.3.1.

Thanks a lot for the heads-up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-stale
Projects
None yet
Development

No branches or pull requests

2 participants