search

bitfocus / companion-module-roku-tv

This module will control Roku TVs using the Roku ECP protocol.
MIT License
3 stars 1 forks source link

TCL Roku TV Connection Fails? Cannot get roku crrrent app error? #18

Open Jibun-no-Kage opened 1 week ago

Jibun-no-Kage commented 1 week ago

TCL Roku TV Connection Fails? Cannot get roku crrrent app error? If the TV is OFF, I get this error consistently. If I turn the TV ON via the remote, companion roku TV module connects instantly, and works fine from that point on. But the initial connection NEVER is successful if the TV is OFF initially.

What is trying to get the current app state? I have NOT enabled feedback or set any triggers. Just added the module and attempting to use it. The logging is not much help seems like the module really does not report anything. Any help appreciated.

Jibun-no-Kage commented 1 week ago

Looking at the source code... What I am seeing is on any initial connection, the following error is always being returned "TCL Roku TV Connection Fails? Cannot get roku crrrent app error?"

How can the current app information be returned, when initial power on is done, but the connection logic never seems to wait for the initial state of the device to be gathered?

Given using the remote to power ON, then the module connection routine always works, this seems to be a timing issue or a sequence issue.

The TCL ROKU TVs I have are, I believe 2022 models, 85in. I can definitely turn the TVs ON and OFF without issue by using curl and direct HTTP GET/POST commands, so I can get around using this module.

The more I use BitCompanion, the more I find that modules I need seem to be created and then forgotten? Too bad, because the StreamDesk is a great product.

josephdadams commented 6 days ago

I updated the module a month ago so I would hardly say it’s “forgotten”. You need to be more careful with your words.

Jibun-no-Kage commented 5 days ago

That was general comment... There are many modules that are not current. My comment was not directed explicitly at your module but the general state of the situation. Maybe you should consider not being personally triggered.

But specific to your module, I am still experiencing the failure of the TV to turn on via the module, when it has been powered off more than a few minutes. I loaded your module a couple of weeks ago, so I believe I have the latest, current module available. The current module is failing to connect from a power down cold state, i.e. longer than a few minutes. But once I use the remote, the connection is fast and works for power on or off, etc.

Interesting is that many LG TVs have this seemly same scenario, where you have to issue a WOL (wake on LAN) packet to the given TV, and only then does it power on, after a considerable powered off duration. The actual WebOS has this design quirk, this is a design issue not a bug.

Moreover, when the WOL is issued, it often takes the LG TVs as long as 90 seconds until the network interface is FULLY functional, query of network status may return good, online, after less than 90 seconds, but call to get the current 'app' state fails, until about 90 seconds.

I mention this, only because the resulting behavior is similar at a functional level between TCL Roku and LG WebOS based TVs. Does appear to be documented (that I could find) if there is common code base used? Thought this might provide you with some context. Roku OS is called a Smart TV OS, but so is the LG WebOS implementation.

josephdadams commented 5 days ago

Well you also said BitCompanion and StreamDesk, so hard to tell. 😂😂😂