Setup for Germany not available and workarounds do not work

[mkloock1-rgb]

The HA Ford Pass Integration version 1.8beta does not provide the possibility to choose Germany. When you change the URLs provided for NL or UK to Germany locale the tokens which are created do not work. AI says there is an old B2C Auth Flow implemented and a new one has to be implemented. Can someone do that? Thanks!

[Hobjersgarden]

It's the same in sweden

[Klipperino]

Same here. Updated to Home Assistant 2025.11 this morning, that might have something to do with it.

Related logs:

This error originated from a custom integration.

Logger: custom_components.fordpass
Source: custom_components/fordpass/__init__.py:247
integration: Fordpass (documentation, issues)
First occurred: 15:23:30 (1 occurrence)
Last logged: 15:23:30

'bool' object is not subscriptable

This error originated from a custom integration.

Logger: custom_components.fordpass
Source: custom_components/fordpass/__init__.py:248
integration: Fordpass (documentation, issues)
First occurred: 15:23:30 (1 occurrence)
Last logged: 15:23:30

Error communicating with FordPass for *REDACTED VIN*

[paulcusick3]

USA not working for me for 24hours. I did not upgrade to 2025.11. I've disabled for now to prevent lockout.

[tempus2016]

Same here. Updated to Home Assistant 2025.11 this morning, that might have something to do with it.

Related logs:

This error originated from a custom integration.

Logger: custom_components.fordpass
Source: custom_components/fordpass/__init__.py:247
integration: Fordpass (documentation, issues)
First occurred: 15:23:30 (1 occurrence)
Last logged: 15:23:30

'bool' object is not subscriptable

This error originated from a custom integration.

Logger: custom_components.fordpass
Source: custom_components/fordpass/__init__.py:248
integration: Fordpass (documentation, issues)
First occurred: 15:23:30 (1 occurrence)
Last logged: 15:23:30

Error communicating with FordPass for *REDACTED VIN*

Same for me. Also have other errors:

This error originated from a custom integration.

Logger: custom_components.fordpass
Source: custom_components/fordpass/__init__.py:247
integration: FordPass (documentation, issues)
First occurred: 5 November 2025 at 22:05:38 (748 occurrences)
Last logged: 14:51:24

'bool' object is not subscriptable

[marksieczkowski]

Mine started failing before 2025.11 => #619 (comment)

[Hobjersgarden]

Mine started failing before 2025.11 Den tors 6 nov. 2025 16:02Mark Sieczkowski ***@***.***> skrev:

…

