Tessi: Unlock charge port

[stjaeger78]

The problem

Tessi integration has no function to unlock the charge port.

What version of Home Assistant Core has the issue?

2024.1

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

https://www.home-assistant.io/integrations/tessie

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]

You can technically do this by calling cover.open_cover when the cable lock is engaged. I'll look into adding a lock entity.

service: cover.open_cover
target:
  entity_id: cover.<name>_charge_port_door

[stjaeger78]

You are right I just tried. Thank you! As HA says the port is open I had to close it first which does not seem to have an effect as it is plugged. Then opening the door again unlocks the plug. A separate lock entity seems more intuitive to me though.

[Bre77]

I'm not sure why but Tessie uses the same API call for both opening the door and unlocking the latch, which is why this is missing in the first place. I made the obviously incorrect assumption no one actually would want to be unlocking the charge cable inside Home Assistant.

[stjaeger78]

My non tesla wallbox doesn‘t do it, so there has to go a zigbee button next to it. And here we are 😀

Brett Adams @.***> schrieb am Do. 4. Jan. 2024 um 22:10:

I'm not sure why but Tessie uses the same API call for both opening the door and unlocking the latch, which is why this is missing in the first place. I made the obviously incorrect assumption no one actually would want to be unlocking the charge cable inside Home Assistant.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/107124#issuecomment-1877764056, or unsubscribe https://github.com/notifications/unsubscribe-auth/BE4KMLSHIYBDN4JQGC5LUFTYM4LDHAVCNFSM6AAAAABBM54LMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXG43DIMBVGY . You are receiving this because you authored the thread.Message ID: @.***>

[Bre77]

Yeah ok that makes a heap of sense. Blame my Tesla Wall Connector privilege.

At least you can use the ZigBee button to both open the door AND unlock the cable, so the current implementation while hard to understand should work perfectly for you.

Maybe I should add the button entity back.

[stjaeger78]

Yes, it does. Thank you!