Hello @Goddeti Dhanasekhara Reddy ,
While using Azure IoT services under the hood, IoT Central is SaaS what does not directly expose the built-in IoT Hub device endpoint and uses DPS to provide the "current" connection string to the devices trying to connect. Saying this, while it is technically possible to retrieve the connection string and use it with a native MQTT client, it is recommended to use the Azure IoT Device SDK for connecting to IoT Central. I believe for a Smart TV this is not an option as you might not be able to install the Azure IoT Device SDK.
Why do you need IoT Central? If IoT Hub is an option, you can follow the instructions to communicate via MQTT with IoT Hub and build your custom visualization with a webapp or use Power Bi.
Alternatively, you can follow a bridging approach where your Smart TV connects to an intermediate service what provides a standard MQTT Broker and forwards the messages via the Azure IoT Device SDK to IoT Central. This intermediate bridging service could run on a Raspberry PI or any other computer in the LAN of your Smart TV or a cloud service providing a central approach for multiple distributed devices. While the concept is outlined in the documentation and sample code for Sigfox and The Things Network exist on GitHub, you would need to build your own custom bridging service.