Next or Previous host do not update the tools page button's ip address.

[zilvernet]

Is there an existing issue for this?

• I have searched the existing open and closed issues and I checked the docs https://github.com/jokob-sk/NetAlertX/tree/main/docs

Current Behavior

This is happening in all the 24 release versions and some 23 latest that i was able to test so far.

In the details of a host the previous and forward do not update the tools buttons ip page.
The tools page get stuck with the ip value of the first host detail that was loaded:

On this example i clicked on the samsung washer from a device search screen.
Then it loaded the details.

Then we go to the tools subpage.

Then we skip and the ip : .131 from the samsung washer still on the tools page.

Expected Behavior

The tools subpage should dinamically change the ip from the current selected host.

Steps To Reproduce

No response

app.conf

No response

docker-compose.yml

No response

What branch are you running?

Production

app.log

No response

Debug 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.

[jokob-sk]

This should be fixed in the next release. If you can, please have a look at the netalertx-dev docker image, in about 15 minutes (or after the last action finishes) from now.

It would be great if you could test this (backup everything first or use a new container) on your end by switching to the above image and letting me know if the issue was resolved.

Thanks in advance,
j

[zilvernet]

Hi @jokob-sk i tested the dev-version, but it seems very buggy.
when i entered to the tools page im not able to see the ip for any of my devices:

[zilvernet]

when i first tested this, i noticed there was no ip on the buttons and when i pressed them i had an error.

Now after a while has passed after I scanned my hosts the buttons are now working. It seems there is a background process that prepares the info for these buttons to be operational. It would be great if the buttons are disabled until they are ready to use to avoid error messages.

[jokob-sk]

Thanks for testing! I think the old JS file cache had to expire because now it seems like the buttons are ready to be used instantly. I will improve this in the future if more users provide feedback related to this behavior.

[jokob-sk]

released 🚀 -> closing