Here’s a step by step for setting this up on a Raspberry Pi running Raspian / OSMC. Note that you will need to prefix most of these commands with “sudo” if you are not already running as the root user or a user with the appropriate access level.

Create config file for homebridge at /var/homebridge/config.json using the config.json_.txt sample attached
Create a file at /etc/default/homebridge from attached homebridge.txt
Create a file at /etc/systemd/system from attached homebridge.service.txt

You should now be able to open the “Home” app on iOS 10 and find and pair the “Homebridge” accessory. From there, you can access all of the LightwaveRF accessories, assign them to rooms, create automation tasks and of course, interface with it via Siri.

Jamie, Thanks for all this. I’d come to the same conclusions, but not had any joy in getting my wifi link to recognise the pairing packet from the box I’d set up to drive all this.

Are there special tricks I should know? Does the MAC address of the wifi link need to go into the bridge section? (as far as I could tell, this was an internal thing for Homebridge, rather than the homebridge-to-lightwaverf communications)?

Or is there a special trick to getting the wifi link to accept the pairing packet? I’ve tried sending the packet within seconds of the link turning on (before it settled into ‘normal’ mode), as well as after it’s been operational a while. I’ve tried clicking the wifi link pairing button then issuing the packet, again to no avail. Nothing from Homebridge seems to make it to the device (it may well have paired invisibly, but as far as I can tell, it hasn’t – and I’ve tried pretty much every open system offering lightwaverf integration out of the box, including the one that makes it take 13 hours to get a kettle to boil)

Hey. You need to register the MAC address of the Pi (not Homebridge) and you can do this using nc and those details are on the homebridge-lightwaverf node project page. I think I had to apt-get install something to get a more recent netcat version before I could do it

Do you have the new WifiLink without the LCD screen? With the older one a registration message appears so it’s more obvious what’s happening. Maybe the limit of devices has been reached for registering with the WifiLink? In the old one you can deregister all devices.

How about sending a command like 100,!R1D1F1 to turn Room 1 Device 1 on and see if the Pi is talking to the WifiLink.

I tried the reset button on the back before issuing the commands. Nada. I believe they’ve magically changed the API too, so the R1 needs to be taken from the web interface – my first room has an ID of 91114 (I hope their security is good!)

I’m going to look into hard resetting everything and driving the initial pairing from the Ubuntu box (rather than any devices). I’m glad these things can be driven locally with a little UDP packet, but they don’t make it easy!

Thanks for all your suggestions though, Jamie – I can at least be sure I’m not doing anything obviously wrong. It means I must be doing something outrageously stupid somewhere… but that’s a fight for tomorrow!

I’ve heard others saying about a new API, but I’ve not seen anything new – the official LightwaveRF app on the iPhone still sends the original UDP message types – I “sniffed” them with Wireshark to work out what they were.

I tried the reset button on the back before issuing the commands. Nada. I believe they’ve magically changed the API too, so the R1 needs to be taken from the web interface – my first room has an ID of 91114 (I hope their security is good!)

I’m going to look into hard resetting everything and driving the initial pairing from the Ubuntu box (rather than any devices). I’m glad these things can be driven locally with a little UDP packet, but they don’t make it easy!

Thanks for all your suggestions though, Jamie – I can at least be sure I’m not doing anything obviously wrong. It means I must be doing something outrageously stupid somewhere… but that’s a fight for tomorrow!

——————————————————————————————–

I’m having trouble controlling the Wifi Link with UDP packets which means that the HomeBridge plugin isn’t working.

I can see everybody referencing R1D1 etc… but as above it looks as though on the manager.lightwaverf.com site my device and room IDs are more like device_id=”31186″ – does that sound right?

I’ve sent the registration packet and accepted it on my wifi link but every command I send after that does nothing whatsoever.