@D-C its exactly what's happening. Crazy issue!!! 

See this picture:

Some notes:

* Enabling/disabling Port Isolation or Loop Prevention don't change anything

* Restarting the switch also don't solve

* Theres no reset button (at least externally, i don't want to open it before try to RMA)

* The 192.168.0.1 don't respond to HTTP, Telnet or SSH ports (maybe it have some way to update or configure?)
* The laptop i'm testing is completly different from the pcs on the site (windows version, softwares, etc), but the behavior is the same

@EliasSoares, the first ping attempt was with the laptop disconnected?  If not I'm truly stumped.  Usually, people need help because they can't ping their switch.  Still might be worth looking at arp -a to get the mac for the 192.168.0.1 address.  There are mac/oui decoders online that might match it to the vendor, curious if it's a TP-Link OUI.  I hate unsolved problems, even if it's not mine!

  @D-C no. Both pings was with the cable connected, just forgot to add the -t flag so i restarted it.

Today morning i took a photo of arp, and yes, its a tplink vendor id.

I'm almost convinced that for some reason it shares hardware with some managed switch, and have some wrong firmware or firmware bug.

Also I'm not alone: https://community.tp-link.com/en/business/forum/topic/825058?replyId=1641962

@EliasSoares, I'm out of ideas. I hope you can get a replacement. Maybe one of the moderators has a fresh idea.  Assuming it's locked to the one IP, you should be able to change the router/gateway IP or network to something else so things will work with the existing switch. Good luck!