So, I know that my HomeBridge installation communicates directly to the LWRF hub over UDP, and there is a command you can type in Terminal to register the machine to be able to send commands.
On mac/linux, you can use netcat to send a UDP command directly to the box like:
echo -ne “null|001,!R3D1F1” | nc -u -w1 192.168.0.10 9760
The first time you do it, you'll have to click the link button on your LWRF Hub to link the device.
I wonder if this communication could come straight from the SmartThings Hub, which would remove the API delay sending it through the website?
So, I know that my HomeBridge installation communicates directly to the LWRF hub over UDP, and there is a command you can type in Terminal to register the machine to be able to send commands.
On mac/linux, you can use netcat to send a UDP command directly to the box like:
echo -ne “null|001,!R3D1F1” | nc -u -w1 192.168.0.10 9760
The first time you do it, you'll have to click the link button on your LWRF Hub to link the device.
I wonder if this communication could come straight from the SmartThings Hub, which would remove the API delay sending it through the website?