View Current Charge Location ID?

[Husky17]

I had an issue today with my Lightning (Unrelated to ha-fordpass) where it didn't abide by the charging limit I have set for a home location and it went all the way to 100%. I'm not sure yet why this happened, but I suspect that it might have been because it didn't realize it was at a known location with a 90% limit.

Anyway, that's related to what I wanted to ask about --Is there a field that would make it possible to see or confirm that the vehicle knows it is at a specific charge locationID?

I saw the newer features that allow us to set the limits through the GUI for different locationIDs and selfishly thought that if we could see what/where the vehicle currently thinks it is, it'd be easier for me to dig into my weird issue.

I really appreciate all the features and additions that have been added over the last 6 months, thanks again!

[marq24]

Just let me repeat what I have understood - you want to see somewhere the raw locationID when the vehcile is connected to one known location at all - right?

[Husky17]

Yea, that's what I was thinking --maybe not necessarily the raw locationID, the name of the location could also serve the purpose I'm thinking of. Perhaps an entity that reports the status if the vehicle currently believes it is at a known charge location or not. If its not connected to a spot, it would say unknown. If its known, then the attributes could have the name of the location, the charge setting for the location, and the raw id.

That was the thought. I've since figured out part of my issue I mentioned in the first post. I have tuck under garage in a town home and the address of the latest charge is my neighbor. Despite the very close proximity of the address, the vehicle didn't recognize that it was at 'home' and didn't use the settings for 'home'.

I had to go to ford pass to understand that.

But looking here in the attributes of the EV entity, I think the snip below is the basic data I was looking for (Sorry, I didn't see it earlier before posting). I might make a template sensor out of this to see how and when it changes. If the data is good and timely (not updated after a charge or something like the trip data when it comes in) it might be nice to have an entity that shows the current known location label.

[marq24]

ok - just let me know, if there is the need to code / implement something

[Husky17]

I've had these template sensors going for a few days now and I think I understand a little more. I've got the snapshot of the graph below that shows how the location IDs change and how fast things are updated.

CurrentUserSavedChargeLocationId - This shows if the vehicle is in a saved location by the location id or '0' if in an unknown/unsaved location. (4th Row)
UserChargeLocation - This one seems to be the same as CurrentUserSavedChargeLocationID but without the unknown '0' locations. (2th Row).

The top bar has the SocChargeTargets which correspond with my settings for those locations.
LocationID = 2, ChargeTarget = 90.0%
LocationID = 3, ChargeTarget = 90.0%
LocationID = 4, ChargeTarget = 95.0%
LocationID = 0, ChargeTarget = 100.0% (Unknown/Unsaved Location)

The last bar on the left for SoC charge target is 85.0% and I used the Ford Pass app to manually set that. I thought that was good because it shows that its updated right away.

I think all of this information is already be accessible except for the actual string name of the location. So while I think a new entity might be a useful way to organize and present this data, its probably not needed since one could still use templates to surface the info. But if you think it would make sense, a new entity arranged like below could be useful to highlight what the current state of the vehicles charge target is and information about the location name/id/target as attributes:

Entity Name = SOC Charge Target
Entity Value = Current SoC Charge Target % --this is what the vehicle is currently configured to charge to.
Attribute1 = Location Name associated with location ID (same name as whats in the charge target level select drop downs).
Attribute2 = Raw Location ID number (CurrentUserSavedChargeLocationId, includes the 0's for unknown locations)
Attribute3 = SoC Charge Target % setting for Raw Location ID Number

--Example--
EntityName = SOC Charge Target
Entity Value = 90.0% (value from the batteryStateOfChargeTargetDisplay)
Attribute1 = 2
Attribute2 = Home
Attribute3 = 90% (Value from the target level setting for Home)

[marq24]

Would you mind sharing your current templates for this bar's ?

[Husky17]

These are the templates I had put together:

template:

• sensor:
  • name: "ford_userChargeLoc"
    state: "{{ state_attr('sensor.fordpass_1ft6w1ev9nwg09188_elveh', 'userChargeLocation') }}"
  • name: "ford_userSavedChargeLocId"
    state: "{{ state_attr('sensor.fordpass_1ft6w1ev9nwg09188_elveh', 'currentUserSavedChargeLocationId') }}"
  • name: "ford_userSavedChargeLoc"
    state: "{{ state_attr('sensor.fordpass_1ft6w1ev9nwg09188_elveh', 'userSavedChargeLocation') }}"
  • name: "ford_userUnsavedChargeLocId"
    state: "{{ state_attr('sensor.fordpass_1ft6w1ev9nwg09188_elveh', 'currentUserUnsavedChargeLocationId') }}"
  • name: "ford_battSocTargetDisplay"
    state: "{{ state_attr('sensor.fordpass_1ft6w1ev9nwg09188_elveh', 'batteryStateOfChargeTargetDisplay') }}"

[marq24]

Thanks ! - I hope I'll find the time to look into that during the week... I'll keep you updated...