-
Notifications
You must be signed in to change notification settings - Fork 101
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
Feature request: Allow "charging_manager" role to use "wake" and "charge-port-open" via BLE #232
Comments
Thanks for the report. This will require a vehicle firmware update to fix. |
Is there any news on this? |
Is there any news on this? Reading the State of Charge (SoC) is also required to allow the "charging_manager" start fast charging to a minimum SoC and then continue with PV-based charging. |
Support for Support for open/closing the charge port by Charging Manager keys makes sense intuitively, but I'm having second thoughts on that because the role was initially intended for remote management. What's the use case where it would be helpful to have a Charging Manager open/close the ports? Presumably there's a human nearby with a more privileged role in cases where this would be useful. |
You come home, park the car and as Home Assistant knows the car is home and since the saying is "Steht er, dann lädt er" it opens the charge port as soon as you go in park. |
Of course, you can also directly select a role with the highest rights and send the commands via BLE. |
Great news. Any idea of the Version number when this will be possible? |
I got recently the update to |
I have just tried out the "charging_manager" role:
The commands:
charging-start
,charging-stop
andcharging-set-amps
work without any problems via BLE.Unfortunately, the following commands do not work via BLE:
wake
andcharge-port-open
.The following error messages are displayed:
wake: Failed to execute command: vcsec could not execute command: genericError:GENERICERROR_UNAUTHORIZED
charge-port-open: Failed to execute command: MESSAGEFAULT_ERROR_INSUFFICIENT_PRIVILEGES
Are these two problems fixable ?
Originally posted by @erikgieseler in #230 (comment)
The text was updated successfully, but these errors were encountered: