Issue reported in the Home Assistant Logs

[TheGabeMan]

Logger: homeassistant.util.loop
Source: util/loop.py:136
First occurred: 5:19:00 PM (1 occurrences)
Last logged: 5:19:00 PM

Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f987ee310a0>, '/usr/local/lib/python3.13/site-packages/certifi/cacert.pem') inside the event loop by custom integration 'zaptec' at custom_components/zaptec/api.py, line 329: async with receiver: (offender: /usr/local/lib/python3.13/site-packages/azure/servicebus/_pyamqp/aio/_transport_async.py, line 210: context.load_verify_locations(ca_certs)), please report it to the author of the 'zaptec' custom integration

For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 227, in sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 213, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707, in run_until_complete self.run_forever() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678, in run_forever self._run_once() File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033, 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 "/config/custom_components/zaptec/api.py", line 329, in _stream async with receiver:

My HA version is 2025.1.
Zaptec Go charger firmware 2.4.1.8

As I don't have my new Electric Vehicle yet, I don't know if the integration is still working correctly.

[sveinse]

Yes, this is most likely related to an old version of Microsoft Azure Servicebus, which Zaptec use. There is a new version of Zaptec using a newer servicebus which most probably fixes the issue. However it haven't been released yet. Please test the zaptec version in master and see if this fixes the issue. Thanks.

[Filipedberger]

I’m using the version from the master branch and get the same warning. However, everything seems to be working fine!