Glad you got it sorted.
For anyone else reading this … EADDRINUSE means “Port in use”. Therefore, you just need to kill the process using that port.
Hi all,I’ve been thumbing this thread for or a wile but is soooo long it’s taking me forever,so the question I have if someone can answer is, what’s lightwave like now via smarthings. Does it work,is it quick enough to use or are there still problems.
Cheers in advance kev
It appears that Lightwave have no got SmartThings integration now - not sure when the blog/news article was posted.
I was able to add my devices using the new SmartThings app (not the old one).
Hopefully this will be of use to some.
Hey, this is great news.
Now I need to make a decision … ahhh
Hold off in hope that there is a a way of integrating the new BG Electrical Smart Plugs or start investing in Lightwave again.
Question, is the response quick when controlling them from SmartThings? Eg instant.
I wonder if it’s local or online based.
Also once added from the new app, I assume they show and work fine in the classic app?
They were showing up in Classic but not necessarily correctly carrying out actions, e.g. a dimmer switch was recognised but would hang at turning on and not actually turn on. They were showing state correctly though (when changing that is - sockets didn’t seem to query for correct state when they were added). The state when first connecting issueswere in the new app as well.
To work around this I looked at the device list in the dashboard and they were listed as placeholder devices with no network ID. I’ve given each a unique network ID and changed the type to either Simulated Dimmer Switch or Simulated Switch - depending on what it is. The dashboard lists them as cloud devices which is no surprise.
I have added some to webCoRE (after changing types) and they seem to work fine there as well (without changing type there was no option for turning switches/sockets on).
Speedwise… doesn’t really seem any slower than using the Lightwave app. It’s definitely quicker than when I was using IFTTT as the proxy to both set and update state. It’s also meant that I can disable approx. 20 (probably more in reality) IFTTT activities that were managing this (setting state and reacting to state change).
Cheers.
I believe, like a number of the brands added in the last couple of months, they are using the new platform integration for cloud to cloud connections which only works with the new V3 app.
Hi, do you still need a Lightwaverf hub for this integration to work ?
Yes, it’s a cloud to cloud integration between your lightwave RF account and your SmartThings account. So you need both hubs.
-
they have to be connected to your lightwave RF gateway because the new official integration is a cloud to cloud integration between your two accounts
-
you can only add them with the new V3 app
-
go into the app, select lightwave from the list of company icons, then sign in with your lightwave account there
I have added my LWRF switches to ST. However, after a few days the show up as offline in the app. I deleted them and readded them all, after a few days, the same thing. The on/off button in the app still works, but I can’t use them in automations with their state as offline.
Anyone experiencing the same?
Yes. Same is happening here.
According to LWRF it’s a Samsung issue…
Hello I know this is an old question, but my SD card in my pi zero got damaged so I am having to rebuild my AdamClarkdev nodejs server (on raspberry pi with forever keeping it running) which I use to integrate the lightwave gen 1 devices with smartthings.
However I don’t seem to be able to access the old legacy stuff Adam used like when I set it up a few years back, like for instance ‘forever’ and nodejs-legacy.
Can anyone point me in the direction of an updated method for setting up a similar raspberry pi interface to help the Gen 1 devices and link talk to smartthings please? It was working like a dream until the pi fell off a shelf and the micro sd card split. Any help gratefully received. Adam Clark are you there please Obi Wan Kenobi?
Cheers
nodejs legacy is gone and so is forever-service. well i installed forever-service and its not working on the latest pi release. forces you to use forever whicvh looks totally different in use.
anyone tried this recently and have it working?
Hi @Chris_Lambourne
Not sure if you are still helping people with support on this but I have a couple of questions for you.
Somebody on Hubitat is trying to get this working using the cloud integration.
So if you don’t mind a couple of questions for you.
They have gen 1 devices and have a 4 digit pin.
Do you know if it is still possible to control LWRF using cloud integration?
Do you have the device handlers for dimmers and outlets using this method?
Anything else needed to get cloud integration working?
If you are no longer supporting this then no worries but just thought I would be cheeky and ask.
Thanks.
@bobbles - sorry, I ditched my LWRF / ST integration last year. I had a choice to either upgrade to Gen 2, or move everything to Z-wave. I opted for the latter and have not regretted it.
I don’t use Hubitat so not sure how it works, and not sure what you are referring to when you say ‘cloud integration’. This integration (above) is all local; ST > Pi > LWRF.
I am guessing you are looking to control LWRF Gen 1 switches from Hubitat. I do that, except I use Domoticz. I am unsure how the two compare. I do not use this integration (above) anymore. I have this connected to my server where Domoticz is installed, and it detects and controls all LWRF devices automatically. It may (or may not) be useful.
If you are trying to implement this integration remotely (cloud based), latency will no doubt increase - which was the main selling point for this integration. I.e. virtually ‘zero lag’.
All the best.
Hi Chris, I’m in the position of making a similar choice - can I ask what Z-Wave kit you chose for your light switches - did you find some Z-Wave switches that suited or go for modules wired in behind them with conventional switches?
Thanks!
@andynash - Hi Andy, I opted for Fibaro Switch and Dimmer modules from Vesternet. It took some effort, as I had to fit deeper pattress boxes. But once done, the result is night and day. It also meant I could then choose any light fittings. I opted for the Schneider Ultimate range, not cheap, but look the biz (and Wife-friendly).
Much appreciated @Chris_Lambourne, will also look at the Aeotec Nano switches/dimmers I think. I’m also tight on depth so may need someone out to deepen the pattresses, though the Nanos are a touch more compact.
The Ultimates look great, though I may stick with Knightsbridge Screwless as we have those elsewhere where we don’t have Lightwave, and they are a good match.
@andynash - I looked at Aeotec too, as I use their Multisensor 6 and Door sensors. Their customer service is excellent, especially Chris Cheng… he helped me a lot when switching to Z-wave. I don’t recall there being much difference in the sizes between Aeotec and Fibaro. But the latter having better reviews. If your walls are plasterboard, switching the boxes is easy to do yourself.