Magically the "tvinput.dtv" section of the ECP has been removed, and deep linking using the "ch=X" argument with launch/tvinput.dtv no longer works. Is anyone else having this issue?
If this change was done on purpose, this has to be the most stupid ******* change. We need that function back, and I want to know how to disable Roku's stupid weekly updates. Awful situation.
I dug a little more, and it looks like the parameter name changed as part of some re-implementation work.
I've found this string should work with both the old and new invocations:
/launch/tvinput.dtv?chan=18.1&lcn=18.1&ch=18.1
We just bought a new Philips 65” Roku tv and the “…/launch/tvinput.dtv?chan=10.1” does not work in the manner in which you want it to on the new tv, but works great on our 2 older Roku tv’s.
When you call a particular channel for example “…/launch/tvinput.dtv?chan=10.1”, it will launch dtv and the last viewed channel but the channel you called for. UGH.
The shortcut for example “…/launch/28”, Pandora or any other app, works as expected on the new tv.
Hopefully someone finds a solution…
To enable full ECP functionality, go to Settings / System / Advanced system settings / Control by mobile apps, and change the setting from "Limited" to "Enabled". This was a change made in Roku OS 14.1 to make devices more secure by default.
@RokuBen I already had this setting set to "Enabled", however, the "ch=X" parameter still doesn't work. Even the Deep Linking Tester channel on the TV itself can't use this parameter correctly.
OK, I can confirm that launch string isn't working. I'll file an internal issue with the team that works on live TV.
@RokuBen Thank you! And as I stated in my original post, that string has also been removed from the online ECP documentation (which is why this change felt like it was on purpose).
I have made the comment before that the ECP documentation does not keep everything the ECP is capable of. If you are making internal issue requests, it would be great for someone to actually update that dev page with all ECP functions.
I dug a little more, and it looks like the parameter name changed as part of some re-implementation work.
I've found this string should work with both the old and new invocations:
/launch/tvinput.dtv?chan=18.1&lcn=18.1&ch=18.1
Okay, I will try this shortly. But just to be clear, the string requires all three parameters: "chan", "lcn", and "ch"?
Update: Never mind, I understand. Depending on the versions the TV has, it will respond to one of the parameters when passed together in a single string. Can you request them add this back to the documentation, and/or is there an easy way for developers to see a list of the Deep Links available in a channel?
The deep link parameters are private to each specific channel, so I can't publish any information outside of tuner.
Yep, that was the almost the first parameter changed after turning it on. Like I said, every other parameter works just fine except calling a particular tv channel.