[0.81.0] Samsung TV not working #17802

Gio76 · 2018-10-26T03:00:21Z

Home Assistant release with the issue:
0.81.0b2

Last working Home Assistant release (if known):
0.80.3

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on a Raspberry Pi 3 Model B (32gb SD)
Hass.io supervisor 138
HassOS 1.11

Component/platform:
samsungtv

Description of problem:
Media player not working under 0.81.0b2. It shows off although the TV is on. Reverted back to 0.80.3 and everything started working again. No specific errors in the log.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

media_player:
  - platform: samsungtv
    host: 192.168.86.67
    name: '[TV] Bedroom'
    mac: [REDACTED]

The text was updated successfully, but these errors were encountered:

Hackashaq666 · 2018-10-26T11:20:12Z

Similar problem here, 2016 model year tv, homeassistant 0.81.0b2, raspberry pi 3b+, hass-os.
Homeassistant frontend shows as TV as "unknown" instead of "on".
I can adjust volume, and turn off from the frontend.
When TV is off, the frontend correctly shows TV as "off", however I cannot turn on from frontend, and log shows samsungtv component is taking longer than expected.
Reverted to 0.80.3, and all functions, front end display work as expected.

arsaboo · 2018-10-26T21:22:58Z

experiencing the same issues...not sure what changed

Gio76 · 2018-10-27T02:00:02Z

updated to 0.81.0 and the issue is still there

Murph24 · 2018-10-27T18:31:52Z

@Gio76

I'm having this issue as well. Unfortunately, it looks like this is a TV firmware update problem. Samsung may have broke or disabled the websocket control. Is your TV on the new firmware 1250?

Here is the underlying library HA uses:
Ape/samsungctl#93

RRacer · 2018-10-27T19:44:45Z

I use the Samsung TV component to turn on or off a few lights based on the state of the TV.
When I updated to 0.81.0 the automation will not trigger.
Updated from .80.2 where it was working.
Using an UE65KS7005.
Downgraded to 0.80.3 and it started working again.

Gio76 · 2018-10-28T08:44:39Z

@Murph24

I'm currently on 1530. If they disabled the websocket that would explain why I don't get a prompt from the TV to allow access to external devices. That sucks, I relied heavily on this components for automations

Gio76 · 2018-10-28T09:11:38Z

@Murph24

I actually don't think the TV firmware is the culprit of the issue. In fact I just downgraded to 0.80.3 and everything is working fine. For reference my TV is a 2015 model: UA55J6200

Tacchi1983 · 2018-10-28T10:25:28Z

I have the same problem. When tv is on the state reports as unknown. In 0.80.3 everything is fine. So the problem isn't a firmware update by samsung. Is it still the same with 0.81.1 ? Hopefully there is a solution because i have few automations too with that

kennedyshead · 2018-10-28T11:46:27Z

There was a change in 0.81 where we removed the ping-check and started sending empty key to determine if the TV is on, this was done due to the fact that a TV in standby mode would answer to ping command and therefor never off.
There where also a change to use unknown rather than on, the frontend did not display play/pause in on mode.

I think we can resolve the "off"-bug if I could get someone to run a couple of scripts on broken system.

Tacchi1983 · 2018-10-28T12:08:49Z

My tv reports always correctly as off in standby mode. Also the ping components report as off. I dont have the off bug in 0.81, only the unknown. Hopefully u can change the unknown state. Grtz

Gio76 · 2018-10-28T12:55:12Z

@kennedyshead

Anything I can help with?

pablolassalle · 2018-10-28T12:57:54Z

There was a change in 0.81 where we removed the ping-check and started sending empty key to determine if the TV is on, this was done due to the fact that a TV in standby mode would answer to ping command and therefor never off.
There where also a change to use unknown rather than on, the frontend did not display play/pause in on mode.

I think we can resolve the "off"-bug if I could get someone to run a couple of scripts on broken system.

@kennedyshead

Me too, if I can help running some script or test, please tell me. My TV is a J5500 from 2015.

arsaboo · 2018-10-28T13:37:44Z

I have NU8000 and seeing the same issue. Let me know if there is anything that I can help with.

Devqon · 2018-10-28T14:26:26Z

Also having issues, cannot turn on the TV, and when it is on the state is 'unknown'

kennedyshead · 2018-10-28T16:40:32Z

