Rusamsungtvcommunicator < CONFIRMED >

: On some older models, it can be used to enable Personal Video Recording (PVR) features that were factory-disabled for certain markets.

| Question | Answer | |----------|--------| | | Only for SmartThings‑enabled TVs (2018+). Legacy TVs work with the 4‑digit PIN method and no account is required. | | Is my TV data sent to the cloud? | No. All communication after pairing is local (LAN). The only cloud traffic is the optional OAuth token exchange, which only transmits the token, not your TV’s IP or usage data. | | Can I control multiple TVs simultaneously? | Yes. Create Profiles for each TV and use the “Room” selector to broadcast a macro to all TVs in that room. | | What if the app can’t find my TV? | 1. Ensure both devices are on the same subnet. 2. Verify that your router does not block UDP port 1900 (SSDP). 3. Disable any “AP isolation” mode. | | Does the app work on a VPN‑connected network? | Only if the VPN runs on the same device and routes local traffic (i.e., split‑tunnel). Full‑tunnel VPN isolates the LAN and discovery will fail. | | Is there a CLI‑only version? | Yes. The binary ships with a --headless flag that disables the UI and accepts commands via STDIN or a config file. Useful for Raspberry Pi‑based automation nodes. | | Where can I contribute translations? | Fork the repo, edit src/i18n/ru_RU.json , and open a pull request. The project also accepts community‑maintained language packs (e.g., uk_UA ). | rusamsungtvcommunicator

alias: "Включить TV перед фильмом" trigger: - platform: state entity_id: sensor.movie_time to: "on" action: - service: media_player.turn_on target: entity_id: media_player.гостиная_tv - service: media_player.select_source data: source: "HDMI 2" target: entity_id: media_player.гостиная_tv : On some older models, it can be

Tip: Keep the TV firmware up‑to‑date. The latest SmartThings API (2023‑04) adds which RUS‑TC uses automatically. | | Is my TV data sent to the cloud