TCL Roku TVs will not power up via API commands sent via Ethernet? WiFi is works fine once TV is turned on via remote. Internet works fine once TV is turned on via remote. Wired connectivity works fine once TV is turned on via remote. The issue is, once the TV is turned off, after an extended period of time, typically about 15 minutes or so.
The TCL Roku TVs we have, we have several in our facility, will not respond via the API via Ethernet, either wired or WiFI connection. The TVs just drop off the network, and can not be pinged. This is happening to ALL of the TVs. So this is clearly a software issue. How do we get this fixed?
We need this command and control via Ethernet, because we have a large facility, and we cannot have some one walk around each morning with a stupid remote control turning all of them on. Clearly turning on the TVs work is via the API over Ethernet is a supported function of the device/product, but clearly it needs a software update to address this bug? How do we get this addressed?
LG TVs have the same basic issue, however, their software (WebOS) allows for the send of a "Wake On LAN" packet to the network interface, that wakes the TV up, so that it powers on, and re-initializes the network interface, so in a few seconds the entire TCP/IP stack on the LG TV is functional. LG TVs power down the Ethernet and WiFi connection when in sleep mode or power off... but do respond to the Wake on LAN packet, in appears that TCL Roku TVs need to implement the same solution!
This is NOT a case where our network is dropping the connection, wired or WiFi, I have setup a monitor and pinged ALL of the TVs, and they return a ping until the TCL Roku TV, after turned off (any method) simply STOPS communicating via Ethernet port or WiFi connection, this happens at the TV end. Watching the network traffic, it is the TV that is dropping the connection, NOT our network.
