Is anyone else having issues with the roku not accepting Channel Commands? Im trying to setup a rule that turns the television on to a certain channel. Everything is working except for the channel command.
groovy.lang.MissingMethodException: No signature of method: user_driver_apwelsh_Roku_TV_710.setChannel() is applicable for argument types: (java.lang.String) values: [8.1]
Possible solutions: setChannel(java.lang.Number) on line 6424 (method setChannel)
Ive adjust this to a number. The error is gone but nothing is happening. Even just putting the number into the device handler doesnt produce any change.
The roku devices have changed the active channel from AntennaInput to Live TV Input. This change prevented my code from sending the key presses. But there are other functional changes in the Live TV app that are also breaking the ability to tune into a specific channel. I am looking into it.
I also removed the useless quiter command, but that a typo (it was supposed to be quieter, but instead of quieter and louder, I went a different route with volume up/down +10 instead. Since the quiter function was never implemented, I removed it.
When you are in the Live TV app, can change channels with the updated code, but the system is far less forgiving. Since I cannot query if the guide is visible or not, I have to assume the Roku is in a state that is can receive channel number key-presses.
Anyone else seeing messages like these in Logs? dev:2892025-09-24 09:52:21.685 PM warn The device appears to be powered off. Please make sure Fast-Start is enabled on your Roku.
dev:2892025-09-24 09:52:21.680 PM error Exception thrown in call to getInstalledApps: groovyx.net.http.HttpResponseException: status code: 403, reason phrase: Forbidden
FWIW, "Fast Start" has always been enabled on my Roku TV (dev:289). Running 2.4.3.latest firmware on my C7 and v1.3.0 of Armand's Roku Connect app.
I understand you suspect there is a problem in the Roku app. There are three sources to this problem that I am aware of.
Changed IP Address
If the IP Address was changed, you will have to make sure the TV is assigned a persistent IP address so this doesn't happen. If you go to the Roku Integration app, and you turn on Auto Detect IP changes of Roku Devices, then the app will enable a feature to kick off an SSDP subscription solicitation every time this error condition occurs. If it receives an SSDP response for the failed devices, and the IP Address has changed, it will update the IP address associated with the Roku device, and the error will clear itself.
If the device frequently gets a new IP address then this is less than practical, and you really should consider a router that supports HDCP reservations, and reserve to persistent IP for the roku -- OR -- you can should manually assign the TV a static IP Address that is outside the range of the router's DHCP server, which mean using manual IP addresses settings on the roku.
Fast Start is disabled
There have been many reports to me, and I have experienced it myself, where the Fast Start features was disabled, and the TV powers off. this happens with certain roku updates, so even if you have turned it on, and checked more than once, it may be worth checking one more time.
Slow Roku API
The message happens generically when the hubitat device driver sends out an HTTP query to the Roku device and does not receive a timely response. This can happen if the Roku device is over worked, or if the network is overly congested. For this, you can change the default Communication Timeout for the Roku device in the hubitat driver instance of the roku that is having problems. Mine are set to 10 seconds, but try increasing to 20 or 30 seconds and see what happens, but this should be if the other two scenarios are not the problem.
Note that 'DC...-13842' corresponds to the (unused) 'Fandango At Home' switch subcomponent. I may try removing that from the mix. (Edit: Tried that. New, similar error now gets thrown for 'Hulu'.)
As for the things you kindly mentioned above, all of them check out (fixed/reserved IP, Fast Start definitely enabled, etc.).
Maybe it's time I do something more drastic, like remove the device from the app (Edit: Yes, this seems to have solved the problem; at least the app no longer throws above error), or reinstall Roku Connect from scratch.
That is very interesting. Can you check the Roku settings.system, advanced:
Make sure device connect is enabled
Make sure control by mobile apps, network access is set to enabled, permissive or limited. Limited may be too restrictive now and you may need to try permissive or enabled.