On the nano Router there is a DHCP server running that is giving the IP addresses to the devices which are setup to use DHCP.
The TXT is asking the nano router for IP address and nano gives it the 192.168.0.11 because 192.168.0.10 is already occupied.
Of course you will see the WLAN symbol in TXT when you got the address 192.168.0.11.
Your network key stored in the TXT is valid and nano offers the next free address to the TXT. Do not change the WLAN setup of TXT.
Check the "DHCP address reservation" option in the nano. Check the MAC address that is reported for your TXT.
Bind the IP 192.168.0.10 to the MAC of your TXT.

- nano_DHCP.png (287.97 KiB) 11737 mal betrachtet
Switch off all devices - drop-pod, nano, TXT.
You must find out which device "drop-pod" is! It is connected to your network - if its connection is WLAN based someone had entered the network key, if it is connected to the LAN (cable) interface of the nano you should see the cable

.
Start up all devices (except drop-pod) again. Now TXT should have correct IP.
It would be great if you post a screenshot of your infrastructure maybe gathered from "angry ip scanner"
like in
viewtopic.php?f=8&t=7877
PLC and RasPi are using fixed IP address setup - you should not change the predefined addresses.
Node-Red app is setup to use the predefined addresses.
Hardware config of TIA portal project is also with fixed IP 192.168.0.1.
So you should keep this!
What was your basic problem with PLC?