Skip to content
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

Merged
merged 2 commits into from
Dec 25, 2024
Merged

Updated troubleshooting page #3353

merged 2 commits into from
Dec 25, 2024

Conversation

Ricc68
Copy link
Contributor

@Ricc68 Ricc68 commented Dec 24, 2024

Made following changes as per Koenkk/zigbee2mqtt#23282 (comment):

  • Added HASH_ERROR_TIMEOUTS and HOST_FATAL_ERROR cases to troubleshooting page
  • Changed 'fails to start' to 'fails to start/crashes runtime'
  • Added requirement to first time run npm install to avoid dependancy issues with 'npm ci'

@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.

Ricc68 added 2 commits December 24, 2024 21:31
…ting page

- Added requirement to first time run npm install to avoid dependancy issues with 'npm ci'
@Koenkk Koenkk merged commit fe9e511 into Koenkk:master Dec 25, 2024
1 check passed
@Koenkk
Copy link
Owner

Koenkk commented Dec 25, 2024

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`
Copy link
Contributor

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.

Copy link
Contributor Author

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.

Koenkk added a commit that referenced this pull request Dec 28, 2024
Koenkk added a commit that referenced this pull request Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants