Skip to content

[Feature request] Remote charging start, authorization mode change and cable unlock/lock via MQTT #325

@wonsky007

Description

@wonsky007

Hi,

I'm a new owner of the go-e Gemini charger. After integrating it with Home Assistant via the official MQTT API (v2), I’m missing a few important control features that would make the integration truly useful in a smart home setup.

Missing MQTT features:

  • Remote start / force start of a charging session when the charger is in authorization-required mode (closed / RFID / app mode)
  • Changing authorization mode — switching between closed (authorization required) and open (Plug & Charge)
  • Remote control of cable lock — ability to lock or unlock the cable on demand

My use case:

I live in an apartment building with a shared parking area. I want to keep the charger in closed mode most of the time to prevent neighbors from using my charger and electricity. At the same time, I don’t want to force my wife to use the app or RFID card every time she wants to charge — it should be simple plug & charge for family members.

With the missing features, I could create a clean automation in Home Assistant based on the car’s entity, for example:

  • device_tracker.car_location == "home"
  • binary_sensor.charging_cable_connected == true

Action: switch authorization mode to open + remotely start charging.

Currently I have to manually change the authorization mode in the go-e app or use an RFID card, which defeats the purpose of a seamless smart home integration.

Suggestion:

Please consider adding the following controls via MQTT (similar to other existing API keys):

  • Command to change authorization mode (ast or similar) — 0 = closed, 1 = open
  • Command for remote/force start of charging session (even when authorization is required)
  • Full remote control over cable lock behavior (ust or dedicated command) — lock, unlock, or auto

These functions already exist in the local HTTP API v2 and in the go-e app, so exposing them via MQTT would make the API consistent and much more powerful for users of Home Assistant, Node-RED, ioBroker, etc.

Is there any plan to add these MQTT commands in a future firmware release?
Are there any workarounds (other than switching to the HTTP API)?

Thanks in advance for considering this feature request! 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions