“2 The beta Android app” does let you set up a favourite entity. I’ve done this with my garage door opener, but you need to be running AA and then open Home assistant in there.
Cheers. That’s one of the two ways I’ve been doing it.
- Home assistant via AA but it’s a few clicks deep
- Created a Google assistant action shortcut that gets added to the apps list. So it simulates says ”hey google open garage door”
But the ultimate goal is a popup, trigger by GPS location.
Here’s hoping for some better integration as more Atto 3s rollout around the world.
1 Like
Hi, looking for ways to get vehicle information for my BYD… so far no luck. Although I did implement an app that uses geofencing to detect when I’m near home and then displays a popup (Android Overlay) on the BYD screen to open my garage. It works, kind of buggy but it is most definitely possible.
1 Like
With BYD wishing to expand into foreign markets, perhaps they can help out 
The Atto3, Seal and Dolphin models are winning awards, hopefully there is commonality in each car’s monitoring app…
This should be possible with an OBDII dongle, Torque sideloaded and the Torque integration.
I’ve been able to setup the Toque integration in HA and install Torque on my Atto 3. Unfortunately it incorrectly reads most values, showing “340,282,346,638,528,860,000,000,000,000,000,000,000” for all relevant data points like SoC, State of health, speed etc.
With other OBD apps like OBD Auto Doctor the data is shown correctly (same as I can see in the driver display), but to my knowledge Torque is the only one with home assistant integration.
I’m hoping for a Torque update with full EV support…
3 Likes
Does anyone know if an approach like this would work for tracking BYD Car Data:
Basically taking screenshots from the cellphone with the BYD app and parsing data to make it available on HA.
Not sure it would work in a similar way …
1 Like
You could look at OVMS
https://docs.openvehicles.com/en/latest/components/vehicle_byd_atto3/docs/index.html
1 Like
I was looking at that wican device. Does it get any useful info for the atto 3 though? I couldn’t find anything that gave me confidence without a lot of work (which is outside my capabilities).
They’ve recently added predefined car profiles that makes it a lot easier. The Atto3 is there but so far all it will return is state of charge, but you could probably work with them to get more data that’s important to you. I’m using it with my Ioniq 5 and it works really well.
I didn’t think OCPP dealt with Car to EVSE communications, that seems to be ISO15118 as mentioned in the page you linked.
My EVSE does have OCPP V1.6 support and it doesn’t get SOC from the car. It seems like extra hardware may be required.
Hi Seano, does this link help show how OCPP can get the vehicle charge state via MeterValues message.
J1772 protocol, ocpp and state of charge (SOC)… · Issue #532 · steve-community/steve (github.com)
How to send OCPP meter values with meterValues.req (ampcontrol.io)
I have found the BYD API website but I’m not smart enough to work out how to use their API
https://oip.byd.com/ (And used a translator)
afaik - this API is on the infotainment system, rather than via BYD servers.
It would need someone to create an Android app that runs on the infotainment system that reads those values then publishes them to Home Assistant some way.
1 Like
Thanks for clarifying. I’m days from ordering a BYD Seal myself, so have been reading this with active interest.
Curious, would the charger be able to possibly have some kind of smarts and be HA connected?
In my case, I use a Wallbox EV charger which integrates (via cloud) to Home-Assistant.
I use the “plugged” entity to detect when a car is plugged in, and with some node-red routine force updates my Hyundai to detect if it’s plugged in:
- if no - then send a notification to input SOC for BYD.
- if yes - get difference between SOC entity and charge limit - “Percent to add”
Once I have the SOC it then calculates the “percent to add” - which is passed onto Intelligent Octopus Go that then schedules the charge via OCPP.
been watching this space for a while and it doesn’t seem byd are doing anything useful for their users. my zj beny doesn’t report soc (into ha), which is pretty weird but also not expected, it’ll usually just pump juice into it until the car fills up and stops it
I did find BYD Atto 3 — Open Vehicles documentation though
Just circling back
I am currently using a slightly lame solution of simply running a script using the macrodroid app on my Android phone on screen going blank.
If the phone is connected to my home wifi and the script hasn’t be run for 30min it opens the BYD app and grabs the SOC from the screen, sending it to an input_number helper in Hass via the Rest API.
It is good enough for my purposes and lets me optimise my EV & home battery charging from solar and limit the BYD charge to 80% as default. The script really only needs to run successfully once a day to serve my purposes as I can estimate current SoC from the last update + energy that the EVSE has put in since that time. (I very rarely charge at night - in those cases I just change the EVSE mode and charge to 100% anyway).
It would be ideal if it could be run this script on an android VM on my proxmox server, but the BYD app requires ARM architecture and I didn’t have the energy to get that working via emulation.
Given the BYD comes with a hotspot built-in (not enabled by default), is there any merit to having a dedicated device connected to the car that feeds info to HA remotely?
Then it could use the OBDII connector to get the data and report back live.
OR, could you have a dedicated Android Auto device with the HA app installed?