I’ve got a Mobotix T24 as door station.
In OH2, I’ve configure it to send a TCP command to launch a DingDong playsound command in openHAB.Today, I don’t know how to integrate it with OH3 … So I also requesting the TCP binding
Thanks for sharing. I’ve checked my configuration against yours and it looks the same but it’s not working for me.
The inbound is fine; if I trigger a command from a PuTTY connection, NodeRed and OpenHAB are getting the response but for the life of me, I can’t get a change in the outbound item to send the string to the device, even though the debug message shows what the TCP node should have received.
I noticed that using your method, NodeRed creates two connections to the device, one for the Tx and one for the Rx. as I’ve limited my device to two connections (for OpenHAB and PuTTY), it was a problem so I’m using the 2-way TCP node. I also tried separating the inbound and outbound items but still no luck.
Hopefully with that incentive we’ll find a friendly developer who’s knowledgeable enough and willing to help with such binding (I’d do it myself if I know how unfortunately I don’t know how).
As it appears to me: help is on its way.
As far as I understand there’s a chance it might be included as of Rel 3.1.1 milestone - see: TCP Binding for OH3
for detail.
As others this is the remaining functionality stopping progress to OH3
Ive added the jar files, created a thing with the binding but cannot get a udp rely to work. This was a simple task with OH2 and so useful.
Is it possible some further guidance could be provided.
OH2
You want to use the binding with OH3 ?
Where did you get the jar file from ? I am not aware of that there is a TCP binding for OH3 at least it is not available in the documentation.
Have you not used channels with Items before? You would configure the channel in the Thing definition, as you seem to have already done, and then if you’re not using the UI tolink then you would give the target channel’s UID for the Item Switch Solar_switch "wall plug" { channel = "tcpudp:client:91607768db:thisrelay" }
or something like
channels not really yet, as all still in OH2.5 which was migrated from OH1 originally.
I think the issue lies earlier on as the thing and channel are not initialized.
The back up plan is the exec binding via bash script.
in things it doesnt say online for the binding.
I use lan udp relays for all sorts of things from boiler control to alarms, so it is essential for my OH setup. If it cant be done right now, will stay with OH2 for a while