Home Assistant Automations - Show them off!!!

[DevSecOps]

What about with the HomeBridge plugin https://github.com/Brandawg93/homebridge-fordpass ?

I have Homebridge and HE working well together. I guess if I needed to I could add Home Assistant to the mix.

Since I don't have either of those, I don't know the answer. Can you read the vehicle status in HE? If you can through HomeBridge then I assume it would work.

Sponsored

 

[RVAtom]

I'm not sure what I may have done wrong. I got Fordpass integrated (v1.63) and it pulled all of my data once, but has not updated since then. Is there something I need to change to make it auto update? I found the "Interval to poll Fordpass API" and left it at 900 seconds, changed it a little to 890 seconds, and back and no change.

Got this figured out. Well, I didn't really, I just removed my vehicle and added it back, and it seems to be working now.

 

[PeeKay]

It works. Some people are just scared to use it.

I don't think the HA integration has ever caused lockouts. It's been other services.

Not clear, what the remedy is... limit polling rate, avoid IP switching ... and more constraints they may apply int the future.

Hopefully they don't block the primary account after multiple secondary accounts are blocked.

 

[DevSecOps]

Not clear, what the remedy is... limit polling rate, avoid IP switching ... and more constraints they may apply int the future.

Hopefully they don't block the primary account after multiple secondary accounts are blocked.

That reddit post is a year old and they don't know the reason the account was locked.

I was told directly from the Ford developer team that locked accounts (a year ago) were almost certainly caused by either unapproved user agents hitting the API or multiple hits to the same account from various IPs.

Those reasons aren't caused by the fordpass ha integration. Even though I don't own a Ford anymore I still poll the API from ha and have never had a problem. I do have a static IP however, which definitely helps. At one point I was querying the API every 10 seconds and never had an issue.

So, I stand behind my statement that the FP HA integration isn't the issue.

 

[PeeKay]

I did run into lockout due to HA, that I originally reported here:

https://www.macheforum.com/site/thr...-use-can-disable-your-fordpass-account.13893/

I'd like to try using the HA integration again, just trying to avoid the painful process of unlocking that I had to go through. Hopefully Ford doesn't mess with my primary account. Fingers n toes ?.

 

[PeeKay]

Update:
Secondary login worked so far without issues on HA. I have set my polling interval to 1hour. I'll try reducing it to 30 and then 15 mins.

Question about the fordpass_tracker sensor:
Is there a way to seperately log the long/lat, so that history of each attribute is recorded? (Possibly graphed on a map?)

Right now it only records at home/away.

 

[DevSecOps]

Update:
Secondary login worked so far without issues on HA. I have set my polling interval to 1hour. I'll try reducing it to 30 and then 15 mins.

Question about the fordpass_tracker sensor:
Is there a way to seperately log the long/lat, so that history of each attribute is recorded? (Possibly graphed on a map?)

Right now it only records at home/away.

Home and away are not part of the sensor. Those are values that Home Assistant reads from what you setup as your home (and not at home). So if the tracker is at home HA says that you're home, not the tracker itself.

In order to break out the lat and long from the sensor you create a sensor for both the lat and long and then you would just create an automation using the service: device_tracker.see to break out the coordinates.

 

[PeeKay]

Edit:
Solved. It had to be state instead of "value_template". For some reason unknown, it did not work initially. :-(

Im not very conversant in yaml or HA.
So I tried the following, but says Unavailable for both:

template:
- sensor:
- name: Mach-E Longitude
value_template: "{{ state_attr('device_tracker.fordpass_tracker', 'longitude') | float }}"
- name: Mach-E Latitude
value_template: "{{ state_attr('device_tracker.fordpass_tracker', 'latitude') | float }}"

but... this one works correctly:

- name: Mach-E 12V Battery Voltage
device_class: voltage
unit_of_measurement: 'V'
state_class: measurement
state: "{{ state_attr('sensor.fordpass_battery', 'Battery Voltage') }}"


PS: I have the appropriate spaces, cut'n paste messed up the format.

 

[DevSecOps]

Im not very conversant in yaml or HA.
So I tried the following, but says Unavailable for both:

template:
- sensor:
- name: Mach-E Longitude
value_template: "{{ state_attr('device_tracker.fordpass_tracker', 'longitude') | float }}"
- name: Mach-E Latitude
value_template: "{{ state_attr('device_tracker.fordpass_tracker', 'latitude') | float }}"

but... this one works correctly:

- name: Mach-E 12V Battery Voltage
device_class: voltage
unit_of_measurement: 'V'
state_class: measurement
state: "{{ state_attr('sensor.fordpass_battery', 'Battery Voltage') }}"

You just have to make the sensors as shown below. I don't have a Ford anymore so you'll need to take this and change it a bit for the MachE ... I'll show you how:

template:
  - sensor:
    - name: Rivian R1T Lat
      unique_id: sensor.rivian_r1t_lat
      state: '{{ states.device_tracker.r1t_location.attributes["latitude"] }}'
      unit_of_measurement: ''
      icon: mdi:map

The above is for Latitude, you'll have to make another for longitude.

Remember that if you have another area with template sensors you need to add this to that area. Don't create another otherwise you'll get an error.

You can change the icon to whatever you want and the names of things as well.

To find the correct attribute you'll need to go to the fordpass sensor in developer tools / states. In filter entity box place the name of the fordpass sensor and then look to the right side for the attributes:

Once you have the above you can make the sensor.

After you make both sensors and do a quick reload you'll see a lat and long.

 

[PeeKay]

Thanks @DevSecOps for those detailed instructions. Lat/Long sensors are now showing correct values.

 

[ziptbm]

How is this group doing now that it seems that Ford is purposely trying to block the Home Assistant integration?

I'm getting emails every 24 hours to reset my FordPass account password due to "suspicious activity" and the integration stops reporting to Home Assistant. The current "workaround" is to reset the password as instructed (note that same password works) and then reconfigure the HA integration...this isn't sustainable and clearly goes against the goal of home automation.

 

[hartmms]

I have fordpass ha only poll every 30 minutes, so I remain under their "suspicious" daily threshold. But that does limit the usefulness of the integration. I really only use the integration to see the lv battery soc and the estimated time until the charge is completed.

I should test out if this current setup allows me to start the car via Google Assistant through HA interface

 

[kodiakng]

currently working for me. it appears 300 reqs/day might be the threshold to stay under their "suspicious" limit. this would give a max of ~5 minute polling to give a buffer. i use 15 minute polling which has been frequent enough for my needs.

@hartmms, just tested and remote start/stop does work via the google assistant integration.

 

[OWG]

How is this group doing now that it seems that Ford is purposely trying to block the Home Assistant integration?

I'm getting emails every 24 hours to reset my FordPass account password due to "suspicious activity" and the integration stops reporting to Home Assistant. The current "workaround" is to reset the password as instructed (note that same password works) and then reconfigure the HA integration...this isn't sustainable and clearly goes against the goal of home automation.

Our use of our data is not Ford's business case for the telemetric data collection and access. And it is not just HA - a number of electric utility EV rebate programs (looking at you ChargeSmart MA) really abuse the API polling every 15 seconds.

I have gone the route of setting up a second FordPass account just to support the integration (and avoid the lock-out of my primary account should the HA access cause an Issue).

 

[ziptbm]

my configuration was at 900 seconds, but I am wondering if my two vehicles are hitting the system more frequently.

Yes, it’s “suspicious” to buy more than one Ford…lesson learned.

I’m also using a second FordPass Account. Given the two vehicles, I may try creating a third.

I rely on this data for optimizing charging to my solar system and for a variety of home automations. Ford just keeps missing revenue opportunities - I would gladly pay an annual fee for secured access for this as it’s far more useful (and has a financial component) than the other half-baked subscriptions they are tying to push.

Sponsored