-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
z2m plugin debug bug #35
Comments
This behavior is very confusing. As you know, I have a lot of devices and the little log shows way too many messages, making it hard to read with all those debug messages I don't need. From a user experience, there are way too many ways to enable/disable debug logs. If you ask me, one log type should be globally selected and then one for each plugin. Everything else is too much. |
Try this video because the upload to GitHub did not work. |
What would you like to have and not to have? |
One option to globally change the log type and one option to enable/disable debug for each plugin should be enough. Another thing that confused me is the log in the home tab shows different content than the log in the log tab. How would any user know this is the expected behavior? The log in the home tab does not have much room and sometimes the debug messages use up a lot of room making it hard to follow. See my example below. |
For the debug:
- the frontend log has his own system and display only matterbridge and plugins:
- the console log displays the matterbridge and matter.js log with the level you select here or from the command line:
![image](https://private-user-images.githubusercontent.com/132135057/342490040-2cd26dab-275e-4b1e-80b0-b8ad7be1cf17.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5NTQ2MzAsIm5iZiI6MTcxOTk1NDMzMCwicGF0aCI6Ii8xMzIxMzUwNTcvMzQyNDkwMDQwLTJjZDI2ZGFiLTI3NWUtNGIxZS04MGIwLWI4YWQ3YmUxY2YxNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwMlQyMTA1MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05ODI2ZjYwOWFkNDc3YTEzMmMyNThhMTI2ODdhNTAzYzE2Njk1ZWU5MDQ4NThhNjJhNWRhMzYzZTA0MTJiYWQ4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.jkzb7-QFF7Lm8R4Cpt0DRMUIS9kSsZTfCk07kGjmnZY)
![image](https://private-user-images.githubusercontent.com/132135057/342490631-72dd472d-28d0-4f91-a4ea-deff7db21c6f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5NTQ2MzAsIm5iZiI6MTcxOTk1NDMzMCwicGF0aCI6Ii8xMzIxMzUwNTcvMzQyNDkwNjMxLTcyZGQ0NzJkLTI4ZDAtNGY5MS1hNGVhLWRlZmY3ZGIyMWM2Zi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwMlQyMTA1MzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02NjI2M2RkOTFiMDVhZjY1MDRjNzU4ZmU0NTBiOGJhMTExZWI5ZGFmNWNmYmI1NjQ5MzQ0OThjN2NiZDNhMTk1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.J8ncSQaR-PSuSx2pT3Mcdc9OIngNMFHm5joBbuVopHA)
- the console log also displays the plugin log with or without debug depending on this:
Originally posted by @Luligu in #33 (comment)
Please take a look at this video and let me know if the debug messages in the home tab are intended.
2024-06-25.22-58-43.mp4
The text was updated successfully, but these errors were encountered: