[BUG] TCP / HTTP remote control no longer working after update to 3.2.1 about companion HOT 2 CLOSED

Are you sending a newline after each TCP command?
I have just checked and the TCP api is working fine for me, tested with telnet on the command line.

And I can't explain the http not working for you, I use that daily without issue. I was using the old api on 3.2.1 until yesterday when I updated the external tool to the new api

from companion.

Yes, I forgot the newline after the TCP command. SORRY MY BAD :( It works now... but the behaviour is somewhat different than version 2.4.2 ! This is what threw me...

If I send a "Location x/x/x DOWN" command in version 3.2.2, I can only tigger the button once. It appears that it ignores subsequent "Down" commands until an "UP" command is sent to that button. This was not the case in 2.4.2. Sending an "UP" command after a "DOWN" command was not necessary. It took a while to figure this out, but now that I know the behaviour I can program things accordingly.

Using the Location x/x/x PRESS work fine as it actually sends both the "DOWN" and "UP" commands at the same time.

After all, this is not really a Bug but a change in behaviour from previous version.

from companion.