It`s an interesting discussion, so I thought I`d ask about something that I haven`t been able to figure out for some time, and maybe someone more knowledgeable would be able to explain it to me.
Well, I have several smart switches and detectors at home, working in the cloud, communicating via WiFi and managed by the Tuya Smart application. The Tuya Smart application has information about each device, including its Virtual ID, IP address (external, variable, currently assigned by the Internet provider`s server), MAC address, WiFi signal strength. And everything would be fine, the detectors and switches provide the same external address, consistent with the address that also appears, among others, in the Speedtest application, except for one motion detector, which provides a completely different IP address. The first two octets of the address match, but the last two octets are completely different. Its address is from the pool of public addresses, it starts with 37. Also the other detectors and switches.
I was already worried that this one detector might be accidentally connected to the neighbor`s WiFi network, but no, it is visible in the list of devices in my router. Her MAC address matches, she even has an internal IP address assigned within my local network.
Please note that I do not use VPN, VLAN or port forwarding in the router. I also don`t have a permanent public address. I only use IPv4 in the router, IPv6 is disabled. When registering the detector in the network, like all the others, I entered the Wifi network name and password, I did not use WPS.
I even tried to ping the other external address provided by this one detector, but it does not respond.
I have already reset the detector twice and registered it again in the network and still the same thing. What this is about? Could it just be a software error in the detector and incorrect reading of the IP address by the application? But is it a more serious matter?