Help with Text over TCP

General
1

Hello All,

I’ve had my R3 for a couple days now and it’s been exciting to discover how much potential it has - and it looks great too!

I’m trying to move away from my Push Controls (rebranded bitwise controller here in Australia which has lost all support) and have question about sending TCP commands.

I’ve attached an image from the Push Controls setup software showing what command I’m trying to send for reference:

UnfoldCirc
UnfoldCirc1920×1137 130 KB

Could someone give me a hand in translating this into a Text over TCP string - one glaring thing I see that is not right is there is no option to send the correct terminator in the advanced setup for kennymc-c intergration.

I also noticed that for this Wyrestorm Matrix unit in the Push Controls software I have to open a socket to the unit, then send the command as shown above, then close the socket. Casting my memory back when configuring the opening/closing of sockets was needed for the commands to go through successfully - is there anything that does this sort of things also?

Thanks - any help would be greatly appreciated - a little bit out of my depth but once I get it working the rest of my bespoke IP devices should be easy to configure (I hope!).

Cheers

2

I use Text over TCP quite a bit. Try:
192.168.0.224:23,“SET SW hdmiin3 out1\r\n”

A really nice thing is the custom entity where you can define your matrix as an entity with all commands like this:

Matrix:
  Features:
    'Off':
      Type: tcp-text
      Parameter:
        address: 192.168.0.224:23
        text: "%1POWR 0\r"

    'On':
      Parameter:
        address: 192.168.0.224:23
        text: "%1POWR 1\r"
  Simple Commands:
    IN3OUT1:
      Parameter:
        address: 192.168.0.224:23
        text: "SET SW hdmiin3 out1\r\n"

You must add your on off and the other functions in this style. If it worked you will have a new entity called Matrix with IN3OU1 as a command.

Ralf

3

Thanks for your reply HarmonyFan,

Unfortunately it still doesn’t work. I’ve tried copying you line into a button to test in the web configurator and no go.

One thing that will keep me busy though - Can you explain what to do with the list of code you have provided? where/how do I create a new intergration with that code? I’ve done a quick google but can’t see anything about this.

Thanks in advance

4

Not an integration you can create an entity/device with the request integration but for that you need to configure 1 command with text over TCP.

5

Can you try:
192.168.0.224:23, "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 33 20 6F 75 74 31 0D 0A"

I converted the text to hex and added the 2 hex terminators at the end as you currently can’t combine text with binary data. If this doesn’t work either I can look into adding hex terminator options.

By default the integration waits for an answer from the client and times out if it doesn’t receive anthing. You can disable the wait for response option in the advanced setup. Then the connection will be closed right after sending the command.

The configuration posted by Ralf can be configured when you choose configure custom entities during the integration setup.

6

Lovely stuff kennymc.c - works like charm.

I think I can roll on from here; and thanks for clarifying about adding the code when installing the intergration - I was pulling what few hairs I have on my head out trying to see where this goes.

Cheers all

7

Hmmm… thought this would work but I get an “"Ooopps”” error when I plug this into the custom entites reconfig.

Background - I installed the custom intergration, then I finished the intergration and then I tried to add the configure custom entities

_vars:
  wyrestorm_ip: 192.168.0.224
  wyrestorm_port: 23

Wyrestorm Matrix 4x4:
  Features:
    'Standby':
      Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 54 41 4E 44 42 59 0D 0A"
    'Wake':
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=57 41 4B 45 0D 0A"
    'Reboot':
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=52 45 42 4F 4F 54 0D 0A"
  Simple Commands:
    OUTPUT1OFF:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 30 20 6F 75 74 31 0D 0A"
    OUTPUT2OFF:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 30 20 6F 75 74 32 0D 0A"
    OUTPUT3OFF:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 30 20 6F 75 74 33 0D 0A"
    OUTPUT4OFF:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 30 20 6F 75 74 34 0D 0A"
    IN1OUT1:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 31 20 6F 75 74 31 0D 0A"
    IN1OUT2:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 31 20 6F 75 74 32 0D 0A"
    IN1OUT3:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 31 20 6F 75 74 33 0D 0A"
    IN1OUT4:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 31 20 6F 75 74 34 0D 0A"
    IN2OUT1:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 32 20 6F 75 74 31 0D 0A"
    IN2OUT2:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 32 20 6F 75 74 32 0D 0A"
    IN2OUT3:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 32 20 6F 75 74 33 0D 0A"
    IN2OUT4:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 32 20 6F 75 74 34 0D 0A"
    IN3OUT1:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 33 20 6F 75 74 31 0D 0A"
    IN3OUT2:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 33 20 6F 75 74 32 0D 0A"
    IN3OUT3:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 33 20 6F 75 74 33 0D 0A"
    IN3OUT4:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 33 20 6F 75 74 34 0D 0A"
    IN4OUT1:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 34 20 6F 75 74 31 0D 0A"
    IN4OUT2:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 34 20 6F 75 74 32 0D 0A"
    IN4OUT3:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 34 20 6F 75 74 33 0D 0A"
    IN4OUT4:
	  Type: tcp-text
      Parameter:
        address: ${wyrestorm_ip}:${wyrestorm_port}
        text: "raw=53 45 54 20 53 57 20 68 64 6D 69 69 6E 34 20 6F 75 74 34 0D 0A"
8

Commands in Features can only be commands that are supported by the remote entity which are on, off and toggle. You find more information in the integration log (settings/development/logs) when an error occurred.

9

Brilliant! - all works accordingly - however now the problem is the matrix doesn’t like having the sockets not being opened - send command - then socket closed.

Unfortunately it is the hardware - I know - but the very last piece of the puzzle is do you know what could be issued as a command to open and close sockets so I can add that to the custom config?

10

The socket/connection is always opened and closed. Is there any error shown when you execute the command or does the matrix itself shows any errors or warnings? Maybe it helps to disable wait for response in the advanced setup if you have errors on the remote.
I also looked at the WyreStorm API and I think why it didn’t work without raw= is the default new line \n (0x0A) terminator thats added automatically to the end of each command by default. If you add \r\n to your command there will be an addiditon \n added to the command. Maybe the matrix doesn’t like this although it’s the same character. You can change the command terminator in the advanced setup. According to the API specs it should also work with just a \n at the end. So you can also try it with only the text and set the command terminator to \n.

11

Hi kennymc.c,

Thanks again with all your help and input. I managed to put a few delays in my sequencing and I’m glad to report everything is working perfectly - actually it is super responsive compared to my previous solution.

Steep learning curve and I’ll need to dig deeper to find out whether the R3 can detect if other rooms are using a shared device through the matrix switch so not to turn off the associated shared devices - but I’m sure it will be implemented in the future even if not able to now.

Wake on lane for a local pc for steam gaming connected to the main sony tv, remote viewing of switching appletv and foxtel stb through the matrix to the same tv - now I just need to setup another page for the cinema room and do it all again - but that’s for another weekend…

Cheers - beer o’clock!