itchannel

It's actually what's returned by the current Fordpass API endpoint. It doesn't include all window information anymore. However there is another potential way I'm exploring based upon information returned when...

That data is pulled straight from the "windowPosition" dictionary, no data is modified. So "oemCorrelationId" is obviously what they use to match the window to car maybe.

So the new API doesn't expose the old Firmware Update attributes. There is a state called "configurationUpdate" shown below but I've not had enough data to be able to see...

Looks like an API change to the login flow. Will try and take a look later today. In the meantime I recommend people disable the integration in HA until I...

Initial looks it seems Ford have enabled Akamai Bot Manager in a fairly aggressive mode to prevent people calling the API Login from tools other than Fords own app. This...

Aware of this but it's part of the original login code. Will be removed in the future version when I have time to refactor and fix the current login issues...

Interesting, i'm guessing you don't have 2 inputs on your apex both called apex_Leak? It does create a unique ID based upon the controller IP/DNS and the input/output name. I...

Ok will mean adapting another breaking change but in the next update I'll change the entity ID to use the DID but keep the name as the name. So theoretically...

So I've been looking and going to try using a select entity as you guys mentioned https://developers.home-assistant.io/docs/core/entity/select I'll try and draft up something this week, just in the Aussie outback...

I'm back so will take a look at all the issues and the suggested changes you've made and look at merging some bits in this week.