-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating EV SOC (State of Charge) data: OVMS #7
Comments
Example code to request and parse data to json
|
Implemented in 234b38d |
I insatlled emoncms on rpi4 and now in daemondshaper get the following error:
|
For demandshaper to be useful for EV charge scheduling the demand shaper ideally needs to know the current SOC (state of charge of an EV). Unfortunately it's not possible to obtain SOC data via the J1772 EV charging protocol.
Various EV's have different proprietary API's retrieve SOC. The API's are often unpublished and reverse engineered. We will try and add support for all EV's (starting the Tesla). However, as a first implementation we have tested integrating with OVMS (Open vehicle Monitoring system). OVMS is an open-source hardware/software telematics platform that supports many types of EV's and is totally independent to the manufacturer.
See OVMS user guide
Data can be retrieved from OVMS via their mobile app, MQTT or HTTP rest API (if using dexters-web OVMS server, default in Europe). See issue openvehicles/Open-Vehicle-Monitoring-System-3#178
Here is an example API call to retrieve OVMS data:
https://dexters-web.de/api/call?fn.name=ovms/export&fn.vehicleid=XXXXXX&fn.carpass=XXXXX&fn.format=csv&fn.types=D,S&fn.last=1
Example responce:
The text was updated successfully, but these errors were encountered: