Regarding the device_id, the How To is quite clear to take the part of the URL. So I have done it correctly, to the best of my knowledge.
Regarding the update_method, I was not aware, that this needs updating, as there is no hint in the How To and also the Read Me does not state clearly what this option is for. Anyways I tried setting it, as you can see in my settup now.
Which leaves the api_key. Visiting the page again will not let me evaluate the key I have copied, but I have enabled the following settings:
Access to the currently selected channel is available. So the connection in general seem to be established. So I guess you are right, that potentially some rights have not been correctly enabled. Would you be able to point out what is missing? Whilst setting up, I checked every box appart from location services.
@T1ppes You don’t need to set the update method to “smartthings”, that’s just for what determines the on / off state of the TV.
You say that “access to the currently selected channel is available”, do you mean in the component or on the SmartThings site? The only way that this component won’t connect to SmartThings is if the API key and/or device ID are not set to the correct values.
Within the component the channel is reported. In my Example above you can see ZDF HD.
The source however is not specified with TV only, or HDMI1, when I switch to my Shield. This always stays as TV/HDMI
Since I got the new TV the Shield is no longer waking up on selection if HDMI, although CEC Settings are on on both devices. I would like to create a home assistant automation to power the Shield, when TV is set to HDMI1.
In this example I use “Manual” for PC, because “Manual” is a google assistant accepted word, so I can use “Hey Google, change input source to Manual” to change to the PC. You could use this keyword also for the Shield if u are a google assistant user.
Tell me if this fixes ur issue.
You can also set channel_list in ur config to switch directly to channels from the HA UI or through voice assistants.
I would remove show_channel_number unless u need it for something in particular.
I was always curious what you meant by this @jaruba. In my language I have not experienced any limitation at all in the names I can use for input source changes. Any TV channel name is also accepted as well as for any other input source. Could it be this is based on an outdated experience or do you still experience this today?
It’s quite possible, when I initially tested this voice command for the feature there was a page on Google Developers explaining that only whitelisted words will work with “change input source”, tested with “PC” and it didn’t work.
I had to use the Wayback Machine to check an older page of the one from Google Developers to see a small list of accepted words and a link to a GitHub repo where they said u can request more words. (the link was broken though)
It may be that they allow any word now, and when I tested they were in a transitioning period to deprecating the whitelist. I’ll test with “PC” again to see if it works now.
Regarding the issue that @T1ppes had, it makes sense to use '{"TV":"ST_TV","HDMI1":"ST_HDMI1","HDMI2":"ST_HDMI2","HDMI3":"ST_HDMI3"}' as the default source_list if SmartThings is enabled.
Still fighting with this. Using the Samsung app I can controll every TV perfectly but using Home Assistant it does work properly on any of my TV’s. Could the use of Nabu Casu be an issue? I have read the documentation over and over again but I can’t find any issues in my config.
No, Samsung just has a terrible implementation which makes third party work more difficult. I have tried all custom versions and the official integration on different Samsung models. They’re all hit or miss based on the model. Either they don’t turn on, or don’t turn off, or certain commands don’t work. Or the off state isn’t reported correctly.
It’s a shame, but I don’t think anyone can create a ‘one solution for all’ thing for Samsung TV’s. Even the smartphone apps of Samsung (official) suddenly don’t detect one of my TV’s.
I’m thinking of just using my Harmony hub for commands and use a BlitzWolf Zigbee power plug (that has a consumption meter) to see if the TV is on/off. Create a binary sensor template that is on/off based on the wattage. Then just create a universal media player and do it that way.
Shame to hear you are still struggling… I just wanted you to know that I experienced the same thing you did where in Smartthings my device was listed but did not show any states… It seemed to at that moment the component in hass also had issues getting the correct channel name from smartthings and to control via smartthings. Now to fix it what I did was to change the TV from ‘placeholder’ type to ‘Samsung OCF TV’ and afterwards it worked just fine for me again, displaying a list of detailed states for my TV (including volume, channel name, on/off state and more).
I believe you had tried this before, but for me that worked and helped me fix it… Just wanted to share my experience with the issue you observed!
Thank you for this. In fact, I did not try the ’Samsung OCF TV’ but used the one in top of that list, ‘2016 Samsung Smart TV’. So now I changed it can see exactly what is going on. The first thing I notice is I can see the correct code for KPN, fjZ4l75rVu.EVA. That differs from what I see on HA, FjZ4l75rVu.EVA. But testing on a 2019 TV does not give me any changes, lol. But I will try this on my other TV and will keep you posted!
Hi. I am using this version of a Samsung Smart TV integration, not sure if this is a fork or yours is the fork but all my HDMI inputs work, and all my apps work apart from Netflix. It will let me select it but will not actually change the tv to it?
So the good news is: Switching to the KPN app works! The ID is fjZ4l75rVu.EVA although it showed up as FjZ4l75rVu.EVA in HA.
The bad news is: I got 3 TV’s and none of them work for the full 100%. On the one that works best, I need to press OK on my remote over and over again to Allow Home Assistant to control it. And I can’t turn it off using HA. But for the rest, it seems to work!
The second is a brand new one, 2019. I can switch to TV of HDMI, but not to Netflix or the KPN app. Volume with + and - work too, but since a Sonos Beam is connected, I can’t use the bar. On and off works fine.
The third one does not have the KPN app so that’s not tested. Off is also an issue and also the volume bar does not work because Sonos is connected.
So, I can live with it of course, but I realy hope that some day all will work for the full 100%.
Firstly fantastic work on this integration! It’s all working perfectly on my Q8.
My question is…
Is there a way to be able to turn the TV on (from power off) directly into Ambient mode? (Like pressing the ambient button on the remote when the TV is off)
My current workaround is to send a magic packet to wake the TV followed by a delay then the KEY_AMBIENT. This all works but you see a programme or whatever channel was last watched for a second as it turns on to a channel before ambient activates. Have tried getting the delay just right but no luck.
Basically it’s to link it to my lighting schedule so as it gets dark the TV comes into ambient mode but don’t really want to see the split second bit of content.
