On startup the wifilink now emits a radio pulse which will turn on selected devices on power restore.
As the protocol doesn’t include status; this isn’t a great solution. You’ve no guarantee that the device received and processed the request. We all know that RF doesn’t always work every time."AlexS":lmnh62eo wrote:"Shadow":lmnh62eo wrote:
[quote]Also, noticed the sockets don’t keep there locked status after a power cut, this is a feature I would prefer that the lock stays on? Example of this would be to lock a socket to off, thus reducing the need for the baby safety plugs? However if they unlock after a power cut, makes this a safety issue ” title=”Sad” />
I see your point, however you need to be able to unlock them this way as a safeguard in case you lose your locking remote and need to reset them – that was how they were designed.[/quote]
Can this not be a feature added on the Wifilink – again after a power cut, selector sockets set to lock or unlock?
So pretty much like the auto on feature, an auto lock feature personally would be a good idea."steven":1z3wphzd wrote:
As the protocol doesn’t include status; this isn’t a great solution.
Better than nowt, tho ” title=”Wink” />"steven":bpaoria2 wrote:"AlexS":bpaoria2 wrote:
[quote]On startup the wifilink now emits a radio pulse which will turn on selected devices on power restore.
As the protocol doesn’t include status; this isn’t a great solution. You’ve no guarantee that the device received and processed the request. We all know that RF doesn’t always work every time.[/quote]
True, but until we upgrade to a bi directional semi-mesh network setup (probably) sometime next year its the best we can do unfortunately as we cant get any feedback from the receivers.
If I have understood this correctly a socket can now be paired so that if there is a power outage then when power is restored it can come back on in a live position; that it does this because it is paired to the LightwaveRF connect box and the latter sends it a message to switch on.
Sounds fine but what if the Lightwaverf connect box is pugged into a remote socket? As it needs to send a signal to the socket to stay live it cannot do it. The socket needs to come on live in order to power up the connect box which can then tell all other sockets so paired to be live to switch on.
Have I undstood that correctly?
My router, broadband and Lightwaverf box are always on for obvious reasons but it seems if I plug them into a remote socket they will never come back on when mains is restored as the socket has defaulted to off and the connect box is not on at that stage to tell it not to.
Or does the pairing to come back on live mean the socket is not dependent on a signal from the box? I.e. it senses power has been restored and switches on so that what needs to be fired up is?
You are right that the ‘auto-on’ feature works by the WifiLink box sending out a simple ‘on’ RF pulse when it is first powered up, and anything that is paired to that pulse will get switched on.
Personally, I would never plug the WiFiLink box into a Lightwave controlled switch, as turning that switch off would disable the whole system. I do have my network router plugged into a standalone Lightwave power socket though (set for auto power on via the WiFiLInk too) as it occasionally slows down and needs a reset. I have a sequence which powers the router off, waits 30 seconds, and switches it back on that runs at 4am daily, so I never need to worry about it. I just have to remember to never press that device ‘Off’ button while roaming, as that would lose the network connection to the JSJS server and I wouldn’t be able to switch it back on remotely until I get home and can do it via the LAN.
That makes sense. I have not tried it but assume the WifiLink does not need to be connected to the Internet just so long as it is on it will send a radio signal to relevant sockets to tell them to switch on?"rhlangdon":1c2xko67 wrote:
That makes sense. I have not tried it but assume the WifiLink does not need to be connected to the Internet just so long as it is on it will send a radio signal to relevant sockets to tell them to switch on?
Correct. Even local iPhone control does not need an internet connection. Android does at present though, as the current official Android app is very basic and does all of its communication via the web server rather than having a ‘remote’ and ‘local’ operating mode. The third-party app is fine via the LAN though.
I have just found this thread, I know its quite old. But there seems to be a flaw in the logic for the LW380 basic On/Off Sockets?
As I understand it the WIFI Link sends out an ON command when it restarts?
The LW380 sockets go into learning mode for 5 seconds as soon as power is applied to them.
So if there is a powercut and all LW380s are off and the WIFI link is off, when power is restored, all LW380s will be in learning mode and the WIFI link will be sending an ON command for them to learn? Is this correct?
This means the next power cut *ALL* devices will turn on, as they learnt the code in the previous powercut?
Can someone confirm if this is the case, as this may explain why all my plugin devices turn on after a powercut
Just catching up with this old thread.
Is this feature been implemented?
How do I setup the devices that need to be ON when the power is back on?
Any documentation or help?
If there is a power outage when the WiFi Link powers back on, devices that were on when the power went off, will remain off until activated by the next instruction from the user or via a timer. It is a safety feature in case something came back on that you would not want on. If you wish to override this so that a device fires up when power is restored then as per the instruction manual you disconnect power from the Wi-fi Link and then as power is restored put whatever device you want to be on into pairing mode. This then removes the automatic off override after a power outage.
I have a couple of plug ins set up this way so that if power goes off my computer and external drives power back up plus any security devices.
Just to expand a bit on how this works and how to set it up.
The link box sends a wake up signal every time it powers up. Any device that is in pairing mode when it receives a wake up signal flash it lights and store this ‘power-on state’. Subsequently devices with a ‘power-on state’ that receive a wake up signal (e.g. when link starts up) will turn themselves on.
So you need to remove power from link, place a device in pairing mode and power up the link. Lights on device should flash if successful. Repeat as needed for other devices. As far as I know you have to clear the device completely to remove this condition.
Quirky way of doing this in my opinion and not nice to have to power on and off link to program it. They could have stored power-on state per device in the link and used regular commands to turn things back on at power up. Takes a bit longer if multiple devices are to be turned on, but much more flexible.
I have a decent install of Gen1 sockets and got the restore function working with a few of those as appropriate, just about to add a Linkplus and some additional GEN2 sockets.
Does anyone know if the GEN2 sockets have a ‘power-on-state’ feature and whether the setup is the same with the Linkplus and GEN1 socket combination?
Any update would be helpful – appreciation in advance.
You must be logged in to reply to this topic.