You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very handy to be able to view the log in the UI sometimes, but when the log is empty it's hard to know for sure if the log file has actually loaded, or if HA or the add-on are having issues and the log just isn't displaying.
For me personally, if I go to the Log Viewer and there are no messages, it makes me think that it might not actually be opening the log file, and I then have to open a terminal so I can to view the log file manually and confirm that it is in fact empty.
I think it might be helpful to some users if in addition to the existing buttons in the bottom right-hand corner of the screen, that there was also a button to add a test line to the log file, so you can confirm that you are in fact viewing the log file.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
It's very handy to be able to view the log in the UI sometimes, but when the log is empty it's hard to know for sure if the log file has actually loaded, or if HA or the add-on are having issues and the log just isn't displaying.
For me personally, if I go to the Log Viewer and there are no messages, it makes me think that it might not actually be opening the log file, and I then have to open a terminal so I can to view the log file manually and confirm that it is in fact empty.
I think it might be helpful to some users if in addition to the existing buttons in the bottom right-hand corner of the screen, that there was also a button to add a test line to the log file, so you can confirm that you are in fact viewing the log file.
The text was updated successfully, but these errors were encountered: