core: AdGuard Integration : Cannot add integration since V4.7.5

The problem

Hello,

I have the AdGuard addon installed, and since the upgrade 4.7.5, the integration was not working anymore. I’ve uninstalled the integration, and everytime I try to reinstall it, i’ve an error message: “Unknown error occurred”

I tried to restarte HA, and to perform a full reboot of the host but the message is still the same.

In the log, I have this error :

Logger: aiohttp.server
Source: components/adguard/config_flow.py:90
First occurred: 20:34:22 (2 occurrences)
Last logged: 20:39:57

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
    return await super().post(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 280, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/adguard/config_flow.py", line 90, in async_step_user
    await adguard.version()
  File "/usr/local/lib/python3.10/site-packages/adguardhome/adguardhome.py", line 224, in version
    return response["version"]
KeyError: 'version'

What version of Home Assistant Core has the issue?

Home Assistant 2022.11.1

What was the last working version of Home Assistant Core?

Home Assistant 2022.11.1

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

AdGuard

Link to integration documentation on our website

https://www.home-assistant.io/integrations/adguard

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 16

Most upvoted comments

Found in my log: 127.0.0.1 on port 45158 (add-on) startup log. Configured the integration with that info worked!

@Gorouk Glad it worked for you this way, but this is indeed not how it was before. My dual setup is now working and I can use the sensors again in statistics and alerting again.

@adekloet I’ve the same kind of structure as you, the HA addon as a primary adguard dns server, and a spare “classic” adguard home as secondary on a separate rpi. I checked the addon start logs and have the same as you, and confirm that using 127.0.0.1 on port 45158 does works for me too as a workaround.