Odometer display FIX

No clue what is going on...

As reported in #25 the odometer has some 'magic' behaviour - I am clueless why the implementation that works for my fordpass integration fails for fordconnect-query. But instead of try to find the reason, there should be no need for special handling (since HA Flag TOTAL_INCREASING should do the required stuff)

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

HA 2026.2 adjustments

Overwrite HA default friendly_name generation

Finally I have found the root cause why with HA 2026.2 the entities include the device name by default as prefix in the new dashboards (which IMHO makes them almost unusable). So with this update the integration will only add the device name, if you have specified a custom name for the device (this name can be deleted btw).

Unfortunately for the entities marked as favourites, HA still ignore the friendly_name attribute and is using some other code, to add the device name in front of the entity name.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

HA 2026.2 adjustments | API Rate-limit enhancements | French translation

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Patch

Ensure that all entity ids and the unique ids are matching the technical requirements]

API Rate-Limit handling

In case that you hit the API rate limit (e.g. caused by integration restarts), the Integration tries to reduce the frequency of further requests - at least the logging should be better

Added French Translation

Kudos @Gouar

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

HA 2026.2 adjustments (patched)

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Patch

Ensure that all entity ids and the unique ids are matching the technical requirements]

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

HA 2026.2 adjustments

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

HA 2026.2 adjustments

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Added Dutch translation

Dutch Translation

Kudos @mrgroen

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Dock Lock State Sensor (showing Lock state of all doors) - Patch#1

Additional (read-only) Sensor for Lock Information

While the Fordpass Integration offers since the initial release a Lock Entity, that allow you to lock & unlock your vehicle, this information has been missing in the FordConnect Query integration #2.

With the new release there is a new sensor showing the different lock states of all the different doors (just in the same way as you know this from the sensor....door_state attributes). While door states are open/closed, the new Sensor will now display lock or unlock.

Patch#1

Make it independent from the Fordpass Integration

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Dock Lock State Sensor (showing Lock state of all doors)

Additional (read-only) Sensor for Lock Information

While the Fordpass Integration offers since the initial release a Lock Entity, that allow you to lock & unlock your vehicle, this information has been missing in the in FordConnect #2.

With the new release there is a new sensor showing the different lock states of all the different doors (just in the same way as you know this from the sensor....door_state attributes). While door states are open/closed, the new Sensor will now display lock or unlock.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Initial release (patch 2) - FordConnect an alternative to my FordPass Integration

Initial Release

patches

• Appropriate Error Message when credentals are wrong (#9)
• For petrol cars: Use Fuel as "device Battery" sensor (#7)
• Fix Integration title (was 'FordPass' now 'FordConnect Query (for EU)')
• Icon has been added (PR @ ha-brands) (#1)
• LastUpdate Sensor will be available (again)
• Restart Issues are fixed (still the rate limit could cause error entries in your HA log)

known Issues

• Indicator Sensor is always show 0 (FordConnect backend does not provide the is info currently)

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA