Core: switch.adguard_protection misbehaving

Created on 4 Feb 2020  路  9Comments  路  Source: home-assistant/core

The problem

switch.adguard_protection does not work as intended

Problem/Motivation

Expected behavior

toggling the switch.adguard_protection from within lovelace should toggle the protection

Actual behavior

switching switch.adguard_protection in Lovelace off or on does not change the status of the add-on. Hence, the switch immediately goes back to its previous state reflecting the actual state of the add-on. In case I switch the add-on off/on from within its GUI the status of the switch.adguard_protection updated accordingly. It appears that the integration to HA lost its capability to switch the protection on/off but at the same time is still capable of reading the actual state of the add-on.

Environment

Latest HASS.io running on a intel NUC

Traceback/Error logs

2020-02-04 07:32:25 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:33:21 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:33:24 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning off AdGuard Home switch.
2020-02-04 07:35:53 ERROR (MainThread) [homeassistant.components.adguard.switch] An error occurred while turning on AdGuard Home switch.

Additional information

adguard

Most helpful comment

Thanks, @wshuman3. I just came here to write the same thing :)
A bit unfortunate 馃槩

I'll patch it up and see if we can put it into the next patch release.

All 9 comments

Which version of Home Assistant are you running? As in the exact version?

Im running:
HA: 0.104.3
HassOS: 3.7
Supervisor: 195

Which version of AdGuard are you running?

AdGuard: 2.3.1 installed via Hass.io Store

Check, thanks! Will look into it!

I can confirm that I have the same issue on HA 0.105.1 (also AdGuard Addon 2.3.1). So it looks like a general issue.
Setting the integration's log to debug doesn't provide further details.

Problem also persisted for me moving to 0.105.1

Looks like you fixed it with 0.4.1 but the merge of PR #30589 reverted that change.

Thanks, @wshuman3. I just came here to write the same thing :)
A bit unfortunate 馃槩

I'll patch it up and see if we can put it into the next patch release.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TheZoker picture TheZoker  路  3Comments

piitaya picture piitaya  路  3Comments

neonandu picture neonandu  路  3Comments

moskovskiy82 picture moskovskiy82  路  3Comments

coolriku picture coolriku  路  3Comments