Closed Soulphalanx closed 2 years ago
Same here, "{ message: 'Unauthorized' }" my model is Classic 280i.
Please ignore the {unauthorized} part. It has to do with my development of the AWS-based API. I'll patch and move this to debug so it doesn't confuse folks.
Please see v0.8.11
This is what I see after the user authorization logs (tokens obscured):
[1/21/2022, 11:13:02 AM] [BlueAir] AWS idtoken: xxxxxxxxxxxx [1/21/2022, 11:13:02 AM] [BlueAir] AWS authorization: xxxxxxxxxxxx [1/21/2022, 11:13:03 AM] [BlueAir] { message: 'Unauthorized' } [1/21/2022, 11:13:03 AM] [BlueAir] Restoring existing accessory from cache: BlueAir 505 Classic [1/21/2022, 11:13:03 AM] [BlueAir] BlueAir 505 Classic of type "classic_505" initialized. [1/21/2022, 11:13:03 AM] [BlueAir] BlueAir 505 Classic: device type not recognized, contact developer via GitHub.