OVMS & Ohme app

I use an Ohme cable at the moment and their app which works very well, but I was wondering if the two could talk to each other? It would be great if the Ohme app knew the SoC (from OVMS) and I just then told the Ohme app what percentage I wanted the car charged to. Like it does with a Nissan Leaf.

This is a big thing for users of both MG and Ohme, does anyone have any contact details for Ohme Technical team? I have an Ohme cable and know most of the back-end of OVMS, the queries needed must be easy compared to any manufacturer/OEM API, and i would be happy to help them.

1 Like

Hi Michael,

I emailed Ohme and this was their reply. It might help if you contacted them too.

Hi Michael

Thank you very much for your message.

I will forward this on to our App Development Team to review.

Seems very exciting as I know that currently MG offer no API for battery state of charge!

Any further queries, please do let me know.

Kind regards

Joshua

Ther is a chap on the Octopus Agile chat Facebook page called Daniel Vocke. Daniel did the magic for us early on to get Ohme working with delayed charging with a few of us running Beta patches to go from trickle to full capability. Top bloke imho. Throw him a DM and I’m sure he will be on it - he is currently sorting Tesla issues with Agile from my reading.

Many of us MG ZS EV owners use Ohme cables, as they were the first to put in the engineering effort to get scheduled charging working properly. So getting OVMS in the MG talking to Ohme would help a lot of people, I think!

The API for Europe OVMS v2 server is very easy to poll and pull the SoC data from (literally one https query). OVMS v3 which uses MQTT is equally trivial.

I have attempted to reach out to Daniel Vocke (CTO of Ohme?) on LinkedIn, if @Mark is still in touch with him can you send me details or invite to connect (on Facebook or anything else)?

I am very up for explaining the API query needed, I just need to get in touch with the right people at Ohme. As I also have a cable I could also help test, so please share my details if you get to the right team.

I’ll do my best but he didn’t respond to my last message, but the team did.
He is on the Ohme Facebook page if you follow that.

Daniel Vocke
CTO
daniel.vocke@ohme-ev.com | +1 415 470 2284

I raised this with Daiel 3 weeks ago, he replied: " A common API would not only make the integration on our end simpler, If it didn’t exist I’d even go as far as considering to host an Ohme queue that those devices could connect to."

Can we integrate with Ohme, I’d rather it was set from the OVMS app’ but happy anyway for delayed charging time up to a desired SoC and end time.

You do not need anything clever to pull the SoC from the v2 server OVMS is using. On the Dexters server it is trivial, just combine the below with your details:

https://dexters-web.de/api/call?fn.name=ovms/export
&fn.vehicleid=my-car-id-goes-here
&fn.carpass=password-from-server-goes-here
&fn.last=1
&fn.format=csv

e.g: https://dexters-web.de/api/call?fn.name=ovms/export&fn.vehicleid=car123&fn.carpass=password123&fn.last=1&fn.format=csv

Out will pop a text stream group of CSV files with all the vehicle statuses last reported by OVMS like below:

#FILE,-log-notification.csv
rec_time,rec_nr,type,text
2020-10-31 10:59:35,51031,A,Standard - Charge StoppedSOC: 76.6%Est. range: 119MODO: 2030.0MSOH: 100%
#FILE,-ovm-debugcrash.csv
rec_time,v,firmware_version,bootcount,bootreason_name,bootreason_cpu0,bootreason_cpu1,crashcnt,earlycrashcnt,crashtype,crashcore,registers,backtrace,resetreason,resetreason_name,curr_event_name,curr_event_handler,curr_event_runtime,wdt_tasknames
2020-10-21 21:29:08,0,3.2.015-146-g48b9b43c/ota_1/main (build idf v3.3.2-881-g22d636b7b Oct 20 2020 19:51:46),27,Crash,12,12,22,0,abort(),0,,0x4008e627 0x4008e8c1 0x400e754c 0x40083f6a ,6,Task watchdog,ticker.1,esp32wifi,0,IDLE1|OVMS DukTape
#FILE,-ovm-serverlogs.csv
rec_time,rec_nr,logtext
2020-11-01 23:06:06,1825,'#82 C rx msg F 3.2.015-146-g48b9b43c/ota_1/main (build idf v3.3.2-881-g22d636b7b Oct 20 2020 19:51:46),PW7CB3FLZ072567,17,1,MG,TP-Link_IoT'
#FILE,-ovm-utilisation.csv
rec_time,direction,bytecnt
2020-11-01 01:00:00,3,140076
#FILE,d.csv
rec_time,0,doors1,doors2,lockunlock,tpem,tmotor,tbattery,trip,odometer,speed,parktimer,ambient,doors3,staletemps,staleambient,vehicle12v,doors4,vehicle12v_ref,doors5,tcharger,vehicle12v_current
2020-11-01 23:06:06,0,64,8,4,16,17,15.5,0,20629,-0.01,38413,16,0,0,0,11.63,0,12.29,128,0,2,16
#FILE,f.csv
rec_time,0,ovms_version,car_vin,net_sq,can_write,car_type,gsmcops
2020-11-01 23:06:06,0,3.2.015-146-g48b9b43c/ota_1/main (build idf v3.3.2-881-g22d636b7b Oct 20 2020 19:51:46),PW7CB3FLZ072567,17,1,MG,TP-Link_IoT
#FILE,l.csv
rec_time,0,latitude,longitude,direction,altitude,gpslock,stalegps,speed,trip,drivemode,power,energyused,energyrecd,motor_power,inv_efficiency
2020-11-01 23:06:06,0,52.688187,-2.770093,308.4,79.2,1,1,-0.00621373,0,0,0,0,0,0,0
#FILE,s.csv
rec_time,0,soc,units,linevoltage,chargecurrent,chargestate,chargemode,idealrange,estimatedrange,chargelimit,chargeduration,chargeb4,chargekwh,chargesubstate,chargestateN,chargemodeN,chargetimer,chargestarttime,chargetimerstale,cac100,charge_etr_full,charge_etr_limit,charge_limit_range,charge_limit_soc,cooldown_active,cooldown_tbattery,cooldown_timelimit,charge_estimate,charge_etr_range,charge_etr_soc,idealrange_max,chargetype,chargepower,battvoltage,soh,chargepower_input,charger_efficiency
2020-11-01 23:06:06,0,48.5,M,231,30,stopped,standard,0,74,36,0,0,0,0,21,0,0,0,0,0.00,0,0,0,0,-1,0,0,0,0,0,0,0,0.00,400.75,100,7.05,0.00
#FILE,w.csv
rec_time,0,fr_pressure,fr_temperature,rr_pressure,rr_temperature,fl_pressure,fl_temperature,rl_pressure,rl_temperature,staletpms
2020-11-01 22:10:55,0,36.5495,19.5,37.7098,19.5,36.5495,19.5,36.5495,19.5,1

File “s.csv”, third item is SoC