@greengolfer, or you could put the component into debug in your HA config, and set the config on this component to get the applist automatically, that will put all the app info id’s in the HA log.
that would probably work, but the tv would need to be turned on when u restart HA, and getting the app list automatically doesn’t work on all TVs (many users complained about it in the past)
it’s worth a try, though
OK. I’ll try that and report back.
Thanks for the tip.
GV
i tried last version by jaruba a few day ago
why send_key is so slow now ? it is impossible to normal use with such speed
can i modify new version for faster speed ?
hello
Anyone noticed that entity representing the TV turns on and off on its own?
Look at times during night.
in this particular case TV was turned on only between 9:04PM and 1:39AM. Was turned on and off using remote control.
My configuration:
media_player:
- platform: samsungtv_tizen
host: "192.168.0.103"
broadcast_address: "192.168.0.255"
port: 8002
mac: "B8:BC:XX:XX:XX:XX"
app_list: '{"Netflix": "11101200001"}'
My TV model is: QE65Q70
Is there a way to “hold” key presses?
That would be super useful.
Any dedicated key to select Optical output for sound?
@pXius not yet, there is a way to add support for holding key presses, but I haven’t had time to implement it
@chris669 All the keys i know of are here: https://github.com/jaruba/ha-samsungtv-tizen/blob/4a52fbe87a0149904c5c11b816b47e86d80095ea/Key_codes.md
There may be other keys that I don’t know about too though, Samsung isn’t very transparent regarding such things…
you mean this whole thread? 290posts? can you point me closer to something?
@maxym sorry, i forgot to add the link, here you go: https://github.com/jaruba/ha-samsungtv-tizen/issues/77
thank you. However I’m not using SmartThings with the integration. I will check it anyway
@maxym alternatively, you can try one of the other update methods (set with update_method in your config), the possible values are: “ping”, “websockets” and “smartthings” (“ping” is the default)
I am having trouble getting this integration to connect to my TV. Are there logs anywhere that might shed some light on what is going wrong? I simply put my IP, name and token and when I click submit it says it cant connect. I have my TV setup and working in the SmartThings app and I can ping the ip.
I had this integration working a while back so it was connected to my TV and one point, but I had to set everything up again and IP addresses changed. I deleted the previous integration and the device in HA so it should be starting from scratch.
UPDATE: I had my TV on a different subnet and after switching it back to the same subnet as HA it was picked up right away. I had removed all firewall rules blocking communication between the subnets, but it still didn’t work. I’m not sure why, but it seems like they need to be on the same subnet. @SimplyGardner - I see you had a similar issue. Did you ever get it working with your TV on a different subnet?
@jaruba - Is there anyway to speed up the detection of the TV turning off. I have automations setup to turn light’s on when the TV turns off but it takes 10+ seconds for HA to know the TV has turned off?
I have tried ping & websockets but they detect at about the same rate.
Hey. Nope, I could not get it to work across different subnets. It had to be on the same which made me give up using it. I do not want my tv on my main subnet.
Hello,
I guess it’s the keypress delay you can find here:
You could open a feature request to ask to have this as an option in the configuration.yaml
Hello @jaruba
Do you know if anybody ever tried to directly change the samsungtv component in the core repo instead of making custom components?
I wonder why nobody ever updated it instead 
I’ve avoided adding my Samsung TV to HA for a long time.
For someone just adding now, would people recommend the jaruba or ollo69 custom component? Why?