Closed vincegre closed 2 years ago
Unfortunately, this is an issue with the Home Assistant Supervisor or the Home Assistant Frontend, not an add-on issue.
Please report your issue with the Home Assistant project. From the add-on site of things, there is nothing I can do to fix this.
../Frenck
Unfortunately, this is an issue with the Home Assistant Supervisor or the Home Assistant Frontend, not an add-on issue.
Please report your issue with the Home Assistant project. From the add-on site of things, there is nothing I can do to fix this.
Thaks for your answer but it would affect only Adguard as all my others add-ons are working fine ??
Additional details: I was previously running beta cthannel for HA but switched back at release channel, got the 2022.8.0 upgrade but problem still exactly the same :( So I think it's really a bug in the add-on !
Thaks for your answer but it would affect only Adguard as all my others add-ons are working fine ??
It is outside of the add-on scope. From an add-on perspective, there is nothing I can do. Please report upstream as instructed. Thanks 👍
I'm sorry to comment in this closed topic. But I have the same problem, and when I restore a backup from 4.6.1 the add-on is working as expected system:
version | core-2022.8.0 |
---|---|
installation_type | Home Assistant OS |
dev | false |
hassio | true |
docker | true |
user | root |
virtualenv | false |
python_version | 3.10.5 |
os_name | Linux |
os_version | 5.15.55 |
arch | x86_64 |
timezone | Europe/Brussels |
config_dir | /config |
See above messages.
@frenck no offense but I was already not convinced by your explanation and close of ticket but it confirms my feeling that problem was well in Adguard addon and not in supervisor ! What a surprise, the update in 4.7.1 of Adguard today has solved the issue.....
@vincegre No offense either, but I know the exact cause of the issue, and it's not an add-on issue. Even without upgrading, in your current instance, it may happen again (e.g., after a reboot of your system or when restarting the add-on).
@frenck Thanks for the details but is there a way to do something on user side if problem occurs again ? as it's quite annoying or have to wait patiently that supervisor issue be fixed ? :/
but is there a way to do something on user side if problem occurs again ?
No, it is a bug upstream in the Home Assistant Supervisor, if you run into such an issue, please report it upstream as suggested above.
Problem/Motivation
Using since a long time Adguard extension in HA. Worked fine till yesterday. After upgrade at 4.7.0 it's still running as it distributes IP in DHCP, but It appears as off in HA and can't start it, and if I want to acess GUI it says me addon is not started ! Logs of addon shows it's working !
Expected behavior
Display proper running status and let me access GUI !
Actual behavior
Can't start the addon in HA, nothing happens when I click start ! GUI not avalaible stating Adguard is not running, but DHCP feature still working as I can see in logs of addon !
Steps to reproduce
Update to 4.7.0
Thanks
Vincèn