-
Notifications
You must be signed in to change notification settings - Fork 21
Understanding error messages
René Vollmer edited this page Jun 16, 2020
·
7 revisions
(First draft, to be continued)
- Library errors
- HTTP errors
- TR-064 errors
- µController errros
See http error messages for an overview. We mostly get 500 errors, when the request is not valid in some way (e.g. asking for details of a device with an unknown MAC address).
From first steps user guide, unless otherwise stated.
Code | Meaning | Note |
---|---|---|
503 | service unavailable | The service may use HTTP status code 503 instead of 401 if too many unauthenticated requests from one client are made |
401 | unauthorized, unknown or obsolete action | |
402 | number of arguments for an action is not as expected or an unexpected argument is used | |
606 | Action not authorized | user is authenticated but has not the needed rights |
866 | Second factor authentication (2FA) required | Action needs 2FA (not supported by library yet) |
867 | 2FA blocked | Action needs 2FA (not supported by library yet) |
868 | 2FA busy | Action needs 2FA (not supported by library yet) |
For ESPs see here.
Possible fix: First ensure you have a really good power supply. This often causes issues. You might have to try different ones. If that does not help, this is tricky. If you believe it has something to do with this library, you can always open an issue.