*marksieczkowski* left a comment (itchannel/fordpass-ha#620) <#620 (comment)> Mine started failing before 2025.11 => #619 (comment) <#619 (comment)> — Reply to this email directly, view it on GitHub <#620 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3FFBKV26TJV6CYS6AIAVS333NPHPAVCNFSM6AAAAACLKO2HHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJXGY2DMNRTGY> . You are receiving this because you commented.Message ID: ***@***.***>

[ruteclrp]

The issues actually started before updating to 2025.11.

This is my log of the issue when starting:
2025-11-05 16:15:19.820 WARNING (MainThread) [custom_components.fordpass] 'NoneType' object does not support item assignment 2025-11-05 16:15:19.820 WARNING (MainThread) [custom_components.fordpass] Error communicating with FordPass for WF0FXXWPMHRL59547 2025-11-05 16:15:19.821 ERROR (MainThread) [custom_components.fordpass] Error fetching fordpass data: Error communicating with FordPass for WF0FXXWPMHRL59547 2025-11-05 16:15:19.825 ERROR (MainThread) [custom_components.attribute_as_sensor.sensor] Attribute (Battery Charge) not found in state attributes for entity sensor.fordpass_elveh Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 689, in state numerical_value = float(value) # type:ignore[arg-type] ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 360, in _async_dispatch_entity_id_event hass.async_run_hass_job(job, event) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 937, in async_run_hass_job hassjob.target(*args) ~~~~~~~~~~~~~~^^^^^^^ File "/config/custom_components/attribute_as_sensor/sensor.py", line 165, in _async_attribute_sensor_state_listener self.async_write_ha_state() ~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1026, in async_write_ha_state self._async_write_ha_state() ~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1151, in _async_write_ha_state self.__async_calculate_state() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1088, in __async_calculate_state state = self._stringify_state(available) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1032, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 691, in state raise ValueError( ...<5 lines>... ) from err ValueError: Sensor sensor.car_battery_soc_2 has device class 'battery', state class 'measurement' unit '%' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 689, in state numerical_value = float(value) # type:ignore[arg-type] ValueError: could not convert string to float: 'unavailable' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.13/logging/handlers.py", line 1509, in emit self.enqueue(self.prepare(record)) ~~~~~~~~~~~~^^^^^^^^ File "/usr/local/lib/python3.13/logging/handlers.py", line 1491, in prepare msg = self.format(record) File "/usr/local/lib/python3.13/logging/__init__.py", line 999, in format return fmt.format(record) ~~~~~~~~~~^^^^^^^^ File "/usr/local/lib/python3.13/logging/__init__.py", line 712, in format record.message = record.getMessage() ~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/logging/__init__.py", line 400, in getMessage msg = msg % self.args ~~~~^~~~~~~~~~~ File "/usr/src/homeassistant/homeassistant/core.py", line 371, in __repr__ return f"<Job {self.name} {self.job_type} {self.target}>" ^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1616, in __repr__ return f"<entity {self.entity_id}={self._stringify_state(self.available)}>" ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1032, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 691, in state raise ValueError( ...<5 lines>... ) from err ValueError: Sensor sensor.car_battery_soc_2 has device class 'battery', state class 'measurement' unit '%' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unavailable' (<class 'str'>) Call stack: File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 229, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 215, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 271, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.13/asyncio/base_events.py", line 712, in run_until_complete self.run_forever() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever self._run_once() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2050, in _run_once handle._run() File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 362, in _async_dispatch_entity_id_event _LOGGER.exception( File "/usr/local/lib/python3.13/logging/__init__.py", line 1555, in exception self.error(msg, *args, exc_info=exc_info, **kwargs) File "/usr/local/lib/python3.13/logging/__init__.py", line 1549, in error self._log(ERROR, msg, args, **kwargs) File "/usr/local/lib/python3.13/logging/__init__.py", line 1665, in _log self.handle(record) File "/usr/local/lib/python3.13/logging/__init__.py", line 1681, in handle self.callHandlers(record) File "/usr/local/lib/python3.13/logging/__init__.py", line 1737, in callHandlers hdlr.handle(record) File "/usr/src/homeassistant/homeassistant/util/logging.py", line 113, in handle self.emit(record) Unable to print the message and arguments - possible formatting error. Use the traceback above to help find the error.

I only updated to 2025.11 around 18:30 today, and this started yesterday.

[ruteclrp]

Trying to reapply the connection getting this error when obtaining a token: Failed to launch 'fordapp://userauthorized/?code=eyJraWQiOiJHS2R2ZTVaVXEtNjBlRVpsTHRINHpiR3JfY1JoU05mWEJXVDZBYUtKTUlvIiwidmVyIjoiMS4wIiwiemlwIjoiRGVmbGF0ZSIsInNlciI6IjEuMCJ9.nwZscTxMdvAgInwqqCigI_uamfiLTwfnzJEU0ABpVISBVALmAcnoLuHvExoJxKsVQhztAbJzGFQ3giT89Q2nBNyVb1we68mNK_RF0tW8oNqsaiNxZLSWIyXKEE5W2zxaFOxiK1rCwnnYX6KAamRu0Jg5LOqg5gWCB68bwNNKlCQVz7B94Fof1cjdi_F-5foxcZ4qCBEAUbkp-V4I2KrKzdFaXIy-_gfDU_I8fi9R9eSB5pn_KgX8RX11HIOV8VnTwJsoxcje4n9HpekvXsIRIVz6khI1CjOrIMoY0YVfBuL3Kg-r43uXpNZglZbrVXFBSE4am1c2L1Rlrdc6O1ypyA.sdvWB1fcn7mS-SyV.-3CLYDl6X5CPqVwUtdcq423GnGGgcO-IML6p1axwpK55R_1cxrN2r0dpieEYZ4zwTaaaWccxFlBc-74EVgnrPJyC3jJSfHUKK-tReop4PEww8zszvHoH1n2vuPuqvEdci8y5ul3BrhHFqu_mHqhTM2kyFXvgi84cUp50yykyqynl-ux6mVxTdEdwDnHeM3_2wOISEDUYNyZtwcs6R68aS93EFiiyEYzCFcN90S4vMrlXpLCuc_mpWfYX98lm_cbU-rvKOPzU7xXgBYR0Gzmmzict-ruvri1RhICHvJ6kOyc077JnTvQ3ftVOTD7gJhsSGqqEDUndbCxIsV9pWJzt0wLSwV5FGzyyjwMXjSSYVFTHRGG3un2cc96h1lz8jb6NxaJ3JYTVx-muJpxs2stA96jS-R3emqbxHERTfoRsfTNhchtQt1RCTFirKlevxJ53_s5GFBXO6GztG39xzC270DXv-6kVo7NJy4A3p5efFuzPBKuacmq2oD2zI92YFsM18m_2dVIvokHvFyTviZcTtbRVHgiYVCM_KomUtJ96ZP_x2fsaOLtlUvOubUXAUYifca3-VmxPclMCFXLnk7zvJQveov8FRZLVlp4eLVwQnib_ROMESPJvZLDggbwu0FptGjgiGs1IdwQ50YmBmxaSVXfPsgBfUevBJquWYTxASu9jUzaQyhtUEhl_2bikWTpdjgCCWq5ozVXgcrqov1ADujf2YyNFgd5szsOUjQw4cDGg9tatUqM5bYeVl8DG5SRXRHy3R4m7pzXxzE9P3TOimm7mLIwZSSRQuM_nUwScDEDEOLgiwHLq.WZMIvJTmLv-PVtqU8OAiRQ' because the scheme does not have a registered handler.Understand this error

[smaegley]

Also in the US and started to fail with 2025.11, I deleted my FordApp integration and tried to re-authenticate (resolution that worked in the past) and it won't authorize.

[kambiumdt]

well, i get error like this whentry to connect:

cannot_connect - 'AADB2C90090: The provided JWE is not a valid 5 segment token. Correlation ID: 70f83a64-7128-4ec8-9c54-d3a662470263 Timestamp: 2025-11-06 19:58:44Z '

[navarrolux]

I'm experiencing the same issue. It stopped working before November 2025, then briefly worked, and now it's broken again. Deleting and re-adding the integration didn't resolve the problem. I am unable to reauthenticate; the process gets stuck at the login stage.

[michal-bartak]

There is no relationship to HA version. I'm still on HA 2025.09.
The integration stopped working on its own yesterday: 2025-11-05 16:26:59

2025-11-05 16:26:59.916 WARNING (MainThread) [custom_components.fordpass] 'NoneType' object does not support item assignment
2025-11-05 16:26:59.916 WARNING (MainThread) [custom_components.fordpass] Error communicating with FordPass for WF0**************
2025-11-05 16:26:59.917 ERROR (MainThread) [custom_components.fordpass] Error fetching fordpass data: Error communicating with FordPass for WF0**************

[mkloock1-rgb]

Sorry, guys, that you all have your issues with this integration. The topic of this thread is NOT to explain the issues AFTER the implementation in HA was done and worked and NOW does not work any more.
The topic of this issue is that the integration for the solution in Germany (and maybe other countries) cannot be implemented at all assumingly because of an old or not working authentication method.

[Hobjersgarden]

1.80-beta5 works perfect in Sweden tanks!

[mkloock1-rgb]

Very good to hear! What are your settings? Have you changed the locale or which market worked for you?