Anyways - Your EV journey, in your hands — Home Assistant Integration

Custom integration that connects Home Assistant to a self-hosted AiwaysCommunity backend. Point it at your backend URL, paste an API key, and every vehicle the key can see shows up as a Home Assistant device with sensors, a location tracker, and buttons/services for the common remote commands.

Cloud-independent EV telematics for the Aiways U5 — the data comes from your backend (fed by the TBox daemon / LTE bridge), not from the manufacturer cloud.

Features

• Config flow — no YAML. Enter backend URL + API key; validated against the live backend.
• One HA device per vehicle, keyed by VIN.
• Sensors: state of charge, range (measured + estimated), odometer, speed, battery voltage/current, gear, charge state, altitude, heading, data source, cell voltage min/max/spread, battery temp min/max/avg, tire pressures & temperatures, active-fault count.
• Binary sensors: charging, fault present.
• Device tracker: live position on the map.
• Buttons: lock, unlock, unlock trunk, flash lights, honk, climate on/off.
• Services: aiways.send_command (generic), aiways.set_climate, aiways.set_charge_limit.

Requirements

• A reachable Anyways backend (default https://host.anywaysev.eu).
• An API key (oaw_…) belonging to your account. You can issue one in the AiwaysApp (it also creates the LTE-bridge key) or via the backend. The key only sees the vehicles you own/co-own.

Installation

Manual (recommended)

Copy the custom_components/aiways folder into your Home Assistant config/custom_components/ directory and restart Home Assistant:

config/custom_components/aiways/…   ← the contents of this repo's custom_components/aiways

You can pull it straight onto the HA host:

cd /config/custom_components
git clone https://limeha.duckdns.org:3080/Anyways/HA-Aiways-Integration.git _aiways_tmp
cp -r _aiways_tmp/custom_components/aiways ./aiways && rm -rf _aiways_tmp

HACS

HACS only supports GitHub repositories, so this Forgejo repo cannot be added as a HACS custom repository directly. If you want HACS-managed updates, mirror this repo to GitHub and add that mirror as a custom repository (category Integration). Otherwise use the manual install above.

Configuration

Settings → Devices & Services → Add Integration → “Anyways - Your EV journey, in your hands”.

Field	Example
Backend URL	https://host.anywaysev.eu
API key	oaw_…

On success every visible vehicle is added automatically. Data is polled every 60 s (cloud polling).

Commands are asynchronous ("eventually consistent")

Pressing a button / calling a service queues a command in the backend (status: pending). It is delivered to the car later by the LTE bridge / app (BLE), not instantly — so a button press means “command submitted”, not “executed at the car”. This matches how the backend command queue works. The type strings follow the AiwaysApp/firmware convention (lock, unlock, trunk_unlock, flash, honk, climate_on, climate_off, set_charge_limit); the backend accepts any string, so aiways.send_command is an escape hatch for anything not covered by a button.

Service examples

# Flash the lights
service: aiways.send_command
data:
  vehicle: "1"          # vehicle ID or VIN
  command: flash

# Pre-condition to 22 °C
service: aiways.set_climate
data:
  vehicle: "1"
  temperature: 22

# Charge to 80 %
service: aiways.set_charge_limit
data:
  vehicle: "1"
  percent: 80

Notes & caveats

• Parked cars produce no fresh data. When the vehicle is asleep the backend gets no new live values, so the latest reading may be hours/days old — that is expected, not a bug. Live values need the car awake.
• charging binary sensor is heuristic (charge_state ≠ 0). The exact firmware coding isn't confirmed yet; adjust _is_charging in binary_sensor.py if it's wrong for your car.
• Some sensors (estimated range, altitude, heading, tire values) are disabled by default — enable them per entity if you want them.
• This is a community project, not affiliated with Aiways.

License

MIT