MisterWil / skybellpy

A thin Python wrapper for the Skybell alarm API
MIT License
9 stars 7 forks source link

Home Assistant Error #18

Open ilikestohack opened 3 years ago

ilikestohack commented 3 years ago

Trying to configure home assistant with my skybell today and im getting this error any ideas why?

ilikestohack commented 3 years ago

Sorry tried to copy and paste the error is here: https://pastebin.com/6DmVKvqH

jhampson-dbre commented 3 years ago

I am also unable to set up skybell with Home Assistant. Error is the same as the one posted by above.

jhampson-dbre commented 3 years ago

I had some time to dig into this. I found some additional error message in Home Assistant debug messages

./home-assistant.log:2021-02-07 15:28:29 DEBUG (SyncWorker_4) [skybellpy] HTTP get https://cloud.myskybell.com/api/v3/devices/xxxxxxxxxxxxxxxxxx/info/ Request with headers: {'Authorization': 'Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'user-agent': 'skybellpy/0.6.3 (HomeAssistant/2021.2.1)', 'content-type': 'application/json', 'accepts': '*/*', 'x-skybell-app-id': 'f802c621-9efc-xxxx-xxxxx-xxxxxxxxxxx', 'x-skybell-client-id': 'ab875aa5-xxxx-xxxx-xxxxxxxxxx'}
./home-assistant.log:2021-02-07 15:28:29 DEBUG (SyncWorker_4) [skybellpy] <Response [403]> {"name":"Forbidden","message":"Device not found"}

I was using a separate account that I create for use with Home Assistant and had the SkyBell shared with that account. I tried logging into the SkyBell app with the shared account and the video from the SkyBell never loaded. I tried to sign out and the app kept crashing. Eventually cleared the SkyBell app storage and I was able to log back in with my normal account. After all that, I updated Home Assistant to use the same credentials as my regular account, deleted the skybell.pickle file in the /config directory, restarted Home Assistant, and the the SkyBell integration was able to connect from Home Assistant.

Hard to say if there is some problem with the alternate account I was using, or if the integration requires an account with full permissions, but at least it is connecting successfully now.