@Gio76 If you try running samsungctl --host 192.168.0.10 --name myremote KEY and give me that output That is if you have the always off problem.
For the turn on problem I think its because it does not support wake on lan.

PDekker · 2018-10-28T18:32:00Z

I can confirm this issue. When the tv is on the state reports unknown. It is not due to a firmware upgrade (d8000 model)

Issue originated in 81.0

tmonck · 2018-10-28T21:30:27Z

Not sure if this will help but this is the error from my logs. I am having the same issue that I can't mute/unmute, turn on, or turn off. The tv is a MU8000 and all of those commands were working in .80.3

Update for media_player.samsung_tv_remote fails
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
await self.async_device_update()
File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 349, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/media_player/samsungtv.py", line 124, in update
self.send_key("KEY")
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/media_player/samsungtv.py", line 145, in send_key
self.get_remote().control(key)
File "/usr/local/lib/python3.6/site-packages/homeassistant/components/media_player/samsungtv.py", line 130, in get_remote
self._remote = self._remote_class(self._config)
File "/usr/local/lib/python3.6/site-packages/samsungctl/remote.py", line 11, in init
self.remote = RemoteWebsocket(config)
File "/usr/local/lib/python3.6/site-packages/samsungctl/remote_websocket.py", line 30, in init
self._read_response()
File "/usr/local/lib/python3.6/site-packages/samsungctl/remote_websocket.py", line 67, in _read_response
response = self.connection.recv()
File "/usr/local/lib/python3.6/site-packages/websocket/_core.py", line 298, in recv
opcode, data = self.recv_data()
File "/usr/local/lib/python3.6/site-packages/websocket/_core.py", line 315, in recv_data
opcode, frame = self.recv_data_frame(control_frame)
File "/usr/local/lib/python3.6/site-packages/websocket/_core.py", line 328, in recv_data_frame
frame = self.recv_frame()
File "/usr/local/lib/python3.6/site-packages/websocket/_core.py", line 360, in recv_frame
return self.frame_buffer.recv_frame()
File "/usr/local/lib/python3.6/site-packages/websocket/_abnf.py", line 334, in recv_frame
frame.validate(self.skip_utf8_validation)
File "/usr/local/lib/python3.6/site-packages/websocket/_abnf.py", line 149, in validate
raise WebSocketProtocolException("Invalid close opcode.")
websocket._exceptions.WebSocketProtocolException: Invalid close opcode.

tmonck · 2018-10-28T21:34:23Z

@kennedyshead I'm also willing to run scripts to help

Gio76 · 2018-10-29T00:28:09Z

@Gio76 If you try running samsungctl --host 192.168.0.10 --name myremote KEY and give me that output That is if you have the always off problem.
For the turn on problem I think its because it does not support wake on lan.

This is the output:

Traceback (most recent call last):
  File "/usr/local/bin/samsungctl", line 9, in <module>
    load_entry_point('samsungctl==0.7.1', 'console_scripts', 'samsungctl')()
  File "/Library/Python/2.7/site-packages/samsungctl/__main__.py", line 110, in main
    with Remote(config) as remote:
  File "/Library/Python/2.7/site-packages/samsungctl/remote.py", line 9, in __init__
    self.remote = RemoteLegacy(config)
  File "/Library/Python/2.7/site-packages/samsungctl/remote_legacy.py", line 22, in __init__
    self.connection.connect((config["host"], config["port"]))
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 61] Connection refused

Hackashaq666 · 2018-10-29T01:10:17Z

@Gio76 If you try running samsungctl --host 192.168.0.10 --name myremote KEY and give me that output That is if you have the always off problem.
For the turn on problem I think its because it does not support wake on lan.

Hi, can you clarify this a bit? Are you saying certain TV's don't support wake on lan or the updated samsungtv component doesn't support wake on lan?

As I understand it, the old component used wake on lan successfully to turn on TV if necessary.

kennedyshead · 2018-10-29T08:12:17Z

@Gio76

is 192.168.1.10 the ip of your TV? (just making sure ;) ).
Is this in ON or OFF mode?

kennedyshead · 2018-10-29T08:15:30Z

and also, try setting the port to 8001 in yaml config.

media_player:
  - platform: samsungtv
    host: 192.168.86.67
    port: 8001
    name: '[TV] Bedroom'
    mac: [REDACTED]

Gio76 · 2018-10-29T08:30:38Z

@Gio76

is 192.168.1.10 the ip of your TV? (just making sure ;) ).

