LightwaveRF lights/switches API

Hey guys,

I was looking at the integrations for LightwaveRF API and it seems its based on the old API.

New API: https://support.lightwaverf.com/hc/en-us/articles/360020665652-Link-Plus-Smart-Series-API-

With the old you only get ‘Assumed State’ which isn’t great.
I’m looking to buy some of these switches, and wondering if anyone else uses them and has the updated api working and working well?
Is there some way to get HA devs to update their integration to work with the new api?

(sorry new to all this home automation and HA)

Don’t have any experience of the new Lightwave switches, but I bought quite a lot of the V1 switches and sockets several years ago and now I’m stuck with them.

The “assumed state” thing is a real issue, to which the only effective solution is never to turn lights on and off manually. You can imagine how that goes down in a large household.

A bigger problem in the long run is what the company calls “cross pairing”. They don’t really explain why it happens, but over time more and more switches turn on and off in error, and re-setting them is quite laborious.

Don’t know if this affects V2 devices as well (the troubleshooting guide suggests it does). I’d try another product.

@Stiltjack have you seen: https://github.com/bigbadblunt/homeassistant-lightwave2

It might help you out.
I’m wondering if anyone else here has any thoughts on this?
Using this git repo or not?

This is really interesting - though I would have to upgrade my hub. Can you confirm that gen1 devices really do work with the gen2 hub? No hidden caveats?

Also, does the gen2 hub make any difference to the cross pairing problem?

I cannot answer, sorry. I don’t have any LW devices yet, still looking into it myself.

This is a very late reply, but just in case it’s useful I can confirm the gen1 devices work fine with the gen2 hub (both through the official app and my custom component).

Gen1 devices don’t communicate back to the hub, so if you use the physical switches, the hub won’t know the correct state, but that’s a limitation of the devices, not the hub.

The hub won’t change the cross pairing problem, that’s a flaw in the gen1 devices themselves.