Frequently Asked Questions

← Frequently Asked Questions


This is a common issue for new users as they do not fully understand how LightwaveRF the system works.
Each hardware device (switch\dimmer\relay etc) can be paired with up to 6 software devices (room\device number combination) and/or hardware remote controls.

If multiple lights are reacting to a single button it is because your lights are paired to multiple room\device combos or multiple devices have the same room\device pairing AS WELL AS the one you actually want.

e.g it is possible for the same light to react to commands for R1D1 (Room1, Device1), R2D2, R2D5, R4D9 etc etc all at the same time. It all depends on how you paired them.

Pairing a device does NOT remove all previous pairings. There is a specific “Clear Pairings” procedure (found in the manual for whatever type of  device you are using) that must be followed if you want the device to stop reacting to commands you have used in the past.

If you have trouble such as the one you are experiencing, you should clear all pairings and re-pair to the button/remote you actually want.

This is not a Lightwaver issue. You would have the exact same issue if using the official app. In fact, the problem would be more apparent if you are trying to use both apps at the same time .
For example. Consider this scenario:
All devices controlled by apps, are identified with their room and device number.
In Lightwaver you have set up a light as R1D1 and a socket as R1D2.
Using a different app, you add the same device but the the other way around. You set up the socket as R1D2 and the light as R1D1.
What you are doing when you are pairing with an app is telling a bulb/switch etc “hey, please respond to this Room/Device number combination”
Essentially you now have a bulb that is R1D1 in one app and R1D2 in another app. If you now pair your devices in Lightwaver using the normal pairing procedure and turn on the light, it works fine. The problem is that turning on/off the switch in the other app ALSO operates the light. You have sent a command to operate R1D1 and ALL devices that have been given this identifier will respond.
If you want to use multiple apps, you MUST ensure that all of the devices are identical in all apps.

Please read the instructions in the manual which is accessible from the Help menu within the app and also on this site here.

Specifically you need the section named “LightwaveRF Accounts”


Lightwaver is not intended as a companion for the official portal. It is a replacement and as such does not offer the ability to upload your data into it.

The intention is that you import your data (if required) and then use Lightwaver exclusively. The portal and official app simply do not have the ability to hold the amount of information that Lightwaver potentially uses.

Official app and portal only allow 1 location. Lightwaver has up to 200 locations.
Portal and official app allows 8 rooms with 6 devices per room (128 devices)
Lightwaver allows 15 Rooms with 16 devices per room. (240 Devices)
Therefore up to 112 devices would be completely missing from the first location if an upload was attempted and every room/location/Device would lose its icon.  All locations except the first would be completely gone.

If you wish to use both apps or the portal then you can edit your data in the official app or on the portal and then import it into Lightwaver when required.

Occasionally you may receive an error when importing your rooms and devices from the LightwaveRF portal.

First of all, please check that you have correctly entered your email address and pin number into the location settings.

If your login credentials are correct, the portal is possibly returning incorrect data and usually corrects itself. This is not a fault in the app. It simply means that the app is unable to interpret what the portal is producing.

All the app does is download data from this URL and parse it into its component parts.<your email address>&pin=<your pin number>

Note that you may need to use the “View as source” function of the browser for the above data to be displayed correctly.


Sometimes you may find that when you try to turn on one device, another one also switches. This is not a fault of the app, more an effect of how the system works if you are not fully aware of the implications of certain actions.

Each LightwaveRF device has 6 “slots” that determine what commands it responds to. This gives you the ability to pair up to 6 different remote controls to control the same device.

If you use the LightwaveRF link box, you can also control devices using apps or other software. The LightwaveRF box translates simple text commands to RF frequency commands.

For example, Each virtual room you create in the app (Lightwaver or LightwaveRF’s own app) is assigned a number from 1 to 15.  Each virtual device you create in each of those rooms is assigned a number from 1 to 16.

When you press a “button” in the app, you are sending a command to the LightwaveRF box which essentially says “Turn On/Off, device number X in Room Y”

Problems can occur if you move a device from one room to another but do not clear any existing pairings before making a new pairing.

For example:

Assume you have a switch in your living room. The switch is brand new and has never been previously paired.

You then create virtual room in Lightwaver and also a virtual switch. As this is the first room and device created, they are assigned the identifiers of “Room1, Device1” (or R1D1 for short).  Putting the hardware switch into pairing mode and pressing the virtual ON switch will use one of the slots in the hardware to remember to respond whenever a command is received to control R1D1.

Later, you move that device to your bedroom so you re-pair it and this time it gets the identifier “R2D1”. You remove the first virtual Living Room device from the app and forget that it ever existed. After pairing your switch, it now responds to BOTH commands R1D1 AND R2D1. Luckily, you do not have anything in your app that would send that command.

Months later, you buy a new lamp. Put it into your Living Room and set up a device in Lightwaver for it. By chance, it is given the identifier R1D1. The lamp is paired to R1D1 so it responds when the appropriate button is pressed.

Now you notice that whenever you turn on your Living Room lamp, your bedroom switch also comes on. This is because your bedroom switch has 2 memory slots used. One for R1D1 and also one for R2D1.

