Skip to content
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

Open
erikgieseler opened this issue Apr 13, 2024 · 8 comments

Comments

@erikgieseler
Copy link

erikgieseler commented Apr 13, 2024

I have just tried out the "charging_manager" role:
The commands: charging-start, charging-stop and charging-set-amps work without any problems via BLE.

Unfortunately, the following commands do not work via BLE:
wake and charge-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)

@sethterashima
Copy link
Collaborator

Thanks for the report. This will require a vehicle firmware update to fix.

@erikgieseler
Copy link
Author

Is there any news on this?

@stumbaumr
Copy link

stumbaumr commented Jun 16, 2024

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.

@sethterashima
Copy link
Collaborator

sethterashima commented Jun 20, 2024

Is there any news on this?

Support for wake was merged into a coming firmware release.

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.

@stumbaumr
Copy link

What's the use case where it would be helpful to have a Charging Manager open/close the ports?

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.
Opening the garage door -> Home assistant unlocks the charge port...

@erikgieseler
Copy link
Author

Is there any news on this?

Support for wake was merged into a coming firmware release.

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.

Of course, you can also directly select a role with the highest rights and send the commands via BLE.
However, for security reasons alone, you should select a role with minimal rights.
The Charging Manager role would be well suited for this.

@pkuehnel
Copy link

Support for wake was merged into a coming firmware release.

Great news. Any idea of the Version number when this will be possible?

@rcasta74
Copy link

Support for wake was merged into a coming firmware release.

I got recently the update to 2024.26.7 but I still get GENERICERROR_UNAUTHORIZED using a key with role charging_manager. What's the firmware version that bring this feature?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants