OpenEVSE and Home Assistant Fordpass range integration is off

[chriserx]

Anyone using this or maybe a similar setup and notice that the range is off by 1.61x. It's obviously a miles to kilometers conversion problem. I've tried different settings in different locations, outside of looking at the code for Home Assistant and HA Fordpass, anyone have a fix I may be overlooking? The only thing I know I haven't tried is changing the Ford app to report km. Range shows right everywhere but in the OpenEVSE entity for Home Assistant. Pretty minor but kinda annoying.

Sponsored

 

[chriserx]

I realize this isn't going to be a super popular setup, I made several automations by myself to control to taper the charge rate without setting a hard cut off limit like most setups for HVB battery life and to support the LVB without a battery maintainer. Then I consulted ChatGPT about it not realizing that I could combine all of the automations into one so I thought I'd share in case anyone else's charger is compatible with Home Assistant, which may require modification.

Prerequisites as is:
OpenEVSE
Home Assistant with HA Fordpass
Home Assistant Helper Toggle labled Full Charge Mode

Variables to replace:
OpenEVSE_device_id
OpenEVSE_entity_id
VIN
--------------------------
alias: OpenEVSE 4-Stage Charge Curve with Cold-Weather Support

entity_id: sensor.openevse_evse_vehicle_state_of_charge
below: 53
sequence:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 48
- conditions:
- condition: numeric_state
entity_id: sensor.openevse_evse_vehicle_state_of_charge
above: 52
below: 66
sequence:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 32
- conditions:
- condition: numeric_state
entity_id: sensor.openevse_evse_vehicle_state_of_charge
above: 65
below: 76
sequence:
- choose:
- conditions:
- condition: numeric_state
entity_id: sensor.fordpass_VIN_outsidetemp
below: 40
sequence:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 20
default:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 16
- conditions:
- condition: numeric_state
entity_id: sensor.openevse_evse_vehicle_state_of_charge
above: 74
sequence:
- choose:
- conditions:
- condition: numeric_state
entity_id: sensor.fordpass_VIN_outsidetemp
below: 40
sequence:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 16
default:
- device_id: OpenEVSE_device_id
domain: number
entity_id: OpenEVSE_entity_id
type: set_value
value: 6
mode: single
--------------------------
Profile has hysteresis but is generally:
0-50% 48A
51-65% 32A
66-75% 16A, below 40F 20A
75-100% 6A, below 40F 16A

 

[jw442]

I have a somewhat related question... Does your OpenEVSE charger work well with the Lightning? Mine gets a red ring whenever charging is complete or using the stop command in the app. I then get a text from FordPass of a charger error. It's annoying getting the error every day. Have you had this?

I am considering a similar setup as yours to pull SOC data. That's a great idea. Right now I just want mine to back off charging to maximize excess solar. I have NodeRED setup working well but the charger seemingly not liking my truck I may need to look for another solution. I actually have 2 Open EVSE units and have swapped parts one by one and the problem remains.

 

[chriserx]

I have a somewhat related question... Does your OpenEVSE charger work well with the Lightning? Mine gets a red ring whenever charging is complete or using the stop command in the app. I then get a text from FordPass of a charger error. It's annoying getting the error every day. Have you had this?

I am considering a similar setup as yours to pull SOC data. That's a great idea. Right now I just want mine to back off charging to maximize excess solar. I have NodeRED setup working well but the charger seemingly not liking my truck I may need to look for another solution. I actually have 2 Open EVSE units and have swapped parts one by one and the problem remains.

I've never had a red ring, on full charge the ring turns off as well as the OpenEVSE, it's likely not the issue since you are charging but its free to try out, pull the manual release in the truck. Latch being stuck is the only time i can recall a red ring. Also consider if it is an automation that the openevse must (and I don't know how or how hard the floor is set) be set at least 6A. It'll cost you some dollars but turn off the HA automations, set the charger to max and see if you still get the red ring.

 

[fhteagle]

I have a somewhat related question... Does your OpenEVSE charger work well with the Lightning?

Second data point. 13 months with Lightning charged by OpenEVSE (v5 mainboard). No red rings ever that I have seen, but the Ford App has shown "charger error" a couple of times recently, but that has always been associated with a quick grid interruption and restoration event. The local utility has their interrupts set to the most sensitive settings during the fire weather season, and we get ~1 second dropout and reconnects at least weekly through the summer. It is enough to screw up the clock on my microwave and piss off the Lightning. Always starts working again by putting the OpenEVSE to pause (0 amps offered) and back to the normal A setting. The rest of the years the OpenEVSE and Lightning work just great together. ~5.5 MWh delivered to the truck roughly in just over a year

 

[jw442]

What firmware are you running? Support has told me it's because of the latest version. It has a 'Relay Saver' feature that keeps the relay/contactor closed for any draw higher than .02amps (I believe can't recall exact value). It is to make sure the relay only opens when there is no draw. I have two lightnings and now two OpenEVSE (As of a few days ago 2nd one in our back shop) and both trucks and chargers exhibit this behavior. When charging is completed the truck continues to draw around 2.8amps even after the Trucks main contactor opens. I am not sure what this is or where this power is going. I am planning to check and see if this exists on other EVSE eventually. My solution at first was to unplug the CT for the current sensor. I have since adjusted the current offset in EVSE settings to 2800 and the problem is resolved. The current on the EVSE is now off by appx 2.8amps but I have adjusted that back to normal in Node Red to compensate. They are letting me know that a new firmware will be out soon to disable the Relay Saver 'feature'. They also agree that the 2.8 phantom amps is odd. My wife's Cadillac IQ does the same thing but it's phantom is only ~1.6 but my brothers Bolt works fine. So strange. I bought both of these to quickly adjust charge amps based on solar avalability. Once I adjusted the offset, it has been working perfectly for this.

 

[fhteagle]

What firmware are you running?

This is one of two. I am quite a bit behind you on the mainboard FW. The other newer one at the other house is 8.?.? IIRC. No issues with either one. Agreed that relay inhibit in 9.0.0 you are talking about is probably a bad idea for many reasons.

 

[chriserx]

Second data point. 13 months with Lightning charged by OpenEVSE (v5 mainboard). No red rings ever that I have seen, but the Ford App has shown "charger error" a couple of times recently, but that has always been associated with a quick grid interruption and restoration event. The local utility has their interrupts set to the most sensitive settings during the fire weather season, and we get ~1 second dropout and reconnects at least weekly through the summer. It is enough to screw up the clock on my microwave and piss off the Lightning. Always starts working again by putting the OpenEVSE to pause (0 amps offered) and back to the normal A setting. The rest of the years the OpenEVSE and Lightning work just great together. ~5.5 MWh delivered to the truck roughly in just over a year

 

[jw442]

I went ahead and purchased a USB programmer and flashed the board firmware down to 8.2.3.CGMI and all is well now. Thanks for all of the help. Sorry for the thread hijack. Finding Lightning users with this charger are hard to find!

Sponsored