AdGuard switches cannot be changed

[JosFis]

The problem

In Home Assistant I cannot change the state of the (e.g. parental control) switches. In Adguard those settings can be changed.

2022-12-07 10:40:58.554 ERROR (MainThread) [homeassistant.components.adguard] An error occurred while turning off AdGuard Home switch AdGuard Versie: v0.107.19 Home Assistant 2022.11.5 Frontend-versie: 20221108.0 - latest

Am I doing something wrong or is this an issue?

What version of Home Assistant Core has the issue?

2022.11.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

AdGuard

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-12-07 10:40:58.554 ERROR (MainThread) [homeassistant.components.adguard] An error occurred while turning off AdGuard Home switch

Additional information

No response

[alexciurea]

Hi, you're not alone, I'm having same issue. Lately, I can disable it from HA, but cannot enable it back. Initially it was completely broken. Indeed, from AdGuard itself the same action works properly.

[Strixx76]

Update: After upgrading to Home Assistant 2023.3.6 (from 2022.11.1) it is working for all 3 instances.

Same here.

I am running 3 different AdGuard Home instances and the versions is: v0.104.1 / v0.105.1 / v0.107.26

With AdGuard v0v104.1 switches is working With AdGuard v0.105.1 there is no switches in the integration, only the "DNS queries" sensor is added to Home Assistant With AdGuard v0.107.26 the switches is not working

[alexciurea]

2023.6.3 still not working...

[home-assistant[bot]]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (adguard) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `adguard` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign adguard` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

adguard documentation adguard source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[alexciurea]

This issue is still relevant. Using latest 2023.10. Probably same issue reported here: https://github.com/frenck/python-adguardhome/issues/795