The official answer is it’s not supported, there are code samples in the threads, feel free to try them out. At best it will be one way like TCP, so you won’t get a response back. I don’t know of any actual working UDP device types, but that doesn’t mean it’s not possible, it just means it hasnt been done… yet.
And that’s exactly the point of this thread. I was asking if anyone has the answer. I expect it to be possible (although happy to be proven wrong), just not documented or supported.
I’ve tried some of the code snippets, as per the code in my original question but to no avail.
I’m stuck, and without some input from someone in the know I’m probably going to have to knock up a web service as a middle man.
Thanks @pstuart - I’m trying to have the fewest dependencies possible.
I’ve written a simple REST api which sends out UDP and added a DeviceType to call my local lan API. It all works, but it’s stuff I’d much rather do on the ST unit directly.
I have some small amount of experience here that may help some of you. LWRF Remote servers are inconsistent to say the least. Local control is preferred at all times even going so far to setup a VPN rather than relying on the LWRF server.
Some years ago I played with Raspberry Pi SBCs, linux and this : http://www.tinkerfailure.com/lightwaverf-php-script/ along with Tasker to enable a voice activated Smart Home thing, you’ve no doubt have seen on Youtube. This script will act as the perfect http to UDP ‘bridge’ and can simply be run on a Raspberry Pi Zero costing no more than £10 and using hardly any electricity.
Having said that, the lights and power sockets are one way so if ST can send UDP, that’ll do for now.