[WIP] Bug: Some errors are logged without timestamp and plugin name #558
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Working on resolving issue #520 where some error messages are logged without timestamp and plugin name.
Analysis & Plan
Current Understanding
The issue appears to be that some error messages bypass the homebridge logging system and are logged directly to console without timestamp and plugin name. The platform correctly listens for rainbird library log events and routes them through proper homebridge logging methods, but there may be an edge case or timing issue causing some logs to bypass this system.
The error messages mentioned in the issue:
These should be caught by the platform's event listener and logged with proper timestamps and plugin names.
Fixes #520.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.