Turning on the bedroom switch does not affect the lamp because the lamp is only responding to R1D1 when you are sending the command R2D1.

To avoid this. Make sure you remove the existing pairing when you move your devices around. (Instructions to do this are in the manual for each hardware device).

Remove a single pairing:
If you find that you press a button and the wrong device responds, put that device into pairing mode and press the “Off” button in the app. This should remove the pairing for that single virtual device just as pressing the “On” button would create a pairing.

Remove all pairings:
If you do not remember what hardware device is paired to which software switch, the easiest thing to do is to clear all pairings of all of your devices one by one then re-pair them with the current configurations of rooms etc in the app.

If you just have one device that is responding to a button that you would

Also a point to note: If you use more than one app, be careful because what could be Room 1 in one app, could very easily be Room 5 in the other so whilst they may be named the same, they are actually completely different as far as pairings are concerned. Similarly, even if the rooms numbers match, the device numbers may not so you could end up with multiple devices responding to multiple different software buttons.



In summary. The pairings do not identify a specific device. They simply store a Room\Device number combination in one of the 6 slots and the device responds when a command is received that matches one of the Room\Device number combinations it has stored in those slots.

An extreme example would be that the same lamp could possibly respond to any of the commands such as R1D1, R1D5, R2D10, R5D11, R7D2, R2D2 which as you can imagine, would be incredibly confusing.


This is a problem installing the app and not a problem with the app itself.  Because of this, support is available directly from Google who are responsible for supply and installation of all apps from Play Store. The error number may change but the effect is the same. The app does not install.

Possible quick fixes:

1. Uninstall the old version and then reinstall the new one. This resolves it for 99% of folks. 

Please remember to backup your data to a safe place before uninstalling. If you backup Dropbox, ensure the backup file is safely there before uninstalling the old version. Check your file in Dropbox so that you know which folder it is in (the default is Apps\Password Safe Pro) and that the date of the backup file matches the date you just made the backup. (See highlighted in the image below)

2. Install manually (avoiding Google Play). The apk is available from here:



5. Contact Google Support directly at as it is they who support Play Store.

I attempted to get an answer from Google Developer Support as to what causes this error but they were unable to help me and simply gave me this stock response.

Thanks for contacting Google Play Developer Support. We’re happy to help with issues that Android Developers experience while using the tools and services needed for distribution of apps through Google Play, however we don’t support Play Store error messages.

To provide users with the best help, please direct them to contact Google Play User Support at

I’m sorry we couldn’t help you any further, though if you have any issues distributing Android apps through the Google Play Developer Console, please feel free to let me know.

Refunds for Android apps are available by following the instructions here:

If your request falls outside the 2 hour limit, you should contact Google directly.

Developers do not know your details so supplying your Google account details does not help.

Refunds for Windows applications are not available. Sales are final because there is a 14 day trial period which you can use to decide if the product meets your needs. After a license is issued, there is no way to cancel it.

Lightwaver does not do this. The import is only for rooms,devices and sequences. It is intended as a “starting point” when you first set up the app to save you entering all of the rooms and devices from scratch. Lightwaver was created as a replacement for the official app and portal rather than as a companion to them.

The import screen specifically states that it imports “Rooms and Devices”. Translation from the LightwaveRF timer/sequence portal data to Lightwaver data is not possible as their data formats are quite different.

I did attempt to make the process 2-way and have the ability to sync data back to the portal but this was abandoned as it would have meant losing some of the features such as changing icons etc as there is no provision for storing the extended data Lightwaver uses on the official portal. Also, Lightwaver offers double the number of rooms and devices that the official app/portal do so any sync would only ever work for the first 8 rooms which could be very confusing to users.

Your data is not automatically saved. You must use the “Backup” feature to save your data.

Any problem which causes data to be lost can be resolved by reinstalling the app from Google Play and then restoring your data from your latest backup.

If you failed to use any of the backup features of the app in the time you have been using it then you have permanently lost your data.

There are a number of reasons an app can Force Close.

If the app force closes as soon as you start it then it is likely been damaged. Apps are simply files on a small computer and if the computer crashes, the files can be damaged just like on their full size computer counterparts.

Uninstalling the app and then reinstalling should resolve the issue in this case. You can then restore your data from your latest backup.

If the app force closes when a specific operation is performed then it is likely that something unexpected is contained within the data and it does not know how to handle it or the data file is damaged.

Again, try restoring your data from a backup.

If the problem still occurs after you have restored, please fill in a support ticket giving as much detail as possible about the problem such as when it occurs, what you are doing/pressing at the time etc. Please also detail what steps you have taken so far to try to resolve the problem.

Some versions of our apps have a “Send Log” feature which will allow you to email the app log directly to us.

To re-install the paid version of the app without paying again, please see this link.

According to Google, in app purchases will be charged to the account that originally downloaded the app so you could uninstall the app and then download it with the account you want to be charged on.


It is unlikely as it simply is not my area of expertise and the user base would be very small.

I wrote the apps for myself then it grew from there so I wrote what I already knew.

I would be happy to share the database specifications if anybody wanted to take on the task.

Comments are closed.