Is this in ON or OFF mode?

My TV's IP is different. I have of course updated the command line when testing:
samsungctl --host 192.168.86.67 --name myremote KEY
You mean if the TV was on or off when I run the command? The traceback I previously sent you, was executed with the TV ON. If the TV is OFF (stand-by) I get this instead:

Traceback (most recent call last):
  File "/usr/local/bin/samsungctl", line 9, in <module>
    load_entry_point('samsungctl==0.7.1', 'console_scripts', 'samsungctl')()
  File "/Library/Python/2.7/site-packages/samsungctl/__main__.py", line 110, in main
    with Remote(config) as remote:
  File "/Library/Python/2.7/site-packages/samsungctl/remote.py", line 9, in __init__
    self.remote = RemoteLegacy(config)
  File "/Library/Python/2.7/site-packages/samsungctl/remote_legacy.py", line 22, in __init__
    self.connection.connect((config["host"], config["port"]))
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 60] Operation timed out

and also, try setting the port to 8001 in yaml config.
media_player:
  - platform: samsungtv
    host: 192.168.86.67
    port: 8001
    name: '[TV] Bedroom'
    mac: [REDACTED]

Port 8001 has never worked for me, even when the component used to actually work (prior to 0.81.0). If the TV is OFF (stand-by) is correctly shows ass off, however if the TV is ON the entity shows as unknown

kennedyshead · 2018-10-29T08:40:15Z

Unknown is unfourtunatly the new ON mode, it will give you the paus/play buttons.

Test this file as a replacement for components/media_player/samsungtv.py in your installation:
https://gist.github.com/kennedyshead/f37d8e3194343594eacc6cdb22fc5c41
@Gio76

Gio76 · 2018-10-29T08:43:59Z

@kennedyshead

Sorry to the silly question, but since I am using Hass.io, do I create the folders components/media_player/ inside config?

Devqon · 2018-10-29T08:46:12Z

Unknown is unfourtunatly the new ON mode, it will give you the paus/play buttons.

Test this file as a replacement for components/media_player/samsungtv.py in your installation:
https://gist.github.com/kennedyshead/f37d8e3194343594eacc6cdb22fc5c41
@Gio76

This is correct, I read it in the release notes of 0.81.0. Though I find it more a weird workaround.
See #6969

kennedyshead · 2018-10-29T08:47:21Z

Oh... hm sorry, I have 0 experience with Hass.io... This file will show you the correct status for the TV as far as I can tell from your stacktrace.
You should enable anynet allshare what ever on the TV and it will work as intended anyway.

kennedyshead · 2018-10-29T08:49:39Z

@Devqon I think its a bit weird to, but I have 0 knowledge of the frontend code and It will do until that is fixed (if it gets a fix). We should create an issue for it

Answer-1 · 2019-10-14T15:41:15Z

