If by chance it has a “fingerprint” that is blank or all zeroes, then it may not be a multi sensor at all, but something else, even a light bulb, with a failed pairing.
Obviously neither of those will solve the issue, but at least it will give you a little more information.
Also, sometimes this problem occurs not because there is a physical device, but because there has been database corruption in the SmartThings cloud. If that’s the issue, you May need to open an official support ticket and have them look at it .
I would suggest trying to detect when it updates any data and then deleting it as quickly as you can. It has the feel of something that is only online in bursts and it may help if you can catch it while it is active.
The trouble with that theory is it ideally needs you being be power cycling a Zigbee repeater somewhere. Your TV doesn’t have a dongle does it? Anything else new? Did anything get turned on before you got your unwanted alarm?
It seems likely to be a fairly early SmartThings branded sensor, the sort of thing that came in the V2 hub kits. That something you currently use or have used in the past? Just trying to work out if we are looking at an ‘own goal’ from a long forgotten or mislaid device that is suddenly showing signs of life.
It can also be done in the ST Advanced Web App. However, when I deleted my neighbor’s device that was showing up on my hub, it would always come back regardless of whether I deleted it with the mobile app, the AWA, or the CLI.
That’s odd. Home Monitor should only add sensors automatically when ‘all sensors’ is enabled with the toggle switch and if it is enabled you can’t select/deselect the devices.