-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Updated troubleshooting page #3353
Conversation
…ting page - Added requirement to first time run npm install to avoid dependancy issues with 'npm ci'
Many thanks! |
@@ -208,3 +208,34 @@ This happens when you edit one or more of the `pan_id`, `network_key` or `ext_pa | |||
``` | |||
ext_pan_id: [0x39,0xaf,0x4d,0x83,0xh2,0xdc,0xb3,0x89] | |||
``` | |||
|
|||
## Error: runtime crash with `status=HASH_ERROR_TIMEOUTS` or fail to start with `status=HOST_FATAL_ERROR` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error is ASH_ERROR_TIMEOUTS
not HASH_ERROR_TIMEOUTS
.
HOST_FATAL_ERROR
is also too generic to put in this context (it can have many, many causes).
I think it's best to remove the references to ember-specific errors since I'm sure the same applies to other stacks. Maybe a header like this: Regular crashes with timeout or failure to start after serial opened
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad for the typo.
I agree that a generic header will help more than references to ember-specific errors.
I will change the header as per your suggestion.
Made following changes as per Koenkk/zigbee2mqtt#23282 (comment):
@Koenkk please review this commit and let me know if I can do something better.
Sorry for too long commit description: it's first time in years that I use git so had to re-learn and I did not remember that is not a good idea to use commit description as changelog.