WiCAN ESP32-based open-source OBD2/OBD-II Vehicle (car or truck) CAN Bus Diagnostics to WIFi/BLE/USB adapter for Home Assistant integration?

Hardware
83

Hey everyone, just found this thread, though I’m not MeatPi, I’ve been contributing on GH, and I’m working with him to do a HA Integration, rather than relying on MQTT, hes adding API endpoints and stuff for the integration to use. Won’t even bother posting a link to the Integration yet, it is well and truley in dev, I’m not even using it myself yet. But hoping to make it even easier to use than MQTT, especially for those that don’t already use MQTT

@vanrees I also have a Kona, and haven’t been able to get Odometer working either, like you said not in car scanner, which is the first place to start adding custom values.

@brjhaverkamp Theres not a list list, but I helped set up the vehicle profiles system, so if you check the vehicle profiles on GH wican-fw/vehicle_profiles at main · meatpiHQ/wican-fw · GitHub each car in there has at least some support. So does not look like anyone has added a bolt. If you can do the car-scanner side and post logs as a GH issue, MeatPi or some others can help get the data out and create a profile for the car

3 Likes
84

@jay-oswald thanks for responding! I have tried through the standardized A6 PID (OBD-II PIDs - Wikipedia) and also tried to make this work Add support for kona/e-niro odometer · Issue #278 · openvehicles/Open-Vehicle-Monitoring-System-3 · GitHub but so far no cigar.

I am far from an expert so it could be I have been doing it wrong. The car is not here at the moment. but will post a screenshot of my attempts later

85

Hi Jay,

Thanks for your answer. I just received my wican and connected it to my car. So I will start playing with it!

86

Hi all,

I’ve been starting with the Wican and my Opel Ampera-e/GM Chevrolet Bolt 2017
Sofar I have been able to get the HA integration up and running and upgraded the Wican firmware from 2.98 to 3.48. So I can start with the Automate tab in the web interface.

I found the list of available PIDs on Chevy Bolt OBD2 PIDs – All EV Info
And I have been trying to implement them in the Wican Autmate tabi. This is what I did sofar:

Screenshot from 2024-10-16 19-46-30
Screenshot from 2024-10-16 19-46-301100×291 31.2 KB

From what I understood, A, B, C, etc. are byte 0, 1, 2. in that files syntax.
In the Wican syntax that means A=B0, B=B1, C=B2, etc. Is that correct?
I just tried two from the csv list that looked interesting. But I have no idea what the Custom Initialisation string is. (Is that always needed?) and the Init part of the Custom PIDs.

And I assume I can leave the “Vehicle Specific” at the top of the autmate tab to “Disabled”, right?

I do see mqtt messages from the Wican in Node-Red. But mostly about getting online and offline. No data from these custom PIDs yet.

Any pointers on the above items, or other advice is welcome.

Bert

87

Recommend repost your questions to wican-fw discussions on GitHub:

88

Awesome!

Read that your custom component will become the official WiCAN integration for Home Assistent.

Hope that more people will contribute addition vehicle profiles or contributing in other ways.

I do not think that there is any harm posting link to the integration even if it is pre-alpha and not ready.

4 Likes