Bus-Profi Forum

Hallo Bus-Profis,

als ich vor kurzem mein DOMIQ Base auf Version 1.8.5 aktualisiert habe, musste ich feststellen, dass ich Base nicht mehr mit TCP-Kommandos auf Port 4224 fernsteuern kann.
Vorher hat z.B. folgendes Kommando funktioniert:
echo "LCN.sendkey.0.5.A1=hit" | nc 192.168.0.216 4224

Seit dem Update reagiert Base überhaupt nicht mehr darauf. Per Telnet funktioniert das Kommando.
Gibt es hier evtl. einen Trick oder hat sich beim Zugriff auf den Port 4224 seit dem Update etwas verändert?

Danke und viele Grüße
Andreas

Hello Andreas, in the latest update we didn't change anything regarding telnet port no. 4224, so maybe problem is somewhere else?:)

Thank you very much for your response.

It's really weird. I'm not able to send keys any more via netcat.
The TCP connection with netcat is successful but DOMIQ never reacts to the commands or delivers answers to requests.

I am able to connect via telnet on port 4242 and I can send the commands without problems. Everything is fine using telnet.
I've compared the TCP packages between netcat and telnet and there seem to be some minor differences. It seems that these differences are the cause that DOMIQ does not respond any more to netcat commands. With an older firmware version of DOMIQ this was no problem.

Can anyone confirm that he can send a key using netcat?
For example: echo "LCN.sendkey.0.5.A1=hit" | nc 192.168.0.XXX 4224

Thank you very much
Andreas

For sure you can send it in this way:
1. nc IP PORT
2. command

For example, if your Base has the following IP: 192.168.10.10 and your command is LCN.output.0.10=100, then use those commands:
nc 192.168.10.10 4224 and then LCN.output.0.10=100

I'm experience the exact same issue.. I'm pretty sure some weeks (month?) ago this worked, but when I try it, the variable isn't set

$ echo "VAR.test=1" | nc 192.168.50.50 4224

While this still works fine:

$ nc 192.168.50.50 4224
VAR.test=1

However, the second is no solution for my, as I need to set and get channels form a shell script.
Any ideas? Might the line break be the problem?

regards
tobias

wired. this seems to work:

$ (echo 'VAR.test=1'; sleep 1) | nc 192.168.50.50 4224

This would mean nc closes the connection too early. Anyone any idea why?

OK, I checked this and this is a problem related to changes we made in handling TCP connections. This issue is now resolved and fix will be available in the next update.

DOMIQ-Support hat geschrieben:OK, I checked this and this is a problem related to changes we made in handling TCP connections. This issue is now resolved and fix will be available in the next update.

Awesome. Thanks for your support.