[Bug]: AdBlock entity unavailable although OpenWrt AdBlock status is enabled

[tdalejandro]

Integration Version

1.6.2

OpenWrt Version

25.12.2

Connection Method

LuCI RPC

Describe the bug

Hi, I found another issue while testing ha-openwrt version 1.6.2 on OpenWrt 25.12.2.

The AdBlock entity appears unavailable in Home Assistant, but AdBlock is enabled and working on OpenWrt.

OpenWrt AdBlock status:

adblock_status  : enabled
frontend_ver    : 4.5.5-r1
backend_ver     : 4.5.5-r1
blocked_domains : 57,861
active_feeds    : 1hosts, oisd_small
dns_backend     : dnsmasq (2.91-r2)
last_run        : mode: start, date/time: 02/05/2026 11:08:55
system_info     : FriendlyElec NanoPi R5C, rockchip/armv8, OpenWrt 25.12.2

However, ubus reports the service instance as not running, but with exit_code: 0:

{
  "adblock": {
    "instances": {
      "adblock": {
        "running": false,
        "command": ["/usr/bin/adblock.sh", "start"],
        "exit_code": 0,
        "pidfile": "/var/run/adblock/adblock.pid"
      }
    }
  }
}

This may be expected behavior for OpenWrt AdBlock, because it loads the blocklist and exits instead of staying as a persistent daemon.

Maybe the integration is checking only running: true, which would mark AdBlock as unavailable even when adblock_status: enabled.

Relevant log output

[github-actions]

Hi @tdalejandro, thanks for opening this issue! 👋

⚠️ Bug Report Received

To help solve this faster, please check the following:

• Is your Home Assistant version up to date?
• Are you using the latest version of this integration?
• Have you checked the documentation for similar issues or configuration tips?
• If applicable: Did you enable debug logging (custom_components.db_infoscreen: debug) and provide relevant logs?

I will investigate this as soon as possible!

---

Please note: I maintain this integration in my free time as a hobby project. I'll do my best to look into this soon, but feedback speed may vary depending on my availability.

[FaserF]

Release 2.0.0 is now available which contains fixes and changes for this issue.

Note: I recommend to do a re-setup of the integration and if the dedicated homeassistant user is being used to re-create it in the config flow from Homeassistant due to changed ACL rules and new features

[tdalejandro]

Fixed thanks!!!