We are just testing out the OT scanning and are running into similar issues. You do need to be very aware of the protocols that are supported, as described in knowledge base (OT supported protocols). Of course, you have to specify which protocols you want to use in your scanning target definitions, and even just including the included defaults will only recognize those that communicate on default ports.
In essence, to really get value out of Lansweeper OT you need to know your OT environment; e.g. what protocols are supported by the devices you want to identify and how those devices are configured. I expect a lot of organizations may not have that knowledge in house; if they do, they are probably already using something else to monitor those devices.
It certainly isn't a product you just 'drop in' to your environment with an expectation of immediate results. At least, that is my experience so far. Time will tell.