[FEAT] Add textentry to documentation about pylips HOT 8 CLOSED

Hey, I think that this endpoint might be used for search (I remember seeing something like that in the mobile app), but I don't have access to a TV right now to test. I'll take a look in a week or two and will report back.

from pylips.

The text entry endpoint is at POST /input/textentry and the body is:

{"currentstring" : "<the full string you want to pass to the textfield>"}

It looks like it works only if the POST /notifychange API returns that "textentry":"requested".

Looks like it works for textfields where the builtin android keyboard is showing on the TV. There are apps that do not use the standard android keyboard (Netflix, HBO GO), so text input did not work there.

That's what I know for now. I checked this by inspecting the calls the Philips Remote iOS app is doing.

from pylips.

Ok, so I've tested the search in the Phillips mobile app, however, it does not use this endpoint...

I'll try to investigate more, but for now I unfortunately have no clue where the textentry enpoint is used...

from pylips.

Closing the issue for now since I don't have any more ideas to test. Will re-open when there is any new info/ideas available.

from pylips.

@zierka, thank you for sharing this! I'll check if it's indeed the case and will update the docs if it works!

from pylips.

FYI one more useful feature is to send chars one by one to POST /input/key
with the body {"unicode" : "A"}

Works pretty well on input fields for my non-Android TV (2019)

from pylips.

Also you could use POST /input/pointer
with
{
"x": 50,
"y": 50
}
which will move cursor 50 points left and 50 points down

from pylips.

/input/textentry

{
  "currentstring" : "<the full string you want to pass to the textfield>",
  "action_id": "IME_ACTION_SEARCH"
}

This also submits the input.

from pylips.