LightwaveRF - New LightwaveRF Binding

try this @integrator : openhab-lightwaverf-compiled/org.openhab.binding.lightwaverf-3.0.3-SNAPSHOT_3.10.jar at main · delid4ve/openhab-lightwaverf-compiled · GitHub

Not sure if I’m doing something wrong, but still isn’t working… looks to be installing, but nothing shows in the UI.

Had to reply twice as I’m a new user:

Scratch that!

I’ve just realised I was looking in the wrong place… I was expecting to find the Lightwave binding in the ‘bindings’ page, but I have just discovered it in the list of things that can be added manually. I entered my login credentials and it’s showing as online. Now on to have fun to figure out how to pull the individual properties to be actual light switches.

You just got to go to Things → + → lightwaverf → scan

You can then click add all
Then you can go to each thing and select channel tab and add what you need

And yes custom bindings don’t show up, just under things as you have now discovered.

1 Like

All working now. Model fully populated. No issues with switching any lights. The only problem I have is that the individual lights have their original names. We changed rooms around a few months ago, and I subsequently updated the names and the binding is getting the original names somehow. The old and the new names must be in the API somewhere and it’s pulling the original rather than the current name. Not a big deal, once I realised what was going on; but I was scratching my head for a while flicking switches with apparently nothing happening. Just a shame I was home alone at the time or I would probably have figured it out sooner from the shouting.

Amazing work from someone who claims to have no IT qualifications. I have a lot of IT qualifications and find this system laborious. Well done you!

They are there, but…
Lightwave uses the structure: Device → featureset → feature
The main device name is the initial name you assigned (and what the binding uses) and this cannot be changed, ever.

A double socket for example has two featuresets (left and right sockets), this is suffixed with a 1 & 2 respectively when you add a device in the app. If you then change a socket name it changes this name.

Features are the channels such as switch, voltage etc.

I could change the binding to concat the two names but just chose to keep it simple and use the device name. Maybe I’ll change it, maybe not… if I buy and add new devices now I just keep it generic such as Bedroom 1 Socket 1. Can always use the identify switch channel to work out where it is.

I know the feeling :stuck_out_tongue_closed_eyes:

A lot of hours (A LOT OF HOURS :exploding_head:)… read, trial and error, read a bit more, break it, start again :joy::joy: was in well over my head when I first started but have learnt so much along the way and it’s rewarding when things come together and work. Oh and… I have one A level but that was mainly MS and the likes of access and excel, not exactly useful here and like hell I remember any of that from 20 years ago :joy:

Hi All,

Thanks so much for all the effort that’s being put into this binding - much appreciated. My setup is as follows:-

  • OpenHab 3.1 on Raspberry Pi,
  • Link Plus (2nd Gen) hub
  • Gen 2 Single Dimmer
  • Gen 1 Double Dimmer

All works perfectly with the exception that the Gen 1 Double Dimmer only has one switch in OpenHab - so I can only use OpenHab to operate one of the two lights that the physical dimmer switch(s) operate. I can see from the documentation that this device (‘Gen 1 Double Dimmer’) isn’t supported. Are there plans for this to change? Or have I misunderstood the documentation? Anything I can do to help?

Thanks
Steve

Hi Steve, I believe @delid4ve had limited testers available to build the support for the Gen1 devices, I expect with some assistance from you he may be able to add the support in

OK. Ready to help…

Yep I can add in - what’s the model number? Should be able to add Friday ready for you to test.

Hi

Very grateful! It’s a LW420 SS - 2 Gang.

Many thanks
Steve

Hi Steve
Haven’t forgot about you, going to be back in office next week so will have some time again

No problem Dave - thanks again!
Steve

@SteveBuckell just added, may not work depending on what version of 3.1 your on as javax measure got changed mid release before 3.2 release, let me know and if not ill compile against an older version.

Version 3.11: openhab-lightwaverf-compiled/org.openhab.binding.lightwaverf-3.2.0-SNAPSHOT_3.11.jar at main · delid4ve/openhab-lightwaverf-compiled · GitHub

Thanks Dave - appreciated. Not at home right now but will get to it as soon as I can

Cheers
Steve

Hi Dave,

I’m on 3.1.0 “main” build (the latest I can get using the Openhab config tool)

I have downloaded the jar, placed in the addons folder and restarted OpenHab3.
I then removed the thing I previously had representing the 2-way dimmer and used the UI to scan for new things. Two things are found but both are showing as a ‘d11’ but a “Generation 1 2 Way Dimmer” should be a “d12” according to the list I see if I were to add a thing manually?

Furthermore, both things have the same device ID of “lightwaverf:d11:buckell-home:5e4473744690cd6d270525a12315xxxxxxxx” (Replaced the last 8 digits with xxxxxxxx in case posting this detail is a security risk)

As an experiment, I manually added a d12 thing using the device ID that the automatic scanning had previously found. The thing does come online and shows channels for two switches. I setup items as follows:-

Switch  Toggle_Lightwave_Lounge_Ceiling_Front  "Lounge Ceiling Light Switch Front"  <dimmablelight> (Random_Lights, All_Lights)   { channel="lightwaverf:d12:242231cb16:1#switch" }
Switch  Toggle_Lightwave_Lounge_Ceiling_Rear   "Lounge Ceiling Light Switch Rear"   <dimmablelight> (Random_Lights, All_Lights)   { channel="lightwaverf:d12:242231cb16:2#switch" }

However, only one switch works (as per the old setup / old jar) and I see warnings / errors in the log:-

2021-08-08 17:35:51.384 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:28.266 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:28.270 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:29.869 [ERROR] [andler.LightwaverfSmartDeviceHandler] - Command ON for device 5e4473744690cd6d270525a1-2-315xxxxxxx+x returned a null featureid and couldnt be sent
2021-08-08 17:36:37.288 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:37.290 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:41.416 [ERROR] [andler.LightwaverfSmartDeviceHandler] - Command OFF for device 5e4473744690cd6d270525a1-2-315xxxxxxx+x returned a null featureid and couldnt be sent
2021-08-08 17:36:44.480 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:44.482 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:53.818 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:36:53.822 [WARN ] [ernal.LightwaverfSmartCommandManager] - Command response for 5e4473744690cd6d270525a1-2-315xxxxxxx+x wasnt processed as there is no listener present
2021-08-08 17:37:01.821 [ERROR] [andler.LightwaverfSmartDeviceHandler] - Command ON for device 5e4473744690cd6d270525a1-2-315xxxxxxx+x returned a null featureid and couldnt be sent
2021-08-08 17:37:10.032 [ERROR] [andler.LightwaverfSmartDeviceHandler] - Command OFF for device 5e4473744690cd6d270525a1-2-315xxxxxxx+x returned a null featureid and couldnt be sent

(again, the xxxxxxx-x is my doing)

Please let me know if there is anything I have done wrong, or anything more I can do to help (returning the thing / item setup to what I had previously, and keeping the new binding, works as before)

Thanks
Steve

Hi Steve

Will take a look next week, must of missed something when I added it in.

Ok. No worries. Let me know if any extra info would help

Hi Steve
I’ve just checked through the code and I cant see anything wrong. Can you remove all the items / things, remove the jar. stop openhab and clear the cache, restart and then add the jar and try again.

can you also change the logging level to trace for the binding once you have added the jar but before you add the account and run discovery.