I don't see how the SmartThings documentation disagrees with @Cobra's use of
info level log messages:
The color scheme of the log level classifications is "locked", because it's part of the Groovy Environment of the hub itself, which apps and drivers have no access to, as far as I know.
To my knowledge
[error] level messages generated by the hub's JVM cannot be silenced or suppressed, and that's a good thing, because they inform the developer (or unwitting user) of unexpected situations in the app or device driver code.
On the other hand, the output and management of
[error] and any other level of log messages generated by apps or device drivers is totally left up to the developer / programmer. I can think of few cases on both the ST and Hubitat platforms where an app / device driver uses the full range of levels and makes use of a logging level "threshold" setting. Most seem to use just the
[info] levels for log messages, and if there's any user control, it's either a permanent or timer-based toggle setting.
If you're looking for a global setting to enable / disable certain levels of log message output, then you'd need to direct that request to Hubitat. I can see some advantages to that, but then there is of course the confusion that comes out of have two control points: globally as well as on a per app / per device basis. I don't think it would be a good idea for an app to have control over the log output levels of a device unless the device was specifically created by the app (e.g., a virtual device, or a bridged device controlling something connected to a third party server/system).