Parent Network Node not the same when clicking on the details of a device (Version 26.2.6)

[edd080]

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

When viewing a device under the all devices or my devices menu; the Parent Network node is showing the correct parent node that I would have chosen; however when I click on one of the devices to view its detail, the Parent Node shows the router instead. This is happening to all devices I have listed.

Expected Behavior

Show the actual parent node when clicking on the details of a device, and not the router as the parent node.

Steps To Reproduce

Go to all devices and click on a device.
Check the Parent Node of the device.

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

  PASTE LOG HERE. Using the triple backticks preserves format.

Docker Logs

  PASTE DOCKER LOG HERE. Using the triple backticks preserves format.

[jokob-sk]

Hi @edd080 ,

Did you refresh the cache in the browser and by clicking the reload button in the blue header?

Try also opening the page in incognito.

[edd080]

Hello @jokob-sk , yes I tried all the above including different browsers (Chrome, edge, firefox) and using incognito, but still the same, for some reason the parent node in the details of a device is defaulting to the router and not the actual parent node.

[jokob-sk]

Could you please confirm you did this in this order:

1. Click the reload button in the blue header
2. Refresh the browser cache (shift + reload button)
3. Optionally check incognito

I cant reproduce your issue if I follow these steps.

[edd080]

hello @jokob-sk , yes I confirm I did the above; I have two Pi's with both the latest version of netalertx installed and both give me the same issue.
I decided to downgrade one of the Pi's to a previous version (26.2.4) and had the same issue, whilst in the device details, if I change back from the default router to the actual parent device and save, when I go back to the main menu and back again in the device details the router again is showing as the parent node. It says that it saved but does not keep the modification for the parent node.
I then went to (26.1.17) and this does not even load the device details, I remember this version was quite buggy for me; so I continued to downgrade to 25.11.29, and modified one of my devices from the router to the actual parent node and this time when I go to the main menu and back in the device details I noticed that these are displaying the parent node correctly.
It seems that the newer versions are not keeping the parent node when viewing the device details; especially when modifying a newly discovered device.
Sorry for the long explanation but I tried to be as much detailed as I could.
Let me know if I can provide you with more details..

[jokob-sk]

Hi @edd080 ,

Regrettably I can't reproduce the issue.

See attached screen recording.

1. I changed the Parent Node from Switch to AP
2. Went to the devices view (you see a cached version): Switch still visible
3. Went to edit the parent node again and changed it to None
4. Went to the devices view -> Refreshed cache -> Correctly no Parent node shown
5. Notice the version in the footer: Version: v26.2.6

Please record a similar video with the above steps and footer visible to demonstrate the issue.

[edd080]

Hello @jokob-sk where can I send you this recording as there is some sensitive info, can I send it directly to you please?

[jokob-sk]

Hi,

You can use netalertx@gmail.com

[edd080]

Thank you so much, I am going to send you a link via onedrive to access the recording. 👍

[edd080]

Hello @jokob-sk just wanted to know if you managed to access the recording.