Samsung TV 2016 No longer working in 0.63

[Hackashaq666]

Just updated and restarted homeassistant 0.63.
Samsung TV (2016 model) is not working after update.
Was fine in previous releases.
Restarted homeassistant again to be sure, still not working.
TV shows as OFF even when on.
Power button in homeassistant does nothing.
Not seeing any error in home-assistant.log

Rolled back to 0.62.1 and is working normally.
(Windows 10, Python 3.6 64bit)

[GrahamH68]

I'm seeing the same issues for 0.63 on CentOS-7 with Python 3.6 for Samsung TV's.

Also seeing "FileNotFoundError: [Errno 2] No such file or directory: 'ping': 'ping'" for Device_Tracker for these and others, plus Cookie issues for ZoneMinder. Seems a lot of things just got broke so there's probably a simple common cause somewhere (hopefully).

[kennedyshead]

I can not say anything about ZoneMinder but for the samsung TV there is a change in how it detects ON/OFF.

Hackashaq666 Could you please open a terminal and ping your TV:
ping _ip_

[Hackashaq666]

When I ping TV when off I get "Destination host unreachable"
When I ping TV when on I get reply "bytes=32 time<1ms TTL=64"

Component is working after rollback to homeassistant 0.59.2 and websocket-client 0.43.0.

[kennedyshead]

could you also run which ping

[roflmao]

Mine is behaving unstable with 0.63. Shows tv as off/on without it being turned on/off. Worked flawlessly with 0.61

config:

- platform: samsungtv
  host: 192.168.66.32
  name: Stue TV
  timeout: 9

state:

19:58:51 <HA1337> TV just changed from on to off
19:58:56 <HA1337> TV just changed from off to on
20:24:10 <HA1337> TV just changed from on to off
20:24:15 <HA1337> TV just changed from off to on

[Hackashaq666]

sorry “which ping” is not valud in windows

[kennedyshead]

The problem is that ping is not working the implemented way on Windows, in CentOS there is something wrong with PATH so the script do not find ping command.

We could go with this solution: #11179

Or we could write a pure python ping

[Hackashaq666]

I can use homeassistant 0.63.3 if I downgrade the samsung.py component to earlier version.

[tiagoroxo]

So I have HomeAssistant(0.63.2) and the following configuration for my Samsung Q6F (2017 model):

platform: samsungtv
host: 192.168.1.XX
port: 8001
name: TV
timeout: 5
mac: cc:XX:XX:XX:XX:XX

I can only see the status (ON or OFF) and the only interaction working(random) it’s Turn ON the TV, the remaning options doesn’t work, like: Turn OFF, volume UP/DOWN, change channel....
I cannot really tell if it was working or not before with this new 2017 model, but I have other Samsung TV from 2014, and that TV used to work in an older homeassistant build, but now it's not working either with same behaviour.

[Murph24]

@tiagoroxo My guess is that your issue is likely that you are missing the 'websocket-client' library that is needed for the newer samsungs. Its not being installed automatically like its should.

The On\Off state reporting and "turn on" functions work because they don't use functions from that library. Everything else does however.

[tiagoroxo]

thanks for your feedback. I can give a try and install the correct version of the 'websocket-client' library, if you can give me the instructions, and then I will let you know the outcome.

[m0wlheld]

My 2017 UE49MU6179 Tv can only be turned on using Home Assistant, but neither turned off or controlled otherwise using Home Assistant 0.63.0, 0.64.0 or 0.64.1 .

I am using the provided Docker container on a Raspberry Pi3. It it required to bind the container to the Raspberrys network (--net=host or network_mode: host (for Docker Compose)), otherwise not even turing it on works.

The configuration is identical to tiagoroxo, except for the IP address of course.

[Murph24]

@tiagoroxo

Assuming you’re not using HassIO, SSH into the Pi and run these
sudo su -s /bin/bash homeassistant
cd /srv/homeassistant
source bin/activate
pip3 install websocket-client
(then restart homeassistant or pi)

@m0wlheld I'm not sure how docker works, sorry.

I put in a request to fix this here. Looks like it'll maybe be in 0.64.2 release
#12769

[tiagoroxo]

@Murph24
Thanks for your feedback.
So I updated to the latest Home Assistant build (0.64.3) available in hassbian and executed the following:

pi@hassbian:/home $ source /srv/homeassistant/bin/activate
(homeassistant) pi@hassbian:/home $ pip3 install websocket-client
Requirement already satisfied: websocket-client in /srv/homeassistant/lib/python3.5/site-packages
Requirement already satisfied: six in /srv/homeassistant/lib/python3.5/site-packages (from websocket-client)
(homeassistant) pi@hassbian:/home $ deactivate
pi@hassbian:/home $ sudo reboot

After the changes, now I got a notification on the TV, if I wanted to accept the remote controller or not, I have accepted it, and now, I have more control but the control it's "erratic".
Example:
Reboot the HA and TV, and tried the following:

1. In HA Dashboad I pressed "TURN OFF" - The TV turns off, but in the HA Dashboard I see that the TV remanins with the satus ON for a couple of seconds (+/- 15 ?!).
   
2. I press on "TURN ON" - The TV turns on, and in HA dashboard, it takes 10 seconds(+/-) to update the status from OFF to ON.
3. Waited 1 minute(+/-) and tried to TURN OFF again the TV, and nothing happened.
4. Waited 1 more minute(+/-) and tried to TURN OFF again the TV, and nothing happened.
5. If I open the TV Card, and play with the volume settings(UP/DOWN), after 2 attempts, I can control the volume UP or Down, mute, and then I again have control to Turn OFF the TV...
   
   But this is very "erratic"... it's not consistent the behaviour.

---

Just to remind that my Tv it's the following: Samsung Q6F (2017 model) with Tizen OS.
And and I have the following configuration:

platform: samsungtv
host: 192.168.1.XX
port: 8001
name: TV
timeout: 5
mac: cc:XX:XX:XX:XX:XX