name | about | title | labels | assignees |
---|---|---|---|---|
Bug report | Create a report to help us improve |
Before creating a new issue please check that you have:
Fulfilling this template will help developers and contributors to address the issue. Try to be as specific and extensive as possible. If the information provided is not enough the issue will likely be closed.
You can now remove this line and the above ones. Text in italic is meant to be replaced by your own words. If any of the sections below are not relevant to the issue (for instance, the screenshots or crash report) then you can delete them.
Bug description A clear and concise description of what the bug is.
Steps to reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Device information
Copy-paste here the information as it is outputted by the device. You can get this information by typing info
via serial, terminal or in the debug tab in the web UI. The relevant information is that surrounded by the scissors-cut lines (---8<-------
).
If you cannot get this info from the device, please answer this questions:
Crash report Save the crash postmortem message, which may look something like:
Exception (28): epc1=0x4021e698 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
ctx: sys
sp: 3ffffc90 end: 3fffffb0 offset: 01a0
>>>stack>>>
...
<<<stack<<<
And, use one of the following tools to decode it:
When using PlatformIO, it is also possible to use a built-in exception decoder when device's serial connection is available:
pio device monitor --echo -e $environment -f esp8266_exception_decoder
Tools used
Additional context Add any other context about the problem here.