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

CONFIG_GOLIOTH_LOG_LEVEL_* doesn't affect golioth_coap_client_zephyr log messages #413

Open
cdwilson opened this issue Mar 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@cdwilson
Copy link
Collaborator

Golioth Firmware SDK Commit Hash

11ed198

Platform/OS

NCS v2.5.2

Hardware Target

Aludel Elixir Rev B

What host OS are you using?

macOS Sonoma 14.4

Current Behavior

Setting CONFIG_GOLIOTH_LOG_LEVEL_* doesn't affect log messages generated by the golioth_coap_client_zephyr module (coap_client_zephyr.c).

For example, if I set CONFIG_GOLIOTH_LOG_LEVEL_ERR=y in prj.conf, I still see the following log messages in the console:

[00:07:45.026,641] <wrn> golioth_coap_client_zephyr: Receive timeout
[00:07:45.028,228] <err> golioth_coap_client_zephyr: Failed to receive: -128
[00:07:45.028,686] <inf> golioth_coap_client_zephyr: Ending session
[00:07:48.565,612] <inf> golioth_coap_client_zephyr: Golioth CoAP client connected
[00:07:48.566,406] <inf> golioth_coap_client_zephyr: Entering CoAP I/O loop

Expected Behavior

I expected that CONFIG_GOLIOTH_LOG_LEVEL_* would set the log level for all log messages generated by the Golioth SDK.

Steps To Reproduce

  1. Set CONFIG_GOLIOTH_LOG_LEVEL_ERR=y in prj.conf
  2. See Zephyr UART console for log messages generated by the golioth_coap_client_zephyr module

Logs, console output, or any kind of debug information

No response

@cdwilson cdwilson added the bug Something isn't working label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant