-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to use a bearer token to access binary sensor #33
Comments
I'm pretty confident this is actually a Hassio bug fixed a few days ago. I'd expect to see it go away in the next release, but if not I'll look into it further. The add-on talks to Home Assistant through an add-on-only proxy that Hassio exposes, its never used API password. |
This log message still comes up when I get rid of api_password on my test rig, so I'm feeling more certain it's just a logging bug on the Hassio side of things. Can't use an api password if there isn't one in the first place. |
Same here, just updated Hassio today to 0.92.2 but the error is still there:
|
Looks like it really is something I'm doing wrong. I'll work on a fix for the next release. |
I've been unable to figure out how I might be using the add-on api wrong, so I've asked the Hassio folks for help. |
Thanks! |
A Hassio dev has confirmed that this is in fact a hassio problem, and that its fixed in their dev branch. I'm not sure when they merge in dev, but I'd expect it to be soon. |
Just upgraded to HA 0.92.1, now I'm getting this error in the log:
api_password is going to deprecate. You need to use a bearer token to access /api/states/binary_sensor.snapshots_stale from 172.30.32.2
This was also mentioned on the community forum topic by another user 22 days ago. I could not find a mention of it in the issues here on Github. Is this something that should be fixed?
The text was updated successfully, but these errors were encountered: