You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Start/Stop charging from HA of KIA / Hyundai.
And at the same time the 'stop' charging can useful to have full control over the charging.
Describe the solution you'd like
Start/Stop charging from HA will be possible.
For the start it solves what seems a bug in the KIA EV6. Include the logs of the end point from Data in HA if this is a sensor
Describe alternatives you've considered
Playing with the target charge states. But it doesn't give the full control as a complete start/stop of the charging.
Additional context
For the start it solves what seems a bug in the KIA EV6.
From the KIA app we have the option to 'start charging'. In itself it is a bit a strange action, as mostly there is no need for this action.
But... when changing the target charge limit in AC, from for example 50% to 100%, and the car (KIA EV6) is somewhere between 50% and 100%, the car doesn't alway start charging. Only when a 'start charging' command is sent the car, it starts charging.
This somehow looks like a bug on the KIA EV6; it has the same behaviour as when the charge limit is set from the app.
The text was updated successfully, but these errors were encountered:
I’m not clear, did you try use the action without it working? This already exists as an action / service call. On Nov 21, 2024, at 12:42 PM, walter-ve ***@***.***> wrote:
Is your feature request related to a problem? Please describe.
Start/Stop charging from HA of KIA / Hyundai.
And at the same time the 'stop' charging can useful to have full control over the charging.
Describe the solution you'd like
Start/Stop charging from HA will be possible.
For the start it solves what seems a bug in the KIA EV6.
Include the logs of the end point from Data in HA if this is a sensor
Describe alternatives you've considered
Playing with the target charge states. But it doesn't give the full control as a complete start/stop of the charging.
Additional context
For the start it solves what seems a bug in the KIA EV6.
From the KIA app we have the option to 'start charging'. In itself it is a bit a strange action, as mostly there is no need for this action.
But... when changing the target charge limit in AC, from for example 50% to 100%, and the car (KIA EV6) is somewhere between 50% and 100%, the car doesn't alway start charging. Only when a 'start charging' command is sent the car, it starts charging.
This somehow looks like a bug on the KIA EV6; it has the same behaviour as when the charge limit is set from the app.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Is your feature request related to a problem? Please describe.
Start/Stop charging from HA of KIA / Hyundai.
And at the same time the 'stop' charging can useful to have full control over the charging.
Describe the solution you'd like
Start/Stop charging from HA will be possible.
For the start it solves what seems a bug in the KIA EV6.
Include the logs of the end point from Data in HA if this is a sensor
Describe alternatives you've considered
Playing with the target charge states. But it doesn't give the full control as a complete start/stop of the charging.
Additional context
For the start it solves what seems a bug in the KIA EV6.
From the KIA app we have the option to 'start charging'. In itself it is a bit a strange action, as mostly there is no need for this action.
But... when changing the target charge limit in AC, from for example 50% to 100%, and the car (KIA EV6) is somewhere between 50% and 100%, the car doesn't alway start charging. Only when a 'start charging' command is sent the car, it starts charging.
This somehow looks like a bug on the KIA EV6; it has the same behaviour as when the charge limit is set from the app.
The text was updated successfully, but these errors were encountered: