This is known behavior for some specific Brands and models. It will happen with any zwave controller that is paired with that device unless the controller company has made a specific device type handler for that model.
You usually have two choices with SmartThings. First, you could probably just change it and assign it to a different device type handler of the correct device class.
Second, there may be a community created device type handler for that specific brand and model which solves the problem. For example, Zooz sensors do this and there is a DTH for them.
The universal device type handler is really cool, but it’s not really for this purpose, and it may not work well for it. For example, if you have a motion sensor reporting as open/close to the hub, you’re not going to get an inactivity report from it if you use the universal device type handler. You need to change to a device type handler which does recognize what the device is actually doing.
The universal device type handler is great for those situations where you have, say, an open/close device and you want it to count in a zone of multiple “motion” sensors. But it doesn’t solve the problem of the device being misidentified, which is what you’ve run into.
So… brand and model of the sensors that are misidentified?