Sorry, only now get to continue.

That means I send

POST /api/v1/remote/id/trigger HTTP/1.1

right?

What does the "id" look like for HDMI1 on a Theater? If you can give an example that would help me a lot.

Thanks!

Marc

Sorry for the late reply, here is an example of switching HDMI input.

from GET /api/v1/remote you get a key, value map of RemoteMenuItem values. An example of this is:

{"0cce0072-55fd-4abb-b5a2-aa4cad606f53": {"actionList": [      {"contentId":"tv://hdmi_3","type":"triggerContent"      }    ],"available":true,"content": {"categories": ["hdmi"      ],"contentUri":"tv://hdmi_3","label":"HDMI C","source": {"value":"tv"      }    },"disabled":false,"dynamicList":"none","fixed":false,"id":"0cce0072-55fd-4abb-b5a2-aa4cad606f53","label":"HDMI C","parentMenuItemId":"1a873cf6-0881-43f4-8ec7-4ff9cb9b7cf2"  },}

To trigger this item (HDMI C / HDMI 3) I would use thePOST /api/v1/remote/{id}/trigger with the id being the desired sources key, so in this case it would bePOST /api/v1/remote/0cce0072-55fd-4abb-b5a2-aa4cad606f53/trigger or with curl:

curl --request POST \  --url http://0.0.0.0/api/v1/remote/0cce0072-55fd-4abb-b5a2-aa4cad606f53/trigger \  --header'Accept: application/json' \  --header'Content-Type: application/json'

Don't hesitate for any clarifications or other questions.

Kind regards.