-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add additional status #25
Comments
Did you check if this info is available in the sensor "reason_for_no_current"? |
There is no sensor in this library, but it isnt available in hass_easee |
Right, of course, I forgot this was for the API. But the is still available, did you check what the reason for no current value returns? |
I havnt checked that out. Ill do that |
When the charger require auth, the reason_for_no_current is None. So no help there :( |
If auth is required to use the charger, in in the app, its called waiting for authorization, however in the api the data that is sent has 'chargerOpMode': 2 (PAUSED)
I think we should check for this add add a waiting for approval or authorization status.
Also we dont use the levelOfAccess that /api/chargers/{id} returns. There is no way to know what kind of access is required. We can check if auth is required using charger.get_config()["authorizationRequired"] but thats it.
If this is something that you want, i can a PR for this.
The text was updated successfully, but these errors were encountered: