Tessie - switch.tesla_model_y_charge - always on

[pedroplusrodrigues]

The problem

The switch is always on. It is not possible to deactivate it. It turns instantly to on. That means that no charge automation is possible.

And no - connected ( charging cable) entity is available.

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tessie

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @bre77, mind taking a look at this issue as it has been labeled with an integration (tessie) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tessie can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tessie Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tessie documentation tessie source _{^{(message by IssueLinks)}}

[Bre77]

Funny enough, i managed to replicate your issue in reverse. My charge sensor is now always off. I will investigate this further.

[Bre77]

Just to add to the complexity, I just retested while my vehicle was awake, and it worked perfectly fine.

Can you go to https://dash.tessie.com/firmware

Look at charge_enable_request and note it's value

Change the charger switch in Home Assistant

Wait 5 second, refresh the firmware page

Look at charge_enable_request and note if it's value has changed.

If your vehicle is asleep while testing, please repeat while the vehicle is awake and see if it's any different. If it is then we may need to raise a support case with Tessie.

[pedroplusrodrigues]

hi Brett, thanks for your support. No change at all regardless what i do. The switch stays "on" and the firmware page the value keeps "true".

[LasseBang]

Just tested it out. And it changed from charge_enable_request false to charge_enable_request true

And was able to turn off just fine.

[dennypage]

@pedroplusrodrigues

Note that the vehicle must actually be connected to a charger for the switch to have any effect. When you are disconnected, the value of charge_enable_request will always be true.

[Edit: I believe this is inherent Tesla behavior, unrelated to Tessie]

[dennypage]

For your automation, you can trigger on binary_sensor.myvehicle_charge_cable to run your initial automation. If you have a gen3 wall connector, there is also binary_sensor.mywallconnector_vehicle_connected that you can use for a trigger as well.

[pedroplusrodrigues]

That’s the solution! Works perfectly now. Thanks!

[Bre77]

I actually think I have a better solution to this problem. It seems the correct value for this switch is user_charge_enable_request instead of charge_enable_request.

EDIT: its a partial fix, because you can turn it off, but you cant turn it back on until the vehicle is plugged in.

[LasseBang]

I actually think I have a better solution to this problem. It seems the correct value for this switch is user_charge_enable_request instead of charge_enable_request.

EDIT: its a partial fix, because you can turn it off, but you cant turn it back on until the vehicle is plugged in.

Make sense that you only can turn on if car is plugged in :-)

[motley-git]

Hello, I see this issue when the charging cable is not connected for my dashboard UI toggle switch. It stays stuck in the "on" state. If I click the HA switch to turn off and hopefully resync the state (when HA/Tessie is connected), it makes the request via Tessie: charge_enable_request: false changes to charge_enable_request: true. It automatically toggles back to charging after a moment or so, even though the charging cable is not plugged in and the charging door is closed. No big deal, I just need to remember to keep the cable plugged in. But, I think the software should be smart enough (HA integration and/or Tessie) to sense it not charging, at least when it next connects to retrieve state. It should know whether the charging cable is not connected, or charging door is closed, and/or if actual charging taking place. If no way the car is charging, flip the charge state in HA back to "off". Also, consider the charge_enable_request action (or user_charge_enable_request?) is not a valid action when the charging cable is not plugged in, or when charging door is still closed.