hassio-plejd: unable to retrieve session token response: Error: Request failed with status code 404 (and 403)

Hi, i’m a first time user of the hassio-plejd add-on and I’m having issues getting it to work.

I’m running my hassio installation on rpi 4 4GB. I have installed and configured the Mosquitto mqtt addon and enabled discovery on the integration page.

I have also added this to my configuration.yaml:

mqtt:
  broker: https://192.168.x.xxx:xxxx
  username: !secret mqtt_uname
  password: !secret mqtt_pw
  discovery: true
  discovery_prefix: homeassistant
  birth_message: 
    topic: 'hass/status'
    payload: 'online'
  will_message: 
    topic: 'hass/status'
    payload: 'offline'

my config page looks like this:

site: Redacted number
username: redacted@redacted.com
password: redacted
mqttBroker: 'https://192.168.xx.xxx:xxxx'
mqttUsername: redacted
mqttPassword: redacted
includeRoomsAsLights: false
connectionTimeout: 2
writeQueueWaitTime: 400

Sometime I get this error:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Plejd
 Adds support for the Swedish home automation devices from Plejd.
-----------------------------------------------------------
 Add-on version: 0.4.7
 There is an update available for this add-on!
 Latest add-on version: null
 Please consider upgrading as soon as possible.
parse error: Expected string key before ':' at line 1, column 4
[14:05:10] ERROR: Unknown HTTP error occured
 System:   (armv7 / raspberrypi4)
 Home Assistant version: 0.112.4
 Supervisor version: 229
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:05:11] INFO: Starting the Plejd service...
[14:05:11] INFO: Verified permissions on startup script
[14:05:12] INFO: Executing startup script
[14:05:12] INFO: Wrote plejd.json
[14:05:12] INFO: Running add-on
starting Plejd add-on v. 0.4.7
plejd-api: login()
plejd-api: logging into **redacted**
error: unable to retrieve session token response: Error: Request failed with status code 404
(node:293) UnhandledPromiseRejectionWarning: unable to retrieve session token response: Error: Request failed with status code 404
(node:293) 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(). (rejection id: 2)
(node:293) [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.`

and sometime I get this error with a status code 403 instead, will update this post when I get that again

edit:

Here it is:

[14:34:01] INFO: Starting the Plejd service...
[14:34:01] INFO: Verified permissions on startup script
[14:34:01] INFO: Executing startup script
[14:34:02] INFO: Wrote plejd.json
[14:34:02] INFO: Running add-on
starting Plejd add-on v. 0.4.7
plejd-api: login()
plejd-api: logging into ***redacted***
error: unable to retrieve session token response: Error: Request failed with status code 403
(node:10605) UnhandledPromiseRejectionWarning: unable to retrieve session token response: Error: Request failed with status code 403
(node:10605) 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(). (rejection id: 2)
(node:10605) [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.

I should also mention I’m a bit unsure what to use on “site:” is it the top name visible in the app, or the account name visible after pressing the hamburger menu?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (1 by maintainers)

Most upvoted comments

Thanks, I’ll give it a go when I’m at the site