HA Error handling and reporting is inadequate and puts too much on the user to make good error reports.
-
Errors in the log are often vague as to the source
-
It’s on the user to figure out the source and often enable other logs and try to determine how to recreate the errors which may not be possible because the user does not know the sequence of events that led to the error. Errors are often posted in the log without a message being raised to the users and when the user is not manipulating the system. These errors are only discovered from a log review
-
The user must determine and supply details of information known to the system
-
It’s on the user to figure out where to report errors when the error in logs don’t prove that information
-
Suggestions for improvements.
Create an error handling and Report system that:
a. Is standardized and consistent across all HA core, frontend, addon, HACS,etc.
b. Provides a Click button to report Error
c. Collects all known (by HA) information automatically
d. Creates and populates a standardized error report in GitHub with ALL system and error information known to HA
e. Clearly identifies the source module or system, of the error in the error log
f. Error log provides all required data and detail for Errors obviating the need to try to recreate.
g. ONLY systems that implement this standard error and report process can obtain the highest quality rating
h. Errors in the log always include a URL to report Errors to the correct owner of the system that created the error
i, A standardized error log entry with mandatory and optional fields that can be easily parsed by (b-f) above