Status of devices imported with ADGUARDIMP are not correct

[0berkampf]

What installation are you running?

Production (netalertx) 📦

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://docs.netalertx.com/

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Edge
• Safari (unsupported) - PRs welcome
• N/A - This is an issue with the backend

Current Behavior

Devices imported from Adguard Home are shown as Online even if they are not.

Expected Behavior

Status of offline devices should be shown as Offline

Steps To Reproduce

No response

Relevant app.conf settings

docker-compose.yml

Debug or Trace enabled

• I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.

Relevant app.log section

No response

Docker Logs

22:41:05 [Plugin utils]  display_name :  AdGuard (Device import)
22:41:05 [Plugins] Executing: python3 /app/server/plugins/adguard_import/adguard_import.py
22:41:05 [Plugins] Output: [plugin_helper] reading config file
22:41:05 [ADGUARDIMP] In script
…………….
…………….
22:41:05 [ADGUARDIMP] Skipping device with 172.20.10.1 as no MAC supplied and ADGUARDIMP_FAKE_MAC set to False
22:41:05 [ADGUARDIMP] Skipping device with fe00:: as no MAC supplied and ADGUARDIMP_FAKE_MAC set to False
22:41:05 [ADGUARDIMP] New entries: 55
22:41:05 [Plugins] SUCCESS for ADGUARDIMP received 55 entries
22:41:05 [Plugins] Processing        : ADGUARDIMP

[jokob-sk]

Thanks for the report. This should be available/fixed in the next release.
It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container (make sure you use a unique PORT and GRAPHQL_PORT if running instances concurrently) with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may revert the changes to avoid introducing bugs.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[0berkampf]

Thanks for your answer, it’s working now!
Do you want me to close this issue or wait for the stable release?

Thx again for your help.

[jokob-sk]

Thanks for testing - will keep the issue open until next release in case someone has the same issue.