hassio-plejd: [plejd-api] Unable to retrieve session token response: Request failed with status code 403 Error: Request failed with status code 403
I have just installed my raspberry pi4, and the purpose of it was that i would like to have all my gadgets in the same box. but i cant get the Plejd integration to work…
this is what i get when i try to start it up…
2021-02-10 00:02:41 ERR [plejd-api] Unable to retrieve session token response: Request failed with status code 403
Error: Request failed with status code 403
at createError (/plejd/node_modules/axios/lib/core/createError.js:16:15)
at settle (/plejd/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/plejd/node_modules/axios/lib/adapters/http.js:260:11)
at IncomingMessage.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:302) UnhandledPromiseRejectionWarning: Error: unable to retrieve session token response: Error: Request failed with status code 403
at /plejd/PlejdApi.js:67:18
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:302) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:302) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 28 (3 by maintainers)
Great to hear you managed to solve it! Closing this now then.
@Cederstrom96 : Probably same issue then - requests are throttled by the Plejd API. Stop the addon for a while and try again.
@Rilleboy : This is a completely different error. I have actually never seen exceptions from the mqtt library, so no real clue what happens here. Has 0.5.1 worked before for you? Have you updated anything else?
That the original error re-appears is due to code structure of the 0.5.X (and earlier) releases, I’m trying to address them in a larger code restructure. Basically what happens is that unhandled exceptions will restart the addon, meaning new requests to the Plejd API. If this happens too often, you will get throttled by the Plejd API.