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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug.yml
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -33,14 +33,14 @@ body:
33
33
attributes:
34
34
label: Firmware Version
35
35
description: Enter the ESPHome firmware version number.
36
-
placeholder: e.g., 2026.3.21
36
+
placeholder: e.g., 2026.4.1
37
37
validations:
38
38
required: false
39
39
- type: input
40
40
attributes:
41
41
label: Blueprint Version
42
42
description: Enter the Blueprint version number.
43
-
placeholder: e.g., 16
43
+
placeholder: e.g., 17
44
44
validations:
45
45
required: false
46
46
- type: dropdown
@@ -93,9 +93,15 @@ body:
93
93
Please follow the guidelines below to ensure the logs are comprehensive:
94
94
95
95
- **Boot Issues**: If the problem occurs during boot, capture the logs from the start of your device to a minute or two after the boot completes.
96
+
97
+
98
+
96
99
Look for errors or unusual messages during this period.
97
100
98
101
- **TFT File Update Issues**: For problems related to TFT file updates, include logs from the moment you press the **Update TFT Display** button until a few seconds after the device restarts.
102
+
103
+
104
+
99
105
Pay attention to any error messages or warnings during the update process.
100
106
101
107
- **Other Issues**: For other types of problems, include logs that encompass the issue's onset and continue for a short duration thereafter. This will help in pinpointing the exact moment and nature of the issue.
@@ -118,4 +124,5 @@ body:
118
124
- **Relevancy is Key**: To expedite troubleshooting, avoid including logs that are not related to the issue at hand. This helps in focusing on the pertinent information.
119
125
120
126
Your attention to sharing targeted and relevant log data is greatly appreciated and aids in efficient problem resolution.
0 commit comments