@arsaboo The one hosted on Mega (https://mega.nz/#!Np01iAgT!DCl9pvl7sZ1odxrsh68R7Dcd2UN9uxScVXBuCNBdyJ8)

byackee · 2019-10-15T11:53:03Z

I just recently bought a new Samsung UA65RU7100W and was really hoping to get lucky with this integration.
Unfortunately it didn't come up in any auto-discovery so I then went to manually enter the info in configuration.yaml
What I found works was

WOL

power state (if using port 8001.)

I changed the port to 8002 but that broke the power state and there was no other bits working either.

I am using Home-assistant Docker container and it didn't even give me the authorization message on the TV so I did a wget from my docker host wget http://xxx.xxx.xxx.xxx:8001 and then found that this gave me the authorization message on the TV. I accepted this but still no luck. the media controls come up with error {'event': 'ms.channel.unauthorized'} each time.

If I browse to http://xxx.xxx.xxx.xxx:8001 with an approved IP it now gives me a 401 error. Googling hasn't helped but I am guessing that I need to have some sort of username and password for the TV?
I believe this could be the missing bit to make this module work but I can't be certain. hopefully this helps someone else in troubleshooting and resolving this issue.

Hi,

I have exactly same on Samsung The Frame 2019

xchwarze · 2019-10-17T02:13:32Z

Hello!
I use this fork https://github.com/xchwarze/ha-samsungtv-custom/releases in 2016+ tv
All TizenOS tv should work

AlexeyUkolov · 2019-10-17T20:05:07Z

Have the same issues with 2017 UE49MU9000 TV.
Using this fork [https://github.com/xchwarze/ha-samsungtv-custom/releases] : I can only turn the TV on from HA, but after that the status of device remains "Off" and nothing more working. I even can't turn the TV off.

Tried to add the TV through SmartThings. In this case I get a switch, that only allows me to turn the TV off.

So using these both methods I can only turn the TV on and off through 2 different entities...

xchwarze · 2019-10-17T22:09:20Z

@AlexeyUkolov Sorry i dont upload all files
try this https://github.com/xchwarze/ha-samsungtv-custom/releases/tag/v1.1.1
tested OK in HA 0.100.1 in Samsung MU6300

AlexeyUkolov · 2019-10-18T10:15:18Z

@xchwarze thank you! Now it works, with the port 8002. Excellent work, thank you again!

xchwarze · 2019-10-20T03:29:31Z

thanks @AlexeyUkolov !

n3snah · 2019-10-21T11:37:12Z

@xchwarze I tried using your custom component.
it recognised the TV was on but that was about as far as I could get. the TV kept popping up an authorize message which I kept accepting but changing channels and other actions didn't seem to do anything.

arsaboo · 2019-10-21T14:57:15Z

@laywah2016 Restarting HA took care of the issue for me.

xchwarze · 2019-10-21T17:26:47Z

@ laywah2016 test lastest release
https://github.com/xchwarze/ha-samsungtv-custom/releases

AlexeyUkolov · 2019-10-21T18:53:17Z

@xchwarze thank you for the new release, all looks excellent (especially the source list). The only issue for me now is that "TV" as a source does not work. I also tried KEY_DTV and KEY_ANTENNA - all without any effect. All the orhers sources are switching. Have you any idea?

xchwarze · 2019-10-21T19:50:01Z

thanks @AlexeyUkolov !
I am working on it but without the documentation of samsung.remote.control it is very difficult to achieve.
Maybe if I got the binary of samsung.remote.control (tizen binary from tv) I could add several improvements

lukasz-galos-ps · 2019-10-21T20:39:55Z

Hi,
I can check status of my tv, but i am not authorized to any changes (volume change, power off).
I recived below info:
Failed to call service media_player/volume_mute. {'event': 'ms.channel.unauthorized'}

Regards
Łukasz

lukasz-galos-ps · 2019-10-22T18:03:52Z

I can also power on TV, but others are unauthorized, power off also

n3snah · 2019-11-01T11:36:20Z

Unfortunately still no luck. I tried rebooting HASS, I also stopped and started my docker container.

maximosm · 2019-12-16T18:04:19Z

For me only open(on). I have try ports 8001 and 8002 but no luck.Is there any help or is total cuted from samsung last update the remote?

xchwarze · 2019-12-16T18:14:33Z

I make this version for tizen tvs https://github.com/xchwarze/ha-samsungtv-custom/releases
Tested on mu6300 and others 2017+ models

maximosm · 2019-12-16T18:25:29Z

I make this version for tizen tvs https://github.com/xchwarze/ha-samsungtv-custom/releases
Tested on mu6300 and others 2017+ models

I have test it at my ue58mu6199 but still have the same problem.Only on.

hjm79 · 2019-12-17T11:23:51Z

I make this version for tizen tvs https://github.com/xchwarze/ha-samsungtv-custom/releases
Tested on mu6300 and others 2017+ models

Can you show me the settings? (configuration.yaml)

I have mu6300 too.

AlexeyUkolov · 2019-12-17T11:29:12Z

@hjm79
Not sure that is usefull, but this works for my MU9000 (LAN connected)

media_player:
      - platform: samsungtv_custom
        host: 192.168.1.2xx
        port: 8002
        mac: "84:c0:ef:ec:86:xx"

hjm79 · 2019-12-17T11:39:14Z

@hjm79
Not sure that is usefull, but this works for my MU9000 (LAN connected)
media_player:
      - platform: samsungtv_custom
        host: 192.168.1.2xx
        port: 8002
        mac: "84:c0:ef:ec:86:xx"

Doesn't it work with wifi?

AlexeyUkolov · 2019-12-17T12:00:43Z

I haven't checked.

xchwarze · 2019-12-17T15:43:16Z

Wifi doest support WakeOverLan.
I think there is one option to activate the fire via WS. If they activate it and do not complete the mac address it should work

tulindo · 2020-03-12T19:52:22Z

@escoand and @MartinHjelmare shouldn't we close this one as well?

escoand · 2020-03-12T19:54:53Z

Obvious yes. Wasn't aware of it.

arsaboo · 2020-03-12T20:07:10Z

Closing this for now. Please open new issue if you are having trouble with Samsung TVs.

Gio76 changed the title ~~Samsung TV not working on 0.81.0b2~~ [0.81.0] Samsung TV not working Oct 27, 2018

fabaff mentioned this issue Oct 28, 2018

Samsung TV state #17907

Closed

beloso mentioned this issue Feb 7, 2020

Samsung TV new integration doesn't work #31504

Closed

arsaboo closed this as completed Mar 12, 2020

This comment has been minimized.

Sign in to view

home-assistant locked as resolved and limited conversation to collaborators Jun 9, 2020

[0.81.0] Samsung TV not working #17802

[0.81.0] Samsung TV not working #17802

Comments

Gio76 commented Oct 26, 2018

Hackashaq666 commented Oct 26, 2018 • edited

arsaboo commented Oct 26, 2018

Gio76 commented Oct 27, 2018

Murph24 commented Oct 27, 2018

RRacer commented Oct 27, 2018 • edited

Gio76 commented Oct 28, 2018

Gio76 commented Oct 28, 2018 • edited

Tacchi1983 commented Oct 28, 2018 • edited

kennedyshead commented Oct 28, 2018

Tacchi1983 commented Oct 28, 2018 • edited

Gio76 commented Oct 28, 2018

pablolassalle commented Oct 28, 2018

arsaboo commented Oct 28, 2018

Devqon commented Oct 28, 2018

kennedyshead commented Oct 28, 2018

PDekker commented Oct 28, 2018

tmonck commented Oct 28, 2018 • edited

tmonck commented Oct 28, 2018

Gio76 commented Oct 29, 2018

Hackashaq666 commented Oct 29, 2018

kennedyshead commented Oct 29, 2018

kennedyshead commented Oct 29, 2018

Gio76 commented Oct 29, 2018 • edited

kennedyshead commented Oct 29, 2018 • edited

Gio76 commented Oct 29, 2018

Devqon commented Oct 29, 2018

kennedyshead commented Oct 29, 2018

kennedyshead commented Oct 29, 2018

Answer-1 commented Oct 14, 2019

byackee commented Oct 15, 2019

xchwarze commented Oct 17, 2019 • edited

AlexeyUkolov commented Oct 17, 2019 • edited

xchwarze commented Oct 17, 2019

AlexeyUkolov commented Oct 18, 2019 • edited

xchwarze commented Oct 20, 2019

n3snah commented Oct 21, 2019

arsaboo commented Oct 21, 2019

xchwarze commented Oct 21, 2019

AlexeyUkolov commented Oct 21, 2019

xchwarze commented Oct 21, 2019

lukasz-galos-ps commented Oct 21, 2019

lukasz-galos-ps commented Oct 22, 2019

n3snah commented Nov 1, 2019

maximosm commented Dec 16, 2019

xchwarze commented Dec 16, 2019

maximosm commented Dec 16, 2019 • edited

hjm79 commented Dec 17, 2019

AlexeyUkolov commented Dec 17, 2019 • edited

hjm79 commented Dec 17, 2019

AlexeyUkolov commented Dec 17, 2019 • edited

xchwarze commented Dec 17, 2019

tulindo commented Mar 12, 2020 • edited

escoand commented Mar 12, 2020

arsaboo commented Mar 12, 2020

This comment has been minimized.

Hackashaq666 commented Oct 26, 2018 •

edited

RRacer commented Oct 27, 2018 •

edited

Gio76 commented Oct 28, 2018 •

edited

Tacchi1983 commented Oct 28, 2018 •

edited

Tacchi1983 commented Oct 28, 2018 •

edited

tmonck commented Oct 28, 2018 •

edited

Gio76 commented Oct 29, 2018 •

edited

kennedyshead commented Oct 29, 2018 •

edited

xchwarze commented Oct 17, 2019 •

edited

AlexeyUkolov commented Oct 17, 2019 •

edited

AlexeyUkolov commented Oct 18, 2019 •

edited

maximosm commented Dec 16, 2019 •

edited

AlexeyUkolov commented Dec 17, 2019 •

edited

AlexeyUkolov commented Dec 17, 2019 •

edited

tulindo commented Mar 12, 2020 •

edited