Still getting the same here, too. Did anyone get a resolve for it? LW not interested in helping.
Thatās a response to a year old issue thatās not been reported again since. Have you experienced the issue the entire time or just started?
I havenāt had this issue for a while, looks like LWRF sorted the offline issue to me.
Hi, I only set up the Smartthings integration about 3 weeks ago. The issue has been there since then.
LWRF support just pushed the question back to Samsung.
Hi Folks - wondering if this is a simple fix or not.
Just moved hard drive to a new machine. Set static IP on the router so it has the same IP as before to avoide updating device settings.
However when i send a command through ST now, node server just repeats āAttempt xx - Sending message :001 etcā¦)ā. It keeps doing this until the 200 limit set in the code.
Any ideas why itās not making it through to the LWRF hub? I seem to remember something about linking, but cant find any info.
Cheers
Sorted it - had to use ST website and run simulator to effect āpairingā after removing all linked devices on the LW hub
Anyone know how to change the Lightwave account linked to Smartthings?
A while back I linked to Smartthings with my Link 1 account and hub, discovering that I needed a
Link 2 hub and account.
I have now acquired a Link 2 hub and account, but canāt work out how to connect to the new account.
If I try to add a new device in Smartthings and select Lightwave it does not give me an opportunity to add the new account details, it just uses the old account details.
Sorry all.
Manged to work it out.
Sorry if this has been asked before or is know.
Has anyone experienced an issue where you will turn on the lightwave switch manually (at the socket not via smartthings or the LWRF app) but the state isnāt updated in smartthings unless you refresh the app? This is partially annoying when you use something like actiontiles on a mobile device (on wall).
Is there a workaround?
That is how the gen1 LW kit works - there is no built in monitoring of the state of the switch.
Or do you have the gen2 LW kit?
I am all gen2.
Should I have to refresh in the app for the state to change?
Not sure if anyone is still using Adamās Smartthings-> nodejs - >lightwaverf local integration but I recently decided to give it a go as the official lightwave integration had got incredibly slow. It worked really well and solved that issue but I have a lot of legacy (gen 1) LightWaveRF devices and working out the room/device numbers was getting tedious. So I thought Iām a developer I can solve this.
So for my own use I have created a Smart App that contacts the lightwaverf connect server logs in with my (or any account) and queries the undocumented api to download the list of rooms and servers. It then creates devices using Adamās handlers for each of the devices on the list assigning all the correct parameters. Devices are named Room Name Device Name for example in my set up I have a Light in the Spare Bedroom and this gets named Spare Bedroom Light.
If anyone is interested I could spend a bit more time to tidy it up for more general use.
Yes please!
Sounds awesome 
Ok first cut is here
garrywma/LightWaveRFSmartthingsLocalDeviceCreator: Note requires https://github.com/adamclark-dev/smartthings-lightwave-node-server
Neil do you still have an account with a PIN. I havenāt been able to test against one. The code uses the api from the modern connect dashboard at manager.lightwaverf.com which requires a password so I suspect it will not work with a PIN but worth a try
Hi Garry. I login to that site with my email and a 4 digit pin. If needed I may be able to āresetā my password to something alphanumeric.
I havenāt had time to test your solution yet, thatās a job for the weekend so will report back soon.
| Garry_Whittaker Developer
March 31 |
- | - |
Neil do you still have an account with a PIN. I havenāt been able to test against one. The code uses the api from the modern connect dashboard at manager.lightwaverf.com which requires a password so I suspect it will not work with a PIN but worth a try
OK it may be that they are treating the pin as being the password for converted legacy accounts will be interesting to see if it works.