We’ve all been there. Let’s start with your router.
I can’t find that model. Is it this?
Anyway, if it’s TP-link the default IP address of the router will be 192.168.0.1 which is the heart of the problem. To talk to each other, every device on the network has to be in the same ‘sub-net’ ie the first three numbers in the IP address must be the same. The problem is, Vero is looking for your NAS on 192.168.1.235 but if you haven’t messed with the router it is assigning your NAS an IP like 192.168.0.x where x is 21 from your screenshot.
Now, the instructions I gave above were to change the router IP to 192.168.1.1 to make it match the NAS subnet that Vero/Kodi is looking for. That’s still what I would do to avoid having to re-scan your library but you need to make sure the NAS ends up with 192.168.1.235 again.
The alternative is to stick with the default 192.168.0.1 and arrange for the NAS to get an IP in that subnet. In fact, it looks like that already happened as it’s 192.168.0.21. Now you have to tell Vero/Kodi to look for your NAS on that IP and not on smb://192.168.1.235/. As @fzinken suggested
You must have done that back when. Connecting to smb sources can be fraught if you’ve forgotten but see here for advice.
Finally, you have to make sure the IP of the NAS is sticky. On a re-boot, the router might assign a different IP to it and Vero/Kodi will no longer see it. So you configure the NAS with a fixed IP or arrange for the router to always give it the same IP.