ChipChop Support Forum
Log in
Log out
Join the forum
My Details
REPLIES: 1
VIEWS: 135
BACK
REPLY TO THIS POST
TomaszB
13 Feb 2026
ChipChop.debug(false) - doesn't suspend logs generation
Hi Gizmo,

It is a minor issue:
Executing ChipChop.debug(false) doesn't suspend some messages sent to serial. Examples are below. Ususally it doesn't hurt, but in case when a serial is used for communication with other devices, it makes a bit of mess. Certainly, it is easy to comment all these lines like: Serial.println("Reconnecting as nothing was received after sending connection request") manually, in your library, but with every update it needs to be done again.
It would be great to have a setting (or just use: ChipChop.debug(false)) to ensure that nothing goes to a serial interface.

send_connection_request
ChipChopModulesManager::start
send_connection_request

Kind regards
Tomasz
Gizmo
13 Feb 2026

I know exactly what you mean and I agree it could be a problem, I will look into that over the weekend.
The issue is that the ChipChop.debug() is only a method for the ChipChopEngine but all other modules can have their own independent logging.

Leave it with me, I'll let you know when it's done