samsungtv platform allows you to control a Samsung Smart TV.
Go to the integrations page in your configuration and click on new integration -> Samsung TV. If your TV is on and you have enabled SSDP discovery, it’s likely that you just have to confirm the detected device.
When the TV is first connected, you will need to accept Home Assistant on the TV to allow communication.
YAML configuration is around for people that prefer YAML.
To use this integration, add the following to your
# Example configuration.yaml entry samsungtv: - host: IP_ADDRESS
Defines an action to turn the TV on.
After saving the YAML configuration, the TV must be turned on before launching Home Assistant in order for the TV to be registered the first time.
If the integration knows the MAC address of the TV from discovery, it will attempt to wake it using wake on LAN when calling turn on. Wake on LAN must be enabled on the TV for this to work. If the TV is connected to a smart strip or requires a more complex turn-on process, a
turn_on_action can be provided that will take precedence over the built-in wake on LAN functionality.
To wake up the TV when switched off you can use the wake-on-lan integration and call a service.
wake_on_lan: samsungtv: - host: IP_ADDRESS turn_on_action: - service: wake_on_lan.send_magic_packet data: mac: MAC_ADDRESS
Changing channels can be done by calling the
with the following payload:
entity_id: media_player.samsung_tv media_content_id: 590 media_content_type: channel
It’s possible to switch between the 2 sources
Some older models also expose the installed applications through the WebSocket, in which case the source list is adjusted accordingly.
Samsung SmartTV does not allow WebSocket connections across different subnets or VLANs. If your TV is not on the same subnet as Home Assistant this will fail. It may be possible to bypass this issue by using IP masquerading or a proxy.
Some televisions from the H and J series use an encrypted protocol and require manual pairing with the TV. This should be detected automatically when attempting to send commands using the WebSocket connection, and trigger the corresponding authentication flow.