A simple curl example:
curl -v -d '' "http://your-ip:8060/keypress/home"
Output
* Trying n.n.n.n:8060...
* Connected to n.n.n.n (n.n.n.n) port 8060
> POST /keypress/home HTTP/1.1
> Host: n.n.n.n:8060
> User-Agent: curl/8.4.0
> Accept: */*
> Content-Length: 2
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 401 Unauthorized
< Server: Roku/12.5.5 UPnP/1.0 Roku/12.5.5
< Content-Length: 0
<
* Connection #0 to host n.n.n.n left intact
Same problem here. any post commands respond with 401 unauthorized. Same experience where it worked just find until March 27th.
I rely on this functionality and the ability to control via API is essential to me and one of the reasons why i purchased this product.
Here are the system details in case it helps
Is it possible the certificate expired on the server on the Roku?
I have the same problem but it is only on one of my rokus, a roku tv that I have set up for my mom with dementia. All of the launch+deep_links work but 401 on the normal keypress commands.
curl -d '' --write-out "%{http_code}\n" -X POST http://n.n.n.n:8060/launch/tvinput.dtv?ch=632
200
curl -d '' --write-out "%{http_code}\n" -X POST http://n.n.n.n:8060/keypress/VolumeUp
401
Model 65R6ASR
Software Version 12.5.0 Build 5101
Just FYI, we have had reports of our customers having a similar issue with their Roku players using our driver that issues ECP commands.
Our tech support has found that issuing a factory reset of the player seems to fix the issue.
Something you all could try.
12 different sites that we reset yesterday, yes on Easter, have all now succumbed to this issue. Waste your time if you must, but the reset devices only work ~24 hours from our experience. Thats a lot of typing in passwords for only a day of proper operation.
Forgot to mention we also recommend disabling automatic updates after factory reset. Don't know if that is why it's reoccurring...
Turning off auto-updates isn't something supported by the existing menu structure on a Roku Ultra. I can get into the secret menus obviously but dont see it in there either. If someone has a approved way to accomplish this and it fixes the issue I am all ears to prevent mass customer removal of Rokus.
Wonder if this is related to an issue I'm facing with 3rd party hub remote
Timelines seem to match, but I also got no support there.
They likely use the API that stopped working. Can you launch Disney+, Hulu or other channels, but not navigate?