Has anyone done this?? The API says Ascii, Hex, Base64, RTF8 with a 128 character limit.? All the commands I have are pronto hex.
For testing, I'm using known working TV commands for a sharp I have at my house.
?
But if I send?
{
? ? "Device": {
? ? ? ? "ControlPorts": {
? ? ? ? ? ? "Infrared": {
? ? ? ? ? ? ? ? "Port1": {
? ? ? ? ? ? ? ? ? ? "TransmitData": "0000 006D 0000 0020 000A 0046 000A 001E 000A 001E 000A 001E 000A 0046 000A 0046 000A 0046 000A 001E 000A 0046 000A 001E 000A 001E 000A 0046 000A 001E 000A 0046 000A 001E 000A 0679 000A 0046 000A 001E 000A 001E 000A 001E 000A 0046 000A 001E 000A 001E 000A 0046 000A 001E 000A 0046 000A 0046 000A 001E 000A 0046 000A 001E 000A 0046 000A 0679",
? ? ? ? ? ? ? ? ? ? "TransmitDataFormat": "Hex"
? ? ? ? ? ? ? ? }
? ? ? ? ? ? }
? ? ? ? }
? ? }
}
?
the IR doesn't flash or do anything. If I enter the wrong data (say remove the spaces so it is one long hex string per TB recommendation), then the IR does really long pulses forever until the IR driver experiences a buffer overrun and the NVX crashes and reboots.
?
So I don't know what exactly Crestron is looking for in the TransmitData field.
