You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am considering making an official integration of ha-plejd, and the first step would be to create a config flow UI. I thought it would be nice to use the Plejd login to get the encryption key and device lists as hassio-plejd does, but when I try the login request in PlejdApi.js with curl, I get 401. I am 100% sure the username and password are correct - they work in the app. Is there anything I am missing in how this request is created?
Unfortunately, I am not running Hass.io, so I cannot try this add-on.
curl -i -X POST https://cloud.plejd.com/parse/login \
-H 'X-Parse-Application-Id: zHtVqXt8k4yFyk2QGmgp48D9xZr2G94xWYnF4dak' \
-H 'Content-Type: application/json' \
-d '{"username":"<redacted>","password":"<redacted>"}'
HTTP/2 401
<Redacted response headers>
Halt! Who goes there? T'is a bot!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am considering making an official integration of
ha-plejd
, and the first step would be to create a config flow UI. I thought it would be nice to use the Plejd login to get the encryption key and device lists ashassio-plejd
does, but when I try the login request inPlejdApi.js
withcurl
, I get 401. I am 100% sure the username and password are correct - they work in the app. Is there anything I am missing in how this request is created?Unfortunately, I am not running Hass.io, so I cannot try this add-on.
Switching to HTTP 1.1 gives same response.
Beta Was this translation helpful? Give feedback.
All reactions