Logging is available in development builds. It helps with troubleshooting firmware issues and configuration errors.
A serial monitor is required. The examples below use Microsoft Visual Studio Code with the Microsoft Serial Monitor extension.
Set serial monitor to:
Microsoft Visual Studio Code Logging settings
You can enable serial logging channels in system settings:
Configuration - read/write config messages
Sensors - sensor messages
Actors - actuator messages
Mash kettle - messages for kettle 1
Brew kettle - messages for kettle 2
NACHGUSS kettle - messages for kettle 3
Fermenter - fermenter mode messages
System - general system messages
Mashing process - mash process events
Nextion Display - display messages
Each channel supports off, error, info, verbose.
No output for this channel.
Only error messages.
Error messages plus process information.
Includes error + info and full diagnostic output, including SSE broadcasts.
System verbose logging also prints curl-like web server request traces.
Example:
Parts:
Message payload:
Boot log example
This shows firmware version, mDNS host, IP, and filesystem mount status.
Test sensor error
You can trigger a test sensor error via URL. Sensors use IDs starting at 0.
Open the same URL again to clear the error.
This is useful for testing Behavior in case of sensor error.
Logging with Microsoft VSCode
You can run VSCode in portable mode.
Download ZIP: Microsoft VSCodearrow-up-right
Extract ZIP into any folder.
Create a folder named data next to Code.exe.
Microsoft Visual Studio Code Install extension Serial Monitor by Microsoft.
Microsoft Visual Studio Code Microsoft Visual Studio Code Open output (Ctrl+Shift+U), select Serial Monitor, then choose COM port and 115200 baud. Start with Start Monitoring.
Microsoft Visual Studio Code